Windows server 2016 не работает кнопка пуск

Так как на устранение этой ошибки у меня ушло уйма времени и я перепробовал кучу всего, я решил все это структурировать и записать в виде отдельной статьи, в расчете, что мой путь будет кому-то полезен

Если вы именно снимите задачу «Проводника», то у вас пропадет все и останется только диспетчер задач. Далее нажмите в верхнем меню «Файл — Создать задачу» и в открывшемся окне введите explorer.exe и нажмите «Enter». Это вернет вам проводник и не потребуется перезагрузка сервера

HKEY_CLASSES_ROOTWOW6432NodeAppID{316CDED5-E4AE-4B15-9113-7055D84DCC97}

C:WindowsSystem32WindowsPowerShellv1.0

cd C:Share
Import-Module .DCOMPermissions.psm1

Grant-DCOMPermission -ApplicationID «{316CDED5-E4AE-4B15-9113-7055D84DCC97}» -Account «NT AUTHORITYПрошедшие проверку» -Type Launch -Permissions LocalLaunch,LocalActivation -OverrideConfigurationPermissions

Get-DCOMPermission -ApplicationID «{316CDED5-E4AE-4B15-9113-7055D84DCC97}» -Type Launch

HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersion DeviceAccessGlobal

Reauired application are not installed correctly. Install the applications

Reauired application are not installed correctly “Microsoft.Windows.ShellExperienceHost” and “Microsoft.Windows.Cortana” applications are installed correctly»

Get-appxpackage -all *shellexperience* -packagetype bundle |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + “appxmetadataappxbundlemanifest.xml”)}

Get-AppxPackage Microsoft.Windows.ShellExperienceHost | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register «$($_.InstallLocation)AppXManifest.xml»}

Get-AppxPackage Microsoft.Windows.Cortana | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register «$($_.InstallLocation)AppXManifest.xml»}

Get-AppxPackage Microsoft.Windows.StartMenuExperienceHost | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register «$($_.InstallLocation)AppXManifest.xml»}

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register «$($_.InstallLocation)AppXManifest.xml»}

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices WpnUserService

Критическая ошибка: Меню «Пуск» и приложение Кортана не работают. Мы попытаемся исправить эту проблему при следующем выполнении входа.

Critical Error: Start menu and Cortana aren’t working. We’ll try to fix it the next time you sign in.

Путь к файлу логу %WinDir%LogsCBSCBS.log

C:WindowsLogsDISMdism.log

Если по каким-то причинам у вас нет возможности скачать мой скрипт, или у вас нет на сервере интернета, то просто выполните по очереди команды:

• sfc /scannow
• DISM /Online /Cleanup-Image /ScanHealth
• DISM /Online /Cleanup-Image /CheckHealth
• DISM /Online /Cleanup-Image /RestoreHealth

не забываем потом перезагрузиться.

sfc /scannow & DISM /Online /Cleanup-Image /ScanHealth & DISM /Online /Cleanup-Image /CheckHealth & DISM /Online /Cleanup-Image /RestoreHealth

У вас должна быть учетная запись, в которой нет проблем с меню «Пуск», так как вам нужны хорошие копии базы данных TileDataLayer для копирования. Это можно сделать с другого сервера с Windows Server 2016

C:Usersваш логинAppDataLocal

net user имя пользователя пароль /add (В моем примере net user pusk 123456 /add)

ms-settings:personalization-start

ms-settings:personalization-start the wait operation timed out

$packages = Get-ChildItem -Path «$env:USERPROFILEAppDataLocalPackages»

if($packages.count -lt 14){

$apps = Get-ChildItem -Recurse -Path «C:WindowsSystemApps»,»C:WindowsImmersiveControlPanel», «C:WindowsPrintDialog»,»C:WindowsMiracastView» -Include «AppXManifest.xml»

Foreach($app in $apps){
Add-AppxPackage -DisableDevelopmentMode -Register «$app» -Verbose}
}
Else{
$null}

Скачать готовый скрипт — https://cloud.mail.ru/public/5NZx/4rrcJzqNr

Обязательно сохраните все данные из поврежденного профиля

Remove-Item «HKLM:SYSTEMCurrentControlSetServicesSharedAccess ParametersFirewallPolicyRestrictedServicesConfigurableSystem»
New-Item «HKLM:SYSTEMCurrentControlSetServicesSharedAccess ParametersFirewallPolicyRestrictedServicesConfigurableSystem»
Remove-Item «HKLM:SYSTEMCurrentControlSetServicesSharedAccess ParametersFirewallPolicyFirewallRules»
New-Item «HKLM:SYSTEMCurrentControlSetServicesSharedAccess ParametersFirewallPolicyFirewallRules»
Remove-Item «HKLM:SOFTWAREMicrosoftWindows NTCurrentVersion Notifications» -Recurse
New-Item «HKLM:SOFTWAREMicrosoftWindows NT CurrentVersionNotifications»

Скачать готовый скрипт — https://cloud.mail.ru/public/3mKR/NZtmoQS95

• Remove From My Forums

• Общие обсуждения

• Есть коллекция терминальных серверов на Windows Server 2016, профили пользователей в примонтируемых дисках.

  Столкнулся с проблемой, не работает кнопка пуск.

  Кортану отключал

  Computer Configuration > Policies > Administrative Templates > Windows Components > Search > Allow
  Cortana

  В диски профилей добавлял

  AppDataLocalTileDataLayer
  AppDataLocalConnectedDevicesPlatform
  AppDataLocalMicrosoftWindows

  Не помогло…

  Кто сталкивался и победил подобную проблему?

  • Изменен тип

    29 октября 2019 г. 9:17

Проблемы с Windows Server могут появляться время от времени, и многие пользователи сообщали, что меню «Пуск» не открывается в Windows Server 2016. Вот как один пользователь описал проблему в Microsoft TechNet :

У меня RODC 2016, и после некоторых обновлений Windows меню «Пуск» больше не открывается, поиск не открывается, а боковая панель уведомлений не открывается. Я перепробовал все приемы, которые использовались в Window 10, чтобы заставить их снова работать, но без кубиков.

В сегодняшней статье мы покажем вам пару решений, которые могут помочь вам навсегда решить эту проблему, так что давайте начнем.

Что делать, если меню «Пуск» не работает в Windows Server 2016?

1. Отключить полноэкранное меню «Пуск»

1. Нажмите клавишу Windows + I, чтобы открыть приложение «Настройки»
2. Теперь перейдите к персонализации
3. Выберите Пуск в меню слева. На правой панели отключите Использовать пуск в полноэкранном режиме.
   
4. После этого проблема должна быть решена.

2. Убедитесь, что служба поиска включена

1. Нажмите Windows Key + R и введите services.msc . Нажмите Enter или нажмите ОК .
2. Найдите Поиск Windows в списке и дважды щелкните по нему.
   
3. Установите для параметра « Тип запуска» значение « Автоматический» и нажмите кнопку « Пуск» , чтобы запустить его. Нажмите Apply и OK, чтобы сохранить изменения.
   

3. Создайте правила упакованного приложения в групповой политике Applocker.

1. Откройте конфигурацию компьютера .
2. Перейдите к Политике> Настройки Windows> Настройки безопасности> Политики контроля приложений> Applocker .
3. Щелкните правой кнопкой мыши Правила упакованного приложения и выберите Создать правила по умолчанию.
4. После применения политики проблема должна быть решена.

Меню Пуск не работает на вашем компьютере? Загрузите средство устранения неполадок в меню «Пуск», чтобы решить проблему автоматически!

4. Воссоздать поврежденный профиль пользователя.

1. Убедитесь, что вы вошли в систему с другой учетной записью администратора.
2. Перейдите в C: Users и удалите каталог поврежденного профиля пользователя. В нашем примере мы будем использовать C: Users WindowsReport .
3. Нажмите Windows Key + R и введите regedit . Нажмите Enter .
   
4. На левой панели перейдите к:
   • HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionProfileList
5. Пройдите все подразделы в левой панели. На правой панели следите за значением ProfileImagePath .
6. Найдите раздел, имеющий значение ProfileImagePath , соответствующее местоположению поврежденного профиля из шага 2 .
   
7. Найдя этот подраздел, щелкните его правой кнопкой мыши и выберите « Удалить» на левой панели.
8. Выйдите из системы и войдите в поврежденный профиль, и проблема должна быть решена.

5. Переименуйте или удалите UsrClass.dat

1. Нажмите клавиши Windows + R и введите % localappdata% . Нажмите Enter или нажмите ОК .
2. Перейдите в каталог Microsoft Windows .
   
3. Перейдите на вкладку « Вид » и выберите « Скрытые элементы» .
   
4. Найдите файл usrClass.dat и переименуйте его.
   
5. После этого проблема должна быть решена.

Вот вам несколько простых решений, которые могут вам помочь, если в Windows Server 2016 не открывается меню «Пуск».

Если вы нашли наши решения полезными, не стесняйтесь сообщить нам в разделе комментариев ниже.

ЧИТАЙТЕ ТАКЖЕ:

• Где я могу скачать Пуск Меню Устранение неполадок?
• Полное исправление: меню «Пуск» исчезает в Windows 10, 8.1 и 7
• Критическая ошибка Меню Пуск не работает в Windows 10 [FULL GUIDE]

All replies

• Have you tried a different user account? Does it work with that?

  • Proposed as answer by

    Saturday, July 14, 2018 5:46 PM

  • Unproposed as answer by
    hagen brown
    Saturday, July 14, 2018 5:47 PM
  • Proposed as answer by
    hagen brown
    Saturday, July 14, 2018 5:47 PM

• Hi,

  Try to restart the server in Clean Boot, and Safe Mode, check to see if the Start Menu and Search work.

  Besides, if the problem happens after Windows Update, try to uninstall the update one by one and check the result. 

  Remember to back up system state/important data before any change.

  Best Regards,
  Eve Wang

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact
  tnmff@microsoft.com.

• Firewall services has to be Start and running Mode

• So to reply in order:

  I had tried a new user account prior to posting to no avail.

  Safe mode made no change to the functionality, and as far as updates are concerned the only ones that list in the Installed updated field are KB’s 3206632, 3199986, and 3192137 the later 2 cannot be uninstalled as per Windows they are required.

  The firewall service is running, so no issue there.

• Hopefully right click on the start works, open a Command Prompt (Admin). Try;

  sfc /SCANNOW

  see if that finds and fixes anything.

• I`m having the same issue, the quickfix I have found is to switch the start menu mode from fullscreen to normal.

  Rightclick on the taskbar, select START en toggle fullscreen mode
  After switching the menu works again.

  It seems fullscreen Start is broken, switching to fullscreen while logged on works.
  But when logging off and logging on, the start menu stops working..

  Having this issue with several 2016 installations (patched or not) at this moment..

  Quickfix for now ; don`t use fullscreen start menu

• I’ve tried SFC /Scannow a bunch of times, as well as DISM /online /cleanup-image /restorehealth and neither detect or repair any issues.

  Tried changing start to full screen and still no response.

  I also ran up a bare 2016 server joined it to the domain and put it in the same OU, it works without issue, so I’m pretty sure I can rule out a GPO based issue.

• Got any virus scanners installed? Or other software that can be blocking the start menu.

  I have only come across this one time before and that was a bug with McAfee and Windows 10. Now Server 2016 isn’t Windows 10 but just check what you got installed.

• None at all, this is actually still a fresh system, and has only just been promoted to an RODC. I wanted to get this issue cleared up prior to adding third-party software.

• Hi,

  You have mentioned that you had tried new user account. Try both local admin account and domain account, and check to see if there is any difference.

  Besides, will there be an responding if you try to using keyboard shortcuts, such as “Win + X” and “Win + S”?

  Best Regards,
  Eve Wang

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact
  tnmff@microsoft.com.

• Win+X works, as well as right clicking on the start button. Win+S does not. I have removed and added the system to the domain so I could log on to the local Admin account and it made no difference.

• Hi,

  You have mentioned that another bare Windows Server 2016 has been joined to the same OU to check the GPO. Please compare below registry entries(including sub entries) on the problematic Windows Server 2016 with the bare Windows Server 2016.

  HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorerAdvanced

  HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionSearch

  Note:
  Remember to back up registry before any change. it would be helpful for restoration if there is any problem happens after the changing.

  Best Regards,
  Eve Wang

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact
  tnmff@microsoft.com.

• Everything looks the same under ExplorerAdvanced Under Search I have a few things different:

  On the RODC I Have the following entries:

  HKEY_CURRENT_USERSOFTWAREMicrosoftWindowsCurrentVersionSearch

  Value Name:
  JumpListChangedAppIds
  Value Data:
  Microsoft.Windows.ControlPanel
  windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel
  

  and

  HKEY_CURRENT_USERSOFTWAREMicrosoftWindowsCurrentVersionSearchJumplistData

  Value Name:
  Microsoft.Windows.ControlPanel
  
  Value Data:
  1d26f48d69daa7f
  
  Value Name:
  windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel
  
  Value Data:
  1d26b35ffa6d3c2

  None of these keys or values are on the other bare server, so not sure why the difference.

• Hi,

  I have check these entries on my Windows Server 2016 (DC) which Start and Search are working, there are similar values as you mentioned.

  If there is any system backup which was created before this problem happened, I would recommend you to have a system restoration. Or, you may consider of system reinstallation/migration.
  
  Best Regards,
  Eve Wang

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact
  tnmff@microsoft.com.

• Ok, a system restore, to before I joined the domain, made no difference.

  I am also seeing in the event logs several errors like:

  The server CortanaUI.AppXfbn8w4s0jbk3tjevpcn9kaxerc6rby8k.mca did not register with DCOM within the required timeout.

  Activation of app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI failed with error: The app didn't start. See the Microsoft-Windows-TWinUI/Operational log for additional information.

  Activation via contract helper of the app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI for the Windows.PreInstalledConfigTask contract failed with Server execution failed.

  etc..

• I`m having the same issue, the quickfix I have found is to switch the start menu mode from fullscreen to normal.

  Rightclick on the taskbar, select START en toggle fullscreen mode
  After switching the menu works again.

  It seems fullscreen Start is broken, switching to fullscreen while logged on works.
  But when logging off and logging on, the start menu stops working..

  Having this issue with several 2016 installations (patched or not) at this moment..

  Quickfix for now ; don`t use fullscreen start menu

  I have this exact same issue.

• I`m having the same issue, the quickfix I have found is to switch the start menu mode from fullscreen to normal.

  Rightclick on the taskbar, select START en toggle fullscreen mode
  After switching the menu works again.

  It seems fullscreen Start is broken, switching to fullscreen while logged on works.
  But when logging off and logging on, the start menu stops working..

  Having this issue with several 2016 installations (patched or not) at this moment..

  Quickfix for now ; don`t use fullscreen start menu

  I have this exact same issue.

  are there any other solutions to this, is there a bug ticket with Microsoft or anything that they’re addressing this issue with?

• Hi BrouseARA,

  Can you try to run this in Powershell and reboot your server?

  Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)AppXManifest.xml”} —

  If this will not work you can try these commands.

  DISM /Online /Cleanup-Image /ScanHealth
  DISM /Online /Cleanup-Image /CheckHealth
  DISM /Online /Cleanup-Image /RestoreHealth

  I would never run /RestoreHealth without running the /ScanHealth and /CheckHealth switches first.

  Yeah, I’ve done both of those more times than I can count. I also mentioned that I tried all of the tricks that get it to work with Win 10, which is where I first encountered the above commands.

• Hello Brouse,

  You can troubleshoot all you want, no matter how you handle it, the startmenu in 2016 is buggy as hell.

  I´m running a 2016 Remote Desktop environment with one broker, two RDS servers and i RDGW.

  If you even think about the using the GPO in: Users -> Admin Temp -> Start Menu and Taskbar -> Start Layout, all sorts a funky sh..  happens. 

  (I exportet the start screen menu with the Export-startlayout cmlet)

  The first thing that happens is, it looks all weird, nothing like the .xml file i just exportet.

  Second thing, i thought i could trick it with the GPO:

  Users -> Admin Temp -> Start Menu and Taskbar -> Force Start to be either full screen size or menu size (Force Full start menu)

  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.. wont even open
  the start menu.

  I checked all the reg keys, i even tried it with loop processing mode in «merge mode» just to troubleshoot, nothing.

  As i see it Microsoft needs to address this with a rollup, and fast! because its annyoing as hell!

• Has anyone figured this out yet?

  We found a post that kind of restored the start menu by doing this:

  1. DISM /Online /Cleanup-Image /RestoreHealth

  2. Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)AppXManifest.xml”} —

  3. Delete this folder for each user: C:UsersusernameAppDataLocalTileDataLayer

  The start menu starts working but our custom layout file doesn’t apply any longer via Group Policy. We are having to do this almost daily. We switched to making desktop shortcuts for all the applications until Microsoft can fix this mess.

  We did find this in the event log every time the start menu is clicked on:

  Activation of app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI failed with error: The app didn’t start. See the Microsoft-Windows-TWinUI/Operational log for additional information.

  Faulting application name: ShellExperienceHost.exe, version: 10.0.14393.447, time stamp: 0x5819bf85
  Faulting module name: Windows.UI.Xaml.dll, version: 10.0.14393.1378, time stamp: 0x594a17be
  Exception code: 0xc000027b
  Fault offset: 0x00000000006d6abb
  Faulting process id: 0x1498
  Faulting application start time: 0x01d3061a969cdfea
  Faulting application path: C:WindowsSystemAppsShellExperienceHost_cw5n1h2txyewyShellExperienceHost.exe
  Faulting module path: C:WindowsSystem32Windows.UI.Xaml.dll
  Report Id: e52d7da4-47a8-45e6-8c49-97e8ed59b29c
  Faulting package full name: Microsoft.Windows.ShellExperienceHost_10.0.14393.1378_neutral_neutral_cw5n1h2txyewy
  Faulting package-relative application ID: App

  Faulting application name: SearchUI.exe, version: 10.0.14393.953, time stamp: 0x58ba5a2f
  Faulting module name: SearchUI.exe, version: 10.0.14393.953, time stamp: 0x58ba5a2f
  Exception code: 0xc000027b
  Fault offset: 0x0000000000174975
  Faulting process id: 0x1480
  Faulting application start time: 0x01d3061a96a89c63
  Faulting application path: C:WindowsSystemAppsMicrosoft.Windows.Cortana_cw5n1h2txyewySearchUI.exe
  Faulting module path: C:WindowsSystemAppsMicrosoft.Windows.Cortana_cw5n1h2txyewySearchUI.exe
  Report Id: 7c440de5-55df-4cfb-8cf5-bb81ab5fabd0
  Faulting package full name: Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy
  Faulting package-relative application ID: CortanaUI

  Here is what it shows in the TWinUI/Operational log:

  Activation of the app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI for the Windows.Launch contract failed with error: The app didn’t start..

  Activation via contract helper of the app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI for the Windows.Launch contract failed with Server execution failed.

  • Edited by
    NETS_skincaid
    Thursday, July 27, 2017 4:12 AM
    Adding information

• Figured it out…

  Most of the errors were Cortana and Windows Search errors. A little Googling and found in Server 2016, Windows Search is disabled by default because it can cause issues with clusters and other high level configuration options.

  In a standard RDS deployment, not an issue so we set it automatic, started it and the event logs errors went away when launching the start menus. A bonus, the start menus actually launched.

  There was another app error from our admin account related to the start menu and we had to fix that by enabling «User Account Control: Run all administrators in Admin Approval Mode» in Group Policy. Poor Start Menu and integration design by Microsoft
  on the Server 2016 side.

  • Proposed as answer by
    NETS_skincaid
    Thursday, July 27, 2017 5:19 AM
  • Unproposed as answer by
    BrouseARA
    Thursday, July 27, 2017 12:03 PM
  • Proposed as answer by
    TheBloodyAlien
    Sunday, January 28, 2018 12:02 PM

• Hi NETS,

  I had already tried setting search on and tried setting local sec policy to run in admin approval mode. In the mean time since I started this tread, I have replaced the RODC with a standard DC, and deployed 2 other 20116 DC’s. All 2016 Domain Controllers
  exhibit this behavior, while none of the other 2 dozen or so 2016 servers do.

  I have placed these servers in an OU where no GPO’s apply, and created a custom Default Domain Controller policy that applies only to those DC’s and have had no luck so far.

• Hi. Please try this. It worked for me

  https://justforadmins.blogspot.com/2016/09/fixed-windows-10-start-button-does-not.html

  • Proposed as answer by
    Erik Pierik
    Monday, June 18, 2018 11:48 AM

• Open Run… and type «ms-settings:personalization-start»

  Uncheck Show more tiles and uncheck Use start full screen.

  Thats it.

  • Proposed as answer by
    Kiwistevo
    Tuesday, May 22, 2018 11:38 PM

• Incredible that this is even an issue. Tried everything suggested without success. What are you guys doing in Redmond? Inexcusable. 

• Hi

  We have 14 RDS Hosts. This issue has been intermittenet. It seemed to be resolved pre spectre patches and then returned. I beleive its when a user changes which host they are on. User profile disks also contribute to this issue. It occured with 1 user with
  administrator rights logged on so I dont believe its a performance/load issue.

  When it does happen %localappdata%Packages only has 1 or 2 folders present. It should have 15.

  I wrote this script

  $packages = Get-ChildItem -Path "$env:USERPROFILEAppDataLocalPackages"
  
  if($packages.count -lt 14){
  
  $apps =  Get-ChildItem -Recurse -Path "C:WindowsSystemApps","C:WindowsImmersiveControlPanel","C:WindowsPrintDialog","C:WindowsMiracastView" -Include "AppXManifest.xml"
  
  Foreach($app in $apps){
  Add-AppxPackage -DisableDevelopmentMode -Register "$app" -Verbose}
  }
  Else{
  $null}

  This should correct he issue it needs to run in the user context.

  Please reply if this resolves the issue for you.

  • Proposed as answer by
    Maxsuel Vieira Orti
    Tuesday, August 14, 2018 11:58 AM

• For me, Matts solution worked.

  Same thing — RDS hosts. Randomly — usually 2 at a time — servers start menu will not open anymore. We are using profile disks. In my case the Packages folder has 15 subfolders. But executing only the install part of Matts script fixes the problem. Let’s
  see — for how long.

  • Proposed as answer by
    hagen brown
    Saturday, July 14, 2018 6:05 PM
  • Unproposed as answer by
    hagen brown
    Saturday, July 14, 2018 6:07 PM

• Corrupt domain user profile on Win2016 caused similar issue for me.

  To resolve, recreated domain  user profile on Win2016 server: user called <corruptuserprofile>

  1. Login to server with a different admin user account.
  2. Delete c:users<corruptuserprofile>
  3. Navigate registry to HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionProfileList
  4. Examine each SID entry for «ProfileImagePage REG_EXPAND_SZ C:users<baduserprofile>»
  5. Delete SID entry.
  6. Logout
  7. Log in as user <corruptuserprofile> to generate new profile

  Issue resolved.

  • Edited by
    hagen brown
    Saturday, July 14, 2018 6:04 PM
  • Proposed as answer by
    Brandon Tahedl
    Tuesday, August 7, 2018 3:00 PM

• Using GPO, I set this script to run at login and used loopback to only apply it to our RDSH server farm and so far it seems to work. When it needs to run, it finishes in about 5 seconds.

  • Edited by
    ssh-pvi
    Monday, July 23, 2018 8:44 PM

• For me, Matts solution worked.

  Same thing — RDS hosts. Randomly — usually 2 at a time — servers start menu will not open anymore. We are using profile disks. In my case the Packages folder has 15 subfolders. But executing only the install part of Matts script fixes the problem. Let’s
  see — for how long.

  Well. My fun ended. The script worked once.

  After a little while the start menu problem re-apeared. If i run the script again, i receive a bunch of IO Exception errors on installing most of the AppX apps, and the problem will not go away. Restart does not help.

  One thing i noticed. When i press start button — then in the USERPROFILEAppDataLocalPackages
    folder for a moment (maybe 1 second) gets created «Microsoft.Windows.Cortana_cw5n…» subfolder. And then I disappears again. So it led me to believe that maybe it’s a cortana related issue. But disabling cortana did nothing…

  • Edited by
    McWax
    Tuesday, July 24, 2018 9:12 AM

• This did it for me!

  I should’ve guessed it was a corrupt profile. Thanks again!

• The first command on Powershell works to me. Thanks!

• Worked in my situation as well.

• Thanks Matt, your solution worked for me as well.

• Hi,

  does anyone got another solution?

  Nothing of this worked for me. I’m getting a non working start menu on several 2016 Server all the time. This is
  not connected to a single userprofile.

  If I try to re-register the windows apps (Matts solution) I get AppX-Package Error:

  Deployment failed with HRESULT: 0x80073CF9, Install failed. Please contact your software vendor.

  It is not possible to open any «ms-settings*» application like windows-update or Setting Application. Am I the only on who got this issue? Restoring the OS from Backups can’t be the solution all the time

• FYI, the above script did not work for me; there were already 15 folders in the $env:USERPROFILEAppDataLocalPackages location.

• Hi,

  after researching for hours I found a issue in the registry with the Windows Firewall, even if the Windows Firewall was turned off.

  Try to execute this commands in PowerShell, this worked for me. About 10 seconds after executing the commands the start menu should work again, if the problem is the same that I had.

  Remove-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyRestrictedServicesConfigurableSystem"
  
  New-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyRestrictedServicesConfigurableSystem

• Hi!

  I had the same issue.

  Rename or delete 

   %LOCALAPPDATA%MicrosoftWindowsUsrClass.dat

• Copy over

  HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionAppxAppxAllUserStore

  and

  HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionAppReadiness

  from a working 2016 Server (ignore the errors that system has some keys open.

  reboot delete the user profile and login as a new user.

• Hi,

  after researching for hours I found a issue in the registry with the Windows Firewall, even if the Windows Firewall was turned off.

  Try to execute this commands in PowerShell, this worked for me. About 10 seconds after executing the commands the start menu should work again, if the problem is the same that I had.

  Remove-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyRestrictedServicesConfigurableSystem"
  
  New-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyRestrictedServicesConfigurableSystem

  This is crazy, but this is THE ONLY solution that worked for my servers. Before I applied this in <g class=»gr_ gr_61 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace» data-gr-id=»61″ id=»61″>powershell</g> I
  went to this location in the registry and waited over an hour for the records to load until I gave up. Then I applied it and the start menu started working.

• This is the only solution that worked for us. All others failed. 

  Most items in the Start menu reappear except the old 16 bit program references which do show up for Administrative accounts logged into these servers. 

• Incredible that two years later this is still a thing. One of my RDS servers suddenly stopped showing the menu. Reading through this thread, I started by enabliing the search service and that magically fixed it. However, I also followed the link to go create
  default rules for Applocker.

  This did start after I enabled app whitelisting on the server (they’re still being configured, thankfully) to keep my users from spreading every virus and ransomware known to man…

  Of course, just because it works now doesn’t have to mean it will continue to do so., Time will tell.

• Thanks for this, fixed my problem immediately. Well done.

  ---

  Scott S.

• Scott,
  Can you verify what fixed your problem? There are multiple solutions in this thread.

• Clarkry, were you able to get a resolution?  Like you noticed, many users have posted the «fix» but I’m somewhat hesitant to just make changes as there’s not a specific agreement for the true solution with the start menu on 2016 RDS.

  Thanks.

  Ken

• Having the same problem with a recently deployed RDS 2016 farm…  CTRL-ALT-END to sign the user out and when they log back in, things are fine.  A fix would be nice.

• CorbettEnders69, have you tried the PS script from earlier in this post to see if it works?

  Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)AppXManifest.xml”}

• I have not as our packages folder contains 15 items.

• That’s a different script that solves the packages folder issue.  Like you, I’m not seeing the reduction in the packages folders for any of my users when they drop access to the Start Menu or the Taskbar.  I did run the other script last night
  and rebooted the RDS box.  So far, I’ve heard of no issues from my users.

  Ken

• This worked for me!  Thanks!

• SOLUTION:

  Remove-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyRestrictedServicesConfigurableSystem"
  New-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyRestrictedServicesConfigurableSystem"
  Remove-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyFirewallRules"
  New-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyFirewallRules"
  Remove-Item "HKLM:SOFTWAREMicrosoftWindows NTCurrentVersionNotifications" -Recurse
  New-Item "HKLM:SOFTWAREMicrosoftWindows NTCurrentVersionNotifications"

  RESTART SERVER

  • Proposed as answer by
    _z0rg_
    Friday, August 23, 2019 5:55 AM

• Matt’s script has been fixing this for me. Thanks!

• Regardless of qty of packages (we seem to have 15 consistently), the replacement of the ShellExperienceHost is what fixes it.  Any user with a broken menu can run this command and the menu is fixed in their session live.

  Add-AppxPackage -Register «C:WindowsSystemAppsShellExperienceHost_cw5n1h2txyewyAppxManifest.xml» -DisableDevelopmentMode

  So we are going to actual set roaming profiles to delete at log off.  This will clear out that folder completely.  Then the folder %localappdata% should get rebuilt (the local doesn’t roam) and hopefully the problem will go away.

• Mine was simply fixed by creating a new profile.  I had noticed that my profile was over 500mb in size (which is probably why it didn’t load quickly enough to display start menu).

  Simply logged on as Domain Administrator, deleted the profile associated with my user account, logged back on and the new profile was fine.

  • Proposed as answer by
    iamkl00t
    Tuesday, May 28, 2019 11:45 AM

• Not a solution. You’ll soon find it breaking again.

• I’ve spent the better part of the last few months trying to find the solution to this issue.  I’ve read and tried many of the steps suggested by others in this thread.  Low and behold, it was a kid on YouTube who had the fix all along.  While
  this fix is for Windows 10, it works perfectly on Server 2016 Standard.  I’m sure Datacenter too.

  1. Since the Start Menu is not working, open the task manager. 
  2. Click on File—> Run new task
  3. Type PowerShell, and make sure to check the box for «Create this task with administrative privileges”
  4. Click OK
  5. Run the following command:

  Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register «$($_.InstallLocation)AppXManifest.xml»}

  Problem solved.  Thanks to this YouTuber: UnionStarGamers

  I can’t post links.  I haven’t verified my account yet.  

• We’ve ran into this problem on some occasions on 2012 and 2016.

  What we found that fixed it was the Policy «Bypass traverse checking» under User Rights.  If there is only one account here, it will cause this issue.  Our fix is to add Authenticated Users to the policy.

• The start menu on one of my Server 2016 Standard machines had stopped responding. Left clicking did nothing. Right clicking brought up the tasks menu, as usual. I had spent several hours trying various things which one always tries when something weird happens,
  without elaborating. Search worked, so I searched PowerShell, right clicked «Run as Administrator» (necessary) and executed the command you provided above verbatim, with cut and Control-V (paste) into PowerShell. It went to work rebuilding. After
  it was done, I clicked on «Start,» quite frankly not expecting it to do anything. It worked… Fixed! Great tip and thanks to your YouTube guy.

  I thought I would post a comment so others could try this fix. I would be curious to know what happened to cause this problem. There was obviously some corruption issue.  Any input as to causes would be appreciated. 

   

• The registry backup and import  was the only fix that worked for me.

  Pull reg keys from working RDS server, clicked start menu after importing the keys and showed after a few seconds.

  • Proposed as answer by
    bolkware.de
    Thursday, November 28, 2019 12:30 PM

• SOLUTION:

  Remove-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyRestrictedServicesConfigurableSystem"
  New-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyRestrictedServicesConfigurableSystem"
  Remove-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyFirewallRules"
  New-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyFirewallRules"
  Remove-Item "HKLM:SOFTWAREMicrosoftWindows NTCurrentVersionNotifications" -Recurse
  New-Item "HKLM:SOFTWAREMicrosoftWindows NTCurrentVersionNotifications"

  RESTART SERVER

  in my case this worked

  • Edited by
    _z0rg_
    Friday, August 23, 2019 5:53 AM

• Ok guys, I have tired so many suggestions here but none of them worked for me.  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
  the reboot, the start menu is missing and search bar is not longer working.  After endless research through online and I found article related to windows 10.  https://www.tenforums.com/general-support/48545-windows-10-start-menu-cortana-not-working-being-caused-gpo-2.html

  I checked my existing 2016 server vs 2016 server DC and in fact the ALL APPLICATION PACKAGES is missing HKLMSOFTWARE on 2016 server DC.  Somehow, after joining the DC and reboot, the group is removed somehow.  After adding back
  the group hklmsoftware in the registry.  It is working right away. 

  Also, it looks like event id 5973 and event id 1000 went away as well.

  This fix also apply 2019 server DC as well.  I hope this will help someone in the future and save them weeks for try to resolve this issue.  Good luck!!!

  Update:

  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.   Also, if I demoted the dc back to regular server, then start menu and search bar are working
  again with «ALL APPLICATION PACKAGES» group back in the registry.

  Does anyone know to good way to report this bug to Microsoft?

  • Edited by
    Killachang
    Wednesday, October 16, 2019 1:40 PM

• It worked for me.

  Thank you

  ---

  Thank you, Falcon

• This worked for me!!! Sorry to wake the dead here, but I had to login and comment. This has been vexing me for months, tried lots of stuff as the other posters have. Even a fruitless case with Microsoft failed to fix the inop Start Menu issue. But the
  above script ran with admin via powershell worked right away for me. Do I know why? No. I don’t know how electricity works either but I don’t have research time; only barely enough for this comment..

• Adding the problem user with Full rights to the HKLMSOFTWARE key fixed the problem for me.

  All Users were there with Read Only Access, but when I added the user who was using RDP to this Key specifically with Full rights, the Start Menu and Search bar now function.

• Remove-Item «HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyRestrictedServicesConfigurableSystem» New-Item «HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyRestrictedServicesConfigurableSystem

  worked like charm, thank you

  • Edited by
    Milordas
    Wednesday, February 19, 2020 9:07 AM

• I logged in as a temporary administrator account, went to c:users and renamed the corrupted profile (in case I needed to restore it)  I then re-logged in using the account with the corrupted profile and the start button was working again. However,
  an error message says that I’m using a temporary profile «we couldn’t sign you in». I then log back out, log in as my temporary administrator profile and rename the corrupt profile back to its correct name. Log back in and the start menu is working
  again. (No profiles removed)

  Just be aware that when removing a profile on Windows Server 2016 that you might have some important software running on your server that is using that profile. For example DirSync or another important application so just be aware of this!

  Also, Sophos Lockdown is known to cause this. A work around in that awful situation when you can’t open anything (start menu, powershell etc) is here:

  • Edited by
    dubsdj — MCITP — CCA-V
    Thursday, April 23, 2020 1:36 PM

• Running below on Powershell worked for me without reboot server

  Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode
  -Register “$($_.InstallLocation)AppXManifest.xml”} —

• thx a lot Matt, this did solve it for me as well, using Remote Desktop Manager connected to windows server 2016 version 1607.

• THANKS

  In my server: all users in D drive and this worked for me:

  Get-AppXPackage | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)AppXManifest.xml”} —

All replies

• Have you tried a different user account? Does it work with that?

  • Proposed as answer by

    Saturday, July 14, 2018 5:46 PM

  • Unproposed as answer by
    hagen brown
    Saturday, July 14, 2018 5:47 PM
  • Proposed as answer by
    hagen brown
    Saturday, July 14, 2018 5:47 PM

• Hi,

  Try to restart the server in Clean Boot, and Safe Mode, check to see if the Start Menu and Search work.

  Besides, if the problem happens after Windows Update, try to uninstall the update one by one and check the result. 

  Remember to back up system state/important data before any change.

  Best Regards,
  Eve Wang

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact
  tnmff@microsoft.com.

• Firewall services has to be Start and running Mode

• So to reply in order:

  I had tried a new user account prior to posting to no avail.

  Safe mode made no change to the functionality, and as far as updates are concerned the only ones that list in the Installed updated field are KB’s 3206632, 3199986, and 3192137 the later 2 cannot be uninstalled as per Windows they are required.

  The firewall service is running, so no issue there.

• Hopefully right click on the start works, open a Command Prompt (Admin). Try;

  sfc /SCANNOW

  see if that finds and fixes anything.

• I`m having the same issue, the quickfix I have found is to switch the start menu mode from fullscreen to normal.

  Rightclick on the taskbar, select START en toggle fullscreen mode
  After switching the menu works again.

  It seems fullscreen Start is broken, switching to fullscreen while logged on works.
  But when logging off and logging on, the start menu stops working..

  Having this issue with several 2016 installations (patched or not) at this moment..

  Quickfix for now ; don`t use fullscreen start menu

• I’ve tried SFC /Scannow a bunch of times, as well as DISM /online /cleanup-image /restorehealth and neither detect or repair any issues.

  Tried changing start to full screen and still no response.

  I also ran up a bare 2016 server joined it to the domain and put it in the same OU, it works without issue, so I’m pretty sure I can rule out a GPO based issue.

• Got any virus scanners installed? Or other software that can be blocking the start menu.

  I have only come across this one time before and that was a bug with McAfee and Windows 10. Now Server 2016 isn’t Windows 10 but just check what you got installed.

• None at all, this is actually still a fresh system, and has only just been promoted to an RODC. I wanted to get this issue cleared up prior to adding third-party software.

• Hi,

  You have mentioned that you had tried new user account. Try both local admin account and domain account, and check to see if there is any difference.

  Besides, will there be an responding if you try to using keyboard shortcuts, such as “Win + X” and “Win + S”?

  Best Regards,
  Eve Wang

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact
  tnmff@microsoft.com.

• Win+X works, as well as right clicking on the start button. Win+S does not. I have removed and added the system to the domain so I could log on to the local Admin account and it made no difference.

• Hi,

  You have mentioned that another bare Windows Server 2016 has been joined to the same OU to check the GPO. Please compare below registry entries(including sub entries) on the problematic Windows Server 2016 with the bare Windows Server 2016.

  HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorerAdvanced

  HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionSearch

  Note:
  Remember to back up registry before any change. it would be helpful for restoration if there is any problem happens after the changing.

  Best Regards,
  Eve Wang

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact
  tnmff@microsoft.com.

• Everything looks the same under ExplorerAdvanced Under Search I have a few things different:

  On the RODC I Have the following entries:

  HKEY_CURRENT_USERSOFTWAREMicrosoftWindowsCurrentVersionSearch

  Value Name:
  JumpListChangedAppIds
  Value Data:
  Microsoft.Windows.ControlPanel
  windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel
  

  and

  HKEY_CURRENT_USERSOFTWAREMicrosoftWindowsCurrentVersionSearchJumplistData

  Value Name:
  Microsoft.Windows.ControlPanel
  
  Value Data:
  1d26f48d69daa7f
  
  Value Name:
  windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel
  
  Value Data:
  1d26b35ffa6d3c2

  None of these keys or values are on the other bare server, so not sure why the difference.

• Hi,

  I have check these entries on my Windows Server 2016 (DC) which Start and Search are working, there are similar values as you mentioned.

  If there is any system backup which was created before this problem happened, I would recommend you to have a system restoration. Or, you may consider of system reinstallation/migration.
  
  Best Regards,
  Eve Wang

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact
  tnmff@microsoft.com.

• Ok, a system restore, to before I joined the domain, made no difference.

  I am also seeing in the event logs several errors like:

  The server CortanaUI.AppXfbn8w4s0jbk3tjevpcn9kaxerc6rby8k.mca did not register with DCOM within the required timeout.

  Activation of app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI failed with error: The app didn't start. See the Microsoft-Windows-TWinUI/Operational log for additional information.

  Activation via contract helper of the app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI for the Windows.PreInstalledConfigTask contract failed with Server execution failed.

  etc..

• I`m having the same issue, the quickfix I have found is to switch the start menu mode from fullscreen to normal.

  Rightclick on the taskbar, select START en toggle fullscreen mode
  After switching the menu works again.

  It seems fullscreen Start is broken, switching to fullscreen while logged on works.
  But when logging off and logging on, the start menu stops working..

  Having this issue with several 2016 installations (patched or not) at this moment..

  Quickfix for now ; don`t use fullscreen start menu

  I have this exact same issue.

• I`m having the same issue, the quickfix I have found is to switch the start menu mode from fullscreen to normal.

  Rightclick on the taskbar, select START en toggle fullscreen mode
  After switching the menu works again.

  It seems fullscreen Start is broken, switching to fullscreen while logged on works.
  But when logging off and logging on, the start menu stops working..

  Having this issue with several 2016 installations (patched or not) at this moment..

  Quickfix for now ; don`t use fullscreen start menu

  I have this exact same issue.

  are there any other solutions to this, is there a bug ticket with Microsoft or anything that they’re addressing this issue with?

• Hi BrouseARA,

  Can you try to run this in Powershell and reboot your server?

  Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)AppXManifest.xml”} —

  If this will not work you can try these commands.

  DISM /Online /Cleanup-Image /ScanHealth
  DISM /Online /Cleanup-Image /CheckHealth
  DISM /Online /Cleanup-Image /RestoreHealth

  I would never run /RestoreHealth without running the /ScanHealth and /CheckHealth switches first.

  Yeah, I’ve done both of those more times than I can count. I also mentioned that I tried all of the tricks that get it to work with Win 10, which is where I first encountered the above commands.

• Hello Brouse,

  You can troubleshoot all you want, no matter how you handle it, the startmenu in 2016 is buggy as hell.

  I´m running a 2016 Remote Desktop environment with one broker, two RDS servers and i RDGW.

  If you even think about the using the GPO in: Users -> Admin Temp -> Start Menu and Taskbar -> Start Layout, all sorts a funky sh..  happens. 

  (I exportet the start screen menu with the Export-startlayout cmlet)

  The first thing that happens is, it looks all weird, nothing like the .xml file i just exportet.

  Second thing, i thought i could trick it with the GPO:

  Users -> Admin Temp -> Start Menu and Taskbar -> Force Start to be either full screen size or menu size (Force Full start menu)

  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.. wont even open
  the start menu.

  I checked all the reg keys, i even tried it with loop processing mode in «merge mode» just to troubleshoot, nothing.

  As i see it Microsoft needs to address this with a rollup, and fast! because its annyoing as hell!

• Has anyone figured this out yet?

  We found a post that kind of restored the start menu by doing this:

  1. DISM /Online /Cleanup-Image /RestoreHealth

  2. Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)AppXManifest.xml”} —

  3. Delete this folder for each user: C:UsersusernameAppDataLocalTileDataLayer

  The start menu starts working but our custom layout file doesn’t apply any longer via Group Policy. We are having to do this almost daily. We switched to making desktop shortcuts for all the applications until Microsoft can fix this mess.

  We did find this in the event log every time the start menu is clicked on:

  Activation of app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI failed with error: The app didn’t start. See the Microsoft-Windows-TWinUI/Operational log for additional information.

  Faulting application name: ShellExperienceHost.exe, version: 10.0.14393.447, time stamp: 0x5819bf85
  Faulting module name: Windows.UI.Xaml.dll, version: 10.0.14393.1378, time stamp: 0x594a17be
  Exception code: 0xc000027b
  Fault offset: 0x00000000006d6abb
  Faulting process id: 0x1498
  Faulting application start time: 0x01d3061a969cdfea
  Faulting application path: C:WindowsSystemAppsShellExperienceHost_cw5n1h2txyewyShellExperienceHost.exe
  Faulting module path: C:WindowsSystem32Windows.UI.Xaml.dll
  Report Id: e52d7da4-47a8-45e6-8c49-97e8ed59b29c
  Faulting package full name: Microsoft.Windows.ShellExperienceHost_10.0.14393.1378_neutral_neutral_cw5n1h2txyewy
  Faulting package-relative application ID: App

  Faulting application name: SearchUI.exe, version: 10.0.14393.953, time stamp: 0x58ba5a2f
  Faulting module name: SearchUI.exe, version: 10.0.14393.953, time stamp: 0x58ba5a2f
  Exception code: 0xc000027b
  Fault offset: 0x0000000000174975
  Faulting process id: 0x1480
  Faulting application start time: 0x01d3061a96a89c63
  Faulting application path: C:WindowsSystemAppsMicrosoft.Windows.Cortana_cw5n1h2txyewySearchUI.exe
  Faulting module path: C:WindowsSystemAppsMicrosoft.Windows.Cortana_cw5n1h2txyewySearchUI.exe
  Report Id: 7c440de5-55df-4cfb-8cf5-bb81ab5fabd0
  Faulting package full name: Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy
  Faulting package-relative application ID: CortanaUI

  Here is what it shows in the TWinUI/Operational log:

  Activation of the app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI for the Windows.Launch contract failed with error: The app didn’t start..

  Activation via contract helper of the app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI for the Windows.Launch contract failed with Server execution failed.

  • Edited by
    NETS_skincaid
    Thursday, July 27, 2017 4:12 AM
    Adding information

• Figured it out…

  Most of the errors were Cortana and Windows Search errors. A little Googling and found in Server 2016, Windows Search is disabled by default because it can cause issues with clusters and other high level configuration options.

  In a standard RDS deployment, not an issue so we set it automatic, started it and the event logs errors went away when launching the start menus. A bonus, the start menus actually launched.

  There was another app error from our admin account related to the start menu and we had to fix that by enabling «User Account Control: Run all administrators in Admin Approval Mode» in Group Policy. Poor Start Menu and integration design by Microsoft
  on the Server 2016 side.

  • Proposed as answer by
    NETS_skincaid
    Thursday, July 27, 2017 5:19 AM
  • Unproposed as answer by
    BrouseARA
    Thursday, July 27, 2017 12:03 PM
  • Proposed as answer by
    TheBloodyAlien
    Sunday, January 28, 2018 12:02 PM

• Hi NETS,

  I had already tried setting search on and tried setting local sec policy to run in admin approval mode. In the mean time since I started this tread, I have replaced the RODC with a standard DC, and deployed 2 other 20116 DC’s. All 2016 Domain Controllers
  exhibit this behavior, while none of the other 2 dozen or so 2016 servers do.

  I have placed these servers in an OU where no GPO’s apply, and created a custom Default Domain Controller policy that applies only to those DC’s and have had no luck so far.

• Hi. Please try this. It worked for me

  https://justforadmins.blogspot.com/2016/09/fixed-windows-10-start-button-does-not.html

  • Proposed as answer by
    Erik Pierik
    Monday, June 18, 2018 11:48 AM

• Open Run… and type «ms-settings:personalization-start»

  Uncheck Show more tiles and uncheck Use start full screen.

  Thats it.

  • Proposed as answer by
    Kiwistevo
    Tuesday, May 22, 2018 11:38 PM

• Incredible that this is even an issue. Tried everything suggested without success. What are you guys doing in Redmond? Inexcusable. 

• Hi

  We have 14 RDS Hosts. This issue has been intermittenet. It seemed to be resolved pre spectre patches and then returned. I beleive its when a user changes which host they are on. User profile disks also contribute to this issue. It occured with 1 user with
  administrator rights logged on so I dont believe its a performance/load issue.

  When it does happen %localappdata%Packages only has 1 or 2 folders present. It should have 15.

  I wrote this script

  $packages = Get-ChildItem -Path "$env:USERPROFILEAppDataLocalPackages"
  
  if($packages.count -lt 14){
  
  $apps =  Get-ChildItem -Recurse -Path "C:WindowsSystemApps","C:WindowsImmersiveControlPanel","C:WindowsPrintDialog","C:WindowsMiracastView" -Include "AppXManifest.xml"
  
  Foreach($app in $apps){
  Add-AppxPackage -DisableDevelopmentMode -Register "$app" -Verbose}
  }
  Else{
  $null}

  This should correct he issue it needs to run in the user context.

  Please reply if this resolves the issue for you.

  • Proposed as answer by
    Maxsuel Vieira Orti
    Tuesday, August 14, 2018 11:58 AM

• For me, Matts solution worked.

  Same thing — RDS hosts. Randomly — usually 2 at a time — servers start menu will not open anymore. We are using profile disks. In my case the Packages folder has 15 subfolders. But executing only the install part of Matts script fixes the problem. Let’s
  see — for how long.

  • Proposed as answer by
    hagen brown
    Saturday, July 14, 2018 6:05 PM
  • Unproposed as answer by
    hagen brown
    Saturday, July 14, 2018 6:07 PM

• Corrupt domain user profile on Win2016 caused similar issue for me.

  To resolve, recreated domain  user profile on Win2016 server: user called <corruptuserprofile>

  1. Login to server with a different admin user account.
  2. Delete c:users<corruptuserprofile>
  3. Navigate registry to HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionProfileList
  4. Examine each SID entry for «ProfileImagePage REG_EXPAND_SZ C:users<baduserprofile>»
  5. Delete SID entry.
  6. Logout
  7. Log in as user <corruptuserprofile> to generate new profile

  Issue resolved.

  • Edited by
    hagen brown
    Saturday, July 14, 2018 6:04 PM
  • Proposed as answer by
    Brandon Tahedl
    Tuesday, August 7, 2018 3:00 PM

• Using GPO, I set this script to run at login and used loopback to only apply it to our RDSH server farm and so far it seems to work. When it needs to run, it finishes in about 5 seconds.

  • Edited by
    ssh-pvi
    Monday, July 23, 2018 8:44 PM

• For me, Matts solution worked.

  Same thing — RDS hosts. Randomly — usually 2 at a time — servers start menu will not open anymore. We are using profile disks. In my case the Packages folder has 15 subfolders. But executing only the install part of Matts script fixes the problem. Let’s
  see — for how long.

  Well. My fun ended. The script worked once.

  After a little while the start menu problem re-apeared. If i run the script again, i receive a bunch of IO Exception errors on installing most of the AppX apps, and the problem will not go away. Restart does not help.

  One thing i noticed. When i press start button — then in the USERPROFILEAppDataLocalPackages
    folder for a moment (maybe 1 second) gets created «Microsoft.Windows.Cortana_cw5n…» subfolder. And then I disappears again. So it led me to believe that maybe it’s a cortana related issue. But disabling cortana did nothing…

  • Edited by
    McWax
    Tuesday, July 24, 2018 9:12 AM

• This did it for me!

  I should’ve guessed it was a corrupt profile. Thanks again!

• The first command on Powershell works to me. Thanks!

• Worked in my situation as well.

• Thanks Matt, your solution worked for me as well.

• Hi,

  does anyone got another solution?

  Nothing of this worked for me. I’m getting a non working start menu on several 2016 Server all the time. This is
  not connected to a single userprofile.

  If I try to re-register the windows apps (Matts solution) I get AppX-Package Error:

  Deployment failed with HRESULT: 0x80073CF9, Install failed. Please contact your software vendor.

  It is not possible to open any «ms-settings*» application like windows-update or Setting Application. Am I the only on who got this issue? Restoring the OS from Backups can’t be the solution all the time

• FYI, the above script did not work for me; there were already 15 folders in the $env:USERPROFILEAppDataLocalPackages location.

• Hi,

  after researching for hours I found a issue in the registry with the Windows Firewall, even if the Windows Firewall was turned off.

  Try to execute this commands in PowerShell, this worked for me. About 10 seconds after executing the commands the start menu should work again, if the problem is the same that I had.

  Remove-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyRestrictedServicesConfigurableSystem"
  
  New-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyRestrictedServicesConfigurableSystem

• Hi!

  I had the same issue.

  Rename or delete 

   %LOCALAPPDATA%MicrosoftWindowsUsrClass.dat

• Copy over

  HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionAppxAppxAllUserStore

  and

  HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionAppReadiness

  from a working 2016 Server (ignore the errors that system has some keys open.

  reboot delete the user profile and login as a new user.

• Hi,

  after researching for hours I found a issue in the registry with the Windows Firewall, even if the Windows Firewall was turned off.

  Try to execute this commands in PowerShell, this worked for me. About 10 seconds after executing the commands the start menu should work again, if the problem is the same that I had.

  Remove-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyRestrictedServicesConfigurableSystem"
  
  New-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyRestrictedServicesConfigurableSystem

  This is crazy, but this is THE ONLY solution that worked for my servers. Before I applied this in <g class=»gr_ gr_61 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace» data-gr-id=»61″ id=»61″>powershell</g> I
  went to this location in the registry and waited over an hour for the records to load until I gave up. Then I applied it and the start menu started working.

• This is the only solution that worked for us. All others failed. 

  Most items in the Start menu reappear except the old 16 bit program references which do show up for Administrative accounts logged into these servers. 

• Incredible that two years later this is still a thing. One of my RDS servers suddenly stopped showing the menu. Reading through this thread, I started by enabliing the search service and that magically fixed it. However, I also followed the link to go create
  default rules for Applocker.

  This did start after I enabled app whitelisting on the server (they’re still being configured, thankfully) to keep my users from spreading every virus and ransomware known to man…

  Of course, just because it works now doesn’t have to mean it will continue to do so., Time will tell.

• Thanks for this, fixed my problem immediately. Well done.

  ---

  Scott S.

• Scott,
  Can you verify what fixed your problem? There are multiple solutions in this thread.

• Clarkry, were you able to get a resolution?  Like you noticed, many users have posted the «fix» but I’m somewhat hesitant to just make changes as there’s not a specific agreement for the true solution with the start menu on 2016 RDS.

  Thanks.

  Ken

• Having the same problem with a recently deployed RDS 2016 farm…  CTRL-ALT-END to sign the user out and when they log back in, things are fine.  A fix would be nice.

• CorbettEnders69, have you tried the PS script from earlier in this post to see if it works?

  Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)AppXManifest.xml”}

• I have not as our packages folder contains 15 items.

• That’s a different script that solves the packages folder issue.  Like you, I’m not seeing the reduction in the packages folders for any of my users when they drop access to the Start Menu or the Taskbar.  I did run the other script last night
  and rebooted the RDS box.  So far, I’ve heard of no issues from my users.

  Ken

• This worked for me!  Thanks!

• SOLUTION:

  Remove-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyRestrictedServicesConfigurableSystem"
  New-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyRestrictedServicesConfigurableSystem"
  Remove-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyFirewallRules"
  New-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyFirewallRules"
  Remove-Item "HKLM:SOFTWAREMicrosoftWindows NTCurrentVersionNotifications" -Recurse
  New-Item "HKLM:SOFTWAREMicrosoftWindows NTCurrentVersionNotifications"

  RESTART SERVER

  • Proposed as answer by
    _z0rg_
    Friday, August 23, 2019 5:55 AM

• Matt’s script has been fixing this for me. Thanks!

• Regardless of qty of packages (we seem to have 15 consistently), the replacement of the ShellExperienceHost is what fixes it.  Any user with a broken menu can run this command and the menu is fixed in their session live.

  Add-AppxPackage -Register «C:WindowsSystemAppsShellExperienceHost_cw5n1h2txyewyAppxManifest.xml» -DisableDevelopmentMode

  So we are going to actual set roaming profiles to delete at log off.  This will clear out that folder completely.  Then the folder %localappdata% should get rebuilt (the local doesn’t roam) and hopefully the problem will go away.

• Mine was simply fixed by creating a new profile.  I had noticed that my profile was over 500mb in size (which is probably why it didn’t load quickly enough to display start menu).

  Simply logged on as Domain Administrator, deleted the profile associated with my user account, logged back on and the new profile was fine.

  • Proposed as answer by
    iamkl00t
    Tuesday, May 28, 2019 11:45 AM

• Not a solution. You’ll soon find it breaking again.

• I’ve spent the better part of the last few months trying to find the solution to this issue.  I’ve read and tried many of the steps suggested by others in this thread.  Low and behold, it was a kid on YouTube who had the fix all along.  While
  this fix is for Windows 10, it works perfectly on Server 2016 Standard.  I’m sure Datacenter too.

  1. Since the Start Menu is not working, open the task manager. 
  2. Click on File—> Run new task
  3. Type PowerShell, and make sure to check the box for «Create this task with administrative privileges”
  4. Click OK
  5. Run the following command:

  Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register «$($_.InstallLocation)AppXManifest.xml»}

  Problem solved.  Thanks to this YouTuber: UnionStarGamers

  I can’t post links.  I haven’t verified my account yet.  

• We’ve ran into this problem on some occasions on 2012 and 2016.

  What we found that fixed it was the Policy «Bypass traverse checking» under User Rights.  If there is only one account here, it will cause this issue.  Our fix is to add Authenticated Users to the policy.

• The start menu on one of my Server 2016 Standard machines had stopped responding. Left clicking did nothing. Right clicking brought up the tasks menu, as usual. I had spent several hours trying various things which one always tries when something weird happens,
  without elaborating. Search worked, so I searched PowerShell, right clicked «Run as Administrator» (necessary) and executed the command you provided above verbatim, with cut and Control-V (paste) into PowerShell. It went to work rebuilding. After
  it was done, I clicked on «Start,» quite frankly not expecting it to do anything. It worked… Fixed! Great tip and thanks to your YouTube guy.

  I thought I would post a comment so others could try this fix. I would be curious to know what happened to cause this problem. There was obviously some corruption issue.  Any input as to causes would be appreciated. 

   

• The registry backup and import  was the only fix that worked for me.

  Pull reg keys from working RDS server, clicked start menu after importing the keys and showed after a few seconds.

  • Proposed as answer by
    bolkware.de
    Thursday, November 28, 2019 12:30 PM

• SOLUTION:

  Remove-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyRestrictedServicesConfigurableSystem"
  New-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyRestrictedServicesConfigurableSystem"
  Remove-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyFirewallRules"
  New-Item "HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyFirewallRules"
  Remove-Item "HKLM:SOFTWAREMicrosoftWindows NTCurrentVersionNotifications" -Recurse
  New-Item "HKLM:SOFTWAREMicrosoftWindows NTCurrentVersionNotifications"

  RESTART SERVER

  in my case this worked

  • Edited by
    _z0rg_
    Friday, August 23, 2019 5:53 AM

• Ok guys, I have tired so many suggestions here but none of them worked for me.  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
  the reboot, the start menu is missing and search bar is not longer working.  After endless research through online and I found article related to windows 10.  https://www.tenforums.com/general-support/48545-windows-10-start-menu-cortana-not-working-being-caused-gpo-2.html

  I checked my existing 2016 server vs 2016 server DC and in fact the ALL APPLICATION PACKAGES is missing HKLMSOFTWARE on 2016 server DC.  Somehow, after joining the DC and reboot, the group is removed somehow.  After adding back
  the group hklmsoftware in the registry.  It is working right away. 

  Also, it looks like event id 5973 and event id 1000 went away as well.

  This fix also apply 2019 server DC as well.  I hope this will help someone in the future and save them weeks for try to resolve this issue.  Good luck!!!

  Update:

  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.   Also, if I demoted the dc back to regular server, then start menu and search bar are working
  again with «ALL APPLICATION PACKAGES» group back in the registry.

  Does anyone know to good way to report this bug to Microsoft?

  • Edited by
    Killachang
    Wednesday, October 16, 2019 1:40 PM

• It worked for me.

  Thank you

  ---

  Thank you, Falcon

• This worked for me!!! Sorry to wake the dead here, but I had to login and comment. This has been vexing me for months, tried lots of stuff as the other posters have. Even a fruitless case with Microsoft failed to fix the inop Start Menu issue. But the
  above script ran with admin via powershell worked right away for me. Do I know why? No. I don’t know how electricity works either but I don’t have research time; only barely enough for this comment..

• Adding the problem user with Full rights to the HKLMSOFTWARE key fixed the problem for me.

  All Users were there with Read Only Access, but when I added the user who was using RDP to this Key specifically with Full rights, the Start Menu and Search bar now function.

• Remove-Item «HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyRestrictedServicesConfigurableSystem» New-Item «HKLM:SYSTEMCurrentControlSetServicesSharedAccessParametersFirewallPolicyRestrictedServicesConfigurableSystem

  worked like charm, thank you

  • Edited by
    Milordas
    Wednesday, February 19, 2020 9:07 AM

• I logged in as a temporary administrator account, went to c:users and renamed the corrupted profile (in case I needed to restore it)  I then re-logged in using the account with the corrupted profile and the start button was working again. However,
  an error message says that I’m using a temporary profile «we couldn’t sign you in». I then log back out, log in as my temporary administrator profile and rename the corrupt profile back to its correct name. Log back in and the start menu is working
  again. (No profiles removed)

  Just be aware that when removing a profile on Windows Server 2016 that you might have some important software running on your server that is using that profile. For example DirSync or another important application so just be aware of this!

  Also, Sophos Lockdown is known to cause this. A work around in that awful situation when you can’t open anything (start menu, powershell etc) is here:

  • Edited by
    dubsdj — MCITP — CCA-V
    Thursday, April 23, 2020 1:36 PM

• Running below on Powershell worked for me without reboot server

  Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode
  -Register “$($_.InstallLocation)AppXManifest.xml”} —

• thx a lot Matt, this did solve it for me as well, using Remote Desktop Manager connected to windows server 2016 version 1607.

• THANKS

  In my server: all users in D drive and this worked for me:

  Get-AppXPackage | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)AppXManifest.xml”} —

• На первый взгляд Windows Server очень похож на Windows 10. Конечно, есть много различий в функциях и совместимости оборудования, но они также имеют много общего кода.
• Меню «Пуск», доступное независимо от выпуска, может не открываться. Отключите полноэкранный режим в меню «Пуск» и убедитесь, что служба поиска включена. Если это не решит проблему, в статье доступны более сложные решения.
• Неотъемлемая часть опыта Windows, а также знаковый символ, Стартовое меню иногда не играет хорошо. Но у нас есть все необходимые исправления.
• Запуск Windows Server может быть постоянной работой. Взгляните на нашу коллекцию Статьи о Windows Server и будьте в курсе событий.

Для решения различных проблем с ПК мы рекомендуем Restoro PC Repair Tool:
Это программное обеспечение исправит распространенные компьютерные ошибки, защитит вас от потери файлов, вредоносных программ, сбоев оборудования и оптимизирует ваш компьютер для максимальной производительности. Исправьте проблемы с ПК и удалите вирусы прямо сейчас, выполнив 3 простых шага:

По-прежнему возникают проблемы?Исправьте их с помощью этого инструмента:

1. Загрузите этот инструмент для ремонта ПК получил рейтинг «Отлично» на TrustPilot.com (загрузка начинается на этой странице).
2. Нажмите Начать сканирование чтобы найти проблемы с Windows, которые могут вызывать проблемы с ПК.
3. Нажмите Починить все исправить проблемы с запатентованными технологиями (Эксклюзивная скидка для наших читателей).

Restoro был загружен 0 читатели в этом месяце.

Часто задаваемые вопросы

• Куда пропало мое меню «Пуск»?

  Если меню «Пуск» перестало отображаться, наиболее распространенным решением является перезапуск проводника. Нажмите клавиши Ctrl + Shift + Esc, чтобы открыть диспетчер задач. Ищу проводник Виндоус в Процессы список. Выберите его, затем нажмите на Запустить снова кнопку в нижнем углу. Это должно вернуть меню «Пуск». Проверьте эту статью, если вы не могу ввести в строку поиска.

• Как исправить, что меню «Пуск» не открывается?

  В Windows Server мы рекомендовали пользователям отключить полноэкранный режим и включить службу поиска Windows. Для Windows 10 см. Здесь, почему стартовое меню исчезает и как это исправить.

• Как мне вернуть свое стартовое меню?

  • в Настройки приложение, перейдите в Персонализация.
  • Нажмите на Панель задач ссылка в левой части экрана.
  • Искать Расположение панели задач на экране и выберите Нижний из раскрывающегося меню. Подсказка: включите параметр «Заблокировать панель задач», чтобы случайно не переместить ее в будущем.

17 Replies