DR 18.6.4 installation error at the 23 percent mark

I keep getting this issue. I am trying to install DR Studio 18.6.4. I get this error at "extraction at 23%" (see image) as I am trying to install on a clean install of Windows 11. My computer specs:

i9-13900k (all updated drivers and BIOS)
Windows 11 (all updated as of 12/16/2023)
2t ssd for c: drive
gpu 4090 Latest nVidia drivers game ready 546.33

What I have tried:
-Unzip and install using Window zip or WinZip.
-Install as Administrator
-Redownload the file in case they were corrupted. Would someone check if the number of bytes matches their download?
-Disabled Windows Defender before installing
-extracted and installed from another drive (ssd)
-I have plenty of space on c: drive
-cleared all temp files
-googled search this issue (no help there)
-re-installed Windows 11 (at least 10 times)
-tried installing DR as first installed program after a windows 11 clean install.

You downloaded from here?

https://www.blackmagicdesign.com/suppor ... and-fusion

Yes.
Are there other places you could download DR Studio from BM?
Did I miss something?

The BM Support page is the correct place to download from.
When you go to install you must double click on the Resolve .exe file and not the .dat file. The .dat files will be installed automatically.

Yes. That is the process I have been using. Any other insight into this issue?

Do your extracted files match mine for size?

DR File Size.jpg (56.23 KiB) Viewed 2786 times

Do you have enough drive space for the install? When installed Resolve occupies over 7GB of space. If you were previously running the Free version that should be uninstalled first.

Thanks Charles for your input.

This is a fresh install from a wiped ssd. No previous version of DR was installed. Yes, the bytes of the download matches and are correct. I have plenty of hard drive space since this is a fresh install on a two terabyte system drive.

I have scanned the system drive for errors and no errors where found.

I am currently scanning ram memory (128g) for errors. That is still in progress.

Question, when DR installs, does it create a temp file on the hard drive or does it do the unpacking all in RAM? I am wondering if it is a RAM issue that is not letting DR to install.

Again, yours and all input is appreciated. I have been fighting this battle all week. Also, I have tried to install earlier versions of DR and get the same issue.

I have only seen this issue on the forums once before but the poster didn't say how they solved the issue other then it just worked one day for them.

Download and Unzip to the Downloads folder, rather than Y.

Make sure to install in the default location on C:.

Make sure Documents and such are also in their default location on C:.

@Jim Simon,

Yes, I've been unzipping to my Download folder by default.
The install location defaults to C:
Documents are also in there default location on C:

Any other thoughts?

[Dwaine Maggart]

The screen shot of the error message you supplied is EXACTLY the error you get if you try to run the Install Resolve 18.6.4.exe file from within the zip.

Are you SURE it's unzipping to your Downloads folder, and not some zip utility representation of the unzipped files?

@Dwaine
Yes. I totally agree with you. It is exactly what I would expect if I tried to install DR within a zip folder. I have unzipped and installed previous versions of DR with no issues. It is just that with this new fresh install in this windows 11 workstation gives me this issue. Also I have tried other 18.5 point releases of DR and still have the same issue.

My process as it has been in the past for installing DR is to unzip in the Download folder and install from there.

I even moved this DR 18.6.4 unzipped files to another computer and it will begin the installation with no problems. But the same files on this particular workstation I get this error. I believe the unzipped installation files are fine. It is just with this computer, I get this error. This is really puzzling. What could this computer have that others don't that prevents DR from installing?

Is there another way to install DR without having to go through this unzipped process? What work around options do I have? Could my workstation be misinterpreting these files for something that they are not?

Additional information:
I have also unzipped the zip file using Windows 11 PowerShell

Expand-Archive -Path "C:\Temp\DaVinci_Resolve_Studio_18.6.4_Windows.zip" -DestinationPath "C:\Temp\Logs"

Then ran the .exe file:

C:\Temp\Logs> .\*.exe

Same error:

DaVinci Resolve-Extraction Failed

Failed to open, extract all files before executing.

Try this. I've always found it superior to other options. (Use the Extract Here option.)

https://7-zip.org/

[Dwaine Maggart]

@William: The fact you say you have the same issue with other 18.5 releases pretty much points to some issue with your system or systems.

The fact you say moving the files to another computer has the same issue, would seem to point to some issue with how the files are being downloaded.

What is the exact size of your zip file, and what are the exact sizes of the unzipped exe and dat files?

@Dwaine: I don't have any issues if I move the unzipped files to another computer. But using the same files on this main workstation I have the error.

I am beginning to suspect that I may have a system issue even though this is a clean install. I have installed Windows 11 at least 10 times now. I even tried to install DR first thing after a Windows 11 install.

The previous same issue that I had with DR 18.6.3 was that I put the install on a network drive and it worked. Yes, I've tried that all ready. No joy.

My files sizes are correct:
.exe=2,261KB
.dat=4,506,408KB

The error happens at the 23% mark. Do you any idea what is going on in the first 23% of the installation? Could this be a CHECKSUM issue?

Create a folder structure at the root of C: such as C:\Install\Resolve
Copy your exe and dat files to that folder (to ensure the total path is short).
Right-click on the exe file and use the option 'Run as administrator...'

Maybe this will work. The idea here is that if the extraction exceeds the max path because you started it too deep in the file system, the extraction might fail. The second part assures that you are running with credentials that will allow you to overcome any privileges that are required to system folder access, etc.

If you do all this (or have already done) and it still doesn't work then I'm out of ideas. Cheers.

@Steve: Yep. I did that too. Same error. Heck, I can't think of anything at this point that I haven't tried. Thanks for your input anyways. This is a real mystery. I'd like to get to the bottom of it...somehow.

Isn't that weird? I figured you'd tried this given your thorough description of diagnostic steps you'd attempted. Sorry I can't help. Good luck.

@Steve: I appreciate it. I am not giving up though this has put me behind on wrapping things up before year's end. I will post an update when I find a solution. I figure it is a super easy solution that I am over looking.

[Dwaine Maggart]

Oh, I thought you had mentioned same issue on another machine.

OK, so specific to this machine.

There will be an install log called ResolveInstallLog.txt in this location:

C:\Users\user_name\AppData\Local\Temp\

Where user_name is your Windows user name.

It may have a clue as to what's going wrong.

@Dwaine:
I checked for an install log "ResolverInstallLog.txt" in the Temp folder as you instructed. There no such file there. This doesn't surprise me because the install doesn't get passed the 23% mark before throwing up the error. So it seem the install doesn't even get to the point to create a log.

Is there another way to install DR?

[Dwaine Maggart]

You can try running the exe from a CMD shell and see what it does.

As soon as you enter the command on the command line, it should open the Extracting window.

You don't need to open the CMD shell as an Admin user. Just open it normally. Although, that said, if it fails in a similar fashion, then DO try opening the CMD shell as an Admin user, and see if that changes the behavior.

@Dwaine
Yep. I did that both ways. Same result.

Do you have any ideal what happens for the first 23% of the installation?

[Dwaine Maggart]

The original screen shot you sent doesn't seem to reference 23%. where are you seeing that?

I get the 23% from watching the progress bar closely many times.

[Dwaine Maggart]

When you launch the Resolve installer exe and you see the Extracted window appear, it is extracting files from the .dat file into this folder:

C:\Users\user_name\AppData\Local\Temp\random_name_folder

So in File Explorer, watch the Temp folder when you start the installer, and see what new folder gets created. if the extraction was completely finished, the randomly named folder would look like this:

resolve_installer_extracted_files_in_Appdata_Local_Temp.jpg (128.65 KiB) Viewed 2010 times

Then this window should appear:

allow_app2.jpg (397.28 KiB) Viewed 2010 times

When you click Yes, that's when the Resolve install log file gets created, and you'll see this window:

resolve_installer.jpg (24.17 KiB) Viewed 2010 times

If this is a first time Resolve install on this system, there will be lots more things to select, mainly a bunch of Microsoft Visual C++ things.

It seems that if the process is failing with the Extract window up, that perhaps it's having issues creating the random named folder in AppData\Local\Temp and/or extracting all the files into that folder.

**************SOLVED***************
**************SOLVED***************
**************SOLVED***************
**************SOLVED***************

I knew it would be something simple.

I removed the Motherboard battery for about an hour. I wanted to ensure I cleared the CMOS.

That was it. Everything works as expected. But why? Not to sound ungrateful. Why would CMOS be the issue?

Thank you to all who contributed to this discussion.

[Dwaine Maggart]

That makes no sense at all, but glad you got it going.

That makes no sense at all, but glad you got it going.

I totally agree. But I will take the win. Believe me I was trying everything. I was getting around to rolling back the BOIS but decided to try clearing CMOS first. Then I tried DR again and it installed as expected. I was having other programs installation issues like Autodesk Maya and a few others. It was a mess. Now everything installs with no issues.

Go figure. After a week and a half of wrestling with this issue it was a simple as clearing out the CMOS that resolves it. I am glad it is behind me. I don't want to repeat that again anytime soon.

I made an account just to say THANK YOU SO MUCH. I have NO IDEA why clearing CMOS worked but it did. Took me over an hour just to find this. Tried it and you saved me quite the headache. Everything the original poster said was my same situation. Fresh clean install of a new OS with new installs of new programs. Im wondering if Blackmagic/DaVinci does something to the BIOs as well that were unaware of? Regardless...I had to make an account to thank OP and to let them know this worked for me as well.

You are welcome.

It seems that only a hand full of people are having this issue. Actually, the issue is wider than with DR for me but got solved across the board once the CMOS was cleared.

I am wondering what is your computer specs?

It has to be a unique combination of things.

I had this issue too and, after weeks of pulling my hair out, think that I may have finally found a fix or at least a hint of what the issue *might* be related too.

There is a major issue with the Intel 13xxx and 14xxx series CPU. Here is a video explaining the issue:

.

Basically the CPUs are being over-volted because motherboard manufacturers are not using the recommended specifications and are instead feeding the CPU's the maximum possible voltage. Yikes. Here's another video exlaining:

My computer uses an Intel i9 14900k CPU on an ASUS z790f motherboard. I was having horrific stability issues. Everything was crashing at completely unpredictable times and I was running into all sorts of weird errors (like this strange installer issue). My computer is basically brand new, has a GTX 4090, and is built by Maingear so it is water-cooled and the whole works. In *theory*, it should be performing flawlessly and yet it's the most unstable computer I've ever used. I have hated owning it, to put it mildly.

THE SOLVE: The motherboard manufacturers have updated their BIOS to include a new setting that actually limit the CPUs to the voltage that they are specified to have. So for owners of 13th and 14th gen i9 CPUs: you have to update your bios firmware and then activate the setting to use the Intel specified voltage. It's sort of the opposite of overclocking: instead of pushing performance at the risk of a crash, you're limiting performance to increase stability, which is our goal in production.

Other things I did:

In the bios I also disabled XMP on my RAM. No reason to push things. Just let it run at the lower clock speeds. Again, trading a little performance for stability.

I re-installed Windows totally fresh.

Lastly, I switched to the studio driver on my 4090 rather than the game drivers. Again trading performance for stability. I just want stable. I am not interested in pushing my computer for a 5% performance boost or whatever. I want to be creative and use my tools.

After doing all of this, I saw a big stability increase on my machine. Blender was working again, which is the next most common program I use. I decided to try to install Davinci again. I "ran as administrator" and it failed again. Same error. (Oh no!) But then I just ran it regularly (after fully unzipping it using 7zip) and it actually installed.

Miracles never cease.

So I don't know what it was in there that was causing all the headache but the TLDR is: update your motherboard BIOS, turn down your settings to "normal" settings rather than overclocked and your computer might start to behave quasi-normally again.

May you have less stress than I did. Good luck. Also please chime-in if you're having issues and also using an i9 processor. I'm curious to know if that's the common thread here.

Great post.

I am aware Jayz2cents Youtube videos you shared. Like yourself, I've done extensive research to solve my unique issues. What I was able to do to solve my issues was to clear my CMOS.