Microsoft Fixes Windows 10 Anniversary Update Freezing

HardOCP News

[H] News
Joined
Dec 31, 1969
Messages
0
Microsoft says it has resolved an issue that was causing some PCs to freeze after installing the Anniversary Update for Windows 10. Hit the link for instructions on how to fix your rig if you are having this issue.

After the launch of the Anniversary Update for Windows 10, Microsoft received a small number of reports of Windows 10 freezing when signing into Windows after installing the Anniversary Update. With the help of users and MVP’s who posted on this thread an investigation determined that a small fraction of users who had moved app information to a second logical drive could encounter this issue. The Windows Update released on August 31st for Windows 10 includes a fix for this issue. This update is automatically applied when installing the Anniversary Update.
 
they didnt fix my "first boot hit a key to enter password and all you get is a blank wallpaper with no entry window ....reboot second time to get the entry window bug" and it only started once i applied the anniversary update. Even sent in the problem with screenshots and full description to no avail so far. :meh:
 
My problem isn't what happens AFTER the Anniversary Update, it's the fact that 2 of my 3 machines can't actually INSTALL the Anniversary Update. Windows Update no longer shows it ready for download, and trying to install it manually throws an error. I'm gonna have to use the Refresh option to bring it back to its original state and try again.
 
I was going crazy trying to figure out all this freezing B.S.. I guess I will just reinstall Windows later this week to fix it. The update still has my PC freezing.
 
It took me 3 days to finally get the update to install.

I had an activate windows notification and went to settings/update/change key to activate
when I clicked on change key it froze up
2 days later I found a youtube video that worked

type uac in the search block
when the settings come up change to always notify, you can always change it back later
save setting

go back to settings/update/change key and now when you click the block the key screen will come up
enter your key
 
Strange, both of my Windows 7 boxes are running fine. /S

As long as you don't need to re-install Windows 7 and run updates......

The so-called fixes for the slow update problems on Windows 7 don't always help.
Even when I have an old image of the system that is a year or 2 old (I usually make an image for any group of the same systems I roll out at the office), the updates still take forever.
It's almost as if Microsoft has purposely messed up the updating in Windows 7, to make people move to Windows 10.
Windows 10 updates happen almost invisibly.

Lucky we have Enterprise licensing so I can upgrade to the latest (but not the greatest) whenever I want.
I've already done the testing and rolled out a few systems. Except for a group of users that still need access to an old application that doesn't work in 10, I'll be moving everyone to Windows 10 & Office 2016 over the next several months. Already built the base image and tested it on a several laptops. Feels faster than Windows 7 on the same box.
I can take a 4-5 year old laptop, clean it up, drop in an SSD with Windows 10, and the user thinks they just got a nice fast/new system. :D
 
You mean they're going to spy on me, serve me ads, and randomly freeze my computer like it's 1995? Thanks Microsoft!
 
Well, glad they were able to fix it. Now, does anyone know what the specific cause was that they fixed?
 
Well, glad they were able to fix it. Now, does anyone know what the specific cause was that they fixed?


The cause is perpetual-beta Windows 10. And it'll never be fixed because of the duct-tape development culture at MS that has always existed, but has really become evident now that they got rid of the QA team.

Now was not the time for MS to build a reputation of the new Windows as being the one to avoid - on top of all the other problems like data collection, ads, forced Cortana and force-fed updates - as the version to avoid all the more because it's continually breaking.
 
Well, glad they were able to fix it. Now, does anyone know what the specific cause was that they fixed?

The problem is not fixed. Windows 10 is a broken mess.

Could you ask your coworkers when they're going to bother fixing Windows Update for Windows 7? I'm getting tired of the product I actually paid for being degraded while Microsoft wastes time on this crap.
 
I was going crazy trying to figure out all this freezing B.S.. I guess I will just reinstall Windows later this week to fix it. The update still has my PC freezing.
They spy too hard, machine gets on its knees :D
 
good to hear, here's hoping that they fix the random BSODs and freezing issues i have been experiencing since installing the AU :shifty:
 
Microsoft the one and only innovators in this galaxy regarding software updates.
In the age of picking your own updates and installing them as you see fit because you have a clue and that works out all the time Microsoft spoils us with :

What does this button do.

Yep unadulterated fun for all ages when trying to update your computer no idea if it will crash your machine or just run normally (well maybe for now but 3 reboots later ...)

Thank you Microsoft for such an innovative feature ....
 
This affected my laptop after the anniversary update, which has a SSD boot drive and a second drive for storage. The problem for me was that my laptop would not read the second drive correctly, sometimes freezing halfway through a file transfer. But it seems to have fixed its self after the latest update.
 
I hate 10, but avoid the typical 10 bashing that goes on here, but honestly, you all should know better than to install a massive update from MS on day one. I waited about 4 days on my laptop and there wasn't any hint of an issue then so my laptop got the update so I could be prepared on what to expect when I finally did my gaming rig, but once there was news of the fuck up, my gaming rig still doesn't have the AU.

I'll wait about another week now, and if it seems clear then I'll push it to my gaming box
 
The cause is perpetual-beta Windows 10. And it'll never be fixed because of the duct-tape development culture at MS that has always existed, but has really become evident now that they got rid of the QA team.

Now was not the time for MS to build a reputation of the new Windows as being the one to avoid - on top of all the other problems like data collection, ads, forced Cortana and force-fed updates - as the version to avoid all the more because it's continually breaking.

Yada, yada, yada, yap yap yap, your trap..... So, anyone really know what the cause was that they fixed?

The problem is not fixed. Windows 10 is a broken mess.

Could you ask your coworkers when they're going to bother fixing Windows Update for Windows 7? I'm getting tired of the product I actually paid for being degraded while Microsoft wastes time on this crap.

Sorry, I do not work for Microsoft, perhaps you can ask you Apple bosses to make their phones more affordable? Or you Google bosses to make their stuff less spy like?
 
Does anyone know that if I were to update my flash drive with the Microsoft Media creation tool, will it include this update already?
 
In his mind, yes. In the real world? Nope.

I had Google set to only look a year back. I went further and found...

Microsoft's Operating Systems Group reportedly affected "immediately" by layoffs

"What does this mean? Foley has heard that some Windows engineers, "primarily dedicated testers" will be let go as part of the layoffs announced today and that product managers and development engineers could take over some of those testing responsibilities."

Christ Microsoft. Seriously? Developers and product managers dont have time to test, they are doing other things. Dedicated QA people are worth their weight in gold.
 
I had Google set to only look a year back. I went further and found...

Microsoft's Operating Systems Group reportedly affected "immediately" by layoffs

"What does this mean? Foley has heard that some Windows engineers, "primarily dedicated testers" will be let go as part of the layoffs announced today and that product managers and development engineers could take over some of those testing responsibilities."

Christ Microsoft. Seriously? Developers and product managers dont have time to test, they are doing other things. Dedicated QA people are worth their weight in gold.

Wait, so they "may have" let go of some primarily dedicated testers and that equates to letting the whole Q&A department go? You are not personally saying this but, the one you quoted did.
 
Wait, so they "may have" let go of some primarily dedicated testers and that equates to letting the whole Q&A department go? You are not personally saying this but, the one you quoted did.

I know people like you who are MS apologists will split hairs to defend them, but the article listed said 18,000 jobs were cut which were "primarily dedicated testers." So, its safe to assume that Microsoft has far fewer QA people than they used to...which shows in how many problems W10 has had.
 
I know people like you who are MS apologists will split hairs to defend them, but the article listed said 18,000 jobs were cut which were "primarily dedicated testers." So, its safe to assume that Microsoft has far fewer QA people than they used to...which shows in how many problems W10 has had.

No, I was serious, I was not splitting hairs at all. Also, having fewer QA people does not mean they do not still have many thousands doing that job nonetheless. For someone to claim that they let go of their entire QA department was disingenuous at best. (Not you, just saying.) Unfortunately, things happen and we have to deal with them. I am more curious what the fix specifically addressed that no one has yet been able to answer. (Not the issue but the cause and solution.)
 
The problem is not fixed. Windows 10 is a broken mess.

Could you ask your coworkers when they're going to bother fixing Windows Update for Windows 7? I'm getting tired of the product I actually paid for being degraded while Microsoft wastes time on this crap.

They did fix it but per typical MS they half assed it. The problem is you have to manually install it to get any benefit. Hell it's not even a mandatory KB. It's optional. -.-

You need KB3172605 in order to fix the "Checking for updates" forever issue (assuming that's the pain in the ass bug you're talking about).
 
They did fix it but per typical MS they half assed it. The problem is you have to manually install it to get any benefit. Hell it's not even a mandatory KB. It's optional. -.-

You need KB3172605 in order to fix the "Checking for updates" forever issue (assuming that's the pain in the ass bug you're talking about).

Thanks for that KB. Unfortunately, that particular one says that it is not needed on the computer I am servicing. (Yep, I did try the proper 64 bit one.)
 
Microsoft the one and only innovators in this galaxy regarding software updates.
In the age of picking your own updates and installing them as you see fit because you have a clue and that works out all the time Microsoft spoils us with :

What does this button do.

Yep unadulterated fun for all ages when trying to update your computer no idea if it will crash your machine or just run normally (well maybe for now but 3 reboots later ...)

Thank you Microsoft for such an innovative feature ....

Are you in some prior "age"? OS'es are moving toward the all or nothing approach, especially mobile which is used by more and more and a major "computing" device.

I completely understand the frustration;"I used to be able to just not install that one update". While true in this stage, imo this is somewhat short sighted. MS's catalog of individual updates is massive and frustrating to manage. Sure you can skip update A but are you keeping track that is has been updated to update B 2 months later? Probably not. Gotta rip that band aid off sooner rather than later.

While obviously MS releases some broken stuff (who doesn't), vendors are also to blame with the liberties they take because MS "allows it". The all or nothing approach in combination with virtual/sandboxing should actually make bugs easier and faster to fix once vendors get on the ball. It's a paradigm shift just like Vista was a major shift in driver handling which caused a lot of similar growing pains.

Once vendor apps become dead in the water they might pay a bit more attention to what is going on and be proactive. I personally am sick and tired of a vendor telling do open security or some other stupid setting because they were lazy with their program and don't want to fix their bad apps.

At work we have a Dental app that just recently announced due to "demand" it will finally update its crap to support .NET 4.6.+ and Windows 10. It shouldn't take a massive amount of customers to bitch to you in order for you to update your app for a released OS or current framework version YOUR app relies apon. If you want to be lazy with your app fine than make it as standalone as possible, FYI to vendors just let you know people install other software on their computers not just yours dipshits.
 
I know people like you who are MS apologists will split hairs to defend them, but the article listed said 18,000 jobs were cut which were "primarily dedicated testers." So, its safe to assume that Microsoft has far fewer QA people than they used to...which shows in how many problems W10 has had.

Maybe the quality of their software is so good now, they no longer need so many testers :p
 
Are you in some prior "age"? OS'es are moving toward the all or nothing approach, especially mobile which is used by more and more and a major "computing" device.

I completely understand the frustration;"I used to be able to just not install that one update". While true in this stage, imo this is somewhat short sighted. MS's catalog of individual updates is massive and frustrating to manage. Sure you can skip update A but are you keeping track that is has been updated to update B 2 months later? Probably not. Gotta rip that band aid off sooner rather than later.

While obviously MS releases some broken stuff (who doesn't), vendors are also to blame with the liberties they take because MS "allows it". The all or nothing approach in combination with virtual/sandboxing should actually make bugs easier and faster to fix once vendors get on the ball. It's a paradigm shift just like Vista was a major shift in driver handling which caused a lot of similar growing pains.

Once vendor apps become dead in the water they might pay a bit more attention to what is going on and be proactive. I personally am sick and tired of a vendor telling do open security or some other stupid setting because they were lazy with their program and don't want to fix their bad apps.

At work we have a Dental app that just recently announced due to "demand" it will finally update its crap to support .NET 4.6.+ and Windows 10. It shouldn't take a massive amount of customers to bitch to you in order for you to update your app for a released OS or current framework version YOUR app relies apon. If you want to be lazy with your app fine than make it as standalone as possible, FYI to vendors just let you know people install other software on their computers not just yours dipshits.

Microsoft made such a mess of things that they can't even update their OS without breaking important things.

If Microsoft took a better approach to windows 10 and diverged certain features to where they would be less critically dependant and yet they did not do it. It is one big mess as any other windows "operating system".
 
Thanks for that KB. Unfortunately, that particular one says that it is not needed on the computer I am servicing. (Yep, I did try the proper 64 bit one.)

This is what has worked for me for getting Windows Update to work correctly/quickly on a reloaded Windows 7 64bit box using factory image from 2 years ago. Just did this yesterday.

- Go to Windows Update settings and set it to never check for updates.
- Install the following updates manually: KB3078601, KB3109094, KB3138612, KB3145739, KB3164033, KB3168965, and KB3177725
- Restart computer
- Open Windows update and change setting back and run the check for updates . Only take 10 minutes or so now instead of all day.

Hopefully this will help you/others was well.

I found this on the web somewhere but don't have the original link.
 
my sony laptop froze at 32% (CPU was probably running at 100% cause the laptop was hot.) the update reverted back to windows 10. Thanksfully I didn't loose anything, I don't have much third party apps installed.
 
They did fix it but per typical MS they half assed it. The problem is you have to manually install it to get any benefit. Hell it's not even a mandatory KB. It's optional. -.-

You need KB3172605 in order to fix the "Checking for updates" forever issue (assuming that's the pain in the ass bug you're talking about).


Yes thats the problem, and no, they have not fixed it. There seems to be a new kb 'fix' every month that works for a bit and stops.

Microsoft knows perfectly well what's going on. They just don't care.
 
I completely understand the frustration;"I used to be able to just not install that one update". While true in this stage, imo this is somewhat short sighted. MS's catalog of individual updates is massive and frustrating to manage. Sure you can skip update A but are you keeping track that is has been updated to update B 2 months later? Probably not. Gotta rip that band aid off sooner rather than later.
You say that approach is short-sighted, but that entirely depends on the situation. Forced updates are only a good thing if nothing goes wrong. If a new update comes out that causes one of your programs not to work properly and it NEVER gets fixed, you're SOL. I've personally had this happen to me on 7, which is why I'm so wary about 10. Just because a problem may not affect the majority of users doesn't mean anything if you're in the minority where something goes wrong and you can't use your system. Manual updating is indeed a bigger pain in the ass, but there are safeguards with it too. At least with manual updating I know I can ALWAYS use my system as intended when I need it, with forced updating I have no such guarantee as it's always changing.
 
my sony laptop froze at 32% (CPU was probably running at 100% cause the laptop was hot.) the update reverted back to windows 10. Thanksfully I didn't loose anything, I don't have much third party apps installed.


My laptop also froze at 32% but it did not revert and I had to do a total wipe of the hard drive. I found out later it was the audio software. Now I've been getting BSOD every time I unplug my mouse with the new update.
 
Back
Top