ThetaSigma

Alright, I downloaded the latest Windows_Server_2016_Datacenter_EVAL_en-us_14393_refresh.iso and attempted to do an offline repair using the install.wim file as source. Similar failures as before. dism_offline.log sfcoffline.txt Edit: from what I can see, "amd64_microsoft-windows-utilman_31bf3856ad364e35_10.0.14393.0_none_301e1b6a47eff339\Utilman.exe" is listed as corrupt by DISM. Is there a way I can get a fresh copy for Server 2016?

Okay thanks. As I said in the OP I have previously tried using offline repair tools, but I can try again in case I missed something before. I know in the past DISM and SFC were broken, but as far as I'm aware in 1607 it isn't supposed to be an issue.

I'll look into it, previously I've used DISM GUI 4.0 to mount WIMs but it's a bit wonky sometimes. Would a fresh install of Windows 10 be better than using a recovery image to commit offline repairs?

That was likely the update I scheduled. It happens regardless of the base GM or updates. The Hyper-V client I'm using for diagnostics is still being updated. I used the EVAL install.wim as my offline source and the problem still persists. Thanks for the quick replies!

My workplace has recently upgraded to Server 2016 (build 1607) via deployment manager installer taken from a Golden Image. As such I don't have (but did request) an installer ISO. While the server OS is functional, we had a recent major crash that ended up with me finding these failures. Currently, our main servers are running with these errors and I don't know of a way to diagnose further until these issues are resolved. I am now working on a Hyper-V image to resolve this. To the issue(s): DISM /Online /Cleanup-Image /RestoreHealth and SFC /Scannow fail in both online and offline scenarios. DISM (Powershell initiated) cites:The source files could not be found. I have tried an offline WIM as source, and removed all group policies that disable looking at Windows Update for the files. SFC (Powershell initiated) cites: Windows Resource Protection found corrupt files but was unable to fix some of them. I have tried this on Windows PE offline repair and it has the same result. I will include the CBS and DISM logs with the most recent attempts. I have more experience diagnosing UNIX logs so more trained eyes on this can hopefully tell me what I'm missing / what to do. I really appreciate any help I can get! CBS.txt dism.log

Just give it time, the servers are being overloaded with the requests and returns.

LTT forum name should be ThetaSigma (not ThetaSigma312). Both the same here and in FAH. Been a while since I signed in...