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 used install.wim (integrated using NTLite). It surely completed 100%. However, in the DISM log, I could see that the WIM was skipped. Can you check your logs to see if the ESD was bypassed/ignored? Look for errors such as: FIOReadFileIntoBuffer:(1456): The system cannot find the file specified. HRESULT = 0x8007007b (And yes, the drive letters are correct, as I can copy and retrieve other files on my USB drive while in WinRE.) However, DISM completed 100% (without any errors in the console window) because the component store on my computer is healthy.

What Install.wim did you use? Is it the same as his? And you got that same error message he did -- where it seemed to run to 100% but then said it couldn't find the files? I'm thinking he used one that may have been tailored to his NTLite USB drive. At least, D: is labeled that way. And F: has the wrong file system (though I'm not sure that matters for this purpose). I'd like for him use a Win 10 Installation USB flash drive made by the Media Creation Tool. I do know, in a thread a while ago, I did run an offline DISM using Install.esd just to see whether it would work. It ran to completion without giving that 0x800f081f error. Unfortunately, I didn't look inside DISM.log to see whether it bypassed the ESD & only used WinSxS. But there was no error message outside of it. Here is the result pulled from that thread... X:\Sources> DiskPart Microsoft DiskPart version 10.0.19041.964 Copyright (C) Microsoft Corporation. On computer: MININT-OP0NSSM DISKPART> List Vol Volume ### Ltr Label Fs Type Size Status Info Volume 0 E DVD-ROM 0 B No Media Volume 1 C PCR Hard NTFS Partition 930 GB Healthy Volume 2 ESP FAT32 Partition 99 MB Healthy Hidden Volume 3 WinRE 21H2 NTFS Partition 847 MB Healthy Hidden Volume 4 D ESDUSB-21H2 FAT32 Removable 14 GB Healthy DISKPART> Exit Leaving DiskPart... X:\Sources>:1 DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:ESD:D:\Sources\Install.esd Deployment Image Servicing and Management tool Version: 10.0.19041.746 Image Version: 10.0.19044.1826 The scratch directory size might be insufficient to perform this operation. This can cause unexpected behavior. Use the /ScratchDir option to point to a folder with sufficient scratch space. The recommended size is at least 1024 MB. [==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully. X:\Sources> SFC /Scannow /Offbootdir=c:\ /Offwindir=C:\Windows Beginning system scan. This process will take some time. Windows Resource Protection found corrupt files and successfully repaired them. For online repairs, details are included in the CBS log file located at windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline repairs, details are included in the log file provided by the /OFFLOGFILE flag. X:\Sources>

Thanks, PCR. I have another update. The same error (ERROR_NOT_FOUND) occurred when running DISM Restorehealth (with either the WIM or mounted WIM as the source, regardless of its location/drive) on my otherwise perfectly working PC. It's not the USB drive or the WIM image either. However, if the required files are in the built-in Component Store (C:\Windows\WinSxS), DISM uses it correctly. I mean, the other aspects of DISM work correctly, except the mount WIM/Source part.

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-29T07:08:16+00:00
I used install.wim (integrated using NTLite). It surely completed 100%. However, in the DISM log, I could see that the WIM was skipped. Can you check your logs to see if the ESD was bypassed/ignored?

Look for errors such as:
- FIOReadFileIntoBuffer:(1456): The system cannot find the file specified.
- HRESULT = 0x8007007b
(And yes, the drive letters are correct, as I can copy and retrieve other files on my USB drive while in WinRE.)

However, DISM completed 100% (without any errors in the console window) because the component store on my computer is healthy.
Was this answer helpful?

0 comments No comments
Anonymous

2022-12-29T06:30:38+00:00

What Install.wim did you use? Is it the same as his? And you got that same error message he did -- where it seemed to run to 100% but then said it couldn't find the files? I'm thinking he used one that may have been tailored to his NTLite USB drive. At least, D: is labeled that way. And F: has the wrong file system (though I'm not sure that matters for this purpose). I'd like for him use a Win 10 Installation USB flash drive made by the Media Creation Tool.

I do know, in a thread a while ago, I did run an offline DISM using Install.esd just to see whether it would work. It ran to completion without giving that 0x800f081f error. Unfortunately, I didn't look inside DISM.log to see whether it bypassed the ESD & only used WinSxS. But there was no error message outside of it. Here is the result pulled from that thread...

X:\Sources>DiskPart

Microsoft DiskPart version 10.0.19041.964

Copyright (C) Microsoft Corporation.

On computer: MININT-OP0NSSM

DISKPART> List Vol

Volume ### Ltr Label Fs Type Size Status Info

Volume 0 E DVD-ROM 0 B No Media

Volume 1 C PCR Hard NTFS Partition 930 GB Healthy

Volume 2 ESP FAT32 Partition 99 MB Healthy Hidden

Volume 3 WinRE 21H2 NTFS Partition 847 MB Healthy Hidden

Volume 4 D ESDUSB-21H2 FAT32 Removable 14 GB Healthy

DISKPART> Exit

Leaving DiskPart...

X:\Sources>:1 DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:ESD:D:\Sources\Install.esd

Deployment Image Servicing and Management tool

Version: 10.0.19041.746

Image Version: 10.0.19044.1826

The scratch directory size might be insufficient to perform this operation. This can cause unexpected behavior.

Use the /ScratchDir option to point to a folder with sufficient scratch space. The recommended size is at least 1024 MB.

[==========================100.0%==========================] The restore operation completed successfully.

The operation completed successfully.

X:\Sources>SFC /Scannow /Offbootdir=c:\ /Offwindir=C:\Windows

Beginning system scan. This process will take some time.

Windows Resource Protection found corrupt files and successfully repaired them.

For online repairs, details are included in the CBS log file located at

windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline

repairs, details are included in the log file provided by the /OFFLOGFILE flag.

X:\Sources>
Was this answer helpful?

0 comments No comments
Ramesh 181.6K Reputation points Volunteer Moderator

2022-12-29T05:25:22+00:00

Thanks, PCR. I have another update.

The same error (ERROR_NOT_FOUND) occurred when running DISM Restorehealth (with either the WIM or mounted WIM as the source, regardless of its location/drive) on my otherwise perfectly working PC. It's not the USB drive or the WIM image either.

However, if the required files are in the built-in Component Store (C:\Windows\WinSxS), DISM uses it correctly. I mean, the other aspects of DISM work correctly, except the mount WIM/Source part.
Was this answer helpful?

0 comments No comments