Normally, you won’t even notice the existence of the Windows Shell Experience Host. Over the years, it has been tweaked and refined with each new build of Windows 10, but its core functions remain the same. ![]() The process made its debut in the OS with the launch of Windows 10. The Windows Shell Experience Host process handles universal app interface behavior with respect to elements like the taskbar, Start Menu transparency, calendar, clock, background behavior, etc. It is the component of the Windows shell (basically, the graphical user interface on Windows) that specifically handles universal apps. It is the Windows component responsible for the windowed display feature of universal Windows applications. ![]() This should bring back the Start Menu and Cortana and all your application shortcuts.The Windows Shell Experience Host is also known as ShellExperienceHost.exe. Once this rule is created, either run a “gpupdate /target: computer /force” in a command prompt or simply reboot the server/computer. Go into your AppLocker GPO and right click the Packaged app Rules and select “Create Default Rules” this should create one rule which allows all signed packaged apps to be executed. The solution was actually really simple and required nothing more than creating another AppLocker rule. As it turns out Packaged Apps is another word for Universal Windows Platform (UWP) apps, these UWP apps are, among other things, handled by the before mentioned “Windows Shell Experience Host”.Īs AppLocker was apparently blocking the Windows Shell Experience, this would explain why my Start Menu wasn’t working properly. My AppLocker GPO was configured to enforce Packaged app rules, however no rules were configured, just like the event viewer was telling me. ![]() Not very helpful! I had Exe rules configured alright, but the “no Packaged app rules have been configured” part was a bit confusing. Well as it turns out, AppLocker was blocking the “Windows Shell Experience Host” and “Cortana”, and apparently both are necessary for the Start Menu to work properly.ĭuring my troubleshooting I came across this message in the AppLocker part of Windows Event Viewer: However in this case I had not configured either Citrix UPM nor Windows Roaming Profile, I had configured FSLogix Profile Container, so why was this happening? To make it even more strange I experienced the issue with an admin user with a local profile as well, so this ruled out any profile handling issues.Īs you may already have guessed, AppLocker had a part to play in the issue I experienced, but what was AppLocker actually doing? I have run into this issue many times before, in both Windows Server 2016 and Windows 10, the main cause was always either Citrix UPM not being able to handle the Tile Data Service database, or plain old regular Windows Roaming Profile just being old and broken. The context menu worked is it should, but nothing happened with a regular left click on the Start button. ![]() The other day I was setting up a couple of Window Server 2016 XenApp VDA servers to do some more extensive tests of the different Citrix policy templates, to evaluate how the settings in these policy templates impacts the user experience.ĭuring these tests I kept running into an issue with the Start Menu not working properly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |