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.4K 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. Ramesh 181.4K Reputation points Volunteer Moderator
    2022-12-22T17:23:59+00:00

    BTW, the command to run is:

    (Let's say Windows drive is E:\ which you can check by running BCDEDIT.)

    Run:

    • md E:\Temp
    • dism /image:E:\ /cleanup-image /restorehealth /source:F:\sources\install.wim /scratchdir:E:\temp

    Where F:\ is your USB boot disk.

    Was this answer helpful?

    0 comments
  2. Ramesh 181.4K Reputation points Volunteer Moderator
    2022-12-22T17:07:35+00:00

    Pls create a Windows 10 USB Setup disk (matching the version of your Windows installation. For example, if your Windows 10 version is 21H2, use Rufus to download the 21H2 ISO and create the USB Setup disk.)

    Boot into WinRE using the USB Setup disk and run DISM /RestoreHealth command.

    See the paragraph "Use DISM Offline to Repair Windows Image" in this article for more information.

    Note: If you have install.esd (instead of install.wim) in the ISO, mention the install.esd file path in the DISM command-line.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-12-22T16:37:08+00:00

    SFC said it fixed some stuff, but not everything. The log file is over 3 MB with 65,000+ lines. I see messages like:

    00000070 Manifest hash for component [l:93 ml:140]'amd64_117b9fa0caf6ec4b0f6cf1b24dda2fc4_31bf3856ad364e35_10.0.19041.1852_none_c279a35b0b2bfd66' does not match expected value.

    000000a8 (F) Unable to load manifest for component [l:93 ml:140]'amd64_1751b9d651379d8e2380ace0b524d314_31bf3856ad364e35_10.0.19041.1852_none_1ab8694852e70f5f'

    0000ea1f Hashes for file member [l:23]'PresentationHostDLL.dll' do not match.

    Expected: {l:32 ml:33 b:308f9597825f518e96f40a67b9b8ef89208a43cc7ca5b6a6a9252a4f1878f19e}.

    Actual: {l:32 b:b56843886ad61b22f7dbd4f7d5f9b3aa0bd919fdc7d8bdb45477e5218a6070d0}.

    0000128e [SR] Cannot repair member file [l:12]'usbprint.sys' of dual_usbprint.inf, version 10.0.19041.2193, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, type [l:14]'dualModeDriver' in the store, hash mismatch

    00001928 [SR] Could not reproject corrupted file ??\C:\Windows\System32\Microsoft-Windows-AppModelExecEvents.dll; source file in store is also corrupted

    There are tons of these.

    Now I just get the BSOD when I try to boot.

    I am using a recovery USB that I created from a different computer (same version of Windows 10); don't know if that matters.

    It's almost as if it broke mid way through doing a Windows update. I didn't get any reports of any viruses before it stopped booting.

    Was this answer helpful?

    0 comments