After Windows 10 1511 Update, Regedit hangs on the Find command

After the Windows 10 1511 Update, Regedit stops working when the Find command is used. Task Manager shows Regedit is running, but the utility never ends. It appears to be in a loop. When you cancel Regedit, a message displays there was a problem and it restarts the utility. This problem is occurring on both of my Windows 10 Pro 1511 PCs. I renamed Regedit in Windows folder, and I replaced it with the one in Windows.old folder.  That seems to fix the problem. At least, Regedit does not hang on a Find.

I am concerned the previous version of Regedit may not be fully compatible with the one in Win 10 Update 1511. Can anyone shed light on this? 

Update: Cumulative Update for Windows 10 Version 1511 (KB3124200) did not fix the problem. Regedit still loops on a "Find".

Update: Cumulative Update for Windows 10 Version 1511 OS Build 10586.122 (KB3140743) did not fix the problem. Regedit still loops on a "Find".

Windows 10 Anniversary Update Version 14393.51 fixed the problem. The newly updated RegeditI finally shows the registry key which caused the 1511 Regedit to hang on "Find" command. In my case, it was a USB key with weird characters that caused the problem.  

 

Question Info


Last updated August 25, 2018 Views 5,665 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Hello Allen,

Thank you for posting your concern in Microsoft community and welcome to the Windows 10 Family.

 

This issue may happen due to system file corruption. I suggest you to run System file checker. System File checker (SFC) scan is done to check if there are any damaged/corrupted system files that could be causing this issue. Kindly follow the below given steps: 

  • Press Windows key + X, select Command prompt (Admin) to bring up elevated Command prompt.

  • In Command prompt type sfc/scannow and press enter.

  • Restart the computer.

Kindly keep us posted on the updated information. If you need further help, feel free to write to us and we would be happy to assist you.

Thank You.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Thank you for the reply.

I failed to mention in my forum post the Regedit Find loop problem is happening on two Win 10 Pro 32 Bit PCs. I replaced the Regedits from the Windows.old (prior to 1511) folder on the two computers.

I ran sfc/scannnow as you suggested on two computers and restarted the PCs. The CBS.log files listed repairing and repaired Regedit.  It did nothing more than replace the Regedit  I copied from Windows.old with the 1511 Regedit.  I tried a Find command with  the repaired Regedit. Sadly, it ran (TaskManager showed memory and cpu usage) for 10 minutes before I canceled it. After I canceled it,  I got "Regedit has stopped working...." message box, and Regedit is restarted. 

Regedit is an important utility for me. I must have a running copy, so I will pull the Regedit.exe from the Windows.old folder.

I have over 45 years IT experience. I have been running Microsoft Operating Systems since the DOS days. Something in the 1511 Update caused this problem which is one of many reported in the Ms Community Windows 10. I am sure it will be fixed, but I hope it is sooner than later.  Have a great day!

11 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

FYI, I ran Regedit32 with the same Find command as Regedit. Regedit32 runs to completion with no hangs or loop on both of the Win 10 Pro 1511 PCs.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hello Allen,

We appreciate the time and effort you have put in to resolve the issue.

Feel free to write to us in future on any issues in Windows operating system and we would be happy to help you.

Thank You.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I am also having this problem with Windows 10 Pro 64 bit after the latest update. I open the Find dialog, type some string in, and the app never returns. I have let it run for hours. I tried using regedit32, but that command was not found. Help would be appreciated. Thanks in advance,

LS

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Update: I tried both regedit.exe and regedt32.exe. Both hang when asked to perform the "Find" command, and never return.

Thanks,

LS

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Sorry, one more update:

I tried the version of regedt32.exe in Windows.old. It hung, same as the version in Windows

I tried the sfc /scannow command as suggested above. I got an unrepairable error, but I don't think it explains why regedit.exe or regedt32.exe do not work. Her eis the error, but I am more concerned with getting regedit.exe to work:

2015-11-28 20:27:26, Info                  CSI    00004edb [SR] Repairing 1 components
2015-11-28 20:27:26, Info                  CSI    00004edc [SR] Beginning Verify and Repair transaction
2015-11-28 20:27:26, Info                  CSI    00004edd Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 ZKw/p0aa8+r0cwGkIvy48AiKnoFYdJ3eMOHmeT5t0Jw=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-11-28 20:27:26, Info                  CSI    00004ede [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-11-28 20:27:26, Info                  CSI    00004edf@2015/11/29:04:27:26.715 Primitive installers committed for repair
2015-11-28 20:27:26, Info                  CSI    00004ee0 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 ZKw/p0aa8+r0cwGkIvy48AiKnoFYdJ3eMOHmeT5t0Jw=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-11-28 20:27:26, Info                  CSI    00004ee1 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-11-28 20:27:26, Info                  CSI    00004ee2 [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"
2015-11-28 20:27:26, Info                  CSI    00004ee3 Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 ZKw/p0aa8+r0cwGkIvy48AiKnoFYdJ3eMOHmeT5t0Jw=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-11-28 20:27:26, Info                  CSI    00004ee4 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 ZKw/p0aa8+r0cwGkIvy48AiKnoFYdJ3eMOHmeT5t0Jw=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-11-28 20:27:26, Info                  CSI    00004ee5 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
2015-11-28 20:27:26, Info                  CSI    00004ee6@2015/11/29:04:27:26.746 Primitive installers committed for repair
2015-11-28 20:27:26, Info                  CSI    00004ee7 [SR] Repair complete
2015-11-28 20:27:26, Info                  CSI    00004ee8 [SR] Committing transaction
2015-11-28 20:27:26, Info                  CSI    00004ee9 Creating NT transaction (seq 2), objectname [6]"(null)"
2015-11-28 20:27:26, Info                  CSI    00004eea Created NT transaction (seq 2) result 0x00000000, handle @0xc28
2015-11-28 20:27:26, Info                  CSI    00004eeb@2015/11/29:04:27:26.761 Beginning NT transaction commit...
2015-11-28 20:27:26, Info                  CSI    00004eec@2015/11/29:04:27:26.777 CSI perf trace:
CSIPERF:TXCOMMIT;13576
2015-11-28 20:27:26, Info                  CSI    00004eed [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired

Thanks again,

LS

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

This update has caused problems on my system as well. I cannot logout from any user after this update. A system restore keeps the problem but clean install from media creator USB works up until this update.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

opencl.dll Microsoft bug have nothing common with regedit Microsoft bug.

pre-1511 regedit works. Just don't forget to copy its MUI.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

opencl.dll Microsoft bug have nothing common with regedit Microsoft bug.

pre-1511 regedit works. Just don't forget to copy its MUI.

What is the MUI for Regedit.exe? I moved regedit.exe from the Windows.old folder to Windows folder. It runs "FIND" to completion. 

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.