New
#11
Greetings from Holly Jerusalem
After the Cumulative Update for Windows 10 Version 1511 (KB3120677) the issue was reoslved
Thanks for everybody
As I already write here, any long >255 chars registry key cause this in new regedit. Use regedit from 10240 instead and ask your Microsoft support to fix their bugs.
How can I "use" the Registry Editor from build 10240 in the latest Windows 10 Pro build? I do not even have build 10240 any more but IF this would fix this issue and NOT cause (add) new ones, I'd give it a try.
I have already reported this to Windows Feedback weeks ago. IF you are referring to phone support or e-mail support from Microsoft, I have never used that all these years I am on Windows. I do not think it would make any significant difference.
Thank you.
PS: if you wish, elaborate a bit more on why this is happening, please, and how can we verify it / test it a bit.
1) Just copy old regedit and its MUI file from any working 10240 system to any directory (preserve subdir for MUI) and use.
2) It happens because Microsoft broke regedit in 10586.
3) To see this bug in action, at least one long key should be present in the registry, usually they are device named ones.
Thank you for your reply.
Just to fully clarify this... When I search for "regedit" in my current Windows folder, I get the following results:
Can you please tell me which files exactly should I copy from build 10240, and where exactly should I paste them on the latest Windows 10 Pro build?
When it comes to me trying this...right now I do not even have the 10240 ISO... It would require me to download it, install it, copy the regedit files and then remove it. I am not sure IF I will try this just for this stupid bug. Your answer might help other members though, or even me when and if I'll decide to perform all this...
Thank you for your support!
regedit.exe and en-US\regedit.exe.mui should be enough.
As popular alternative looking very similar you can try OO RegEditor