Tried a few of the suggested fixes found on this site and elsewhere but nothing has worked. I don't have dev profile activated, yes I have firewall running, no I haven't installed any other software other than the update to make this happen.... This is a bone stock W10 virtual machine that I use for development and only have VS2019 installed. It was running fine then I ran the update. Now the taskbar and start menu will not work.
- Can't open start menu, it attempts to spawn to the start menu process and then that process immediately gets killed
- Can't open the settings app, it spawns the app if I click on it but after the window appears it is immediately killed
- Can't right click on items on taskbar
- I did restart explorer.exe task and that for about 10 seconds fixes the problem then it immediately goes back to not working
It sure seems MS has a rogue background task that is monitoring processes and if the magic setting/config/info isn't set in a valid way that background process kills the start and property window activation's.
So, since I'm sick of MS and an obvious and downward spiral over past few years to Windows stability, it's clear I have to move to Mac and Linux for all dev work.... Sadly, I prefer to run Windows VMs locally to save money so I don't have to pay for AWS or some hosted VM option to development software for Windows. But, at this point, seems that's the only way I can use Windows today. I suppose AWS is not having this bug affect new EC2 instances b/c they use Windows Server desktops but I wouldn't be surprised if the bug hits their server UI layer as well eventually.
MS.... you're broken. If anyone has truly a deep or accurate understanding of the problem please share, I still see lots of others that also do not have a fix yet.