Start Menu Broken Down After Upgrading to Windows 10 Fall Creators Update

I just ran the built in Windows Update Troubleshooter and this was the result.


The only update, besides WD Definition Updates, was a store application which I can't even find installed - 3D Viewer. It must be part of another application, Mixed Reality Viewer perhaps? Funny that after running the Troubleshooter I received another WD Def's update.

 

I am sure it does for you, but I just see continual issues being reported about forced updates etc, so I don't need all that hassle.

 

But have you actually experienced those issues?
Just because a few people are experiencing issues doesn't necessarily mean you will too.

 

Well of course the experience will vary from one computer to the next. But, I've seen very few issues on tens of PCs I've upgraded to or done a clean install of Windows 10 on. I have no issue with the forced updates, as I always want to install every update, rather than picking and choosing what updates to install. Also, I've never had any serious issues arising from Windows 10 updates. The worst thing I've experienced, is that at one point in time, my main computer was unable to install updates, and it would try to install updates at every boot, fail to do so and then rollback the changes. This made boot times much longer, but did not cause any problems with Windows.

I've seen so few issues arising from installing Windows Updates over the last 20 years or so, that I see no need to wait, or read up on potential issues before installing them. Some people have lots of issues with updates, I have close to zero.

 

Sigh. It doesn't matter how many times I shut down or restart today the Start menu will not work. I ran the Start Menu Troubleshooter I mentioned earlier and it didn't find any problems either.

I hate Microsoft!

 

OK, this time Ctrl + Alt + Del > Sign out, then sign back in got the Start menu working... for now.

Edit: I ran Windows Update Troubleshooter and once again this was the result.

 

Store applications failed to update. I wonder if disabling Store application updates would stop this nonsense?

 

Hi,

I'm a new user here, from France.
Figured I had to register to support you, poor Krusty.

FCU 1709 landed on my main machine on Saturday.

Since then, I experienced the very same symptoms :
- No more left click on start menu
- Big latency launching explorer processes
- Message "MS\windows\plug and play device install reboot required" hangs on reboot

Things I tried :
- Last drivers installs => same problems
- Full wipe & clean install of 1709 image => same problems, even after updates

I gave up and ended with a clean install of a 1703 image +last cumulative patch + a "hidden" 1709 update to prevent upgrade (works like a charm).

Some pointers regarding my (fairly old) setup :
- Windows 10 x64 French (Home/Family)
- Asus P5E - Intel Q6600 - 8Gb - Samsung850Evo (Sata3 Adapter card) - 2xCaviarBlack - Radeon 7850 - Xonar STX2 sound card

I suspect some driver is still (will stay ?) broken on 1709.

I'll try again 1709 in a distant future.

 

I am so, so sick of this. Two of my three machines had the bug yet again this morning.

Fix it Microsloth!

 

Krusty I admit that I admire you for still trying to solve this problem. I would give up long time ago.

 

Mate, I did give up on one machine, hid 1709 and used O&O Shutup 10 to stop the upgrade but Microsloth ignored all that and upgraded me anyway. Then I couldn't restore a Macrium Reflect image for some unknown reason, so am stuck with 1709.

 

Sorry to hear this. Did you consider using any replacement like Classic Shell or something similar? I hesitated to use it on Windows 8.1, but I got used to it and now kind of like it.

 

I ran Win8.1 on one machine few a few days last week and installed Classic Shell (which is EOL now) but didn't really like it, not for a Win10 machine anyway. Win10 Start menu has grown on me now. I also ran Win7 on another machine and forgot how nice it was to use and how pretty the Aero looks.

 

I don't know if it is just a coincidence or not but every time I've had this bug a Windows Store application has updated. I've now gone into Store Settings and disabled "Update apps automatically" and will see how that goes.

 

Do everyone that have this issue also have Malwarebytes installed?
https://forums.malwarebytes.com/top...tart-button-not-working-with-mwbytes-drivers/

 

Yes, and a Logitech Bluetooth mouse.

But post #114: https://www.wilderssecurity.com/thr...ll-creators-update.397421/page-5#post-2717115 seemed to fix it for me.

 

I have had this happen on a clean install of Win10 1709 with no other programs installed at all.

 

Never had either Malwarebytes or Logitech and the big 5 month old Y900 was badly messed up by the Fall CU. I tried but there doesn't seem to be much in the way of common denominators software- or hardware-wise, just Windows Fall CU (unless someone comes forward with the explanation). Last time I conjured up this "bug" was via flushing dns and resetting winsock.

 

I do, but I have all real-time protection disabled.

 

I was suspicious of the network adapter a while back already. Does anyone else use Ethernet and the Realtek PCIe GBE Family Controller? I boot the machine before the "handshake" and the boot is literally just a few seconds--this is machine that was crippled by the Fall CU. No problems with start menu/taskbar under those circumstances. The driver's version dates 3/2017--guess one has to wait for any new one, as usual. The other has the Intel network adapter and had no problems.

 

Unfortunately I can confirm that this update (KB4058043) does NOT solve the Start menu bug. The machine with the most recent clean install had it today but strangely I didn't have the Plug and Play driver thing when shutting down.

 

Yes, one machine does but that machine is the least affected.

 

OK, thank you for that info, Krusty. I went to the Lenovo updates page and installed a later LAN driver and the death of the start menu/taskbar returned. Uninstalled it and let the older driver install itself upon reboot. Fix it, Lenovo! lol. Strange: same big problem, with mysteriously different possible causes.

 

But my 'problem' machine is a Lenovo ThinkPad.

@Krusty Are your machines Lenovo?

 

Paul,

One is an HP desktop and is least affected. One is an Acer laptop and is somewhat affected. The other is a low spec Lenovo laptop but hasn't had this bug much since the latest clean install. Once after the Win10 1709 install and once today.