Newby here.
Just thought I'd confirm in our household, three X64 machines don't have the problem.
After stuffing accesschk.exe in to windows directory and running the batch file, three X86 machines give a success message from the batch file but still fail creating a system image with the RPC 0x800706BA error.
Welome to TenForums @Gordonp and thank you for the confirmation.
Yes - x64 has no problems that I've seen and none have been reported elsewhere. So far all the x86 installs of 1803 that I've done have the RPC error, and all reports I've seen for this error on the web are for the x86 version.
Even booting to advanced startup from the 32-bit 1803 install media and trying to restore an image fails with an RPC error.
Hello Bree,
From SimonFastEddy
Here we are again! I can confirm the same problem on a Dell GX620 running Windows 10 Pro v1803 -32 bit.
On a pair of Dells (760 and 755) running Windows 10 Pro v1803 -64 bit, all is fine.
The Windows 10 system imaging software fails but Macrium Reflect 7 is capable on the 32 bit machine.
I am also getting System Restore failing with 0x80070005 "AppxStaging" again.
Days wasted!
Nice to see you are around.
Simon.
Hi,
I use the winpe recovery cd/ flash media to do system images
Usually end up using it to recovery anyway so might as well get used to using it plus it's faster :)
Hello Bree
From SimonFastEddy
You are correct.
I tried the "rlattling" method but started with a W10 v1709 image as a source of wbengine. With the usual dance around with permissions I copied it into a W10 v1803 image with the v1803 wbengine renamed and Restarted.
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.
Bree, you are correct it is the recovery environment that is on the MCT that has issues.
W10 v1803 is a mess:
Windows Live Mail corrupted but resolved
AppxStaging back
RPC error
Network Explorer turned off but resolved.
Spotlight inert, had to be resolved with the fixes available.
Don't any of the graduates at Microsoft check their work... or are they" I'm Bloody Marvelous (IBM)" I don't ever make mistakes? I am not a software expert; I'm a microbiologist and I checked their work.
Thanks Bree... You are confirmed a Guru
Thank you for your kind words @SimonFastEddy. Yes, I get the impression that MS had painted themselves into a corner by deciding to call this the 'April 2018 Update' and felt constrained to get something out before the last day of April had come and gone.
It feels like it was a few cumulative updates away from being 'release-ready'. Today's 'Patch Tuesday', let's see what that brings...
PS: re Spotlight - I turned it on for my 32-bit 1803 system. It took about 24 hours before it started to work, but it seems reliable now it's going.
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 command prompt after booting with a 1709 install or recovery USB.
startnet
ipconfig (to verify IP)
net use {\\NetworkAddress} user:UserName {Password}
wbadmin get versions -backuptarget:{Network address of folder containing WindowsImageBackup} -machine:{Computer name}
(the version identifier is in the form 'M/D/YYYY-HH:MM')
wbadmin start sysrecovery -version:M/D/YYYY-HH:MM -backuptarget:{\\NetworkAddress} -machine:{Computer name} -recreateDisks -restoreAllVolumes
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
Quote
