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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-01-02T01:57:18+00:00

    IT BOOTED!!! Sort of...the main screen came up, but my mouse and keyboard don't work! I'm wondering if it's the HidUsb.sys driver. Here are all the files on the bad drive:

    C:\Windows>dir /s hidusb.sys

    Volume in drive C has no label.

    Volume Serial Number is 5092-80BF

    Directory of C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.2006.1.7\amd64_dual_input.inf_31bf3856ad364e35_10.0.19041.868_none_06aed3f048cb8494\n

    06/10/2021 02:58 AM 19,256 hidusb.sys 

               1 File(s)         19,256 bytes

    Directory of C:\Windows\System32\drivers (Moved here)

    12/29/2022 09:12 PM 44,032 HidUsb.sys 

               1 File(s)         44,032 bytes

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

    12/15/2022 12:39 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

    12/26/2022 01:55 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 09:01 PM 19,258 hidusb.sys 

               1 File(s)         19,258 bytes

    Directory of C:\Windows\WinSxS\amd64_dual_input.inf_31bf3856ad364e35_10.0.19041.868_none_06aed3f048cb8494

    04/21/2021 07:28 AM 44,032 hidusb.sys 

               1 File(s)         44,032 bytes

    Directory of C:\Windows\WinSxS\amd64_dual_input.inf_31bf3856ad364e35_10.0.19041.868_none_06aed3f048cb8494\n

    04/08/2021 04:45 PM 19,256 hidusb.sys 

               1 File(s)         19,256 bytes

    I'm not even sure if all of these files match. The version on my work laptop is dated 11/14/2022.

    Assuming we can get it to boot successfully WITH keyboard and mouse, what's the next step to getting it REALLY fixed? Do we run SFC, or DISM /online, or something else?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-01-02T01:35:44+00:00

    I don't see that one at your dropbox. I see...

    2022-12-30 17:39:15, Info DISM DISM.EXE: Executing command line: dism /image:c:\ /cleanup-image /restorehealth /scratchdir:c:\temp

    That is, no ESB was specified at all. So, it didn't even try to access it. It again went ahead & did access your c:\Windows\WinSxS. But it looks to me the Manifest is still corrupt or missing.

    I want to suggest to copy the WinSxS folder from your Install.esd & paste over the one on C: -- but I think I've seen it tried in other thread(s) & it failed to be a solution. But maybe it's worth a try just before resorting to a clean install. What is your objection to a clean install?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-01-02T00:36:10+00:00

    Just uploaded all latest logs for SFC, logged boot and dism. Same URL as last time. This time, I ran dism from my USB D:\Sources folder with /Source:install.esb since it seems to want to pre-pend the current folder.

    Was this answer helpful?

    0 comments