Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
It feels like you two are talking past each other. Is it taking 5 hours for the KB fix to apply from WSUS, or is it taking 5 hours to install the msu manually from a download?
I don't personally subscribe to the "go five years without an update" model for client machines. I prefer my computers and devices be up to date (whichever OS they use) and I prefer the devices I support to be up to date as well.i've got to love this "you're out of date there for sky is falling" straw-man. I've ran many a system 24/7 *and* connected to the internet *gasp* - and sky's ever fell. From Win95, Win98, Win2k, WinXP, Win7 for up to 5 years even.
Just because a software developer wants you to update because the hax0rz, doesn't really mean your system will burn down the moment a new version number comes out and the sky falls because oh no you don't have the latesttelemtry updatepatch!
Yes, the entire "Windows Update System" is seriously borked. It now takes 5-12 hours for each of my Win 7 and Win 8.1 workstations to complete the "Checking for Updates" task. Really pathetic.
There's a lot of fools in this forum.Only a fool would laugh at people who want to control their own machines.
Correct me if I'm wrong, but it seems strange to me that you seem to be attributing the fact that you haven't had an issue with Windows 10 rebooting for two years to Active Hours.Seriously, you gotta be kidding me. I've used Windows 10 for the past 2 years and I have never, ever had the system just reset because it felt like it. I set my hours from 7AM-7PM and set update time at 3AM: if my PC happens to be on all night, it'll restart at 3AM, otherwise, the update will finalize whenever I turn it off.
I don't personally subscribe to the "go five years without an update" model for client machines. I prefer my computers and devices be up to date (whichever OS they use) and I prefer the devices I support to be up to date as well.
Forget for a moment the mess of the weekly and monthly updates we see. Let's just look the major upgrades.
Since July 2015, Microsoft has released three major OS releases, even though only one of them, the original Windows 10, was marketed as such. But Windows 10 versions 1511 and 1607 were in fact major OS releases too. They are delivered, installed, and serviced as such, and they come with the same risks as any major OS upgrade. They might have been branded as Windows 11 and 12 had Microsoft not arbitrarily decided to stop the branding at Windows 10 and pretend that this was the final version of Windows.
The result: We've had to install, troubleshoot and maintain as many new versions of Windows in the past 15 months as did in the 6 years between Windows Vista in 2006 and Windows 8 in 2012. Think about that for a moment. (And then remember that Windows 8 was so bad it needed two major updates of its own, Windows 8.1 and Windows 8.1.1, to set things right.) And when you add in Windows 10 version 1703, you get four major Windows upgrades in just two years.
And that, essentially, is the problem with Windows as a Service: It has created more platform fragmentation, not less. That was not the goal of this initiative.
i've got to love this "you're out of date there for sky is falling" straw-man. I've ran many a system 24/7 *and* connected to the internet *gasp* - and sky's ever fell. From Win95, Win98, Win2k, WinXP, Win7 for up to 5 years even.
Just because a software developer wants you to update because the hax0rz, doesn't really mean your system will burn down the moment a new version number comes out and the sky falls because oh no you don't have the latesttelemtry updatepatch!
Correct me if I'm wrong, but it seems strange to me that you seem to be attributing the fact that you haven't had an issue with Windows 10 rebooting for two years to Active Hours. It seems strange to me because Active Hours is a feature in the Anniversary Update that is only a few months old that was implemented because of the issues being described in this thread by people and the article you labeled as "click-bait."
Active hours are not long enough in some situations. Needing to have a system active for more than a 12 hour period is not a problem. There are programs that can take days to process. Not everyone can switch to enterprise. So no this isn't clickbait. Just because something works for you doesn't mean it works for everyone else.
So we're back to the days of "shut your computer down at the end of the day"? I thought we left those behind with ...what was it, Windows 95 when that was last the case?Fair enough. If you fall into the - quite small - pool of people using consumer win10 yet needing to keep the PC on for days (hence making updating at, say, 3am useless) then I feel for you - there is currently no good choice in that case. However, that's a pretty small group of the general windows pie, and you must admit that forcing the general userbase to upgrade and be secure is a good thing overall. Either way, the article blatantly says WU is broken just because it won't fit a small minority of users. Kind of hyperbolic, I'd say.
So we're back to the days of "shut your computer down at the end of the day"? I thought we left those behind with ...what was it, Windows 95 when that was last the case?
I find myself shutting down more often only because it boots up so fast I don't care.So we're back to the days of "shut your computer down at the end of the day"? I thought we left those behind with ...what was it, Windows 95 when that was last the case?
That's a verry narrow minded statement. Windows 10 has updated and destroyed both my accounting software as well as productivity software. I've lost days worth of work. This was after following a tutorial on turning updates off. Microsoft's stupidity has the potential to run small businesses into the ground with this crap.If you're leaving unsaved work up when leaving your PC for long periods of time... you deserve whatever you get. Windows update, power surge, or Jimmy the janitor knocking the plug out of the wall / the cat walking across the keyboard. Nothing wrong with the update system, something wrong with the user.
So we're back to the days of "shut your computer down at the end of the day"? I thought we left those behind with ...what was it, Windows 95 when that was last the case?
Tell that to the people who ditched Windows long ago... for Linux.
It feels like you two are talking past each other. Is it taking 5 hours for the KB fix to apply from WSUS, or is it taking 5 hours to install the msu manually from a download?
It's less a case of talking past and more of him not listening. He's clinging to a broken process and wants to nurse his grievance instead of fixing his issues.
Why should I listen to you when you make stupid blanket statements about how things should be done? You are neither an expert nor an authority on anything that would require my attention.
Do you mean LibreOffice?office substitutes on the Java side are damn good
Have you ever done a computation intensive task that takes 48-72 hours? Just think before you talk shit.If you're leaving unsaved work up when leaving your PC for long periods of time... you deserve whatever you get. Windows update, power surge, or Jimmy the janitor knocking the plug out of the wall / the cat walking across the keyboard. Nothing wrong with the update system, something wrong with the user.
... You're savvy. Install the third party app, make the policy edits. Zero reason to be whining.
Fair enough. If you fall into the - quite small - pool of people using consumer win10 yet needing to keep the PC on for days (hence making updating at, say, 3am useless) then I feel for you - there is currently no good choice in that case. However, that's a pretty small group of the general windows pie, and you must admit that forcing the general userbase to upgrade and be secure is a good thing overall. Either way, the article blatantly says WU is broken just because it won't fit a small minority of users. Kind of hyperbolic, I'd say.
Yep Windows 10 update sucks balls. Recently when the anniversary update came out last month. IT TOTALLY FUCKED MY SYSTEM! I couldn't even recover, tried every recovery option available. WTF?
Never had this happen before in 15 years. I ended up formatting and reinstalling.
What happened to your backup drive(s)? External? You lost access or data?I've been a fan of Windows 10. Last night I got around to installing the Anniversary Update to try out the Forza 3 Demo and I was in for a nice surprise. I came back into Windows with all the telemetry settings reset(no surprise), my backup hard drives disappeared and apparently corrupted, and some of my drivers were corrupted an had missing features. I was about to roll back but after the hour and a half or so wait, I decided against it. Another mistake I made. The system was rock solid and was super smooth until I installed this garbage. I mean I heard there was some problems with updates but I've NEVER seen anything like this before.
What happened to your backup drive(s)? External? You lost access or data?
I don't personally subscribe to the "go five years without an update" model for client machines. I prefer my computers and devices be up to date (whichever OS they use) and I prefer the devices I support to be up to date as well.
You're entitled to your opinion and if you are happy with the model you have in place, hey, more power to ya.
You know, I've heard that mentality repeated so much on this forum, I really wonder if ANYONE has evidence of this sort of thing, or if it's all conjecture. What are the stats on people who know what they're doing on their system actually getting hacked by OS exploits? 1 in 100? 1 in 10,000? 1 in 100,000? Anyone? I HAVE seen Windows XP machines compromised by exploits, but I've never seen it on Windows 7 onward personally unless the operator was opening an unknown email attachment or something on that level of recklessness.These machines weren't on any kind of "model to not update". They just got used for 8+ hours a day and were on 24/7. they worked. They never faltered. There was no real need to update them so it just never happened (especially with the amount of pressure on the user to produce on said machines). Then all of a sudden years later.... oh shit. these havent been "Windows Updated" for yonks and they work absolutely perfectly, so much for imploding because its not UP TO DATE!
Which of course anyone with a brain knows doesn't happen, its just what they want you to believe so you buy into their "must do everything your told" scare tactic.
never had these issues.
You know, I've heard that mentality repeated so much on this forum, I really wonder if ANYONE has evidence of this sort of thing, or if it's all conjecture. What are the stats on people who know what they're doing on their system actually getting hacked by OS exploits? 1 in 100? 1 in 10,000? 1 in 100,000? Anyone? I HAVE seen Windows XP machines compromised by exploits, but I've never seen it on Windows 7 onward personally unless the operator was opening an unknown email attachment or something on that level of recklessness.
I imagine despite having updates, there was a hell of a lot of security going into even a 1.0 release from Microsoft. I'm sure all these exploits are real, but what I DON'T know is if actually getting hit is on par with winning the lottery or not. Or maybe something is a serious exploit IF you don't use a firewall, or can only happen from someone physically logging in at your machine, or something that may be a non-issue for the majority of users. It makes you wonder how much of this is a real and present danger security risk, including the savvy user, and how much is just update bogeyman talk. I'm not saying it's one way or the other, I'm saying I'd love to see STATS on just how a big a risk not updating at the drop of a hat actually is. Without that info, it all turns into speculation.
Most users will also say ok to UAC prompts anyway. Heck 99% of the time it's safe to do so, because it's something that needs to be done so that whatever you are doing works. Then the one time it's actually something malicious... you'll probably hit OK anyway from muscle memory. UAC was the wrong approach to security. Sandboxing is a better approach. Browsers, mail clients etc should be in a sandbox by default. In Linux there is chroot too, I feel most apps should take advantage of that. No reason not to chroot the web browser for example. Chroot is not a true sandbox though, not sure what happens if a malicious site executes bad code to launch a separate piece of code, I think it could fairly easily break out of the chroot. Or could it?
Thank youGood for you.
ThenOEM said: They'll never fix that because no one is leaving Windows in droves. Until they start feeling it in their wallet they won't care. And, there is no viable option to Windows. No matter how much you want it to be, Linux is not a viable option.
It's an option for US. It's not an option for 99% or more of the population unless YOU want to be the support person for all those people. As much as I feel good about helping and teaching people, I no longer want to be doing it 24/7, and have no delusions that the general population will miraculously become computer savvy anytime soon, no matter how much we wish they could.As long as everyone thinks with this kind of prejudice, it will never be unfortunately.