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: Most helpful
Most helpful Newest Oldest
  1. Ramesh 181.6K Reputation points Volunteer Moderator
    2022-12-29T18:24:01+00:00

    Yeah. And I checked the list of missing subfolders/DLLs in WinSxS (reported in the DISM log). None of them were in the component store of a Windows 10 22H2 computer. So even if DISM ran, it wouldn't find the manifests and DLLs (the version DISM expects) from the 22H2 ISO. I think you have to try the other methods -- uninstalling the update using DISM or copying the missing files to USB and then to Windows\System32, or Dism /RevertPendingActions.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-12-29T18:15:06+00:00

    I created a new USB with the Media tool which now has D:\Sources\install.esd. I basically got the same results:

    Microsoft Windows [Version 10.0.19041.2006] (c) Microsoft Corporation. All rights reserved.

    X:\Sources>diskpart

Microsoft DiskPart version 10.0.19041.964

Copyright (C) Microsoft Corporation.
On computer: MININT-FLRVJ2I

DISKPART> list vol

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     C                NTFS   Partition    476 GB  Healthy
  Volume 1     E                NTFS   Partition    853 MB  Healthy    Hidden
  Volume 2     D   ESD-USB      FAT32  Removable     28 GB  Healthy

X:\Sources>dism /Get-WimInfo /WimFile:D:\Sources\install.esd

Deployment Image Servicing and Management tool
Version: 10.0.19041.1949

Details for image : D:\Sources\install.esd

Index : 1
Name : Windows 10 Home
Description : Windows 10 Home
Size : 15,098,360,792 bytes

Index : 2
Name : Windows 10 Home N
Description : Windows 10 Home N
Size : 14,326,729,982 bytes

Index : 3
Name : Windows 10 Home Single Language
Description : Windows 10 Home Single Language
Size : 15,101,147,257 bytes

Index : 4
Name : Windows 10 Education
Description : Windows 10 Education
Size : 15,438,612,142 bytes

Index : 5
Name : Windows 10 Education N
Description : Windows 10 Education N
Size : 14,676,047,995 bytes

Index : 6
Name : Windows 10 Pro
Description : Windows 10 Pro
Size : 15,435,570,649 bytes

Index : 7
Name : Windows 10 Pro N
Description : Windows 10 Pro N
Size : 14,673,174,575 bytes

The operation completed successfully.

X:\Sources>dism /Image:C:\ /Cleanup-Image /RestoreHealth /Source:ESD:D:\Sources\install.esd:6 /ScratchDir=C:\temp /logpath:c:\dism.log

Deployment Image Servicing and Management tool
Version: 10.0.19041.1949

Image Version: 10.0.19045.2364

[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at c:\dism.log

X:\Sources>

    Here are some of the errors from the dism log file. There are 600+ lines of similar errors:

    2022-12-29 12:02:29, Error CSI 00000008 (F) CertCreateCTLContext returned ERROR_INVALID_DATA.

    2022-12-29 12:02:29, Error CSI 00000009@2022/12/29:20:02:29.240 (F) Attempting to mark store corrupt with category [l:14 ml:15]'CorruptCatalog'[gle=0x80004005]

    2022-12-29 12:02:29, Error CSI 0000000a@2022/12/29:20:02:29.240 (F) onecore\base\wcp\componentstore\corruptionrepair.cpp(71): Store corruption detected in function `anonymous-namespace'::VerifyManifestAgainstCatalog expression: 0

    2022-12-29 12:02:30, Error CSI 0000004f (F) CertCreateCTLContext returned ERROR_INVALID_DATA.

    2022-12-29 12:02:30, Error CSI 00000050@2022/12/29:20:02:30.787 (F) Attempting to mark store corrupt with category [l:14 ml:15]'CorruptCatalog'[gle=0x80004005]

    2022-12-29 12:02:30, Error CSI 00000051@2022/12/29:20:02:30.787 (F) onecore\base\wcp\componentstore\corruptionrepair.cpp(71): Store corruption detected in function `anonymous-namespace'::VerifyManifestAgainstCatalog expression: 0

    2022-12-29 12:02:44, Error CSI 000003d7@2022/12/29:20:02:44.772 (F) onecore\base\wcp\rtllib\win32lib\delta_library.cpp(287): Error NTSTATUS_FROM_WIN32(ERROR_INVALID_DATA) originated in function Windows::Rtl::DeltaDecompressBuffer expression: g_pfnApplyDeltaB(( (DELTA_FLAG_TYPE)0x00000000 ), ReferenceInput, CompressedInput, &UncompressedOutput)

    2022-12-29 12:02:44, Error CSI 000003d8 (F) Hydration failed with error NTSTATUS_FROM_WIN32(ERROR_INVALID_DATA) . Delta Type: Reverse Delta , IntegrityState Valid: true , RetrievedChecksum: 3507685353 , ComputedChecksum: 3507685353[gle=0x80004005]

    2022-12-29 12:02:44, Error CSI 000003d9 (F) Hydration failed for component dual_bthprint.inf, version 10.0.19041.1806, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, type [l:14]'dualModeDriver' on file bthprint.inf with NTSTATUS -1073283059. Matching Component = dual_bthprint.inf, version 10.0.19041.1806, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, type [l:14]'dualModeDriver'. FileHasForwardReverseDeltas = true[gle=0x80004005]

    2022-12-29 12:02:59, Error CSI 000003e0@2022/12/29:20:02:59.834 (F) onecore\base\wcp\rtllib\win32lib\delta_library.cpp(287): Error NTSTATUS_FROM_WIN32(ERROR_INVALID_DATA) originated in function Windows::Rtl::DeltaDecompressBuffer expression: g_pfnApplyDeltaB(( (DELTA_FLAG_TYPE)0x00000000 ), ReferenceInput, CompressedInput, &UncompressedOutput)

    2022-12-29 12:02:59, Error CSI 000003e1 (F) Hydration failed with error NTSTATUS_FROM_WIN32(ERROR_INVALID_DATA) . Delta Type: Reverse Delta , IntegrityState Valid: true , RetrievedChecksum: 4250705628 , ComputedChecksum: 4250705628[gle=0x80004005]

    2022-12-29 12:02:59, Error CSI 000003e2 (F) Hydration failed for component dual_pci.inf, version 10.0.19041.1949, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, type [l:14]'dualModeDriver' on file pci.inf with NTSTATUS -1073283059. Matching Component = dual_pci.inf, version 10.0.19041.1949, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, type [l:14]'dualModeDriver'. FileHasForwardReverseDeltas = true[gle=0x80004005]

    2022-12-29 12:06:06, Error CBS Failed to parse package manifest: \?\C:\Windows\Servicing\Packages\HyperV-HvSocket-Package~31bf3856ad364e35~amd64~~10.0.19041.1706.mum [HRESULT = 0x800f0900 - CBS_E_XML_PARSER_FAILURE]

    2022-12-29 12:06:06, Error CBS Failed to parse package manifest: \?\C:\Windows\Servicing\Packages\HyperV-IsolatedVM-SVC-Package~31bf3856ad364e35~amd64~~10.0.19041.1706.mum [HRESULT = 0x800f0900 - CBS_E_XML_PARSER_FAILURE]

    2022-12-29 12:06:06, Error CBS Failed to parse package manifest: \?\C:\Windows\Servicing\Packages\Microsoft-Hyper-V-Package-base-Package~31bf3856ad364e35~amd64~~10.0.19041.1682.mum [HRESULT = 0x800f0900 - CBS_E_XML_PARSER_FAILURE]

    2022-12-29 12:06:06, Error CBS Failed to parse package manifest: \?\C:\Windows\Servicing\Packages\Microsoft-OneCore-EventLogAPI-Package~31bf3856ad364e35~amd64~~10.0.19041.1682.mum [HRESULT = 0x800f0900 - CBS_E_XML_PARSER_FAILURE]

    2022-12-29 12:06:07, Error CBS Failed to parse package manifest: \?\C:\Windows\Servicing\Packages\Package_10_for_KB5005699~31bf3856ad364e35~amd64~~19041.1220.1.0.mum [HRESULT = 0x800f0900 - CBS_E_XML_PARSER_FAILURE]

    2022-12-29 12:06:07, Error CBS Failed to parse package manifest: \?\C:\Windows\Servicing\Packages\Package_10_for_KB5014035~31bf3856ad364e35~amd64~~19041.1737.1.2.mum [HRESULT = 0x800f0900 - CBS_E_XML_PARSER_FAILURE]

    Was this answer helpful?

    0 comments
  3. Ramesh 181.6K Reputation points Volunteer Moderator
    2022-12-29T09:30:01+00:00
    1. No. Because, as I stated, my WinSxS is healthy.
    2. Yes. The error codes are the same except for the file named (install.esd instead of install.wim)

    Was this answer helpful?

    0 comments