New
#81
I have not heard a word from MS but I did get some new reply's with other members having the problem as well. I did get this :
In your discussions with other users, I noticed that you have previously submitted this question in the Feedback Center. If it's convenient, would you please share this link here so that we can vote for you.
We have also submitted this question through internal channels. If you can share this feedback link, we will submit your feedback content to the relevant team for investigation through internal channels.
Best Regards,
Mitchell | Microsoft Community Support Specialist
Regards,
Don
Still just riding it out. Thank you.
Hey there
Sorry about that. I thought the the green tick would be enough to mark it as solved. It's been a month and i have not had the problem come back but whether or not it resurface after the next update tuesday remains to be seen. I haven't tested out that with the preview update as it isn't broken why fix it
-------------Update---------------:
Installed 19045.4412 and the problem has not come back thankfully so for some Samuria's solution does appear to work
Last edited by shadowblade; 1 Week Ago at 16:43.
Still doing it, and I'm up to date on updates.
Same here. looks like MS is not going to address it - anyone get any feed back from them? I'll do a sys restore back till March I guess and then hide all updates till it gets fixed. Its annoying seeing all these red X's in reliability history.
I just finished installing the latest Patch Tuesday updates. I will let you know if these solved the problem which I will be surprised if it does.
Don
- - - Updated - - -
Guess what? Just as I suspected it was not fixed. I am so sick of this c**p.
Don
- - - Updated - - -
I have posted a new FeedBack Hub post here https://aka.ms/AAqgy2h so please go there everybody and ask them the same question I asked them about why this has not been fixed.
Don
yes, it was fixed for me until the May updates came through yesterday.
I retried the process in #13 which unfortunately didn't work this time. However, I retried the process in #13 using the following command in the powershell step:
Get-appxpackage -all *shellexperience* -packagetype bundle |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + “\appxmetadata\appxbundlemanifest.xml”)}
So far it's working fine - no issues since yesterday.
Note: I routinely run diskcleaner, sfc /scannow and create macrium system backups before installing monthly windows updates. After I installed the May updates and went through the process in #13, sfc found and repaired corruption, so clearly the updates are messing something up.