1803 creating a system image fails with RPC server error 0x800706BA

SimonFastEddy said:

Hello Bree
From SimonFastEddy
Although an image does save without RPC server unavailable there is no way to re-install an image either with W10 v1709 or W10 v1803 installation discs.

I can recover an image created using 1709 version of wbengine with a 1709 recovery disk. Yes a 1803 recovery disk gives me a RPC error but a 1709 recovery disk works fine ?

Hello Bree
From Simon (FastEddy)

Thanks for the "re:Spotlight" message posted
Some things in 1803 work after a bit of juggling...

There are fixes for Spotlight Lock Screen going inert if you still get stuck:
There is a fix for Windows Live Mail displaying poorly, if you like to keep it as a backup.

Link for Spotlight fix: How to fix Windows Spotlight Lock screen errors | Windows Central

RPC again: TenForums is revealing an inconsistency in the behavior of the software. The installation discs don't work but the recovery discs seem to work. Is there any merit in investing more time in finding a resolution? Sporadic performance is a nightmare.

Thanks from Simon

Hello Bree (From SimonFastEddy)

Thanks for the news.
While we were away: I did a bit of work on WindowsApps. Basic work: getting permissions for the contents of the folder "WindowsApps" and deleting them. I was left with Skype and a language pack. I uninstalled Skype and retested to see if there was a (assumed to be) broken file remaining. I still had the AppxStaging error. Last year we reasoned it was "GetOffice" but I am not sure now. We need a magazine petition or the source code.

I need to do some road cycling; I've modified a pair of LUCK carbon soled road-race shoe to change them from 3-bolt cleats to SPD cleats and put a solid heel on them. Milling and turning with silver soldering; project a success again, done it before!. I can't stand single sided pedals in town. So - I will go missing it will seem but: "I will be back".

We don't always get the manufactured product we want.

Keep the faith...Simon

" .....Instead i retrieved the 1709 version of wbengine.exe from the 32-bit installation media and used the recovery command prompt to rename the 1803 version and insert the previous version in its place. System image backup works fine once again.[/QUOTE]

This sounds as the best (and only) advice. Only my problem is that I can't break thought the securities that forbid to rename or delete the 1803 version of wbengine.exe.
Please, can somebody explain how to work around the innate filelimitations (I can't change them as normal in "properties")

Boot from the recovery/installation media and use the command prompt.

rlatting said:

Boot from the recovery/installation media and use the command prompt.

My Dos knowledge is a bit gone. I copied the wbenging.exe (version 1709) under another name in system32, and now I will use the prompt to rename the existing exe, and than rename the 1709 version to wbenging.exe. I think I still can do that ;-)

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 named wbengine.1709.exe

cd /d C:\Windows\System32
rename wbengine.exe wbengine.1803.exe
rename wbengine.1709.exe wbengine.exe

Reboot
Try an image backup

Thanks, rlatting, so i can use copy-paste in stead of trial and error