Windows 10 can't boot - Critical system driver is missing or contains errors

Anonymous
2022-12-21T17:22:28+00:00

Hi,

The file in question is: \Windows\system32\drivers\VmsProxyHNic.sys, error 0xc000007b

The file is there. I'm using an SSD. From a bootable USB I've tried:

  1. chkdsk C: No errors reported.
  2. Startup Repair - Says it couldn't repair my PC.
  3. Uninstall latest feature - Says it can't
  4. Restore from a prior point - There are none
  5. Copying the file in question to a .bak, then deleting the original and copying it back - No effect
  6. Can't boot into Safe Mode

Any other things I can try? I'd like to get this to boot again so I can at least see what programs I have installed.

Thanks.

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Ramesh 181.6K Reputation points Volunteer Moderator
2023-01-04T03:32:15+00:00

After running that command, have you checked the CBS log to see which components are missing?

And regarding the failed repair installation, you can check setupact.log and setuperr.log in the Panther folder. Or download SetupDiag from this link and run it. The tool collects the setup logs and saves them into a zip file named Logs.zip on your desktop.

Was this answer helpful?

1 person found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2023-01-04T02:39:21+00:00

(1) I still say to try the repair-install again. It must be run from a Normal Boot (not Safe Mode), if you can get back there. Do the clean boot first, which unfortunately will require a 2nd boot to Normal Mode before you can do the repair-install. (But possibly the clean boot can be set up in Safe Mode, then boot to Normal Mode.). Definitely, wear a neckless of garlic this time. But a repair-install is the thing.

(2) Had you made a system image after that successful boot to Normal Mode, you'd have locked the goodness in. Hopefully, you can get back there easily, though. Restore Points aren't as powerful. For one thing, a repair-install wipes them out.

Was this answer helpful?

1 person found this answer helpful.
0 comments

75 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2023-01-02T02:41:00+00:00

    Since you got so close to a Normal Mode boot, maybe Safe Mode will get the rest of the way. Try it with Networking. Then, yeah, see whether DISM & SFC will be a fix. After that, the next try would be a repair-install which keeps files & apps. Too bad a repair-install can't be run from Safe Mode.

    (a) Boot to your Win 10 Installation USB drive.

    (b) Click "Repair your computer" instead of to install.

         The computer will reboot to the Recovery Environment at the "Choose an Option" screen.

    (c) Click "Troubleshoot > Advanced Options > Command Prompt".

    (d) Enter the following for Safe Mode with Networking ...

    bcdedit /set {default} safeboot network

    (e) Exitthe Command Prompt.

    (f) Finally, click "Continue" to get to Windows in Safe Mode with Networking.

    (g) Do a Windows Update. I don't think yours is OS Build 19045.2364.

      Your LCU package is saying: 19041.2006.1.7.

    (h) Try DISM & SFC, then reboot to Normal Mode. Good luck.

    I think that will be a one-time boot to Safe Mode. If not, type the following to turn it off...

    bcdedit /deletevalue {current} safeboot

    Here are my HidUSB in 22H2, OS Build 19045.2364. I seem to have only 5 compared to your 7. I guess the most important one is in the Drivers folder. We've got the same size there....

    C:\WINDOWS\system32>dir /s C:\hidusb.sys

    Volume in drive C is PCR Hard

    Volume Serial Number is F4D4-2928

    Directory of C:\Windows\servicing*LCU\Package*_for_RollupFix~31bf3856ad364e35~amd64~~19041.2364.1.4\amd64_dual_input.inf_31bf3856ad364e35_10.0.19041.2251_none_9d8e6d8b9f1f91ec\n

    11/04/2022 11:01 PM 19,258 hidusb.sys 

               1 File(s)         19,258 bytes

    Directory of C:\Windows\System32\drivers

    11/08/2022 03:49 PM 44,032 hidusb.sys 

               1 File(s)         44,032 bytes

    Directory of C:\Windows\System32\DriverStore\FileRepository\input.inf_amd64_292ece99a27cec96

    11/08/2022 03:49 PM 44,032 hidusb.sys 

               1 File(s)         44,032 bytes

    Directory of C:\Windows\WinSxS\amd64_dual_input.inf_31bf3856ad364e35_10.0.19041.2251_none_9d8e6d8b9f1f91ec

    11/08/2022 03:49 PM 44,032 hidusb.sys 

               1 File(s)         44,032 bytes

    Directory of C:\Windows\WinSxS\amd64_dual_input.inf_31bf3856ad364e35_10.0.19041.2251_none_9d8e6d8b9f1f91ec\n

    11/04/2022 11:01 PM 19,258 hidusb.sys 

               1 File(s)         19,258 bytes 

 Total Files Listed: 

           5 File(s)        170,612 bytes 

           0 Dir(s)  947,757,625,344 bytes free

    C:\WINDOWS\system32>

    Was this answer helpful?

    0 comments
  2. Ramesh 181.6K Reputation points Volunteer Moderator
    2023-01-02T03:50:31+00:00

    See if any driver load errors are recorded in the system event log.

    c:\windows\system32\winevt\Logs\System.evtx

    (Zip/upload it.)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-01-02T17:43:31+00:00

    Here are the warnings I see related to drivers:

    The driver \Driver*HidUsb* failed to load for the device USB\VID_413C&PID_2001&MI_01\7&154b00c4&0&0001.

    The driver \Driver\HidUsb failed to load for the device USB\VID_413C&PID_2001&MI_00\7&154b00c4&0&0000.

    The driver \Driver\HidUsb failed to load for the device USB\VID_2687&PID_FB01&MI_01\6&1d095b5f&9&0001.

    The driver \Driver\HidUsb failed to load for the device USB\VID_2687&PID_FB01&MI_00\6&1d095b5f&9&0000.

    The driver \Driver*NVHDA* failed to load for the device HDAUDIO\FUNC_01&VEN_10DE&DEV_0012&SUBSYS_10DE0101&REV_1001\5&c7a669e&0&0301.

    The driver \Driver\NVHDA failed to load for the device HDAUDIO\FUNC_01&VEN_10DE&DEV_0012&SUBSYS_10DE0101&REV_1001\5&c7a669e&0&0201.

    The driver \Driver\NVHDA failed to load for the device HDAUDIO\FUNC_01&VEN_10DE&DEV_0012&SUBSYS_10DE0101&REV_1001\5&c7a669e&0&0101.

    The driver \Driver\NVHDA failed to load for the device HDAUDIO\FUNC_01&VEN_10DE&DEV_0012&SUBSYS_10DE0101&REV_1001\5&c7a669e&0&0001.

    The driver \Driver*nvlddmkm* failed to load for the device PCI\VEN_10DE&DEV_0E22&SUBSYS_23211462&REV_A1\4&7e682fb&0&0010.

    The driver \Driver\NVHDA failed to load for the device HDAUDIO\FUNC_01&VEN_10DE&DEV_0012&SUBSYS_10DE0101&REV_1001\5&c7a669e&0&0301.

    The driver \Driver\NVHDA failed to load for the device HDAUDIO\FUNC_01&VEN_10DE&DEV_0012&SUBSYS_10DE0101&REV_1001\5&c7a669e&0&0201.

    The driver \Driver\NVHDA failed to load for the device HDAUDIO\FUNC_01&VEN_10DE&DEV_0012&SUBSYS_10DE0101&REV_1001\5&c7a669e&0&0101.

    The driver \Driver\NVHDA failed to load for the device HDAUDIO\FUNC_01&VEN_10DE&DEV_0012&SUBSYS_10DE0101&REV_1001\5&c7a669e&0&0001.

    The driver \Driver*WudfRd* failed to load for the device ROOT\WPD\0000.

    The driver \Driver\nvlddmkm failed to load for the device PCI\VEN_10DE&DEV_0E22&SUBSYS_23211462&REV_A1\4&7e682fb&0&0010.

    There are many others such as:

    The Microsoft Edge Update Service (edgeupdate) service terminated unexpectedly.

    The NVIDIA Update Service Daemon service failed to start 

    The Google Update Service (gupdate) service failed to start 

    The Dropbox Update Service (dbupdate) service failed to start 

    The AppX Deployment Service (AppXSVC) service terminated with the following error: 

    AppX Deployment Service (AppXSVC) is not a valid Win32 application.

    The Backupper Service service failed to start

    The dsNcService service failed to start 

    The hns service depends on the VfpExt service which failed to start

    Was this answer helpful?

    0 comments