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.

Yes, pls upload the latest SFC log. //I have no idea which ones of these we really need to get it to boot.// If it's not even getting to the sign-in screen, then you may try boot logging via Startup settings (WinRE). ***Enable Boot Logging.*** With this option enabled, Windows creates a log file that lists the names and status of all drivers loaded into memory. To view the contents of this file, look for Ntbtlog.txt in the %SystemRoot% folder. If your system is hanging because of a faulty driver, the last entry in this log file might identify the culprit. *//*I'm unclear; is dism still a viable tool running offline?// It's still a useful tool to detect component store corruption online/offline. Unfortunately, it's unable to repair the corruption when run from RE. I'm yet to test it on WinPE/HBCD kind of bootable media.

ntbtlog contains a bunch of BOOTLOG_LOADED and then some BOOTLOG_NOT_LOADED. The last ones in the file are: BOOTLOG_LOADED \SystemRoot\System32\drivers\USBSTOR.SYS BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys BOOTLOG_NOT_LOADED \SystemRoot\SysWow64\drivers\hidusb.sys BOOTLOG_LOADED \SystemRoot\System32\drivers\usbccgp.sys BOOTLOG_NOT_LOADED \SystemRoot\SysWow64\drivers\hidusb.sys BOOTLOG_NOT_LOADED \SystemRoot\SysWow64\drivers\hidusb.sys BOOTLOG_NOT_LOADED \SystemRoot\SysWow64\drivers\hidusb.sys BOOTLOG_NOT_LOADED \SystemRoot\SysWow64\drivers\hidusb.sys I'll upload the files ASAP.

" I'm unclear; is dism still a viable tool running offline? " I think I'll agree with Ramesh that DISM was worth a try although it couldn't access an ESD or WIM for any of us. Looking again at your DISM.log, DISM was able to access your c:\Windows\WinSxS folder. But, in your case, it looks like there was corruption inside. The CBS (Component-Based Servicing) could not parse the Manifest. Mine & Ramesh's were parsed, just not yours. 2022-12-27 10:29:27, Info CSI 00000002 Shim considered [l:123]'??\c:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.2300_none_7e14edbc7c88b7d5\wcp.dll' : got STATUS_SUCCESS 2022-12-27 10:29:40, Info CBS Failed to parse the manifest from the buffer. [HRESULT = 0x800f0900 - CBS_E_XML_PARSER_FAILURE] It was worth a try. Too bad it failed. Still hoping to see a success in this thread.

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

Ramesh 181.6K Reputation points Volunteer Moderator

2022-12-31T07:26:02+00:00

Yes, pls upload the latest SFC log.

//I have no idea which ones of these we really need to get it to boot.//

If it's not even getting to the sign-in screen, then you may try boot logging via Startup settings (WinRE).

***Enable Boot Logging.***With this option enabled, Windows creates a log file that lists the names and status of all drivers loaded into memory. To view the contents of this file, look for Ntbtlog.txt in the %SystemRoot% folder. If your system is hanging because of a faulty driver, the last entry in this log file might identify the culprit.

*//*I'm unclear; is dism still a viable tool running offline?//

It's still a useful tool to detect component store corruption online/offline. Unfortunately, it's unable to repair the corruption when run from RE. I'm yet to test it on WinPE/HBCD kind of bootable media.
Was this answer helpful?

0 comments No comments
Anonymous

2023-01-01T03:21:06+00:00

ntbtlog contains a bunch of BOOTLOG_LOADED and then some BOOTLOG_NOT_LOADED. The last ones in the file are:

BOOTLOG_LOADED \SystemRoot\System32\drivers\USBSTOR.SYS

BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys

BOOTLOG_NOT_LOADED \SystemRoot\SysWow64\drivers\hidusb.sys

BOOTLOG_LOADED \SystemRoot\System32\drivers\usbccgp.sys

BOOTLOG_NOT_LOADED \SystemRoot\SysWow64\drivers\hidusb.sys

BOOTLOG_NOT_LOADED \SystemRoot\SysWow64\drivers\hidusb.sys

BOOTLOG_NOT_LOADED \SystemRoot\SysWow64\drivers\hidusb.sys

BOOTLOG_NOT_LOADED \SystemRoot\SysWow64\drivers\hidusb.sys

I'll upload the files ASAP.
Was this answer helpful?

0 comments No comments
Anonymous

2023-01-01T23:58:22+00:00

"I'm unclear; is dism still a viable tool running offline?"

I think I'll agree with Ramesh that DISM was worth a try although it couldn't access an ESD or WIM for any of us. Looking again at your DISM.log, DISM was able to access your c:\Windows\WinSxS folder. But, in your case, it looks like there was corruption inside. The CBS (Component-Based Servicing) could not parse the Manifest. Mine & Ramesh's were parsed, just not yours.

2022-12-27 10:29:27, Info CSI 00000002 Shim considered [l:123]'??\c:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.2300_none_7e14edbc7c88b7d5\wcp.dll' : got STATUS_SUCCESS

2022-12-27 10:29:40, Info CBS Failed to parse the manifest from the buffer. [HRESULT = 0x800f0900 - CBS_E_XML_PARSER_FAILURE]

It was worth a try. Too bad it failed. Still hoping to see a success in this thread.
Was this answer helpful?

0 comments No comments