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: chkdsk C: No errors reported. Startup Repair - Says it couldn't repair my PC. Uninstall latest feature - Says it can't Restore from a prior point - There are none Copying the file in question to a .bak, then deleting the original and copying it back - No effect 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.

I can't find that offline run in my DISM.log although the date of that run (7/20/22 going by the thread) is in there. I think, for me, an offline run does not go into that log. A few using Install.esd that were run online do appear in the DISM.log. Those do not crash, but for the life of me I can't find a reference to Install.esd or its letter (E:) other than in these lines... 2022-07-20 00:14:16, Info DISM DISM.EXE: Executing command line: DISM /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\Sources\install.esd:1 2022-07-22 23:38:34, Info DISM DISM.EXE: Executing command line: DISM /online /Cleanup-Image /RestoreHealth /Source:ESD:e:\Sources\install.esd:1 /Index:1 ...So, I'm actually unsure Install.esd was used. But there was no crash & no error message at the Command Prompt.

FWIW, you may try " /logpath:c:\dism.log " at the end of the command-line. This overrides the default output directory/file name. (where C:\ is your Windows partition.) I created a Windows 11 USB setup disk using MCT. It had install.esd and the image version is 10.0.22621.525. Ran DISM Restorehealth offline. Opened the DISM log to see that the ESD was indeed bypassed . The error codes are the same. Sorry to bring in Windows 11 here, but the results would be the same in Windows 10, I think.

(1) Did you get any message at the Command Prompt like he did? (2) Is there a reference to Install.esd or its letter in the log? I'll try tomorrow with /logpath. Must hit the sack.

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

Anonymous

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:

chkdsk C: No errors reported.
Startup Repair - Says it couldn't repair my PC.
Uninstall latest feature - Says it can't
Restore from a prior point - There are none
Copying the file in question to a .bak, then deleting the original and copying it back - No effect
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.

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 Volunteer Moderator

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.

0 comments

Answer accepted by question author

Anonymous

(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.

0 comments

75 additional answers

Anonymous

2022-12-29T08:50:30+00:00

I can't find that offline run in my DISM.log although the date of that run (7/20/22 going by the thread) is in there. I think, for me, an offline run does not go into that log. A few using Install.esd that were run online do appear in the DISM.log. Those do not crash, but for the life of me I can't find a reference to Install.esd or its letter (E:) other than in these lines...

2022-07-20 00:14:16, Info DISM DISM.EXE: Executing command line: DISM /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\Sources\install.esd:1

2022-07-22 23:38:34, Info DISM DISM.EXE: Executing command line: DISM /online /Cleanup-Image /RestoreHealth /Source:ESD:e:\Sources\install.esd:1 /Index:1

...So, I'm actually unsure Install.esd was used. But there was no crash & no error message at the Command Prompt.
Was this answer helpful?

0 comments No comments
Ramesh 181.6K Reputation points Volunteer Moderator

2022-12-29T09:06:33+00:00

FWIW, you may try "/logpath:c:\dism.log" at the end of the command-line. This overrides the default output directory/file name.

(where C:\ is your Windows partition.)

I created a Windows 11 USB setup disk using MCT. It had install.esd and the image version is 10.0.22621.525. Ran DISM Restorehealth offline. Opened the DISM log to see that the ESD was indeed bypassed. The error codes are the same.

Sorry to bring in Windows 11 here, but the results would be the same in Windows 10, I think.
Was this answer helpful?

0 comments No comments
Anonymous

2022-12-29T09:20:20+00:00

(1) Did you get any message at the Command Prompt like he did?

(2) Is there a reference to Install.esd or its letter in the log?

I'll try tomorrow with /logpath. Must hit the sack.
Was this answer helpful?

0 comments No comments