As we all know, Windows 10 has changed the Windows OS landscape by using us as guinea pigs to test their updates. After the Anniversary Update, I noticed that my system would simply freeze up every now and again. As it turns out, I'm not the only one. In addition to that, the IE11 that I primarily use freezes up three or four times a day now, as well. Pages also seem to randomly refresh for no particular reason, and some get stuck during that refresh, too. They've actually admitted to the problem with the OS freezes, but only partially, saying only particular systems are affected, which turns out to NOT be true.
One solution they put forth is to roll back to a previous build. Well, that's great, until Windows 10 automatically updates to the Anniversary Edition again, which shouldn't be too long after you restart, and which we can't stop from happening.
Thanks, Microsoft. We really appreciate the privilege of testing your products for you. I suppose those who upgraded to Windows 10 for free don't really have much of a leg to stand on, but what about those who paid for Windows 10, including those that purchased a computer with Windows 10 already installed?
Again, thank you so much, Microsoft. You really know how to endear your customers.
No, this has absolutely zero to do with Hughesnet, but I'm just wondering how many of you are experiencing the same type of thing.
If it continues I'm definitely going to be looking at using Chrome on a more permanent basis. Right now I only use it for a few things, but if this keeps up, and I think it will, IE11 is going to have to go by the wayside. I don't care for Edge, so Chrome it will be.
Microsoft is trying to say it's only affecting a computer with this, or only affecting a computer with that, but it's nonsense. There doesn't seem to be any rhyme or reason to it. I knew this forced update thing would eventually cause a problem with them using us as guinea pigs.
The entire computer freezing up doesn't happen nearly as often, but it still happens.
I could try the rollback and defer the updates, and maybe in the two months or so it waits to force them they will have released a fix or an updated Anniversary update. My notebook doesn't have Pro, so no deferral, but I only use it as a testing computer for programs I want to use on this and my main laptop, and with not using it much I haven't seen it happen on that, as of yet.
Oh well. Life could be worse. My Keurig could stop working and I'd have no coffee...knock on wood. LOL.
I'm lucky enough that I still have my Windows 8 disk that came with my Dell laptop, which will also work with my notebook, due to them both having the embedded product keys (I've used it on both before). I'm thinking about at least reinstalling Windows 8 on the laptop, then upgrading to 8.1, of course. I'm stuck with W10 on this (desktop), though, due to using my purchased OEM upgrade copy of Windows 8.1 being installed on my folks' laptop.
I saw it coming, as well, but took the dive anyway. With the exception of the very recent problems, I actually like Windows 10. Sure, us being update guinea pigs caused this, and may cause other problems in the future, but hopefully they will iron things out. I know...that's a lot of hoping. LOL.
but hopefully they will iron things outLol, I got some ocean front property in Arkansas I'll sell you.
That's awesome! I've been looking for some. How much?
Got a bridge, too?
Changes coming for the format of updates in 7/8/8.1
Further simplifying servicing models for Windows 7 and Windows 8.1Further simplifying servicing models for Windows 7 and Windows 8.1
In our announcement earlier in May, we introduced a Convenience Rollup update for Windows 7 SP1 and a shift to monthly rollups of non-security updates for Windows 7 SP1 and Windows 8.1. Based on your feedback, today we’re announcing some new changes for servicing Windows 7 SP1 and Windows 8.1. These changes also apply to Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2. (Note: A rollup is multiple patches rolled together into a single update.)
Why we’re introducing Windows servicing changes
Historically, we have released individual patches for these platforms, which allowed you to be selective with the updates you deployed. This resulted in fragmentation where different PCs could have a different set of updates installed leading to multiple potential problems:
Various combinations caused sync and dependency errors and lower update quality
Testing complexity increased for enterprises
Scan times increased
Finding and applying the right patches became challenging
Customers encountered issues where a patch was already released, but because it was in limited distribution it was hard to find and apply proactively
for further information
»blogs.technet.microsoft. ··· ows-8-1/
From a dlsr thread:
Personally I am down to only two remaining Windows based machines and while not recommended they both have had updates disabled and those are seldom used.
I just don't think much of the direction that Microsoft is heading.