get_one_drive_paths fails on latest W11 24H2 security update

[BreakPoints]

Quick summary

After a Windows 11 update, the following error appears on startup for RPCS3:
E SYS: get_one_drive_paths: RegQueryValueExW failed: The system cannot find the file specified. (0x2)

Details

I hadn't seen this error before updaing Windows 11 24H2 to the KB5050009 security patch. If "one_drive_paths" is referring to Microsoft OneDrive folders, functionality may have changed in the recent Windows update to snub an exploit.

RPCS3 runs fine with this error. I assume this is a check to avoid installs to OneDrive shared folders.

Attach a log file

RPCS3.log.gz

Attach capture files for visual issues

No response

System configuration

Windows 11 24H2 - Build 26100.2894

Other details

No response

[Megamouse]

Not an issue. But I can decrease the log level

[dragonloverlord]

Yeah I also am encountering this issue with Win11 24H2 Build 26100.2894 also if you previously had onedrive active but disabled it completely then RPCS3 falsely detects itself as being in a onedrive folder despite onedrive being completely disabled granted Windows doesn't actually revert the whole user\onedrive\documents thing when disabling onedrive so maybe that's tripping it up. Anyways would definitely be nice to be able to override a false detection if nothing else.

Also in my case this does actually prevent the starting of the emulator which was previously fine.

Edit: works fine if I delete the OneDrive variable from the system path as it wasn't removed when Windows deactivated onedrive so harmless to remove but potentially confusing to those who don't know about path variables and such.

[Megamouse]

So it was just the PATH and not the registry entry causing this issue?

[dragonloverlord]

So it was just the PATH and not the registry entry causing this issue?

Yes as after adding the onedrive variable back to the path and setting it to any directory in which RPCS3 is either within or a subdirectory of it will then fail to start again. It will not however fail if said variable is set to say C:\user\Name\Downloads assuming RPCS3 is with C:\user\Name\Documents however if it's set to say C:\ then RPCS3 would technically fail to start at all unless the install is on another drive. Additionally should it be erroneously blanked albeit not possible via user interaction but programmatically possible or set to a self dependent variable for example .\ then RPCS3 will simply fail to start irregardless of install location.

For context this is on a computer with onedrive completely removed as in no app be it system, user, or otherwise is present within the OS so no install or registry variables pertaining to one drive are present.

After having tested multiple RPCS3 versions I have deduced that the breaking change occurs between version 0.0.34-17347 and version 0.0.34-17348 as version 0.0.34-17347 starts well version 0.0.34-17348 does not when placed under a directory of C:\test\<rpcs3 version number>\ with the OneDrive path variable set to C:\test\