Windows 10 Fall Update causes Regedit to crash on certain registry keys

[Batu69]

A bug in the Windows 10 registry editor (Regedit.exe) makes it crash since the large Fall update. The bug causes it to end up in an endless loop after which the application crashes. The issue happens when the search reaches a key of which the full path is longer than 255 characters.

 

 

The German website Heise found that once Regedit attempts to access a subkey with a full path longer than 255 characters, the application gets stuck in an infinite loop. Regedit also fully utilizes the CPU when in the loop. Trying to end the search by clicking ‘Cancel’ finally crashes Regedit after which the application restarts. The Windows Event Viewer lists an error with commctl32.dll. Heise so far only found that the issue occurs on long keys, Regedit always shows the issue when the first key longer than 255 characters is found.

 

Also previous versions of Windows 10 had issues with Regedit and long keys. In build 10240 (RTM) nothing happened when a long key was double clicked. In build 10586, the version before the Fall Update, an error message occured when such a key was double clicked.

 

Heise also mentions that it’s unclear how these long keys end up in the registry. They found that a clean installation of Windows 10 with the Fall Update didn’t have any long keys but nevertheless most computers they tested did contain them after some time. These kind of keys should have never end up the registry because it has a limit of 255 characters. Developers should know to not use longer key as they also caused issues in the past.

 

Article source

[mikie]

Question;     How do we easily/quickly find the offending key(s) ?

[vibranium]

You could try the Nirsoft utility RegScanner to search around the registry. Regedit is in a mess now and needs to be patched.

 

Quote

In addition to the standard string search (Like in RegEdit), RegScanner can also find Registry values by data length, value type (REG_SZ, REG_DWORD, and so on), and by modified date of the key.

 

 

The more important question is how to get rid of those keys if regedit is stuck in an infinite loop and the keys violate registry structure limitations. I haven't tried it yet but it might be possible to do this by merging REG files coded with key removals.

 

Personally, I would wait for more news to come out, because this statement from the researchers is both puzzling and disturbing:

 

Quote

They found that a clean installation of Windows 10 with the Fall Update didn't have any long keys but nevertheless most computers they tested did contain them after some time.