WIndows 2016 DISM Offline Repair

This article is for Windows 10, the link notes that. "The install.wim file must be of the same version, edition as well as language of the operating system you are using."



https://www.backup-utility.com/windows-10/dism-offline-repair-windows-10.html

To you, an offline repair means what?
Is windows booted but just no internet access, or are you trying the repair from a command prompt of windows PE?

Windows will not boot and in Windows PE

when I try to run sfc in offline mode I keep getting the message " Windows Resource Protection could not preform the requested operation."

Please note, I have run chkdsk on the volume twice, including mounting the vmdk on and other VM and had the same result

Could it be that your setup disk that you use for repairs has a lower patch level than your current windows installation?
Please retry with a disk that you have updated to the same level as your OS using commands following this tutorial:
http://woshub.com/integrate-windows-updates-into-windows-8-image/

Then use this command in windows PE:

DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:e:\sources\install.wim

Select allOpen in new window

(it works here that way)

When I run the command you listed, I get the error: The Cleanup-image option is unknown. Please note, I was careful on the case of the syntax

Some browsers misinterpret hyphens ("-"). Please type the hyphen manually and not via copy and paste.

I did type it out... no luck

Ok, please try this: start your unbootable machine 3 times. After it fails to start for 3 times, it will offer to go to recovery options. There, select troubleshooting ->command line. On that command line, you should get a dism that knows the option "cleanup-image".

did that same result

May I ask you for a screenshot of that?

If I had a server 2016 test VM, I would try to reproduce it right away...but I haven't.
Let me do this tomorrow.

Thanks your help. I ended up rebuilding the server and mounting the old VMDK to pull what data we could off of it. I believe the problem stemmed from the old VMDK drive being corrupted.