windows Windows 10 Creator Edition

[music_man]

I installed Creators Edition the same day it came out. I never had any problems until today 10/22.

When I turn on the computer and log in as normal, I have no start menu and no search menu. Right-click works fine on those.

So I created a new Administrator account and the start menu and search all work with this account.

Then I put a few tiles on the start menu for this administrator account....

When I switched users back to me, everything worked but I had to clean up the tiles to what they used to be.  Then shut down.

When I turn on the computer again, with my normal user, I again have no start menu, no tiles, no search....again....

I switch users to the Administrator. As soon as it comes up, I switch users back to me again.

Voila....my account start menu, tiles and search are all back up correctly.

 

So my question is:  Why do I have to have the new administrator account running when I want to use my normal account (which is an admin account as well)?  The only way I can use my normal user is by having this new Administrator account running.

[AlTech]

When you say Creators Edition, what update to do you mean?

 

There's nothing formally called Creators Edition.

 

There's the Creators Update (Build 15063 released in April) or the Fall Creators Update (Build 16299 released last week).

[music_man]

Creators Update (Build 16299 released last week).

 

[Kyle_N]

Open Task Manager, More details (if not already fully open), look for Shell Experience Host (under the first tab), in background processes.

 

This app contains the Start menu, Cortana, Action Center, and the taskbar flyouts (network, battery, clock). If you end it, it will restart automatically. This should fix it. 

 

Alternatively you can go down to the bottom of the list, and restart Windows Explorer. It will restart ShellExperienceHost along with it. 

[music_man]

It worked!

Just for info, I found it will also work if you come up with the Administrator, then switch my normal account from admin to normal user. Switch back to my normal account, which is now not an admin. Reset....go back into the Administrator account and switch my normal account back to Admin. Reset, log on as normal and everything works. Maybe there is some subtle difference between an Administrator prior to October and the new update. In any case, your solution was the quickest and easiest so I thank you so much for your help. Hope you have a great day!

[music_man]

OOPS...I spoke too soon. When I turn on the computer and log in, I have no start menu, tiles or search. But right-click works. So I right-click the start menu and sign out. Then I just log back in and everything works. This is a consistent problem. Every time I turn on the computer, I have to do this now.

By the way, when it doesn't work (no start etc), when you sign out you get a shutdown message about pnp. But when its up and running correctly, and you shut down, there is no message.

[music_man]

ok, I've been working on this. It looks like it is some kind of timing problem with my ASUS motherboard.

1) sometimes, I turn on the computer, type my password, press enter and it comes up immediately with everything working.

2) sometimes I turn on the computer, type my password, press enter and it sits on that screen for about 5 seconds and then goes in. If that happens, I have no start menu.

3) If I have no start menu, I right-click on start, switch users and log back in. It comes up right away but the live tiles are not live. In this case I have to sign out and in again and now everything works.

 

When I have no start menu (#1 above) I always get a message about waiting for a pnp device. When I have the start menu and switch users or log off or shutdown, that pnp message doesn't appear. The pnp message only comes up if there is no start menu.

I noticed that things are really slow when #2 above. It's like some process is waiting. I tried typing my password and waiting for about 5 min before pressing enter, but it makes no difference: still no start menu.

I am sure this is an ASUS motherboard problem . I do know that both MS and ASUS are trying to find out what's going on. In the meantime, I'll just keep doing the above 3 steps. It eventually comes up, but it really bugs me.