Error key DaVinci v,20.1

[RodjAI]

09:36:58 [INFO] attempting to patch resolve!
09:36:58 [ERROR] read registry key error: Error {
code: HRESULT(0x80070002),
message: "Не удается найти указанный файл.",
}
09:36:58 [ERROR] failed to patch resolve: Resolve could not be located.

[examresultportal-ai]

Bro Something Find For Works on resolve?

[PaulieGualtieri991]

Unfortunately, it only works with DaVinci Resolve 20.0. Any version above that does not work

[ratijas]

DaVinci Resolve does not seem to create that Registry key anymore.

The signature still applies though, the rest works fine.

The workaround is to modify the code to specify the full path to Resolve.exe instead of relying on the registry lookup. The change is trivial, basically (assuming default installation directory):

    let resolve_path = r#"C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe"#;

[unknowntrojan]

Yeah. Correct. But if you can't figure that one out, you probably shouldn't be opening issues or pull requests "fixing" the code with ChatGPT. Please look at the PRs on this fucking repo, I'm losing my mind.

I am working on updating it. Finding a more versatile way of locating the binary and an improved patch for >18.6.2 that removes an antipiracy check. I am really busy irl right now so don't have a lot of time to dedicate to this project, and I've encountered an issue with one of my other crates that needs addressing.

I will update this repo soon, please be patient.

[ratijas]

Yeah. Correct. But if you can't figure that one out, you probably shouldn't be opening issues or pull requests "fixing" the code with ChatGPT. Please look at the PRs on this fucking repo, I'm losing my mind.

yeah, I saw that, and I feel bad for you that you had to deal with them :(

[unknowntrojan]

I have published a patch on master for 20.x versions. Any feedback/testing is appreciated, so knock yourself out with the new Resolve versions.

[ratijas]

The amount of engineering you put into versioning is truly amazing.

Unfortunately, it makes both 20.0 and 20.2.2 versions crash on launch:

Faulting application name: Resolve.exe, version: 20.2.2.10, time stamp: 0x00000000
Faulting module name: Resolve.exe, version: 20.2.2.10, time stamp: 0x00000000
Exception code: 0xc000001d
Fault offset: 0x0000000003acbfd9
Faulting process id: 0x1158
Faulting application start time: 0x1DC3E078B522AA4
Faulting application path: C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe
Faulting module path: C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe
Report Id: 92a182c2-29e3-420f-aa65-ac6dcdcccc65
Faulting package full name: 
Faulting package-relative application ID: 

Here's a screenshot of procmon, if that helps:

There is another generic "application crashing event":

Windows cannot access the file for one of the following reasons

Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program DaVinci Resolve because of this error.

Program: DaVinci Resolve
File:

The error value is listed in the Additional Data section.
User Action

1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
   • It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
   • It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: 0x0
Disk type: 0x0

I rolled back the patch tool, reinstalled DaVinci Resolve and run again. That one still works, for both 20.0 and 20.2.2 versions.

---

The script also fails to set the environment variable in registry, for some reason:

19:51:07 [ERROR] failed to set global environment variable RLM_LICENSE=blackmagic.lic. please set manually!!! Access is denied. (0x80070005)

which I did manually instead.

[unknowntrojan]

The amount of engineering you put into versioning is truly amazing.

Unfortunately, it makes both 20.0 and 20.2.2 versions crash on launch:

Faulting application name: Resolve.exe, version: 20.2.2.10, time stamp: 0x00000000
Faulting module name: Resolve.exe, version: 20.2.2.10, time stamp: 0x00000000
Exception code: 0xc000001d
Fault offset: 0x0000000003acbfd9
Faulting process id: 0x1158
Faulting application start time: 0x1DC3E078B522AA4
Faulting application path: C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe
Faulting module path: C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe
Report Id: 92a182c2-29e3-420f-aa65-ac6dcdcccc65
Faulting package full name: 
Faulting package-relative application ID: 

Here's a screenshot of procmon, if that helps:

There is another generic "application crashing event":

Windows cannot access the file for one of the following reasons
I rolled back the patch tool, reinstalled DaVinci Resolve and run again. That one still works, for both 20.0 and 20.2.2 versions.

The script also fails to set the environment variable in registry, for some reason:

19:51:07 [ERROR] failed to set global environment variable RLM_LICENSE=blackmagic.lic. please set manually!!! Access is denied. (0x80070005)

which I did manually instead.

well, that sucks.
can you try specifically 20.0.49? that's the one I reversed, I was hoping these patches were more permanent....
it's really tedious to work with.
I'll have a deeper look sometime this week when I have time

[ratijas]

Sure. Where did you get specifically .49 from? I can't find it on the support page

[ryorichardo]

The amount of engineering you put into versioning is truly amazing.

Unfortunately, it makes both 20.0 and 20.2.2 versions crash on launch:

Faulting application name: Resolve.exe, version: 20.2.2.10, time stamp: 0x00000000
Faulting module name: Resolve.exe, version: 20.2.2.10, time stamp: 0x00000000
Exception code: 0xc000001d
Fault offset: 0x0000000003acbfd9
Faulting process id: 0x1158
Faulting application start time: 0x1DC3E078B522AA4
Faulting application path: C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe
Faulting module path: C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe
Report Id: 92a182c2-29e3-420f-aa65-ac6dcdcccc65
Faulting package full name: 
Faulting package-relative application ID: 

Here's a screenshot of procmon, if that helps:

There is another generic "application crashing event":

Windows cannot access the file for one of the following reasons
Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program DaVinci Resolve because of this error.

Program: DaVinci Resolve File:

The error value is listed in the Additional Data section. User Action

1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.

2. If the file still cannot be accessed and

   • It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
   • It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.

3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.

4. If the problem persists, restore the file from a backup copy.

5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data Error value: 0x0 Disk type: 0x0

I rolled back the patch tool, reinstalled DaVinci Resolve and run again. That one still works, for both 20.0 and 20.2.2 versions.

The script also fails to set the environment variable in registry, for some reason:

19:51:07 [ERROR] failed to set global environment variable RLM_LICENSE=blackmagic.lic. please set manually!!! Access is denied. (0x80070005)

which I did manually instead.

Same here, tried with version 20.0.1 and 20.2.2 and got the same result. Where can I get the version 20.0.49 tho?

[ratijas]

Tangentially related to patching DaVinci Resolve, and infinitely hilarious:
https://old.reddit.com/r/davinciresolve/comments/1k2jy2d/custom_davinci_resolve_splash_screen/

IMHO if you are hacking the app, it should come with a splash screen like Never Gonna Give You Up or something like that :D

[tedaimengtech]

Use the followed Regedit command to add the record(Please change it to your real path). It WORKS on my computer.
``
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Classes\ResolveBinFile\shell\open\command]
@=""C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe" "%1""

[HKEY_CURRENT_USER\Software\Classes\ResolveDrpFile\shell\open\command]
@=""C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe" "%1""

[HKEY_CURRENT_USER\Software\Classes\ResolveDBKeyFile\shell\open\command]
@=""C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe" "%1""

[HKEY_CURRENT_USER\Software\Classes\ResolveTimelineFile\shell\open\command]
@=""C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe" "%1""

[HKEY_CURRENT_USER\Software\Classes\ResolveTemplateBundle\shell\open\command]
@=""C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe" "%1""
``

[MagonYT]

Running each one of these achieves the same as the above, though more reliable with more verbose logging.

reg add "HKCU\Software\Classes\ResolveBinFile\shell\open\command" /ve /d "\"C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe\" \"%1\"" /f
reg add "HKCU\Software\Classes\ResolveDrpFile\shell\open\command" /ve /d "\"C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe\" \"%1\"" /f
reg add "HKCU\Software\Classes\ResolveDBKeyFile\shell\open\command" /ve /d "\"C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe\" \"%1\"" /f
reg add "HKCU\Software\Classes\ResolveTimelineFile\shell\open\command" /ve /d "\"C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe\" \"%1\"" /f
reg add "HKCU\Software\Classes\ResolveTemplateBundle\shell\open\command" /ve /d "\"C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe\" \"%1\"" /f

[rabbitman92]

Thanks @tedaimengtech and @MagonYT for the reg commands.

I'm trying to get this running for 20.3.2, but having the same crash on launch as @ratijas .

Are people having success with the current resolvepatch or only a rolled back version? When I run the older commit from Jul 8, 2025, I get compile errors on coolfindpattern.

Compiling coolfindpattern v0.1.6

error[E0635]: unknown feature `array_chunks` --> C:\Users\xxx\.cargo\registry\src\index.crates.io-1949cf8c6b5b557f\coolfindpattern-0.1.6\src\lib.rs:1:27 | 1 | #![feature(portable_simd, array_chunks)] | ^^^^^^^^^^^^

Compiling deranged v0.3.11
error[E0599]: no method named array_chunks found for struct Vec<u8> in the current scope
--> C:\Users\xxx.cargo\registry\src\index.crates.io-1949cf8c6b5b557f\coolfindpattern-0.1.6\src\lib.rs:106:14
|
105 | let chunks: Vec = bytes_extended
| _________________________________________-
106 | | .array_chunks::()
| | -^^^^^^^^^^^^ Vec<u8> is not an iterator
| |_____________|
|
|
help: call .into_iter() first
|
106 | .into_iter().array_chunks::()
| ++++++++++++

error[E0599]: no method named array_chunks found for struct Vec<bool> in the current scope
--> C:\Users\xxx.cargo\registry\src\index.crates.io-1949cf8c6b5b557f\coolfindpattern-0.1.6\src\lib.rs:107:32
|
107 | .zip(mask_extended.array_chunks::())
| ^^^^^^^^^^^^ Vec<bool> is not an iterator
|
help: call .into_iter() first
|
107 | .zip(mask_extended.into_iter().array_chunks::())
| ++++++++++++

[ratijas]

It never worked well for me.

Even with a "properly" patched version it would export videos with a big flickering bar on top, so I'd export videos taller than they are, and crop them down with ffmpeg. Some people suspect it is an anti-piracy measure.

Eventually I installed one of those distributions from rutracker¹ with R2R Emulator (DVREMU2), which basically emulates a physical license USB stick. Note that there is no source code available; I have no idea how safe it is. But hey, it renders without flickering.

¹ https://rutracker dot org/forum/viewtopic.php?t=6815866