Windows 10 Anniversary Update Rollout May Not Be Done Until Early November (zdnet.com)
Microsoft released Windows 10 Anniversary Update last month. But the trickling of the company's latest major update users could take as much as three months, the company has said. Many users have been complaining about not seeing an update pop-up on their system. When ZDNet's reporter Mary Jo Foley asked Microsoft about this, the company confirmed that it hadn't seeded the update to all Windows 10 users. From the report: Microsoft began rolling out the latest version of Windows 10, the Anniversary Update, on August 2. At that time, Microsoft officials said the rollout would be staggered, but didn't get too explicit as to how -- or how long it might take the company to push Windows 10 Anniversary to consumers and business users who are on the so-called Current Branch of Windows 10. It's worth repeating that those who really want the Anniversary Update immediately have options to proactively go get it. I received a Microsoft blast email just over a week ago that included a footnote that mentioned it might take up to three months for Microsoft to push the Anniversary Update to those set up to get it. That means those currently waiting may still have another month and a half to wait.
I want more government spying now!!!
I haven't been able to update since day one. It constantly downloads, reboots whenever it likes, installs, fails, rolls back, reboots, then tries all over again. I'm glad i don't use it for anything but playing a game and some work related stuff else I'd be even more disappointed. Maybe one day I'll try to reinstall it but for now I just don't care
This is a good thing right?
Maybe Microsoft wants to roll it out slowly because it did not do enough QA on the release to assure it would be a smooth release cycle. So the early ones to get it are likely the real-world testers.
Despite an update to the update Microsoft claims fixes the system freeze, I have yet to get Anniversary update to work correctly. Freezes my entire machine a few minutes after login. Here's hoping there's an update to the update to the update.
ralphbarbagallo.com
Hey, if they pushed the update to everyone at once, they'd put a big load on the servers - which would undoubtedly crash, since they're running Windows.
First they complain about the update popup bugging them, now they miss it.
Get your ass into gear and migrate to Linux, we only have 2 more months before our computers get bricked.
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
Anyone figured out where they moved the "Password protection on wakeup" setting to in the AU?
I have a lot of computers with no password so the prompt is just a PITA.
Minimum threshold fixed. Thanks!
It was rolled out to newer systems with UEFI and Secureboot first. My new laptop got it day one.
If you use the media creation tool it will create a windows 10 ISO/DVD/USB drive with the anniversary update (Version 1607) already installed.
The big releases are pretty much a reinstall anyway - The entire OS get swapped out during the update. One of the reasons they are going these "big" releases is so you don't end up with the problem of previous windows versions - IE the latest official media (Win7 sp1, win 8 RTM, or win 8.1 RTM) All have 150+ updates or more after a clean install.In win7's case you end up downloading 2x more data than the original size of the win7 media itself.
Another problem with all those updates is you run in to platform constancy issues. After hundreds of updates something can go wrong, and you end up with situations like windows update being broken out of the box. Big releases are a periodic refresh that gets everything back to a reference point. Do that at least once a year and updates are easier to deal with.
I would really prefer that this not happen.
I run grub, which has killed previous updates. Microsoft needs to have greater respect for the operating systems that I have installed on my PC. If I have to lose one, I'd prefer it not be Linux or BSD.
Bye Microsoft.
Why not call them SP's or even windows 10.X then?
Just to make things easier for people to do a quick check to see what ver they are running?
I wish I didn't get the update. I happen to have one of the systems that gets 30 second random pause/lockups after updating. Even after a complete wipe and fresh install I still have the issue.
Once again Micro$oft reminds us that if you are happy with your computer - and it is doing what you need it to do - think through the consequences before updating.
Mine was a video editing computer. Currently it's only good to get email. Sometimes.
We are not married to Windows 10 you know.
Windows? Microsoft? What are these? I suspect its a OS-wanna-be kind of thing... well, who cares...
Ah, yes...another person suggesting the installation of a security/stability nightmare...
Open action center, click updates, click more info about updates. It takes you to a website describing the anniversary update and a manual install file.
Why not not upgrade now?
Ah, yes...another person suggesting the installation of aNOTHER security/stability nightmare...
I have the Anniversary running on 3 computers since the first week of general availability. After the last update, one of the computer's task bar would be unclickable if I left the computer running more than 3 hours. Haven't had time to track down the problem but I'm going to guess it's because of GeForce Experience. GE has been so problematic for me. If I started after running a game it would fail to start.
Are your services crashing, by any change? Or is this the familiar separate partition problem?
If you're still in the 90 day Windows 7/8 rollback period the update will not deploy. Because deploying the anniversary update kills your ability to roll back to the prior OS. And after employing the anniversary update, you can only roll back to pre-anniversary-update version on Win 10.
We figured that out in the week following the rollout of anniversary update, when a test machine that was updated months before we deployed Win 10 (in the month before the free period ended,) started pestering us about anniversary update. All other machines had to have manual deployment of it per MS' instructions. (Sorry to not post the link to the manual deployment instructions here.... but I don't was MS getting any more help from me since they screwed us so good with Win 10. Their bankruptcy can't happen soon enough IMVHO.)
Agreed. He should upgrade to Linux, BSD, Mac OS or any other real OS away from that marketing malware platform called "Windows".
That wouldn't be a conspiracy theory. All these machines are made by Chinese and Taiwanese manufacturers like Asustek, Gigabyte, Compal, Quanta, Foxconn, et al. They do their best to cut costs by cutting corners - like on the firmware, which would explain some of the issues
The delays are not based on user accounts. I have 3 computers at home all running Windows 10 Pro and only two of them have received the update. It's not a matter of AMD vs Intel or AMD vs nVidia either as the two machines that did update are running each (one Intel+AMD, the other AMD+nVidia), the one machine that has not updated is running a 32TB storage space which is the only major difference amongst the machines.
Re-create the swap file by turning off virtual memory, reboot, turn virtual memory back on, reboot. System > Advanced System Settings > System > Performance > Advanced > Virtual Memory. The swap file got corrupted. You can verify by checking Task Manager, if DISK is at 100% usage when the freezing occurs, that is the most likely cause. The second most likely cause is the system is using the default Microsoft SATA driver and is experiencing an MSI issue with your hard drive. There is a registry fix but you will need to Google for it as I forget the exact change required. It involves figuring out the device ID in the driver details and then locating that device in the System section of HKLM to make the change.
Re-create the swap file by turning off virtual memory, reboot, turn virtual memory back on, reboot. System > Advanced System Settings > System > Performance > Advanced > Virtual Memory. The swap file got corrupted. You can verify by checking Task Manager, if DISK is at 100% usage when the freezing occurs, that is the most likely cause. The second most likely cause is the system is using the default Microsoft SATA driver and is experiencing an MSI issue with your hard drive. There is a registry fix but you will need to Google for it as I forget the exact change required. It involves figuring out the device ID in the driver details and then locating that device in the System section of HKLM to make the change.
Oh yes I am sure the majority of Windows 10 users know how to do that.
Just by going to Microsoft site and download the update, I did it, it works fine. A quick google search gives me:
https://support.microsoft.com/...
"Science will win because it works." - Stephen Hawking
I can't believe how much easier than Linux this is!
After several occasions where windows decided to update itself without giving me any other options, installing faulty drivers that required removing the driver and all settings for the device, wasting time and money, then proclaiming triumphantly that all my files are where I left them, as if not destroying all my files is some sort of fucking achievement and not the least you can fucking expect...
No Microsoft, I'm not installing your fucking updates, hopefully disabling the update service will take care of that problem.
And I'm definitely not using that piece of excrement OS for anything that actually matters.