[SOLVED] Unable to open "Device Manager Shortcuts"

Jul 3, 2021
3
0
10
Hello all

So, this is frustrating the <Mod Edit> out of me. I have not updated nor have I installed any programs since and now when I try to open device manager from the WIN+X shortcut it displays this error
Have tried the following:
Dism /Online /Cleanup-Image /CheckHealth Dism /Online /Cleanup-Image /ScanHealth Dism /Online /Cleanup-Image /RestoreHealth sfc/scannow
It opens fine when I open it through "devmgmt.msc" although not through any shortcuts?
Any suggestions would be greatly appreciated!

RDEIRrf.png
 
Last edited by a moderator:
Solution
well, in the MS link that suggests DISM/SFC it also suggests a clean boot

Try a clean boot and see if it changes anything - make sure to read instructions and make sure NOT to disable any microsoft services or windows won't load right - https://support.microsoft.com/en-au/help/929135/how-to-perform-a-clean-boot-in-windows

if clean boot fixes it, it shows its likely a startup program. You should, over a number of startups. restart the programs you stopped to isolate the one that is to blame.

https://answers.microsoft.com/en-us...e/4128fff8-22d2-43ef-85a1-1059626282ed?auth=1

could try running chkdsk on C drive

Colif

Win 11 Master
Moderator
well, in the MS link that suggests DISM/SFC it also suggests a clean boot

Try a clean boot and see if it changes anything - make sure to read instructions and make sure NOT to disable any microsoft services or windows won't load right - https://support.microsoft.com/en-au/help/929135/how-to-perform-a-clean-boot-in-windows

if clean boot fixes it, it shows its likely a startup program. You should, over a number of startups. restart the programs you stopped to isolate the one that is to blame.

https://answers.microsoft.com/en-us...e/4128fff8-22d2-43ef-85a1-1059626282ed?auth=1

could try running chkdsk on C drive
 
Solution
Jul 3, 2021
3
0
10
Thanks for getting back
No luck with the clean boot unfortunately although when I updated to the latest windows (21H1) it started working which I found a little odd
May have had to do with a previous updated Im guessing. Not sure how long it was doing it for without me taking notice to it
 
Jul 3, 2021
3
0
10
so replacing windows - updating to 21H1 - fixed it?

It does replace the entire install so that sort of makes sense.

Yeah, updating to 21H1 fixed the issue.

It seemed like it was a broken shortcut to the default location through control panel ( %windir%\system32\control.exe /name Microsoft.DeviceManager)
Because when I re-directed the shortcut to go to the devmgmt.msc in System32 it had no issues in doing that