Windows 10 Start Button Stopped Working

Windows 10 Start Button Stopped Working

After a while of testing Windows 10 and everything running smoothly, I finally encountered a bug which was really annoying. The Windows 10 start button stopped working, it just didn’t open anymore. Luckily, I found a solution after reading some forums.

You have to re-register the package used for the start menu and it’s a four-step solution.

  1. Press CTRL+ALT+DEL and start “Task Manager”
  2. Select “Run new task” in the “File” Menu
  3. Type “PowerShell” and select the checkbox “Create this task with administrative privileges”
  4. Finally, type or paste the following in the PowerShell: Get-appxpackage -all *shellexperience* -packagetype bundle |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + “\appxmetadata\appxbundlemanifest.xml”)}

TIP: CTRL+C and then CRTL+V doesn’t work in PowerShell, instead use CTRL+C to copy and then right-click in the PowerShell to paste!

Hopefully, this will fix any problems with a Windows 10 start button that is not working.

UPDATE: If you also encounter problems with the Cortana search box and/or your metro apps, also run the following code in your PowerShell. This command will re-install all of your metro apps, including Cortana Search.
Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}


Posted

in

by

Comments

5 responses to “Windows 10 Start Button Stopped Working”

  1. Brad Wright Avatar
    Brad Wright

    This didn’t work for me. I the command line you suggested, and it didn’t do anything. If I don’t check the administrative privileges box, I get the expected access denied errors. If I check the box, PowerShell just returns to the C:\Windows\System32 prompt, and does nothing.

    1. robustica Avatar
      robustica

      Hi Brad, could you let me know which build of Windows 10 you are currently using? Also, maybe stating the obvious are you on the main windows account (not a subacccount)? And maybe something went wrong with copy-pasting, I had : connected to the command in the post (changed it now), that will also cause the prompt to return to C:\Windows\System32.

      1. Brad Wright Avatar
        Brad Wright

        I was using 10130, but I’ve updated to the leaked 10147, and no longer have the problem. It was weird with the 10130 build because I was never able to resolve it even with multiple clean installs.

        1. robustica Avatar
          robustica

          Yeah, it’s always tricky with the technical previews, I’m using 10130 at the moment and haven’t had any problems with the start button so far. I think I had the problem in version 9926. Good to hear that the newest update fixed your problem!

Leave a Reply

Your email address will not be published. Required fields are marked *