Microsoft Confirms It Is Dropping Windows 8.1 Support
snydeq (1272828) writes "Microsoft TechNet blog makes clear that Windows 8.1 will not be patched, and that users must get Windows 8.1 Update if they want security patches, InfoWorld's Woody Leonhard reports. 'In what is surely the most customer-antagonistic move of the new Windows regime, Steve Thomas at Microsoft posted a TechNet article on Saturday stating categorically that Microsoft will no longer issue security patches for Windows 8.1, starting in May,' Leonhard writes. 'Never mind that Windows 8.1 customers are still having multiple problems with errors when trying to install the Update. At this point, there are 300 posts on the Microsoft Answers forum thread 'Windows 8.1 Update 1 Failing to Install with errors 0x80070020, 80073712 and 800F081F.' The Answers forum is peppered with similar complaints and a wide range of errors, from 800F0092 to 80070003, for which there are no solutions from Microsoft. Never mind that Microsoft itself yanked Windows 8.1 Update from the corporate WSUS update server chute almost a week ago and still hasn't offered a replacement.'"
Windows 8.1 is no longer supported, so users must update to Windows 8.1?
"a wide range of errors, from 800F0092 to 80070003, for which there are no solutions from Microsoft."
Story of our Lives. Here we are.
My turnips listen for the soft cry of your love
Apple doesn't support more than one version of iOS. If you want to fix a problem with 6.1.2, you get to go to whatever version is current (7.1). You don't get to go to 6.1.3, you don't get to go to 7.0.5 or 7.0.6, you go to 7.1. Your choice is "upgrade or don't."
John
Just patch windows 8.1 with the update. It makes the OS unequivocally better. Whining about it is just silly.
You should be able to upgrade/downgrade/sidegrade to any version that suits your needs
My turnips listen for the soft cry of your love
They make things so confusing, whoever makes these decisions are the ones that should be fired from Microsoft! Windows 8.1 and Windows 8.1 Update 1. Just name the damn thing 8.2 or Service Pack 1 that everyone is familiar with. Then to top it off Windows 8.1 isn't getting any more updates!!!
Then you have a pro version, this version and that version!
Sorry but life is much more simpler in the Mac world! 10.9.0.....10.9.1....10.9.2.......etc. Then you have Delta Updates that are the point releases and Combo updates that will update you from the 10.9.0 to the latest version say 10.9.9 in one download and one install. Then you don't have 200 updates to download and install.
I think the Microsoft way is superior as you can install/uninstall individual updates incase of problems, but its too complicated!
if you have wsus without ssl, it works fine after importing the update from the catalog.
i don't see the need of ssl on an internal small server, anyway even with ssl you can enable tls 1.2 manually and it will work.
this article is also misleading, since the update itself is a regular update and not labeled "update 1" or even a service pack, but on every windows version out there there are updates that depend on other updates, especially service packs, so nothing new here.
Open Source Java Web Forum with LDAP authentication
Microsoft only support the current service pack level and all those less than 24 months old for Windows Client and Server.
That's the agreement they've given to their customers.
They will drop support for 8.1 in 24 months time.
http://support.microsoft.com/l... .... wait a minute. They should at least update their support policy before cutting support.
Why not upgrade from Windows 8.1 to Windows 7?
Tell him that M$ have done the same old, same old, attempted to correct their failures in the cheapest way possible by shoving the cost back on consumers. Can't get the upgrade to work, suck it up, format, re-install, repatch, re-upgrade and repatch and the restore you back up data, don't have backups, M$ answer to you, well, that's your fault for trusting their software.
Chaos - everything, everywhere, everywhen
How is this any different than MS stating in the past that updates required a certain Service Pack in order to be installed. It's worded very poorly, since everyone is going to assume the worst when you say 'Windows 8.1'. Mainly because they're not calling them service packs anymore or incrementing the updates. Windows 8.1 Update 1 would make more sense to people if they simply called it Windows 8.2.
The Amarri pray for god, the Caldari pray for profit. the Gallente pray for peace, but the Minmatar pray their ships hol
Why not go back to the old SP system and stop this mess of a new update system where some stuff is in the windows store and others is in the windows update system.
As for this not working for all does it have any thing to do with 8.0 to 8.1 being more like a full os upgrade then an SP? and why did make the 8.1 iso not take Windows 8 product keys?
MS needs to go back to how it used to be with XP, vista, 7. Where it's not lot's of separate updates it is rolled up on to big install that has it all or least offer that as a choice not only for people who say have 2-4+ pc's and don't want to have re download the same updates on each pc but in some cases that combo updates work better.
Windows 8.0 was installed on this machine, and it sucked immensely. Then a couple of months ago I got an upgrade to Windows 8.1 courtesy of Windows update, and it hardly sucked at all. Then, a couple of days ago I got my old Windows 8.1 upgraded to new Windows 8.1, and I know it is different because now apps have the big red "X" back in the right hand corner of the window and you can terminate them while they are running. Awesome! At this rate Windows 8.1 will turn into Windows XP around Labor Day. Maybe the boys will rediscover POP3 email at some point.
After four tries, the update finally worked. What does it do? I now have an App Store icon in the task bar. Only took some 880 Mbytes to do that.
I installed the update at work - it worked. I installed the update on my old PC - it worked. Tried to install it on my current PC - failed, after taking something like 20 minutes. It then took another half-hour to revert the changes. (On those machines where it worked, it took only 5 minutes or so to install).
Digging around online showed that fiddling around on the command line with dism might help. The online image is corrupted but it's repairable... that is, until you try and use /restorehealth, at which point it moans that there are no sources. Of course there aren't, it was upgraded to 8.1 from 8.0 via the online store.
So, after faffing around and grabbing an install.wim from an old 8.1 iso I had saved at work (not the 8.1 update 1 iso currently on the MS website) I find that dism won't use the image, even after mounting it.
I couldn't then even attempt to reinstall the update, as it failed immediately. Dism was called upon again to remove the update package, then at least it would let me try again... only to fail. Another 45 minutes wasted.
It looks as though the only way to "fix" it is to nuke Windows entirely, then go through the painful 8.0 > 8.1 > 8.1 with Media Center route. Except, of course, to get Media Center reinstalled you have to buy it again - there's no option I can see to re-enter your Meda Center key again because, guess what, when you upgrade to Media Center your Windows product key is changed. And a Windows 8.1 with Media Center key isn't accepted by the 8.1 iso (or at least wasn't when I tried earlier)...
Looks like a long and boring Easter weekend coming up.
On the other hand, I might just reinstall Windows 7 instead.
You can upgrade by installing Windows Me, then Vista Ultimate, then enable start menu, disable start menu, 8.0 SP1, Windows ME again but holding ALT-F5 until BSOD appears, then quickly insert the 3.5 floppy with 8.1 patch on it (if you didn't keep a floppy drive.. oh you're so screwed!).
A timely reminder why users should stick with a stable, proven OS such as Win7 (and to a lesser extent, WinXP).
Less fancy unnecessary features like Metro also means less chances for cock-ups to happen.
If MS' intention is to migrate users of older OSes to Win8.1, it is not doing itself any favors here.
Yes, apple want you to upgrade to iOS 7, but if you don't want to (or can't because your hardware is too old) they still provide security patches for iOS 6.
The last update was iOS 6.1.6 in Feb:
6.1.6 was only released for devices that cannot run iOS 7. If you have a device that can run iOS 7, you had to upgrade to iOS 7 in order to get the important security fix, even if the device had iOS 6.x at the time. There was never an iOS 6.1.6 released for iPad 2 or 3, for example.
If they had released an iOS 6.1.6 for iPad 2/3, it would've allowed downgrading from iOS 7.x to iOS 6.x then jailbreaking, something Apple hates with a passion.
"Screw Sun, cross-platform will never work. Let's move on and steal the Java language." - Visual J++ Product Manager
That's because you're programming against it. If you go easy on .Net and only program alongside it, then it'll start throwing it weight around like an unruly child.
This whole thread is absurd, as are all the people jumping on the "bash MS" bandwagon.
* Microsoft will continue to support 8.1, and everyone here KNOWS that.
* Everyone knows that because Microsoft has a bigger problem with having to support old platforms than any other vendor out there. Many posters here generally know this, too, but are being obtuse so that they can harp about Microsoft ending support for a new platform (which isnt even remotely believable).
* The author of the blog even knows that! The Microsoft technet entry says almost the opposite of what the blogger does-- that 8.1 WILL recieve updates. All he got right is that you do need to install a prereq to get them, like we've seen with countless other OSes. The venerable XP does this, too.
* Half the people gloating over the "bugginess of Windows" are fans of an OS that is experiencing one of the biggest internet vulnerabilties in about a decade in its SSL stack, but thats OK in their eyes somehow because its not packaged with the OS and therefore theyre allowed to be buggy.
* Some people are taking the time to smirk about the confusing version numbering of Win8-- which is doubly hillarious given how ridiculous Linux's versioning was until about a year ago.
* And if I had to guess, the aforementioned problems could possibly be related to the aforementioned heartbleed bug, as we dont know what all was leaked and Microsoft is almost certainly not going to want to go into it.
But yea, dont let that stop the fun.
Winows 8.1 update 1.
It's just an awkward versioning scheme. If this was the unix world, they'd be talking about no longer updating 8.1.0 and requiring customers update to 8.1.1.