Also, if I demoted the dc back to regular server, then start menu and search bar are workingĪgain with "ALL APPLICATION PACKAGES" group back in the registry.Those horses will be comin’ round the mountain in just a few days. So this fix seem to only fix temporary until the server is rebooted. And once you add the group back to the registry, it is working again. I hope this will help someone in the future and save them weeks for try to resolve this issue. This fix also apply 2019 server DC as well. It is working right away.Īlso, it looks like event id 5973 and event id 1000 went away as well. Somehow, after joining the DC and reboot, the group is removed somehow. I checked my existing 2016 server vs 2016 server DC and in fact the ALL APPLICATION PACKAGES is missing HKLM\SOFTWARE on 2016 server DC. After endless research through online and I found article related to windows 10. The reboot, the start menu is missing and search bar is not longer working. Here is my situation, I joined server 2016 to domain and start menu and search bar still working fine, but as soon as I promo it to DC and after Ok guys, I have tired so many suggestions here but none of them worked for me. Here is what it shows in the TWinUI/Operational log:Īctivation of the app _cw5n1h2txyewy!CortanaUI for the Windows.Launch contract failed with error: The app didn't start.Īctivation via contract helper of the app _cw5n1h2txyewy!CortanaUI for the Windows.Launch contract failed with Server execution failed. Report Id: 7c440de5-55df-4cfb-8cf5-bb81ab5fabd0įaulting package full name: _1.3_neutral_neutral_cw5n1h2txyewyįaulting package-relative application ID: CortanaUI Report Id: e52d7da4-47a8-45e6-8c49-97e8ed59b29cįaulting package full name: _3.1378_neutral_neutral_cw5n1h2txyewyįaulting package-relative application ID: Appįaulting application name: SearchUI.exe, version: 3.953, time stamp: 0x58ba5a2fįaulting module name: SearchUI.exe, version: 3.953, time stamp: 0x58ba5a2fįaulting application start time: 0x01d3061a96a89c63įaulting application path: C:\Windows\SystemApps\_cw5n1h2txyewy\SearchUI.exeįaulting module path: C:\Windows\SystemApps\_cw5n1h2txyewy\SearchUI.exe See the Microsoft-Windows-TWinUI/Operational log for additional information.įaulting application name: ShellExperienceHost.exe, version: 3.447, time stamp: 0x5819bf85įaulting module name: Windows.UI.Xaml.dll, version: 3.1378, time stamp: 0x594a17beįaulting application start time: 0x01d3061a969cdfeaįaulting application path: C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exeįaulting module path: C:\Windows\System32\Windows.UI.Xaml.dll We did find this in the event log every time the start menu is clicked on:Īctivation of app _cw5n1h2txyewy!CortanaUI failed with error: The app didn't start. We switched to making desktop shortcuts for all the applications until Microsoft can fix this mess. The start menu starts working but our custom layout file doesn't apply any longer via Group Policy. Delete this folder for each user: C:\Users\username\AppData\Local\TileDataLayer We found a post that kind of restored the start menu by doing this:ġ. DISM /Online /Cleanup-Image /RestoreHealthĢ. Get-AppXPackage -AllUsers | Foreach -ģ. I checked all the reg keys, i even tried it with loop processing mode in "merge mode" just to troubleshoot, nothing.Īs i see it Microsoft needs to address this with a rollup, and fast! because its annyoing as hell! It works like a charm if the GPO is off and the users edit the start menu for them selfs, as soon as you force it on with a GPO and turn on the "Start Layout" again an point to the xml file you have exported, its stops working. Users -> Admin Temp -> Start Menu and Taskbar -> Force Start to be either full screen size or menu size (Force Full start menu) Second thing, i thought i could trick it with the GPO: The first thing that happens is, it looks all weird, nothing like the. (I exportet the start screen menu with the Export-startlayout cmlet) If you even think about the using the GPO in: Users -> Admin Temp -> Start Menu and Taskbar -> Start Layout, all sorts a funky sh. I´m running a 2016 Remote Desktop environment with one broker, two RDS servers and i RDGW. You can troubleshoot all you want, no matter how you handle it, the startmenu in 2016 is buggy as hell.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |