New
#11
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\software\Classes\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\shell\Manage\command]
@="mmc.exe compmgmt.msc /s /64"
Highlight the code above like this:
Rt click the highlighted code and select copy
open notepad and paste it in.
save it as compmgmt.REG
dble click the compmgmt.reg file you just made , Yes to the message "are you sure you want to continue" .
Not sure why you are getting that. It works fine for me.
Might be due to the permissions on that key.
try it this way:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\shell\Manage\command]
@="mmc.exe compmgmt.msc /s /64"
Sorry I didn't wait. I went ahead and did a repair install, and that 'fixed' the problem. The problem no longer exists. I can now access "Manage" in the My PC context menu. Thank you very much for the help. Much appreciated.
I'm going to take this opportunity to review the warnings and errors that are showing up in the newly created logs documented in the event viewer. Any suggestions on how to resolve these? Should I go ahead and start a new message thread instead?
---
P.S. I'm wondering about those surprising errors in eventviewer. I wasn't expecting them after a 'repair install'. Instead of dealing with these errors, I'm wondering if now might be a good time to upgrade to Win 11. Your thoughts on this? Would you recommend upgrading to Win 11 after doing an incremental backup? Thanks.
Last edited by bofhlusr; 13 Jan 2022 at 20:53. Reason: Added more questions.
I agree. But, before taking any other remedial action, I do suggest making a new system image so you can at least get back to where you are now if anything goes seriously wrong.
I don't recall Repair install ever going seriously wrong but I still make a new system image and a backup copy of all my own files before I run it.
1 Download the ISO - use one of the sources identified in Download Windows 10 ISO File -TenForumsTutorials [one of them, the MS MCT tool, achieves both steps 1 & 3] The ISO & any USB made using the MCT include all common Editions. You'll see this evident when choosing the ISO to download.
2 If you are running an 'InPlace upgrade' / 'Repair install' procedure then you can do so directly from the downloaded ISO file as well as from an InstallUSB but, in both cases, you boot into Windows normally not from the USB.
Repair Install - TenForumsTutorials
Note that the Repair install procedure will recognise your currently-installed Edition and repair that so you'll have no Edition-related problems at all.
3 You will only ever need to consider making an InstallUSB if you want to run a clean install [or to carry out specific repairs such as Startup repairs] - Create Bootable Installation USB - TenForumsTutorials
4 For info -
Startup Repair - TenForumsTutorials
Clean Install - TenForumsTutorials and, in preparation for one, consider Backup and Restore Device Drivers - TenForumsTutorials
OK. That will not make any difference to running a Repair install [or a Clean install for that matter].
Many people say that upgraded systems can experience odd problems here & there. But others say that they have been running their upgraded system since 2015 without any incidents at all.
It's always nice to talk to somebody who has a sense of humour.
All the best,
Denis
I managed not to see this post of yours while I was writing my last one.
The most appropriate response to most entries in Event viewer is to ignore them.Event viewer can be useful in tracking down the cause of a fault symptom.If you do want to pursue anything then make it each one a new thread and make sure you include the Event log, Source & EventID in each thread title. And, as your opening sentence in each thread, say why you think the matter is worth investigating.
Assuming there is a fault to fix because of an entry in Event viewer is not always appropriate.
I would not recommend that.
All the best,
Denis