@Joanne you can take a look at this thread at the MC and see if the second post helps.
Basically it say's to take ownership of the one you have now, change the name to regedit.bak or regedit.old and replace it with another(older) one.
You can try using my copy from RegEdit, it's from my 11102 VM. Just download it, open properties and unblock it, then extract it and copy it to your Windows folder.
regedit.zip
Hi Cliff S , and thank you for your support! I have already downloaded your attachment and I am ready to use your suggestion, on my Insider build at first, and then if it will work, on my main OS, as well.
Please clarify to me the following, though: after searching for regedit.exe in my Windows folder here are the results:
- Which file(s) exactly should I take ownership of, rename and backup? Which one(s) from all those files?
Thank you!
It's easier & faster to go directly there in File Explorer: Windows C: drive >> Windows and scroll towards the bottom, no need to open anything.
What you're seeing are copies in WinSxS(Windows side by side) and user interface files. You want regedit.exe or the so called application. Here is a screenshot, you want what's highlighted:
There is no issue with registry search so long as what you ask it to find is in the registry--search works fine & perfectly for that, which is why this is a low priority bug. Here's what you can do to see it for yourself:
1) Run regedit
2) Search for "Treetop" & select the "match whole string only" option
You will see the normal "searching through registry" box come up, but it will stay up no matter how much time you give it. Hit the cancel button at that point and regedit will crash and then immediately restart. That's the bug. When it's fixed, regedit will simply exit with a "Finished searching through the registry" notification, which will let you know that the item you searched for was not found.
It's a very minor bug and that's why they are taking their time--they have much bigger fish to fry...
Thanks for clarifying that for me.There is no issue with registry search so long as what you ask it to find is in the registry--search works fine & perfectly for that, which is why this is a low priority bug. Here's what you can do to see it for yourself:
1) Run regedit
2) Search for "Treetop" & select the "match whole string only" option
You will see the normal "searching through registry" box come up, but it will stay up no matter how much time you give it. Hit the cancel button at that point and regedit will crash and then immediately restart. That's the bug. When it's fixed, regedit will simply exit with a "Finished searching through the registry" notification, which will let you know that the item you searched for was not found.
It's a very minor bug and that's why they are taking their time--they have much bigger fish to fry...
Quote
