Windows 10: Fall creators upgrade messed up my system

id revert back to 1703 for now
the bugs with 1709 are just horrible.

 

Weird! Strange too. I've updated to the Creator's Fall Update on three computers & have had zero problems. Why is it always me that is left out of the problems like this. The only thing I can whine about is the Windows.old Folder is still there but only with a massive 76 kb's. Plus, when I updated on the three machines, I had & have Norton Security on each with none of them deactivated. Sometimes it has me thinking some have been hacked by Klingon's or someone similar.

 

This stupid problem resolved after instal "Kaspersky Anti-Virus".

 

By me after 1 month everything still OK.

 

The problem *Sad has returned, so i have now "Classic Shell".

Settings/Start button/Custom button/Button size: 44

 

Boy, look at the vast amount of replies you've received here. Did you ever get his resolved s1p0?

 

I had similar misgivings about CU and FCU. My new (April 2017) box wanted to install CU last spring. I disabled that.

It wanted to install FCU some months later. I implemented a registry mod (the "metered" thing) to prevent it.

But now with the spectre of Spectre (and Meltdown) I thought it wise to accede to House of Microsoft and jump in and allow FCU to do its deed. (I thought the Meltdown/Spectre fix would only be available on updated systems ... those with FCU or CU. But it seems I was wrong. The fix is available for Win 10 Anniversary and it precedesors, too.)

FCU installed with almost no issues.

1. Classic Shell immediately popped up a dialog saying that it was "adjusting" its configuration to suit, and it did so in a couple of seconds. No problems.

2. The desktop icon size/spacing was altered a bit, but I fixed that quickly.

3. Behavior of some of the context menu items (which I've customized heavily) were altered a bit, but no big worries.

So I count myself lucky.

My wife's laptop updated to FCU about a month ago. She was not aware of it. Since I seldom use it I didn't notice until much later. There were no problems.

Lucky for us! But I still have to agree with xXWhackerXx:
"I really wish MS would stop using the word update when every 6 months it's a full-blown iso replacement."

 

I've not had such success. My HP Laptop got corrupted with a virus (my mistake -- from using FREE WiFi!) and I had to go back to October backup to get a clean reinstall. That worked fine for several days, so I thought I would do the FCU by mounting an ISO.

That appeared to go OK at first, but then, I started having problems in two areas:
1) Raimeter would not work properly on the second account
2) My using an HDMI cable to connect the laptop to my Sony Bravia TV no longer worked properly. I got Video but no Audio. Seems the Upgrade messed up the devices and I could find no way to fix that.

So, I reverted back to 1703 and everything is working OK again.

And, yeah, I know I COULD do a Clean-Install, but that is a LOT of work, and at this point, I might just wait until the next Windows "version" in the Spring and do a Repair-Install then.

 

I was having this same problem on one of my computers after performing a clean install of latest version of 1709. The only way I could fix this was to move my main boot drive to Sata port 0. If it was on any other port then it would boot and start, mouse, taskbar, nothing worked. I have seen a lot of strange things installing this latest version.

 

Version 1709 is by far the WORST Windows 10 update to date! If your stuck on 1709 with no way of going back to 1703 then follow these steps if your ok with modifying the registry to fix this stupid 1709 bug:

- add a DWORD (32bit) "DelayedAutostart" and set it to 1
- add a DWORD (32bit) "AutoStartDelay" click on Decimal and set it for 60 (for 1 minute)

I found this to be the only fix for the Start Menu, Cortana & the Action Center that doesn't have the problem re-occur. Start Menu & Cortana work instantly without delay, but Action Center is delayed for me for the 60 seconds I set it to. Keeping my fingers crossed this workaround will continue to work for me & others out there too.

BTW: Give up on thinking reinstalling programs alone will fix this problem, it wont, the problem will re-occur after the next Microsoft update or program installs you do. This was the only way I could fix the problem for good. It looks like this problem is not going away in 1709 anytime soon, so I'm hoping that 1803 is better than this crappy update.

 

Guess a location to add these registry tweaks might help.

"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WpnUserService"

- add a DWORD (32bit) "DelayedAutostart" and set it to 1
- add a DWORD (32bit) "AutoStartDelay" click on Decimal and set it for 60 (for 1 minute)