This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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:
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.
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.
(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.
I also checked my files and registry for version information:
C:\Windows\System32>dir /od c:\windows\winsxs\amd64_microsoft-windows-servicingstack_31b*
Volume in drive C has no label.
Volume Serial Number is 5092-80BF
Directory of c:\windows\winsxs
12/07/2019 01:31 AM <DIR> amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1_none_bf506ecc66a800df
08/24/2021 01:20 PM <DIR> amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1161_none_7e3076a27c733477
09/23/2021 06:13 PM <DIR> amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1220_none_7e21bc567c7ed16b
11/15/2021 12:07 PM <DIR> amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1310_none_7e15ec207c87d405
12/28/2021 05:17 PM <DIR> amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1371_none_7e1bd7147c8285b0
04/16/2022 02:39 PM <DIR> amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1613_none_7df538047ca074bb
06/09/2022 10:10 AM <DIR> amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1704_none_7de951067ca990f6
06/16/2022 07:44 AM <DIR> amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1737_none_7dec0d8c7ca729de
08/19/2022 06:59 AM <DIR> amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858
09/14/2022 12:36 PM <DIR> amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1940_none_7dd80d767cb5c7b0
12/15/2022 12:19 PM <DIR> amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.2300_none_7e14edbc7c88b7d5
0 File(s) 0 bytes
11 Dir(s) 110,740,889,600 bytes free
C:\Windows\System32>
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version
10.0.19041.2300
%SystemRoot%\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.2300_none_7e14edbc7c88b7d5
So this seems consistent. If only we could get dism to run...
I did as suggested. Here's what happened. Note that Dism.exe and DismApi.dll were not replaced. I tried copying those two files from my work laptop which is also Version 10.0.19045.2364 (I think) but the files are the same. Note that running dism from the X: drive, which is built using the latest ISO, does run, but shows an older version number.
Maybe I just need those two files from your 19045 installation?
C:\Windows\System32>dir dism*
Volume in drive C has no label.
Volume Serial Number is 5092-80BF
Directory of C:\Windows\System32
12/25/2022 08:49 AM <DIR> Dism
03/11/2021 08:50 AM 288,048 Dism.exe
12/15/2022 12:57 PM <DIR> Dism.old
03/11/2021 08:50 AM 1,068,368 DismApi.dll
2 File(s) 1,356,416 bytes
2 Dir(s) 110,737,620,992 bytes free
C:\Windows\System32>dism /image:C:\ /cleanup-image /restorehealth /source:D:\sources\install.wim /scratchdir:C:\temp
Deployment Image Servicing and Management tool
Version: 10.0.19041.844
Error: 193
An error occurred. DISM could not be initialized in the local folder.
Ensure that DISM is installed correctly and that all of the binaries are present.
C:\Windows\System32>
X:\sources>dism /?
Deployment Image Servicing and Management tool
Version: 10.0.19041.1949
The DISM modules are corrupt, and the operation fails with the error 0x800700c1 ("ERROR_BAD_EXE_FORMAT").
* * *
2022-12-24 13:36:31, Info DISM PID=1580 TID=1584 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadLocalImageSession
2022-12-24 13:36:31, Error DISM PID=1580 TID=1584 Failed to create the local image session. - CDISMManager::GetLocalProviderStore(hr:0x800700c1)
* * *
I've uploaded the modules here (Download dism.zip) from a 19045.2364 system. Unzip and copy the folder to your USB drive.
Boot from the USB drive on the subject computer. Using Command Prompt, rename C:\Windows\System32\Dism to Dism.old. Copy the DISM folder contents from the USB drive to C:\Windows\System32\DISM.
The commands would be:
(Where D:\ is your USB drive and C:\ is your Windows partition.)