Thanks for the warning, quiteman7!
Evidently had forgotten that yesterday was Patch Tuesday, the first such time I've missed the day in 2-3 years. So fortunately it was pulled before it got to me. One of the oddest things about this month's patches, after 20-22 updates on Windows 7, 8 & 8.1, there were a couple more to follow. That has happened prior, but has been some time for me since I've seen a slew of updates followed by two more.
These were KB3034196 & KB3001652 that was mentioned above. Evidently, Microsoft must have solved that one fast, so far have installed it on four Windows 7 & two 8.1 systems, with no negative issues to report so far. Could have been that it needed to be installed after other updates. Maybe I was fortunate that I had overlooked Patch Tuesday.
I don't know why some people would decide to stay under Windows 8 as they'll have to eventually move to Windows 8.1, and it's even better if they upgrade to it right now.
Aura, check out the Windows 8 section, and you'll very quickly find quite a number of Topics of failed upgrades from 8 to 8.1 for varying reasons, or there were hurdles to overcome after the upgrade. Wireless cards not working is a top issue, as well as OEM features no longer working as intended. On some Dell notebooks that's still current, the only thing that prevents the upgrade is a USB SD card reader, not an item that many customers can do anything about. First off, any warranty will likely be voided if the notebook is torn down this far (same with wireless cards). Secondly, Dell is pointing the finger with MS, and MS is pointing the finger right back. Dell is in the right, MS should have been more concentrated on their largest user share, rather than using customers as a clinical study to see if this type of SP delivery would work seamlessly. Many to this date still cannot apply the upgrade. I was able to on a couple of older models (2010 & 2011 ones), but never bothered with that which shipped with my Dell. Which was clean installed my myself, and know by experience of the prior two & others, that upgrades aren't the same. One of which took two attempts to get it right.
MS pulled the 8.1 Upgrade (really Windows 8 SP1 as far as long term support goes) w/out letting all of the OEM's know well ahead of time, so that retailers could round up as many Windows 8 systems as possible. Allowing these to be sold well beyond the release date, many at major retailers, not all second tier ones, initially not knowing the issue was there. Only after it became well known there were various issues with 8.1 not properly applying, was most of the stock of Windows 8 computers pulled off of retail shelves & first rate online retailers. Second tier retailers were still moving the units as fast as possible. Others were offering at an extra cost, an upgrade to Windows 7, stable ground.
I can't speak for all of the OEM's issues, just the Dell XPS 8700 that I own. There is a whole different set of drivers for 8.1, as these were sold with Windows 7, 8 & 8.1, and of course the 8.1 ones were the last released. This is beyond the scope of the everyday consumer, whom rightfully expects their computers to be working fine just weeks or a couple of months after purchase, and an undue burden. Dell's position, as well as other OEM's, is that they support the OS the computer was shipped with, there isn't Windows 8.1 drivers for every component of every model sold, even if there were, they'd have to be applied post upgrade, and the result would again be upgrades that didn't take & reversed. The days of floppy drives to insert needed drivers for the OS to install are a relic of the past for the majority of us.
Under the old rule of applying service packs, most consumers reported positive results, even if some drivers had to be updated afterwards. There is no need to have to perform a reinstall of the OS to install a service pack. If this trend continues with Windows 10, it will cost MS market share. MS contends that 'new features' were added, and rather than helping customers, pointed the finger at the OEM's. I find it odd, that prior SP's offered new features & enhancements, one that many of us are using to this date (Windows Firewall) was delivered by traditional service pack.
As far as customers having to do it because they may eventually have to, while this may be true, that decision should be left up to the consumer, not Microsoft. Some consumers has other plans than to go with 8.1 & then 10, some may revert to 7, others may make other moves. Some may decide to wait until the end of support for Windows 8, to see how 10 goes before making this decision, not wanting to be burned a 2nd or 3rd time. If Microsoft is going to be delivering these updates underhanded, then they should be supporting their OS's by on site service if something goes wrong. Another reason why I'm skeptical of them promising to support Windows 10 when released, but that's for another Topic.
Like TechnicianOnline pointed out, there are businesses running Windows 8. Loss of service can cause business disruption, including loss of customers. Some, including myself, don't care to hear that a business computers are down when walking through the door & have to return at another time. Unless it's a place I'm really loyal to, that will be the last time I walk through their door, because in a case like this, it's obvious they had no backup plan in place, including that to safeguard my data. Businesses should have 24/7 non-stop backup, which will allow for a quick revert when needed & consumers should backup before Patch Tuesday of each month.
Had I not been going through those Windows 8 updates carefully, would have had to revert to the update taken on Sunday to prevent a background update to take place. These are stable releases, unlike participants of the Windows Insider Program. KB3008273 was a pre-checked update after I hid it 3-4 months back. Shouldn't have shown again w/out my consent. This was also an issue nearly 4 years back with KB971033 for Windows 7, consumers had the right to not install the update, and MS promised that it wouldn't be mandatory. At the time, I did allow it to install, and after seeing that it was 'phoning home' at every boot, removed the update & hid it. 3-4 months later, it again reinstalled itself, but MS openly apologized for that one, after removal & hiding again, never seen it. While I do allow the update to go through on clean or reinstalls, will remove a few days later. As consumers, we shouldn't have to prove we paid for a license to operate Windows 7 at every boot.