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.

So, I ran it offline & you are sadly right... 2022-12-29 19:18:48, Info DISM DISM.EXE: Executing command line: dism /Image:C:\ /Cleanup-Image /RestoreHealth /Source:ESD:E:\Sources\install.esd:1 /ScratchDir=C:\BU\temp /logpath:c:\BU\dism.log 2022-12-29 19:19:11, Info CBS Session: 596_442125 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null) 2022-12-29 19:19:11, Info CBS Exec: Addsource called, Session: 596_442125, Client: DISM Package Manager Provider, from GPO: No, Path: X:\Sources\ESD:E:\Sources\install.esd:1 2022-12-29 19:19:11, Warning CBS The alternate source path directory could not be accessed [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND ] 2022-12-29 19:19:11, Info CBS Failed to add new file source [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND] 2022-12-29 19:19:11, Info CBS Failed to add alternate file source [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND] 2022-12-29 19:19:11, Info CBS Failed adding alternate source directory [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND] 2022-12-29 19:19:11, Warning DISM DISM Package Manager: PID=596 TID=1240 CBS AddSource failed with HRESULT=0x80070003! - CDISMPackageManager::Internal_Finalize It looks like the DISM command is entered correctly going by what I see at TenForums & elsewhere. I don't know why "X:\Sources\ESD" is attached to what it calls the Path in that log. There were other errors in the log preceding this, like three "providers" couldn't load. Also, there was this which appeared twice, but I don't know what file it refers to... [988] [0x80070002] FIOReadFileIntoBuffer:(1452): The system cannot find the file specified. [988] [0xc142011c] UnmarshallImageHandleFromDirectory:(641) [988] [0xc142011c] WIMGetMountedImageHandle:(2906) I guess I can never recommend an offline DISM again. It's a pity. But thanks for the heads-up.

(1) Ramesh is right. The offline scan can't find Install.esd (or ...wim). His & mine will still run to a seemingly successful conclusion because we have a good WinSxS folder. You get a crash at the Command Prompt because you lack a good one (or maybe even that can't be accessed in your current state). (2) I see Ramesh is locating the files SFC complained of. I hope putting them into the right folders will get the offline SFC to work & that it will achieve a successful boot. (3) If all fails, you can use your Win 10 Installation USB to do a clean install. If you make it a UEFI install, it will give you your missing EFI partition. UEFI is better than Legacy. Good luck. I'll be watching & hoping for the best.

SFC log says these drivers are missing. Cannot repair member file [l:15]'BasicRender.sys' of dual_basicrender.inf, version 10.0.19041.2006 Cannot repair member file [l:11]'BthMini.SYS' of dual_bth.inf, version 10.0.19041.2364 Cannot repair member file [l:10]'hidusb.sys' of dual_input.inf, version 10.0.19041.2251 Cannot repair member file [l:11]'WSDScan.sys' of dual_sti.inf, version 10.0.19041.1806 Cannot repair member file [l:12]'usbprint.sys' of dual_usbprint.inf, version 10.0.19041.2193 Cannot repair member file [l:10]'vmbusr.sys' of dual_wvmbusr.inf, version 10.0.19041.1466 Cannot repair member file [l:13]'xinputhid.sys' of dual_xinputhid.inf, version 10.0.19041.2311 Cannot repair member file [l:11]'mskssrv.sys' of Microsoft-Windows-KernelStreaming, version 10.0.19041.2364 Cannot repair member file [l:10]'wdmaud.drv' of Microsoft-Windows-Audio-MMECore-WDM-Audio, version 10.0.19041.1 C:\Windows\System32\Drivers\mskssrv.sys C:\Windows\System32\Drivers\netbt.sys C:\Windows\System32\Drivers\pacer.sys C:\Windows\System32\Drivers\msquic.sys Official Microsoft Download Links Set 1: BasicRender.sys [ Download ] 10.0.19041.2006 BthMini.sys [ Download ] 10.0.19041.2364 HidUsb.sys [ Download ] 10.0.19041.2251 (Skipped the other items for now) Set 2: C:\Windows\System32\Drivers\mskssrv.sys [ Download ] - 10.0.19041.2364 C:\Windows\System32\Drivers\netbt.sys [ Download ] - 10.0.19041.572 C:\Windows\System32\Drivers\pacer.sys [ Download ] - 10.0.19041.546 C:\Windows\System32\Drivers\msquic.sys - [ Download ] - 10.0.19041.488 By default, the 1st set of items loads from the "\SystemRoot\System32\DriverStore\FileRepository<subfolder_####>" location. The 2nd set goes to the System\Drivers directory. But now I'd put them all in System32. The driver paths must be updated offline (for the 1st set of items) in the registry. (Ref: Offline registry edit )

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-30T03:45:32+00:00

So, I ran it offline & you are sadly right...

2022-12-29 19:18:48, Info DISM DISM.EXE: Executing command line: dism /Image:C:\ /Cleanup-Image /RestoreHealth /Source:ESD:E:\Sources\install.esd:1 /ScratchDir=C:\BU\temp /logpath:c:\BU\dism.log

2022-12-29 19:19:11, Info CBS Session: 596_442125 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null)

2022-12-29 19:19:11, Info CBS Exec: Addsource called, Session: 596_442125, Client: DISM Package Manager Provider, from GPO: No, Path: X:\Sources\ESD:E:\Sources\install.esd:1

2022-12-29 19:19:11, Warning CBS The alternate source path directory could not be accessed [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]

2022-12-29 19:19:11, Info CBS Failed to add new file source [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]

2022-12-29 19:19:11, Info CBS Failed to add alternate file source [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]

2022-12-29 19:19:11, Info CBS Failed adding alternate source directory [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]

2022-12-29 19:19:11, Warning DISM DISM Package Manager: PID=596 TID=1240 CBS AddSource failed with HRESULT=0x80070003! - CDISMPackageManager::Internal_Finalize

It looks like the DISM command is entered correctly going by what I see at TenForums & elsewhere. I don't know why "X:\Sources\ESD" is attached to what it calls the Path in that log. There were other errors in the log preceding this, like three "providers" couldn't load. Also, there was this which appeared twice, but I don't know what file it refers to...

[988] [0x80070002] FIOReadFileIntoBuffer:(1452): The system cannot find the file specified.

[988] [0xc142011c] UnmarshallImageHandleFromDirectory:(641)

[988] [0xc142011c] WIMGetMountedImageHandle:(2906)

I guess I can never recommend an offline DISM again. It's a pity. But thanks for the heads-up.
Was this answer helpful?

0 comments No comments
Anonymous

2022-12-30T03:18:22+00:00

(1) Ramesh is right. The offline scan can't find Install.esd (or ...wim). His & mine will still run to a seemingly successful conclusion because we have a good WinSxS folder. You get a crash at the Command Prompt because you lack a good one (or maybe even that can't be accessed in your current state).

(2) I see Ramesh is locating the files SFC complained of. I hope putting them into the right folders will get the offline SFC to work & that it will achieve a successful boot.

(3) If all fails, you can use your Win 10 Installation USB to do a clean install. If you make it a UEFI install, it will give you your missing EFI partition. UEFI is better than Legacy.

Good luck. I'll be watching & hoping for the best.
Was this answer helpful?

0 comments No comments
Ramesh 181.6K Reputation points Volunteer Moderator

2022-12-30T02:14:35+00:00
SFC log says these drivers are missing.

Cannot repair member file [l:15]'BasicRender.sys' of dual_basicrender.inf, version 10.0.19041.2006

Cannot repair member file [l:11]'BthMini.SYS' of dual_bth.inf, version 10.0.19041.2364

Cannot repair member file [l:10]'hidusb.sys' of dual_input.inf, version 10.0.19041.2251

Cannot repair member file [l:11]'WSDScan.sys' of dual_sti.inf, version 10.0.19041.1806

Cannot repair member file [l:12]'usbprint.sys' of dual_usbprint.inf, version 10.0.19041.2193

Cannot repair member file [l:10]'vmbusr.sys' of dual_wvmbusr.inf, version 10.0.19041.1466

Cannot repair member file [l:13]'xinputhid.sys' of dual_xinputhid.inf, version 10.0.19041.2311

Cannot repair member file [l:11]'mskssrv.sys' of Microsoft-Windows-KernelStreaming, version 10.0.19041.2364

Cannot repair member file [l:10]'wdmaud.drv' of Microsoft-Windows-Audio-MMECore-WDM-Audio, version 10.0.19041.1

C:\Windows\System32\Drivers\mskssrv.sys

C:\Windows\System32\Drivers\netbt.sys

C:\Windows\System32\Drivers\pacer.sys

C:\Windows\System32\Drivers\msquic.sys

Official Microsoft Download Links

Set 1:
- BasicRender.sys [Download] 10.0.19041.2006
- BthMini.sys [Download] 10.0.19041.2364
- HidUsb.sys [Download] 10.0.19041.2251
(Skipped the other items for now)

Set 2:
- C:\Windows\System32\Drivers\mskssrv.sys [Download] - 10.0.19041.2364
- C:\Windows\System32\Drivers\netbt.sys [Download] - 10.0.19041.572
- C:\Windows\System32\Drivers\pacer.sys [Download] - 10.0.19041.546
- C:\Windows\System32\Drivers\msquic.sys - [Download] - 10.0.19041.488
By default, the 1st set of items loads from the "\SystemRoot\System32\DriverStore\FileRepository<subfolder_####>" location. The 2nd set goes to the System\Drivers directory.

But now I'd put them all in System32. The driver paths must be updated offline (for the 1st set of items) in the registry. (Ref: Offline registry edit)
Was this answer helpful?

0 comments No comments