Unable to search or click START after upgrading to Windows 10 Home

*Moved the thread*

Hello,

A couple of days back I upgraded to windows 10. I upgraded from Windows 7 to 10 successfully and no problems. After that today I open my laptop and I have a black screen. I move my touchpad thinking I'm going to get to the login screen but still nothing happens. I hit the power button on my laptop to shut down and it does that. I turn on my computer I'm able to get to the login screen. I put my password then I see a black screen. I have IObit Advanced SystemCare so in the corner that's what I see but the rest is black. I wait for a while nothing happens then shut off the pc. Same thing happened and then I think at the third or fourth time I turn on my computer then go to the living room and come back and it's fixed. I play Minecraft so I was doing that. I also have a touchpad issue where when I hold the keys down I can't move my mouse but I already know the solution for that and so when I go to click the start button nothing happens. I was confused and thought maybe it was just slower than normal. I clicked the search button; nothing happened. I then search up on the web "unable to click start button on windows 10" and I find a post with a solution but wasn't really for me:
---------------------------------------------------------------------------------------------------------------------------------

1. Open Windows PowerShell as Administrator
   
   1. Right click Start button
   2. Choose Command prompt (Admin)
   3. Key in Powershell in the black window and hit Enter
   
   
2. Paste the following command in the Administrator: Windows PowerShell window and press Enterkey:Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
3. Wait for PowerShell to execute and complete the command. Ignore the few errors (in red color) that may pop up.
4. When it finishes, try hitting Start and hopefully it’ll start working. If not, this solution won’t apply to you, unfortunately.

---------------------------------------------------------------------------------------------------------------------------------

This didn't actually work I have my cmd open still and nothing has happened. Anything else that can resolve this issue? Any help is appreciated!

Any help? :'(

I believe I have the solution to your problem, which would be to create a new admin account through the cmd prompt.
Ctrl+Shift+ESC then run prompt as an admin.

http://operating-systems.wonderhowto...ndows-0125689/

seagula said:

I believe I have the solution to your problem, which would be to create a new admin account through the cmd prompt.
Ctrl+Shift+ESC then run prompt as an admin.

http://operating-systems.wonderhowto...ndows-0125689/

But then wouldn't I be losing everything I have on my current account??

No it just makes a new user that has a cleaner startup process, you can always go back in explorer and copy your user files back over to the new account.

Vatsan said:

But then wouldn't I be losing everything I have on my current account??

seagula said:

No it just makes a new user that has a cleaner startup process, you can always go back in explorer and copy your user files back over to the new account.

Ok, how can I make a new user? And will it be the new admin?

I had this problem several days ago and I tried the "Get-AppXPackage" command you mentioned in your first post and it did fix the issue.

From the source I found the command, the poster also recommended that:
1. try to run the command several times if you see some errors (in red color);
2. reboot after the command finishes.

seagula said:

I believe I have the solution to your problem, which would be to create a new admin account through the cmd prompt.
Ctrl+Shift+ESC then run prompt as an admin.

http://operating-systems.wonderhowto...ndows-0125689/

I've just done this but now how exactly do I switch to the other user?

cameos said:

I had this problem several days ago and I tried the "Get-AppXPackage" command you mentioned in your first post and it did fix the issue.

From the source I found the command, the poster also recommended that:
1. try to run the command several times if you see some errors (in red color);
2. reboot after the command finishes.

It never did finish, or I wasn't sure when it did.

Different user just press windows key + l to lock it then click on other user and try to login