System Restore fails: AppxStaging %ProgramFiles%\WindowsApp 0x80070091

Bree said:

...could this be the one?

Apparently not...

Thank you for checking. :)

Bree said:

Apparently not...

dencal,
Scannow and dism will both run and report no problems, however System Restore will still fail to complete. Very early in the piece the MS crew were offering these as suggested paths to problem identification but it pretty quickly became evident that the use of these instruments was of no value whatsoever in relation to this problem.

I know the WindowsApps Rename Method works, but without getting rid of the Get Office app, soon as it updates your right back to a broken System Restore. Doesn't really surprise me tho, that there is no mention of this on M$ Community Forum :)

There is a bit of discussion about the whole problem over in the Community pages. I've mentioned the finer details but it doesn't go far from that. Just doing the WindowsApps rename is the preferred stop-gap method so knowing about the actual cause doesn't seem to count much. It appears that there are lots of people who just visit the community and are capable of fixing it by themselves using the instructions given. There are also a few who are too timid or unsure of their own level of ability to have a go, which is fair enough.

Around the internet there is still some opinion that the Cumulative Update caused it even though it didn't. The similar timing is purely coincidental.

On March 19, I used the 'fix' mentioned in ms forum community on one of our devices in the network. Did not work and returned a new error. Reinstalled the image I created before trying the fix. I will wait for ms to fix at their convenience!!

It was possibly the error about the Restore Point being damaged or deleted. It is still the Appxstaging issue but with the Source and Destination reversed which is easily missed. The error pop up Window looks very similar but without the number 0x80070091 error code. I did encounter this problem as well during testing and did what you did, ie; Restore from an image.

So far as I've seen there is no suggested fix for this one yet, but it is the reverse end of the same problem. What I did notice when this happened to me was that System Restore went reading from an External Hard disk for some reason.

Seems 'Get Office' app causing more than just System Restore issues. I just did a Reset Everything on Win10 Pro x64 and sure enough, got the warning.

https://answers.microsoft.com/en-us/...8-c198651cb717

The Get Office App is nothing short of forced Adware. Considering the damage it is doing we might even be tempted to call it full malware. If it wasn't by MS and part of the O/S it would be targeted by every malware removal tool in existence.

The actual differences between Office versions over the last 15 years or so have been mostly cosmetic. There is very little I want to do with Office 2016 that I couldn't do on 2010, 2007 or right back to 2003 and even before that. More often than not, with each new release it was just a nuisance to have to adapt to a new user interface in order to perform the exact same functions.

The new model for this Office 365 is the same thing that Adobe did with CS. Basically they are all saying now that we aren't allowed to purchase and own a licenced copy of the program and use it within the rules of a licence agreement. By making it a user pays subscription service we have to keep paying.

Fortunately, at the moment, even Office 2010 will install and run in Windows 10. As for how long they allow these "owned" versions to keep running is anybody's guess.

Any word from Microsoft?