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.4K 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.4K Reputation points Volunteer Moderator
    2022-12-23T02:41:22+00:00

    Can you please upload the full log file and also the iorate.sys file? Let me see if we can manually copy those files from USB.

    Was this answer helpful?

    0 comments
  2. Ramesh 181.4K Reputation points Volunteer Moderator
    2022-12-23T02:22:44+00:00

    0x800700c1 means ERROR_BAD_EXE_FORMAT. The full error message might be:

    * * *

    There is a possible 32-bit versus 64-bit cross architecture issue with the provider (or one of its dependencies). - CDISMProviderStore::Internal_LoadProvider(hr:0x800700c1)

    * * *

    Can you try changing the prompt to C:\Windows\System32 by running the "cd /d c:\windows\system32" command and try running DISM again?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-12-22T23:40:30+00:00

    I really appreciate you trying to help. I must be cursed. I used Rufus to download the latest version and had it create a bootable USB. From that command prompt, I verified using bcdedit that my osdrive is C: so my command was:

    X:\sources> dism /image:C:\ /cleanup-image /restorehealth /source:D:\sources\install.wim /scratchdir:C:\temp

    Note: When the USB boots it's in X: and the install.wim does not exist under X:\sources. It does exist on the USB drive at D:\sources so that's what I used.

    It blew up. The dism log file has:

    2022-12-22 17:31:54, Error DISM DISM Proxy Image Session: PID=1304 TID=1308 Failed to get the provider store from the image session object. - CProxyImageSession::InitializePointers(hr:0x800700c1)

    2022-12-22 17:31:54, Error DISM DISM Manager: PID=1304 TID=1308 Failed to load the image session from the temporary location: C:\Temp\2A66A06F-918C-4051-A502-12DB478AEE0A - CDISMManager::CreateImageSession(hr:0x800700c1)

    2022-12-22 17:31:54, Error DISM DISM.EXE: Could not load the image session. HRESULT=800700C1

    2022-12-22 17:31:54, Error DISM DISM.EXE: Unable to start the servicing process for the image at 'C:'. HRESULT=800700C1

    What does it mean it cannot load the image session?

    Why aren't these !(@*&#(!* tools doing anything?

    Was this answer helpful?

    0 comments