Nvidia: "Can't open/create old registry keys" error

wkduffy

Distinguished
Sep 16, 2012
39
0
18,540
Hi Toms! I’ve Googled around but have come up trump on this: I’ve got 2x 970 GTX in SLI (the MSI 4G version), latest driver as of yesterday.

Ever since switching to Win 10 (might be a coincidence), when installing new nVidia drivers, I get the error

Registry Merge: Can't open/create old keys in the registry

This happens specifically while the 3D Vision stereoscopic driver is installing (and yes, I do occasionally use it with my Asus 144Hz monitor, nVidia emitter, and glasses with some older games).

I click OK through it two or three times (I forget), and install finishes successfully. I never worried about it since it didn’t seem to make a difference…until (keep reading).

BTW, I use Display Driver Uninstaller (DDU, latest version 15.5, I think) in safe mode to remove all old drivers before installing new. Error still happens.

BUT yesterday a bizarre thing happened: Trying to play Quake 4 (nostalgia), and the game’s error screen came up ”Texture Compression not available.”

I opened the nVidia control panel to see what was up and found that my entire list of menu items (Manage 3D Settings, Enable SLI and Surround, Resolution, Color, Desktop resizing, all of it) was gone, EXCEPT for “Enable Stereoscopic 3D” which was still sitting there by itself.

I booted into safe mode, used DDU, and reinstalled new drivers. At this point, control panel was back to normal, EXCEPT there was no option for me to enable SLI any more.

I shut down, opened the rig, unplugged the SLI bridge and left it that way, and rebooted to see what was up (if both cards would be recognized).

At this point the control panel was fully back to normal INCLUDING ENABLE SLI even though the SLI bridge was disconnected. WTF?

I reconnected everything and all is normal again. BUT I worry about the “Can't open/create old keys in the registry” error message and can I correct this to avoid future probs and also make sure my drivers are fully installing correctly?

BTW, on nVidia’s forum from a few years ago, someone mentioned this registry problem and it might be connected to locked registry keys related to a 3D “depth hack” (something I’ve not fiddled with to my knowledge). He included a .bat to run to unlock any keys. I used it, but it had no effect. Someone has also said to delete the nVidia TEMP folder, which I have done, to no effect.
Thanks?
 
Solution
I'm going to go out on a whim here and say that getting this error ever since switching to Windows 10 "might NOT be a coincidence."

Also - do you get this error when reinstalling the driver without the 3D-Vision? Try that please. Windows 10 is still very new and while it has gone smoothly for most users (including myself thankfully) there have been issues reported. The most common comlaints I've heard have been video related. Use the NVIDIA "perform a clean installation" option during the install. If it doesn't help - I would recommend a clean install of Windows 10 by following these steps...
www.tomshardware.com/faq/id-2784691/ditch-problematic-win10-upgrade-replace-clean-install.html

Some cards do not need an SLI bridge to run...
I'm going to go out on a whim here and say that getting this error ever since switching to Windows 10 "might NOT be a coincidence."

Also - do you get this error when reinstalling the driver without the 3D-Vision? Try that please. Windows 10 is still very new and while it has gone smoothly for most users (including myself thankfully) there have been issues reported. The most common comlaints I've heard have been video related. Use the NVIDIA "perform a clean installation" option during the install. If it doesn't help - I would recommend a clean install of Windows 10 by following these steps...
www.tomshardware.com/faq/id-2784691/ditch-problematic-win10-upgrade-replace-clean-install.html

Some cards do not need an SLI bridge to run SLI as described here...
http://www.tomshardware.com/forum/369979-33-cable

Good luck! :)
 
Solution

wkduffy

Distinguished
Sep 16, 2012
39
0
18,540
R4lNM4N: Thanks for the ideas. I always do check the "clean install" box, btw. I will re-install w/o the 3D Vision drivers to test if the same error shows up. I have a feeling it won't, but I'll report back. I'll also see if my cards will SLI w/o the bridge--I did not know that was possible--which would explain my WTF moment. I thought w/o the bridge they would show as 2 cards, but working independently only. (I wonder if there's a benefit to using or not using the bridge? Anyway, I'll read your linked article.) I'd hate to have to resort to a clean install but if it seems necessary, thanks for that link too. I might try to hit up support at nVidia live chat, but I know that's a crap shoot. More info coming...