I dont want to touch windowsapp but only its officehub related folders.
Doing that i should not harm the OS because i remove folders from an app that i just uninstalled and because i dont use office 365 in fact i use the old standard version of office.
1) i hope doing so to re-have RP working
2) i hope i didnt broke anything else
But there are only hopes.
I am a fresh full image so i could try.
I noticed that many of the metro apps (like Solitaire Collection & Sticky Notes) don't work any more. If I download & install the Solitaire Collection & use it, the Start Menu on my ClassicShellSetup doesn't work, unless I logoff & logon again.
So my "fix" may have created other problems. Do you think the upgrading to the CU would fix that?
Thanks again,
Phil
Its enough for me to avoid the fix and stay with anniversary waiting an official stable CU.
Also, doing all these images instead of use my beloved RP that i use from xp and now broken.
MS: very bad.
I'm looking at a W10 Home 64-bit system that apparently screwed up a user and their profile folder ("Can't log you into your account ..blah blah blah.... Temporary account " crap). It's not just the usual ProfileList key fixup. I've been working on it for a while now without success, so I decided to do a restore to a time when it apparently was working ok (i.e. pre an update several days ago). Restore "initializes" for about an hour, then informs me that it has failed with the AppxStaging --> ..\Windows Apps syndrome. I tried it several times on earlier restore points, with the same result!
I started reading this thread from the beginning, but before getting too bogged down in the details I thought I would ask if:
1. Is the renaming/etc of \Windows Apps a recommended method, or does it cause too many other side effects?
2. Has the procedure been encapsulated in a separate post anywhere, or do I comb it out of this thread?
Thanks, Roger
This problem is specific to 1607. If you have another version (like 1703) then it may not be relevant.
I have followed this thread as it grew, so can point you to a few highlights. There are mixed reports in this thread, a few had problems, others had none. For myself...
Post #263 in this threadAlthough I knew about it, I never used it myself. My first instinct is that while such fixes can work, there may be unintended consequences later on when Microsoft get round to an official fix. ... In my case the official Microsoft 'fix' turned out to be the upgrade to Creators Update :)
Upgrading to Creators is probably a step to far for you, so...
Post #70 is probably the closest to 'an encapsulation', but there's an alternative. The Get Office app has been identified as a cause, you could just try to delete that one app.2. Has the procedure been encapsulated in a separate post anywhere, or do I comb it out of this thread?
Post #141 (which also gives a concise summary of the findings so far)This has worked for me and is a bit simplier ... un-install the 'Get Office' app, if the following 2 folders don't get deleted from the 'WindowsApps' folder, YOU have to delete them before System Restore will work.
Bree, thank you very much. It is indeed 1607, so I'll pursue it. Your post pointers are much appreciated, and the news about the Get Office app is something I hadn't come across so far. I'll go to bed now, knowing that there is hope for tomorrow. :)
Bree, I've done a lot more reading today, including Eagle51's post #141. Like him, I discovered that a normal uninstall of Get Office did actually remove the two recalcitrant files with no further action by me. At that point it seems to me that I should be able to do a system restore from some earlier date..... except he says
Unfortunately, I didn't try creating a restore point there and then. What I did do was try and restore to an earlier time (about a week ago), but it's looking very much like it is not going to work ... SR has been "initializing" for 30 minutes already. So Eagle51 appears to be correct. But why? What am I missing? I thought that the reason SR was failing was because it was trying to restore to still-existing folders (i.e. folders that it had failed to remove).
Roger
Hey rlh99,
Yea, System Restore can take awhile. The potential issue with using a Previous Restore Point (before the fix) ... it could put back the Get Office App and those 2 folders. If it does, then System Restore would be broken again you would have to do the fix again.
Hello Eagle51.
Yes, I totally understand, and agree... and in fact that's (partially) what it did, and what I expected.
Here was the situation at the time I became involved:
A user was suddenly (but it was ok yesterday...) unable to log in.
After looking at the usual causes, I decided to do a restore to a time a few days before the problem arose. The restore failed, and I ended up at this thread.
After reading your post #141 I decided to try a simple uninstall of Get Office before mucking around with permissions etc, so I pulled the network cable, set PreInstalledAppsEnabled to zero, and uninstalled Get Office. That worked with no fuss, and the two Microsoft.MicrosoftOfficeHub_ .... folders were gone from WindowsApps.
I then started the restore. It stayed at the "initializing" message for about an hour, then reported the identical failure to previous attempts. I believe it, because some new accounts that I had created still exist, etc.
However, every sub-folder in the WindowsApps folder shows a modified date/time covering a period of about 4 minutes during the restore operation, and the OfficeHub folders have reappeared. The PreInstalledAppsEnabled key has been set back to '1', but Get Office hasn't been reinstalled (possibly because I still have the network cable unplugged?).
I am now unable to delete those OfficeHub folders, even from the 'real' Administrator account. I'll have to do the permissions dance.
Note that it (probably) appears that it wasn't the restoring of those folders that tripped the restore up, because the date/time on those folders is in the middle of the time interval during which all of the other WindowsApps folders were 'restored'.
Not sure where I go from here...
Roger
I do not want to resurrect this thread, and I did not want to do it either, but peoples are claiming that this issue has been fixed in 2018. Really, fixed is all you can describe? For me I have the same error here!
To update, this problem is NOT fully solved. There are several users like myself who still have this problem and it reappeared after the April Update. Users contacting Microsoft at first were given steps to fix this issue, but then were finally told that it's been confirmed as bug and is going to be fixed as of June 2018. The exact date for this bug fix has not been revealed yet.
I am trying the methods, but at this point, since Microsoft now says it's a bug, I'd rather wait than do the method now.
Quote