Win10 Anniversary Update 14393.222 slays many small bugs, but three biggies remain

Topic

New Reply

The new build tackles dozens of little bugs, but three big ones – installation failures, disappearing disks, and frozen network shares – are still the
[See the full post at: Win10 Anniversary Update 14393.222 slays many small bugs, but three biggies remain]

Reply | Quote

Replies

And there are also some AppReadiness issues that didn’t get mentioned in the main article. They appear to be version mismatches for two SystemApps: Microsoft.AccountsControl_cw5n1h2txyewy and ShellExperienceHost_cw5n1h2txyewy

Reply | Quote

Hi Woody! If you recall, I was the one who had to wipe and reinstall Windows 10 AU on a secondhand laptop. Luckily, my system seems to be free from most of the problems plaguing AU.

One question, I need to run Windows Update to grab some drivers so should I grab this new update or hide it using wushowhide?

Reply | Quote

I’d say hide it. Not enough there – and those three big problems are… big problems.

Reply | Quote

Thanks! Not counting all the bugs, I actually quite like the new stuff in AU. It’s a real shame that after almost 2 months installing it feels like playing Russian roulette.

Reply | Quote

This may be a total coincidence . . . but I’m experiencing a pattern on my test machines when trying to install 14393.222 aka KB 3194496.

So far this week, the test machines with a single hard drive and ONLY a C: drive partition have installed KB 3194496 without issue.

On the other hand, all of my multi-drive or multi-partitioned workstations have failed this update during the boot up segment of the patch process. They roll back, reboot again, then after logging in attempt to install again. None of them have succeeded yet.

Even more aggravating is that turning off the release/slow/fast preview ring for 5 days has not stopped these machines from attempting to install this patch over and over again.

Can anyone else corroborate this behavior of single drive versus multi-drive patch success or failure?

~ Group "Weekend" ~

Reply | Quote

So much for the coincidence regarding patch failure on multi-drive systems. one of my test machines with two physical drives just succeeded at applying this patch. The others are still failing today though . . . no rhyme or reason to it that I can discern.

~ Group "Weekend" ~

Reply | Quote

Hi Woody,

Question, how long will the Wushowhide tool hide Ver. 1607 before I am forced to upgrade to it? Both my systems Win 10 pro desktop and Win 10 home laptop are both running fine. I would rather keep Ver. 1511 and don’t see anything that I need or want from Ver. 1607. The pro system has 1607 defered, so I think I’m good till about December. I’m really more concerned with the home system given that it does not have Group edit or the ability to defer using
Settings>Update and security section.

Reply | Quote

Wushowhide should work forever, as best I can tell.

Reply | Quote

Woody,

For Kennedy, shouldn’t Noel C’s tool (program) he offered to us Home Premium ver 1511 users prevent the download of anything that appears ready to download until Kennedy hides it with Wushowhide? On April 8 you gave instructions on how to obtain and install it.

Installing Noel C’s tool combined with Wushowhide has eased some of my horrid uneasiness with Win 10 updates–that is until you give the go ahead to install, then I get all tied up in knots inside again, but so far so good!

Having only 1 computer is really the pits in this era of MS unleashing an unproven product on people/business, and worst of all, on those of us who just chose fields other than computers or just want to be a simple user. Microsoft has stolen that from people too because no computer is reliable for any length of time with these buggy updates that disrupt whole systems.

So many people I know with 7 and 8 just have updates turned off. They feel their anti-malware programs are safer bets than relying on MS who will destroy what they have as a functioning tool/computer. Those of us with 10 just are not a happy set of customers.

Reply | Quote

Hey, @K

Thanks for reminding me! I did download Noel’s tool, but since my systems have been updating smoothly, I have not needed any extra help. The Wushowhide tool on the home system and Group policy edit on the pro system has been doing an OK job so far.

Reply | Quote

KB 3194496 installed fine on my laptop, and so I thought on my desktop ! Installed ok and I restarted, everything seemed ok.

However, when I went to shut down the desktop, it got stuck in the Getting Windows ready screen.

After leaving it for an hour or two, I had to do a hard shut down. Thanks, MS !

Since restarting, everything seems to be working, but who knows with the lottery that is MS updates, nowadays !

Reply | Quote

I noticed there were a lot of drivers, like chipset drivers, that showed up in wushowhide but does not appear when I run Windows Update. Is this normal? Not sure if this is the cause but I only hide KB3194496 and the servicing stack update KB3176936.

Reply | Quote

If it was a regular Windows Update, based on your description it looks like TrustedInstaller.exe did not shut down correctly and got stuck.
As MSE update is not a regular WU update but rather behaving like an external associated application (Microsoft Update vs Windows Update), think Office and .NET Framework 4.x on Windows 7, I can’t precisely say that it was TrustedInstaller, but it is still likely.
If this was the case, you would not have further issues or side effects.

Reply | Quote

Hello to everyone , i am reading all informations from this site and i must say i am currently on 1511 latest patch without any issues(btw its gaming pc , and i am sorry for my english) my huge problem was system freezing after few moments after boot on au update, and i run into one silly solution for slow login on 1511 build found on youtube its simple you just uncheck autohide taskbar and voila my pc now boots to desktop under 10 seconds (with ssd). Thank you all and Woody for sharing solutions and advices for windows problems.

Reply | Quote

I put this on the Facebook page last week, but nothing came of it.
I have the wushowhide plan installed. One morning, I hadn’t even checked for updates, but when I came back after lunch my computer wanted a re-start and sure enough I now have 14393.222 installed.
This evening I was using Edge and it locked up and said I had a virus, not to delete the page and to call a number. I just forced a shutdown and waited. However, when I came back to Edge the same thing happened. My Firefox is working just fine.
Any suggestions?

Reply | Quote

I don’t check the Facebook page nearly often enough. Far better to post here or just send me an email.

Sounds like Edge is sitting on a bogus web page. Try opening a different web page or – better – using Chrome or Firefox.

I don’t think I’ve ever seen a time when wushowhide didn’t work – but it’s entirely possible that MS re-releases patches, thus overriding wushowhide. But wushowhide has to hide a specific patch, identified by KB number. That’s the trick with using wushowhide – you have to know the patch you want to block before you can block it.

http://www.infoworld.com/article/3053701/microsoft-windows/block-windows-10-forced-updates-without-breaking-your-machine-part-2.html

Since KB 3194496 (the “patch” that upgraded you to 14393.222) was released on the 29th, you would’ve had to specifically use wushowhide to block KB3194496, and you would’ve had to use it on the 29th.

Reply | Quote

Hi,ch. Yes, it seems likely it WAS the Trusted Installer.

Does anyone trust anything from MS ?

Reply | Quote

Only their own installer which is by definition “trusted”

Reply | Quote

KB3194496
We couldn’t complete the updates. Undoing
changes. Don’t turn off your computer.

Note: When performing the following, log in with the built-in Administrator. If needed and this was not done before, enable the Administrator account and set a complex password. This is the only account with full access to the system but without access to any of the Universal Apps, which is by design. It is meant to be used only for critical administrative tasks and not on a daily basis.

Solution:
http://www.ghacks.net/2016/09/30/cumulative-windows-10-update-kb3194496-installation-issues/

Delete the folder C:WindowsSystem32TasksMicrosoftXblGameSave on the system. Please note that you can only do so with elevated privileges.
Delete the Registry key HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsNTCurrentVersionScheduleTaskCacheTreeMicrosoftXblGameSave

Once done, retry to install the update. Reports indicate that it should install fine now. The folder and Registry key are re-generated automatically by Windows. We suggest you back up the folder and Registry key before deleting them just to be on the safe side of things.

Reply | Quote

Check my other post. I experienced the same issue but it worked correctly after following the procedure presented. It looks like some permissions are missing or there is a timing error when KB3194496 fails.

Reply | Quote

So the Anniversary Update downloaded and installed itself before I knew this was going to be a problem, and made my desktop super unresponsive and slow on a day that– surprise!– I needed it to get a lot of things done. I was waiting minutes between clicks and for programs to open, which turned my machine into a practically useless piece of junk.

Today I rolled back the system to the previous build, grabbed wushowhide to hide the AU update, and used Noel C’s tool to change the registry update settings… but it had already started downloading the AU update again (even though I had also switched my wifi connection to metered, too) and has scheduled it to install, despite my checking the registry to make sure those changes were correct.

…Is there any way to stop it from installing again? And if not, is there anything to be done about the ridiculously laggy performance issues? At this point I’ve pretty much decided to try and rake up the cash to jump the windows ship and buy a mac, but I need it to actually function in the meantime.

Reply | Quote

Once the install has been scheduled I don’t kn ow of a reliable way to abort it. There should be a way, but I haven’t seen it.

The easier method is to just let it install, then immediately back it out using Start > Settings > Update & security, on the left choose Recovery, then under Go back to an earlier build click Get Started. I’ve used that several times, and it seems to work.

Make sure you block the update when you’re all done.

Reply | Quote

In my experience, yes.

However, if you really want drivers from Microsoft, there is always the Device Manager way to get them, and you could check to see that you haven’t used Advanced Settings to decline all driver updates in Automatic Updates.

Personally, I would get drivers only from the PC manufacturwer, not from the individual component manufacturers. Generaic drivers can be as harmful as Microsoft Drivers on some systems with OEM variants.

And as many experts advise, for drivers — if it ain’t broke, don’t fix it!

Reply | Quote

Works for me, too on three Win 10 Pro PCs.

Reply | Quote

Distrust by default. Applies to almost anything in tech these days. Even when trusted, trust but verify periodically.

Reply | Quote

Or to put it anohter way, run the entire wushowhide series just ahead of opening up the Metered Connection, if applicable. That avoids surprise patches like this one. That’s what I do, and at worst I may have to reset MS Updates to get the newest paatches to show up in my intentional runs.

Reply | Quote

When applied before the download, Metered Connection and wushowhide do block the AU for me on two PCs. (The NUC was built after the AU came out, so it has the AU, for better or worse.) But i should emphasize that I run wushowhide just before opening up the MEtered Connection, not the other way around. All available updates still show (unless my DNS is acting up) but nothing can automatically download at that point.

Woody is right that once an update is scheduled for installation, it is too late to stop the installation. Rolling back by whatever method and trying to block the update from the previous system state is the best I can offer for a solution.

Hence my continued use of system imaging before messing with MS Updates.

Reply | Quote