Build 14366 issues detected: Shell doesn't work and Start does nothing

3 min. read

Updated on January 10, 2017

updated on January 10, 2017

Readers help support Windows Report. We may get a commission if you buy through our links.

Dona Sarkar seemed extremely confident in her blog post announcing the Windows 10 build 14366. This build opens the Windows 10 Anniversary Update June Bug Bash, marking the final stages of the Windows 10 build program. The June Bug Bash aims at fixing existing bugs and identifying potential issues not yet discovered.

Judging by the list of fixes and improvements, build 14366 should indeed make the Windows 10 experience smoother.

Here is a short list with the most important fixes this build brings:

Navigating to the Privacy pages in Settings app will no longer crash the Settings app.
Cortana search results have been updated with information about file location.
Full screen Remote Desktop is now available.
An active VPN connection no longer blocks the PC from going from idle into sleep.
Microsoft Edge no longer uses large amounts of CPU when opening a page with many animated gifs.
The battery flyout now correctly reports overall charging state for devices with two batteries.

These fixes really work as Insiders confirmed this on Microsoft’s forum:

Ja, it was a surprise, downloaded and installed. Lots of bugs fixed.

However, not everybody was so lucky after installing buil 14366, as some Insiders encountered serious issues related to Office activation, too much CPU usage and unresponsive Quick Access buttons:

Downloaded and installed, took over two hours so not the quickest install.

Same issues with a non working synaptics driver being installed (easily corrected) Also I notice that Office loses its activation again easily sorted but I’ve not noticed this one before.

Still have an issue with Runtime Broker using way too much cpu, so I wonder when this will get fixed.

My quick access buttons have stopped working again, hopefully like in the last build they will repair themselves!

Unfortunately the issue list doesn’t end here, as another user reported he had to roll back to the previous build in order to be able to use his computer:

Totally borked for me. Shell doesn’t work. Half of taskbar icons are gone. Start does nothing. Task manager takes forever to show anything after not responding. Rebooting is no help. Nothing using cpu or excessive memory. Not certain how roll back, will have to figure out how to do it from the command line launched from task manager.

Had to do “start ms-settings:” From cmd.exe launched from taskmgr. Took forever to do anything. Finally got settings and started recovery to previous build. First time I’ve been forced to roll back.
Roll back to 14361 succeeded and everything works again.

We haven’t detected any particular issues on the computer we installed this build on, but we’ll keep you updated should we find other bugs.

Have you installed build 14366 on your computer? Is it running smoothly or you have encountered issues too?

RELATED STORIES YOU NEED TO CHECK OUT: