Windows 10: Exporting registry with regedit "hangs"

I have recently noticed that exporting my registry "hangs" forever. I did a little investigation and found that there appears to be a looping entry into the exported registry keys:

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{14654CA6-5711-491D-B89A-58E571679951}\KlifTmp02918B99\KlifTmp194DED95\KlifTmp1ECF62D3\KlifTmp792EFA24\KlifTmp2E0756F6\KlifTm p7E0D8DE7\KlifTmp3B927D69\KlifTmp70F1FB9A]@="Microsoft TBAuth Single-Sign On Protocol"[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{14654CA6-5711-491D-B89A-58E571679951}\KlifTmp02918B99\KlifTmp194DED95\KlifTmp1ECF62D3\KlifTmp792EFA24\KlifTmp2E0756F6\KlifTm p7E0D8DE7\KlifTmp3B927D69\KlifTmp70F1FB9A\InProcServer32]@="C:\\Windows\\System32\\tbauth.dll""ThreadingModel"="Apartment"

This repeats over and over.

Running Windows 10 Pro

:)

 

Windows 10 Pro... regedit doesnt complete...hangs about 80-90% thru registry...

just went to windows 10 pro about a week ago....had to clean out the registry for some hardware that win10 doesn't support...ran regedit... do a find on device name and regedit starts scanning..found of couple of instances and removed them...did another
" find next" and regedit hangs..waited 20 mins and never completes.. the scroll bar on the right side window shows it about 80-90% thru the registry.. after 20 I click to close the window and it responds that registry editor isn't currently running and restarts
it...

 

Windows 10 creates registry key names in excess of 256 characters for many flash drives and breaks regedit search functions

I've found that Windows 10 Regedit "Find" function would always fail before reaching the end of the registry if the search object was not found or when the search got to certain points in the registry. The Find function would hang without terminating.
Sometimes Regedit would lockup, crash or restart. I traced the search failures to long file names in excess of 256 characters for flash drives. A few flash drives had registry keys shorter than 256 characters, but most had names as long as 267 or 268 characters.
These keys were found in my registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{7f108a28-9833-4b3b-b780-2c6b5fa5c062}. The keys could not be renamed because they were too long and renaming failed. The keys would either fail
to open or have iterations of subkeys named "#" below them when they should only have one # subkey. Regedit would hang, crash or restart when the search came across one of these long key names. At this time, I don't have a work around.

 

Have you tried using Hiren's Boot Disc or the Reg.exe Command tool?

 

Good morning bro67. I did try the reg.exe command. HKEY_LOCAL_MACHINE hangs in that utility also. I will check out Hiren's boot disc.

I have been reading that the most recent Windows 10 update broke the "find" and "export" regedit commands due to limiting registry keys to 255 bytes. I'm hoping a fix from Microsoft will come soon

 

Hi, which is your Windows build?
(Windows key + R, winver).
This used to be a problem in 1511 I think - that's very old.

Note 'latest update' means quite different things to different people, given the different builds they are on and that updates are not delivered everywhere simultaneously.

See the News section where there is a thread per update. You can check for experience with your particular update there.

Otherwise:

Try a different registry editor e.g.
O&O RegEditor
(freeware)

 

Hello dalcina,

My Windows 10 Pro version is 1703 (OS Build 15063.540).

I did try the OOReg Editor. It hangs in the same way (i.e. keeps re-writing the same pair of registry keys into the export file - over and over).

I am trying to determine if I have a Windows-related issue or if a virus or rogue program wrote things in the registry causing this.

Thanks

 

Try some clean-up first. Then re-boot and see if it still hangs on you. Copy and paste the following code into an Admin Command prompt. It will run about 20 minutes or so. Re-boot when it finishes, the try your export.

fsutil resource setautoreset true c:\&fsutil usn deletejournal /d /n c:&Dism.exe /online /Cleanup-Image /StartComponentCleanup&sfc /scannow&Dism.exe /Online /Cleanup-Image /RestoreHealth&sfc /scannow&Dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase&pause

 

f14tomcat, I tried as you prescribed. No Joy. But on the bright side, I did learn a lot about some advanced Windows commands

 

Did you ever run a chkdsk (check for disk errors) to see if maybe there is a funky block or sector that you're hitting, causing Windows to loop? Just to rule it out. At admin command, run this. It will ask to reboot and will run for a while, so go do something else. It's a deep boot-time check-disk with repairs if needed.

chkdsk C: /f /r /x