Question Device Manager & Disk Management won't open, and other issues ?

[DellvlloN]

I have an HP Pavilion desktop and recently installed a new NVMe SSD. After cloning the original and getting everything loaded up, I noticed that the Device Manager and Disk Management will not open and options to open Command Prompt with administrative privileges won't open, either. I have found a workaround to access CMD with administrative privileges but I cannot get Device Manager or Disk Management to open no matter what I try. I've already checked the drive for errors; Windows reports that there are no issues with the drive. I have also run DISM and SFC, again no errors were reported, so I am at a loss.

Does anyone have any idea what is causing all of this? Does anyone know of any solutions? I could really use some help; this is a completely new problem to me.

HP Pavilion 570-p033w
CPU - i7-7700
RAM - 16GB DDR4 (2x8GB)
SSD - Netac NV3000 250GB NVME M.2 PCIe Gen 3x4 2280
HDD - Seagate ST2000DM001 2TB
Windows 10 Version: 21H2 / OS Build: 19044.3086 (I am in the process of updating this to 22H2) **Updated to Version 22H2 / Build: 19045.3996**

 

[Ralston18]

Update your post to include full system hardware specs and OS information.

Regarding "I have found a workaround to access CMD with administrative privileges":

What was that workaround? Some app or utility, registry edit?

 

[DellvlloN]

Update your post to include full system hardware specs and OS information.

Regarding "I have found a workaround to access CMD with administrative privileges":

What was that workaround? Some app or utility, registry edit?

HP Pavilion 570-p033w
CPU - i7-7700
RAM - 16GB DDR4 (2x8GB)
SSD - Netac NV3000 250GB NVME M.2 PCIe Gen 3x4 2280
HDD - Seagate ST2000DM001 2TB
Windows 10 Version: **Updated to Version 22H2 / Build: 19045.3996**

If I've left out information you feel is pertinent, please let me know what you're looking for and I will provide that information for you.

The workaround I spoke of for command prompt, and now Device Manager and Disk Management, was to open them through folder view after going into Control Panel. The problem seems to be isolated to just the actual right-click menu on the "Start" button. Like I said, I've never seen this type of error happen before. It's as if the shortcuts on the right-click menu of the start button just aren't working. Some are, but the ones pertaining to the system are the ones that are not responsive (although the "System" link, itself, on the start menu is working fine).

It's just weird because I've ran virus scans with both Windows Defender and Malwarebytes Anti-Malware premium and both report that the system is virus free.

 

[Ralston18]

When you right click the Start button to get the menu - does left clicking the choice work?

= = = =

Look in Reliability History/Monitor and Event Viewer.

Either one or both tools may be capturing some error code, warning, or even an informational event when a selected menu choice fails to work.

Start with Reliability History - much more end user friendly and the timeline format may prove helpful.

Event Viewer requires more time and effort.

To help with Event Viewer:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

Any given event entry can be clicked for more details. The details may or may not be helpful.

 

[DellvlloN]

When you right click the Start button to get the menu - does left clicking the choice work?

Answer - Not all of them. This is the main issue I am having and why I am seeking help. I will list in chronological order which ones work and which ones do not.

Apps & Features - Yes. Works with no issues.
Power Options - Yes. Works with no issues.
Event Viewer - No. Left clicking does not work.
System - Yes. Works with no issues.
Device Manager - No. Left clicking does not work.
Network Connections - Yes. Works with no issues.
Disk Management - No. Left clicking does not work.
Computer Management - No. Left clicking does not work.
Windows PowerShell - No. Left clicking does not work.
Windows PowerShell (Admin) - No. Left clicking does not work.
Task Manager - No. Left clicking does not work.
Settings - Yes. Works with no issues.
File Explorer - No. Left clicking does not work.
Search - Yes. Works with no issues.
Run - Yes. Works with no issues.
Shut down or sign out - Yes. All sub-menu items work with no issues.
Desktop - Yes. Seems to work with no issues.

= = = =

Look in Reliability History/Monitor and Event Viewer.

Either one or both tools may be capturing some error code, warning, or even an informational event when a selected menu choice fails to work.

Start with Reliability History - much more end user friendly and the timeline format may prove helpful.

Reliability History -

The only errors reported are an improper shutdown; happened due to power outage, and then a failed update for KB5034441; which fails because I am not using Windows Recovery Environment; this is normal according to Microsoft details.

Event Viewer requires more time and effort.

To help with Event Viewer:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

Any given event entry can be clicked for more details. The details may or may not be helpful.

Event Viewer - There are a few errors and warnings. I'll list a summary of the errorsbelow:

Application:

Errors:
1. Volume Shadow Copy Service Information: Com Server with CLSID {4e14fba2-2e22-11d1-9964-00c04fbbb345} and name CEventSystem cannot be started. [0x8007045b, A system shutdown is in progress.

2. Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x8007045b, a system shutdown is in progress.

3. Volume Shadow Copy Service Information: Com Server with CLSID {4e14fba2-2e22-11d1-9964-00c04fbbb345} and name CEventSystem cannot be started. [0x8007045b, A system shutdown is in progress.

4. The Cryptographic Services service failed to initialize the Catalog Database. The ESENT error was: -1409

5. Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x8007045b, A system shutdown is in progress.

System:

1. Source: Service Control Manager. Event ID 7001 - The Intel(R) Dynamic Application Loader Host Interface Service depends on the IP Helper service which failed to start because of the following error: The operation completed successfully.

2. Source: Windows Update Client. Event ID 20 - Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone.

3. Source: Service Control Manager. Event ID 7023 - The Network List Service service terminated with the following error: The device is not ready.

4. Source: Service Control Manager. Event ID 7030 - THe Printer Extensions and Notifications service is marked as an interactive service. However, the system is configured to not allow interactive services. The service may not function properly.

Those are all of the errors listed in Application, Security, Setup, System and Forwarded Events. There are some warnings, as well, but they are related to Kernel PnP and the aforementioned failed Windows Update error of KB503034441.

I apologize in the delayed response. My area has had excessive rainfall and flooding due to the rainfall and subsequent melting of approximately 10" of snow we had from last week.

If you need any other information, just let me know. Thanks again!

 

[USAFRet]

After cloning the original and getting everything loaded up, I noticed that the Device Manager and Disk Management will not open and options to open Command Prompt with administrative privileges won't open, either.

After a proper clone, that can't happen.

The new drive is a literal copy of the old.


What did you use to clone?
At the end of the clone process, did you physically disconnect the old drive, and allow the system to boot up from only the new?

 

[DellvlloN]

After a proper clone, that can't happen.

The new drive is a literal copy of the old.


What did you use to clone?
At the end of the clone process, did you physically disconnect the old drive, and allow the system to boot up from only the new?

I used Macriom Reflect to clone the disk. Once the process was completed, the software said the process had completed successfully. Yes, once the clone was completed, I disconnected the original HDD and booted up from the NVME drive. to verify that the drive was working independently, solely on its own.

 

[USAFRet]

I used Macriom Reflect to clone the disk. Once the process was completed, the software said the process had completed successfully. Yes, once the clone was completed, I disconnected the original HDD and booted up from the NVME drive. to verify that the drive was working independently, solely on its own.

hmm....

Is the original drive still fully functional?
If so, I'd suggest redoing the clone.

To me, it sounds like something went wrong. Even if Macrium reported success.

Specific little parts not working....not a full clone.

 

[DellvlloN]

hmm....

Is the original drive still fully functional?
If so, I'd suggest redoing the clone.

To me, it sounds like something went wrong. Even if Macrium reported success.

Specific little parts not working....not a full clone.

Allow me to explain my situation a little further as to provide more insight. I am doing the NVME drive update for a friend. I never bothered checking specific functions regarding CMD, PowerShell, Device Manager, etcetera. I did, hower, fully scan the original HDD with both Malwarebytes Anti-Malware and Windows Defender before attempting the clone; both reports completing with no threats or warnings detected (I wanted to make sure the system was clean before cloning, and both programs reported that the file system is clean of any malware or threats). I clone the disk and then, as I stated, unplugged the original drive to ensure that Windows did, in fact, boot successfully from the NVME drive. I began updating the system and removing HP's bloatware from the new drive and that's when I discovered the issues I am currently having.

That said, I have just removed the NVME drive and booted back into the old HDD to see if I could open CMD, PowerShell, Device Manager, etcetera. The original HDD is afflicted with the same issues presenting on the new drive. So, the clone was indeed successful, but the original drive is responsible for the problems that have been brought over to the new one.

I've never experienced a loss of link functionality before, ever, so I did not have the foresight to check for these issues before cloning the drive. The whole reason for the clone is so that I can save my friend the trouble of having to reinstall all of their hardware and software drivers; remember specific credentials (i.e. login information; saved data-entry fields, etc.). Apparently, however, it appears as if I might have to save the files, documents and folders from the current installation, do a fresh install of Windows to the NVME drive, and then migrate those items over to the new system; leaving my less-computer savvy friend responsible for installing everything else on their own.


Still, I would love to know what is causing this issue to begin with; when antivirus/anti-malware software reports no issues and the system otherwise functions exactly as it should. I'm just at a loss.

 

[USAFRet]

Right.
So the problem existed before the clone.
As such, it exists after the clone.

I have NO idea what could be the cause of that. Nor, a fix.

Yes, this does look like a full reinstall, and abandoning the clone idea.
Faulty source = faulty target.

 

[DellvlloN]

Okay. I've given this post a week to try and see if someone might reply who's faced this issue before, but it appears as if it's an odd fluke/glitch. Since I have already reinstalled a fresh copy of Windows and have returned this computer to its owner, I guess it would be okay to close the thread. Thanks for the insights, fellas.