W 8.1 KB4541509 loads a temporary user profile after installation. [SOLVED]

[mrwoof]

Hi
After installing KB4541509, I get a new desktop with a "temp user profile" message.
 Recovered with System restore.
I found a reference to this issue :
https://borncity.com/win/2020/02/16/windows-8-1-update-kb4537821-kills-also-user-profiles/

Have you come across this before ?
thoughts welcome
Ran SFC /Scannow, detected and unable to fix, then ran DISM /Online /Cleanup-Image /RestoreHealth. Completed with "Component store  corruption recovered". Wont chance repeating update till I have a fuller understanding of issue & trigger.
Came across this possible explanation &solution
https://www.youtube.com/watch?v=7BZJd-E1UUg

[Boggin]

My Win 10 machines are up to date but I haven't experienced that, but it looks like it's not restricted to Win 8.1

That YT video looks like it has the solution but I'd create a manual restore point before making any changes to the registry.

When a sfc /scannow reports that it is unable to fix some files, then run the dism /restorehealth cmd followed by another sfc /scannow which should then report it has fixed them or no integrity violations.

I'd try the steps in that video after creating a manual restore point and then run the dism and sfc /scannow cmds again just to ensure everything is fine.

[mrwoof]

 Let me bring you up to speed on my finding a solution working from within System restored image:

Stopped all the relevant services,
Deleted contents of "Software distribution"
Restarted relevant Services
Resumed Check for updates & installed all. (4 at this stage)
Reboot & all well.
Please mark as "Solved" for your many viewers who turn to you for much needed help.
Enjoy your day

Attch shows current Profile list

[Boggin]

So it could have been a buggy update install, although that wouldn't explain all of the other articles I found when I Googled it.

Generally when you experience adverse effects after an update, you can take that up with Microsoft for free help - although that doesn't mean that it will be fixed - as I've found

I'll mark the thread as Solved for you.