Windows Start button no longer works after driver install completes

[wumpus42]

I've used NVCleanstall on three machines (1 Win10Pro desktop, 1 Win10Home desktop, 1 Win10Home laptop) to install NVCleanstall's "Recommeded" driver options. On each of the three machines the Windows Start button no longer responded after the nvidia driver installation had completed and I'd closed NVCleanstall. Left--clicking the start button does nothing, but right-clicking it allowed me to restart the computer(s) which caused the Start button to behave normally after reboot.

 

[W1zzard]

First time I hear about that. Anyone else encounter the same problem?

 

[wumpus42]

I'll attempt to re-produce and document. Maybe it's a local environment thing. Seeing as how there's a work-around, it's not really that important.

 

[jsfitz54]

First time I hear about that. Anyone else encounter the same problem?

Yes, I've had the same experience for the last few builds. I just reboot when the install finishes and all goes back to normal.

 

[FordGT90Concept]

I have the same exact problem whenever I update graphics drivers (Windows 10 1903). I just hit CTRL+ALT+DEL and click restart. When the computer comes back up, it's fixed.

 

[W1zzard]

I have the same exact problem whenever I update graphics drivers (Windows 10 1903). I just hit CTRL+ALT+DEL and click restart. When the computer comes back up, it's fixed.

Even without NVCleanstall?

 

[jsfitz54]

Even without NVCleanstall?

Happens with NVCleanstall with Windows OS 1909.

Have not tried standalone NV installer since starting using your utility.

 

[FordGT90Concept]

Even without NVCleanstall?

Never ran NVCleanstall. It's been happening since at least November with almost every driver update. Not even the Win key works to bring up the start menu.

One can use Task Manager to restart explorer.exe which fixes it, but easier just to restart.

Have not tried standalone NV installer since starting using your utility.

Try it, might happen regardless of NVCleanstall.

 

[bobbybluz]

You can create a direct shutdown shortcut by right clicking > New > Shortcut then enter this in the text box: shutdown.exe -s -t 0
To create a restart shortcut do the same as above and enter -r instead of -s.

 

[newtekie1]

I think this is a bug with nVidia's drivers or maybe Windows itself freaking out when the GPU is disabled briefly during the driver install. Because I've noticed it when installing the nVidia drivers without NVCleanstall too.

One can use Task Manager to restart explorer.exe which fixes it, but easier just to restart.

I just log out and back in again.

 

[Japie073]

It happens whenever graphics drivers are installed no matter which gpu vendor this always happens. At work when doing clean installs on the latest WinX build this happens all the time. Just use the Winkey+X and restart from there and it's fixed.

 

[W1zzard]

Good so not a nvcleanstall problem.

Does this happen every time or only sometimes (on affected systems)?
If always, might be worth exploring to add something like "restart explorer" to nvcleanstall

 

[Japie073]

It happened with systems using Intel igpu's (Lenovo E590, E560, L540 etc.) also systems with a Radeon RX550M (Lenovo E590) a GTX 1060 6GB so not a nvcleanstall issue. Generation or model does not matter it happens all the time. This might be something with the Windows UWP platform or the Generic display driver, win7 works fine.

Also don't think it's specific to systems. Noticed it happen on 1903 and 1909 builds.

 

[Calmmo]

It happens on 1909 on pretty much every recent nvidia driver update.
Just a classic ol'bug. Kill explorer.exe and run it again, there's no need for shutdowns.

 

[FordGT90Concept]

Good so not a nvcleanstall problem.

Does this happen every time or only sometimes (on affected systems)?
If always, might be worth exploring to add something like "restart explorer" to nvcleanstall

The only way I made it not happen is by spamming the start menu as setup installs the new driver but, that's just a theory.