New
#51
Version 1809 is due in October. As this problem has now been addressed in recent Insider versions, I would be surprised and disappointed if it were not fixed in that release.
In the mean time, there are workarounds....
Creating a system image works after replacing the 32-bit 1803's version of wbengine.exe with one from another version, the 32-bit 1709 is the usual choice.
Restoring a system image works when booting from a recovery drive made by 1709 or any earlier version.
However, Microsoft's System Image Backup (SIB) has been a deprecated feature for a year now. It looks like it will still be in 1809, but it can only be a matter of time before it is removed.
Features removed or Deprecated in Windows 10 Fall Creators UpdateMicrosoft said:
The 'other vendor' I use successfully in 32-bit 1803 is Macrium.
Tested now that the Windows 10 October 2018 Update now available - Windows 10 Forums.
Both creating a system image and restoring one work correctly in the 32-bit version 1809, build 17763.1.
Hello Bree,
There are problems with Windows 10 v 1803 32-bit but the 64-bit is mostly OK, as we know.
I've been trying "RollBackRx Home" by Horizon DataSys: it does snapshots and matches system restore's functions. It lacks a mouse pointer in the Home Recovery (boot and dab Home key to access the splash screen) so it gets stuck in it's mini-OS outside of Windows frequently. It hangs and crashes like a stock-car racer. The only way to use this alternative software is to install it, use at and uninstall it before closing down the PC.
It occurred to me that it could be a Windows 10 issue and not a RollBackRx Home problem. Possibly Microsoft is losing interest and scrapping the 32-bit versions in due course.
Thanks for the news about Windows Update but KB4464218 is trying to re-download and install itself on the 32-bit PC like the random jack-ass that it is. If you need a toy to play with, try Reset Windows Update Agent to augment M$'s Windows 10. Loads of fun.
From SimonFastEddy
Yes, I tested both backup and restore in the public release of 1809 and reported success in this thread on 3rd October. There is still no fix for 1803 though, so I won't be marking this thread as solved.
Come to that, there's no publicly available 1809 now either, not until MS fix the bug that caused them to withdraw it.
Edit: fixed now and 1809 has been re-released.
Last edited by Bree; 06 Dec 2018 at 14:37.
For a feature that was deprecated two years ago the built-in system imaging has had a remarkably long stay of execution. As it is still included in 1903 it's only fair to test it.
I can confirm that in the 32-bit version of 1903 both system image backup and restore work correctly.
Hello Bree, (From SimonFastEddy)
Individual systems may still cause issues: on 16 Jan 2019, I installed W10 v1809 (32-Bit) and had the AppxStaging error return - Error 0x800705aa. It took me until 17 March 2019 before I resolved it. In the interim I had stripped-out everything from Windows 10 with the exception of the Windows Store and Microsoft Edge, to no effect. I increased the space allocated to System Protection and did an in situ Windows v1809 Upgrade downloaded and installed, and that resolved the issue.
All OK now! System configuration all wrong I expect.
If anyone gets stuck similarly and needs a restore program then I suggest using RollBackRxHome until the problem resolves.
I am currently waiting for W10 v1903 to behave suitably and not re-assign a drive letter for my USB stick which I often leave plugged-in during the installation process. It messes with my syncBackFree profiles!
All hail Macrium... All hail Powershell... All hail Horizon Data Systems...
God give me strength, a fast bike, an open road and sunshine. Keep well Bree, it's good that you are around.
From SimonFastEddy