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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2023-01-03T21:05:06+00:00

    (or with the slipstreamed/22H2 WIM as the source)

    • Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\Sources\install.wim:#
    • sfc /scannow

    From normal boot, I ran:

    dism /online /cleanup-image /restorehealth /source:wim:D:\sources\install.wim:6

    Then, further down we get the same error that it can't find the source.

    2023-01-03 14:26:27, Info DISM DISM Package Manager: PID=6560 TID=6092 Error in operation: source for package or file not found, ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f) - CCbsConUIHandler::Error

    2023-01-03 14:26:27, Error DISM DISM Package Manager: PID=6560 TID=6232 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)

    2023-01-03 14:26:27, Error DISM DISM Package Manager: PID=6560 TID=6232 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg

    2023-01-03 14:26:27, Error DISM DISM Package Manager: PID=6560 TID=6232 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-01-03T14:29:36+00:00

    More bad news...it was still at 31% this morning so I clicked Cancel and now the machine is locked-up (no Caps Lock or mouse movements.) Maybe it's possessed. I'll wait a short while and then press the reset button I guess.

    No, I didn't do a system image because I was asking what to do after we get everything upgraded and working; if I should have done that before now I misunderstood.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-01-03T04:30:31+00:00

    That is sad. I guess I'd let it run another 1.5 hours at least before clicking cancel for hopefully a graceful exit. Then, yeah, show us those logs. But I suppose they will look the same. Then I'd say, do a full-fledged clean-boot, & try the repair-install again...

    https://support.microsoft.com/en-us/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd How to perform a clean boot in Windows

    Be sure to do as step 3 says, i.e., hide the Microsoft services before you click "disable". Did you make a system image as Ramesh smartly advised?

    Was this answer helpful?

    0 comments