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
    2022-12-27T18:37:04+00:00

    All files uploaded to the same URL I sent earlier.

    Was this answer helpful?

    0 comments
  2. Ramesh 181.6K Reputation points Volunteer Moderator
    2022-12-27T02:18:21+00:00

    Ok. We're making progress. Now, we need the latest CBS log. Fixing the error 0x800f081f should resolve all other issues. I think we don't need to bother about the SFC report now.

    Pls check these locations:

    C:\windows\Logs\CBS\

    X:\windows\Logs\CBS\

    Pls upload *all* files in those folders.

    Also upload the output of this command redirected to "c:\packages.txt":

    • dism /image:c:\ /get-packages /format:list >c:\packages.txt

    No need for the DISM log, as the servicing issue has been resolved. It's a CBS problem.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-12-26T23:49:00+00:00

    I looked at the SFC log and tried copying over files from my work laptop and re-ran SFC to no avail (I renamed the existing files to .old). I'm still getting errors like:

    00001b2c Hashes for file member [l:17]'BluetoothApis.dll' do not match.

    Expected: {l:32 ml:33 b:ca8e99e2961492b4a0cea897aa0d4b451fdc4671ace1241395b0ae4558dc5c3a}.

    Actual: {l:32 b:78f2410d03645b7a57fef973d2dec7e836cc6cf80d71a8b825f188d6af485ac8}.

    00001b2d [SR] Cannot repair member file [l:17]'BluetoothApis.dll' of Microsoft-OneCore-Bluetooth-UserApis, version 10.0.19041.546, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    00001b2e Hashes for file member [l:17]'BluetoothApis.dll' do not match.

    Expected: {l:32 ml:33 b:ca8e99e2961492b4a0cea897aa0d4b451fdc4671ace1241395b0ae4558dc5c3a}.

    Actual: {l:32 b:78f2410d03645b7a57fef973d2dec7e836cc6cf80d71a8b825f188d6af485ac8}.

    00001b2f [SR] Cannot repair member file [l:17]'BluetoothApis.dll' of Microsoft-OneCore-Bluetooth-UserApis, version 10.0.19041.546, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    00001b30 [SR] This component was referenced by [l:159]'Microsoft-Windows-Client-Desktop-Required-Package05110~31bf3856ad364e35~amd64~~10.0.19041.2364.40DF5D77812A1F052AD9A12D9A900470424C73A66CC8FFCCA32FD6E08FE8C629'

    00001b31 [SR] This component was referenced by [l:158]'Microsoft-Windows-Client-Desktop-Required-Package0511~31bf3856ad364e35~amd64~~10.0.19041.2364.5F855EAD21B5D159A77F8E79CFE40397CD51A1F3AD5F11F3BC64C8B5F69815BF'

    00001b32 Hashes for file member [l:17]'BluetoothApis.dll' do not match.

    Expected: {l:32 ml:33 b:ca8e99e2961492b4a0cea897aa0d4b451fdc4671ace1241395b0ae4558dc5c3a}.

    Actual: {l:32 b:78f2410d03645b7a57fef973d2dec7e836cc6cf80d71a8b825f188d6af485ac8}.

    00001b33 Hashes for file member [l:17]'BluetoothApis.dll' do not match.

    Expected: {l:32 ml:33 b:ca8e99e2961492b4a0cea897aa0d4b451fdc4671ace1241395b0ae4558dc5c3a}.

    Actual: {l:32 b:78f2410d03645b7a57fef973d2dec7e836cc6cf80d71a8b825f188d6af485ac8}.

    00001b34 [SR] Could not reproject corrupted file ??\C:\Windows\System32\BluetoothApis.dll; source file in store is also corrupted

    There were also a bunch of manifest files listed, e.g.:

    \winsxs\manifests\amd64_00d36c5e5f91977781683a7f80289e8d_31bf3856ad364e35_10.0.19041.1852_none_c6b9a6bedf3cfffe.manifest

    \winsxs\manifests\amd64_117b9fa0caf6ec4b0f6cf1b24dda2fc4_31bf3856ad364e35_10.0.19041.1852_none_c279a35b0b2bfd66.manifest

    etc,

    Was this answer helpful?

    0 comments