Windows 10: Start menu does not open after Power Shell Command

So my mail app was not opening links. So I looked up how to reinstall the mail app. Got to this: http://www.howtogeek.com/224798/how-...stall-window...

I uninstalled the apps, then ran the powershell command: Get-AppxPackage -AllUsers| Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”} to reinstall the mail app.

A bunch of red errors appeared in the prompt and now my start menu, notifications, onedrive,... won't work.

How do I restore these functions? sfc also does not work in Powershell but does work in CMD. Also, it does nothing.

:)

 

Problem with Windows 10

What happens when you press the Windows Key on the Keyboard? Does the Start Menu open up?

Also do you get the RUN box to appear if you press the Windows Key + R

How To: Open Windows 10 Settings Using Shell Commands

How To: Open Windows 10 Settings Using Shell Commands

Troubleshoot problems opening the Start menu or Cortana:

Troubleshoot problems opening the Start menu or Cortana

[FIX] Your Start Menu Isn’t Working. We’ll Try To Fix It The Next Time You Sign In.

[FIX] Your Start Menu Isn't Working. We'll Try To Fix It The Next Time You Sign In.

 

File explorer does not open in Windows 10.

Hi,

I have exactly the same problem on Win 10. I recently upgraded from Win 7 64-bit.

The File Explorer does not open. I tried the following:

- Clicking on File Explorer Icon on taskbar.

- Typing C:\Windows\explorer.exe on Run prompt.

The screen flashes for 5 seconds and then nothing happens. File explorer does not open.

While trying various things to solve the problem. I tried changing the screen resolution from 1600x900 to 1440x900.

Apparently, I was able to open File Explorer without any issues in this screen resolution. But then, I noticed other apps i.e. Start Menu, Store, Internet Explorer, was not opening up in this screen resolution. Then I followed some other article which had
a Power shell command (apologies, I missed to save that article). It ran for a while and after that I was able to open Start menu etc.

Also, I had created couple of more user accounts, everything worked fine when I logged as other users.

So, basically, I got 2 workarounds to this problem:

1. Changing the screen resolution.

2. Login as other user.

P.S. : Changing the screen resolution from 1440x900 to 1600x900 recreates the problem (strange behavior with a specific screen resolution).

I'll try to search and post the URL of the article which had the Power shell command to fix the issue (after changing the screen resolution) with Start menu, IE, Store etc.. the command actually fixed all other issues with Start menu, IE, Store etc. but
did not fix issue with File Explorer.

I hope this issue will be fixed in upcoming Windows 10 updates.

Thanks.

 

Hi, unfortunately this seems to be a known bug which MS is puzzled about (from what I read elsewhere) and this is the typical consequence of running this command.

Two options:
1. restore from your most recent disk image. (Everyone needs to use disk imaging - Aomei Backupper or Macrium Reflect - both free - a lesson only learnt after some suffering for too many people, alas).

If you don't use disk imaging (yet) then

2. In place upgrade repair install using a Win 10 installation medium
(See Tutorials for a guide if unsure).