New
#71
Meeker Morgan, try the latest preview KB5036979? Has it fixed the error?
I have updated to the above to 19045.4355, the error didn't come back as some predicted.
Meeker Morgan, try the latest preview KB5036979? Has it fixed the error?
I have updated to the above to 19045.4355, the error didn't come back as some predicted.
Still not fixed.
If I go a week without it happening I'll report and mark it solved,
I got that update KB5036979 today as well but I do not know if it fixed this problem. I would greatly appreciate any feed back if this solved it.
Respectfully,
Don
I just opened the Start Menu as I had to reinstall an App and wanted to pin it to my taskbar and as soon as I did the **** StartMenuExperienceHost failed again so sorry to report that the latest Preview Cumulative Update KB5036969 did not fix the error we have been getting. @Meeker Morgan and @qbdp .
Well thats a bummer. Hopefully enough people will report it and MS will address it. I certainly am not reinstalling Windows. Now its a waiting game.
Which build are you running now, 19045.4291 (april cumulative) or 19045.4355 (latest preview update)?
Did you really install KB5036892 - the april cumulative update? You wrote 'KB5037036' twice, so I'm just making sure. If you did, then I find it strange that your file was modified on that day and remains with that same modification date. Have you done the same tasks detailed in post #13? Because I did, and my file shows as having been modified in january, despite the fact that I'm running an up-to-date build of 19045.4291. What I didn't do was install any of march's updates. This might be significant, maybe Microsoft introduced some change in them, but didn't include the same change in aprils updates. This goes against the whole idea of cumulative updates, but mistakes happen. But the deal is that I too got these errors until I ran those aforementioned commands, just as instructed. And as I said, then there's the file's modification date that differs from yours. The cause of this error is obviously more complicated than it seems.
Last edited by i486; 1 Week Ago at 04:59.
I simply ran the same commands as in OP's post #13. The DISM ones from a normal account (online), and with admin rights. The PowerShell script after having logged in to an admin account, but I still opted to run PowerShell as an admin just in case. Online, just like with the DISM commands. Running the PS script from a normal account didn't seem to change anything, still I got the errors.
FWIW, the DISM routine did fix some corrupted files for me, even if it didn't fix my original problem.