T
TheViking28
I've replicated this now and need help understanding what is causing the issue.
I stand up a new Server 2016 standard, I patch it, I join it to a domain, and then I install ADDS and promote it to a DC.
As soon as I reboot the system after it has become a DC, then the start menu ceases to function at all.
I can still right click and get that menu. I can not left click and get the normal start menu. Also the white paper "notifications" area to the right of the clock doesn't work either.
I have scoured the internet to find an answer without success. I did find a few hits of similar issues but people were suggesting all kinds of powershell commands to reset settings etc. I tried every fix I found and nothing helps.
I even found a thread here on Technet where someone had made a ticket with Microsoft and they narrowed it down to being an issue with DCOM permissions. Well, I went and checked those and mine already match up with how they should be.
I've also enabled and started the Windows search service as I saw that can be an issue.
So overall when I look in the event viewer here is what I see.
"Activation of app Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy!App failed with error: the app didn't start." event 5973
Also "Activation of app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI failed with error: The app didn't start." event 5973
Like I noted earlier, I have found a few hits on these errors but they point to doing things like restoring system files with DISM and doing integrity checks of the file system etc. This is a totally fresh VM install of Server 2016 patched up to date. I can literally duplicate this entire process over and over and over.
What absolutely triggers the issue is becoming a domain controller and rebooting. I don't see anything in the group policy that can explain this either. It is only as a domain controller that the issue starts. I can have 2016 servers joined to the same domain all day and no issues.
What is going on???
Continue reading...
I stand up a new Server 2016 standard, I patch it, I join it to a domain, and then I install ADDS and promote it to a DC.
As soon as I reboot the system after it has become a DC, then the start menu ceases to function at all.
I can still right click and get that menu. I can not left click and get the normal start menu. Also the white paper "notifications" area to the right of the clock doesn't work either.
I have scoured the internet to find an answer without success. I did find a few hits of similar issues but people were suggesting all kinds of powershell commands to reset settings etc. I tried every fix I found and nothing helps.
I even found a thread here on Technet where someone had made a ticket with Microsoft and they narrowed it down to being an issue with DCOM permissions. Well, I went and checked those and mine already match up with how they should be.
I've also enabled and started the Windows search service as I saw that can be an issue.
So overall when I look in the event viewer here is what I see.
"Activation of app Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy!App failed with error: the app didn't start." event 5973
Also "Activation of app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI failed with error: The app didn't start." event 5973
Like I noted earlier, I have found a few hits on these errors but they point to doing things like restoring system files with DISM and doing integrity checks of the file system etc. This is a totally fresh VM install of Server 2016 patched up to date. I can literally duplicate this entire process over and over and over.
What absolutely triggers the issue is becoming a domain controller and rebooting. I don't see anything in the group policy that can explain this either. It is only as a domain controller that the issue starts. I can have 2016 servers joined to the same domain all day and no issues.
What is going on???
Continue reading...