- WINDOWS 10 START MENU NOT WORKING 2020 WINDOWS 10
- WINDOWS 10 START MENU NOT WORKING 2020 SOFTWARE
- WINDOWS 10 START MENU NOT WORKING 2020 WINDOWS 7
\TempState\ Add-AppxPackage -register "C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\AppxManifest.xml" -DisableDevelopmentMode Add-AppxPackage -register "C:\Windows\SystemApps\_cw5n1h2txyewy\AppxManifest.xml" -DisableDevelopmentMode Start-Process "explorer.exe" \TempState\ cd $Env:localappdata\Packages\_cw5n1h2txyewy Remove-Item -Recurse -Force. The only thing that helped yet was to start the following command (found it at another post) at the powershell at the users context: taskkill /F /IM explorer.exe taskkill /F /IM SearchApp.exe taskkill /F /IM SearchUI.exe taskkill /F /IM ShellExperienceHost.exe taskkill /F /IM StartMenuExperiencehost.exe Start-Sleep 2 cd $Env:localappdata\Packages\_cw5n1h2txyewy Remove-Item -Recurse -Force. If a AD userprofile (no roaming profile or something else special) was deleted through the "normal" method with deleting the key at ProfileList and the files at c:\users, the startmenu is broken after a new login. I've absolutely the same problem at our customers. I have so far been unable to find any solution to this.ĭoes anyone have any other suggestions? This is clearly a new problem which has emerged with 2004. If the user then attempts to log in again, the start menu is completely broken, and clicking the start button produces the error shown in the screenshot above. The user profile folder and registry key (HKLM\Software\Microsoft\WindowsNT\CurrentVersion\ProfileList) for the user are deleted (irrespective of whether the user account has a roaming profile) logging in and out, then logging in with an admin account and deleting the profile folder/reg key for the test account, reboot and log in again with the test account - and the problem again appeared, so it's not specific to roaming profiles.Ī machine is running W10 2004 and is joined to a domain I then tried using a domain account without a roaming profile - i.e. I then upgraded it to 2004, and tested - and the problem was back. I then set one up running W10 1909, domain joined and tested.
WINDOWS 10 START MENU NOT WORKING 2020 SOFTWARE
I set one up running W10 2004 (no other software installed), domain joined it and tested - and it did exactly as described above, so it's nothing to do with Office 365.
I've carried out some more investigation, using virtual machines. It only seems to affect the W10 (2004) machines - the terminal servers (Server 2016 and Office 365) are not affected, and removing the local copy of the profile doesn't cause this issue on them. This happens if they log in again, even after a reboot - basically it means that the user account cannot be used on the affected computer. When they click the start button they get the following message: What happens is that once the profile and registry key have been deleted as described above, the start menu is completely broken next time the user logs in. It has occurred since we upgraded from Office 2013 to 365, but I don't know whether that's related.
WINDOWS 10 START MENU NOT WORKING 2020 WINDOWS 10
Recently on Windows 10 (2004 version), I've encountered a serious problem with this. Been doing this for years with no issues.
WINDOWS 10 START MENU NOT WORKING 2020 WINDOWS 7
We use roaming profiles, and for many years (since at least Windows 7 days) the local copy has occasionally become corrupt or stops syncing properly, and sometimes deleting the local copy of the user profile folder and the associated registry key for the user (HKLM\Software\Microsoft\WindowsNT\CurrentVersion\ProfileList) works - next time the user logs in, it pulls down the server copy and work again.
0 kommentar(er)
