Boot to recovery media
Select keyboard layout
Select Troubleshoot
Advanced options
Command prompt
Since you already have a copy of 1709's wbengine.exe in the System32 folder, I'll assume it's...
Type: Posts; User: rlatting
Boot to recovery media
Select keyboard layout
Select Troubleshoot
Advanced options
Command prompt
Since you already have a copy of 1709's wbengine.exe in the System32 folder, I'll assume it's...
Boot from the recovery/installation media and use the command prompt.
The nice thing about wbadmin is that it can find all those backup sets that sysrestore can't. Apparently it doesn't care about MediaID.bin.
wbadmin | Microsoft Docs
Also see: wbadmin get items
I could be wrong but my impression is that RPC can't talk to 1803's wbengine.exe, the RPC "server" that's not available. But it CAN talk to 1709.
For restoring from a NAS i use wbadmin from the...
Done.
Inside of sources\boot.wim on the 1803 x86 repair disc is Windows\System32\wbengine.exe version 10.0.17134.1, the same version that fails while making a system image. I think it's safe to assume it's...
My point is that it has little to do with the RPC server. The RPC server could not contact wbengine.exe.At least not the 1803 version. I have install media and repair discs for 1709 so I'd say the...
I was on the phone with MS for over 3 hours trying to figure out this problem (32-bit System Image backup failure). The solution was "wait for an update that fixes it."
Instead i retrieved the...