Windows 10 Is Broken: Fix It, Microsoft!

Easiest way is to just nuke the Windows Update service. Or firewall the Windows Update servers.

Every "release" of Windows 10 adds more bugs without fixing the previous ones. I feel like I am using Debian Sid or something.
 
  • Like
Reactions: DPI
like this
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.
 
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 latest telemtry update patch!
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.
 
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.

Turn OFF automatic updates, reboot. Then install "Windows Update Client July 2016" (or newer if one is available) reboot, then this:

https://support.microsoft.com/en-us/kb/2889748

Then reboot. Then check for updates. It should pick them up quickly. I still do a bunch of fresh Win 7 installs (and fix Win 7 update in general) and this fixes it.
 
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.
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."
 
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.

Except its not five years or nothing. There's a middle ground. And for anyone insane enough to be running Windows 10, it's probably wise to wait at least 6 months between updates due to the track record of unreliability, and new updates breaking as much as they fix.

Paul Thurrott makes some great points on this issue:

https://www.thurrott.com/windows/windows-10/84339/windows-service-isnt-working-premium

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.
 
Last edited:
WIndows 10 issues and Apple's lack of innovation makes this a terrible time to upgrade my laptop.
 
Welcome to the future pleebs! We update your PC whenever we want! See, it's now less problems for us, except more problems for you of when you get to use your PC! See it's better, we said so! Also, we say it's so much more secure, except the fact there are just as many exploits now as ever! Although we discount that fact by not mentioning it! Why would you ever need a few days of update free computing time to finish a large task? We did not see that as a requirement in Win 10! Enjoy!
 
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 latest telemtry update patch!


Exactly. Updates are a never ending game, you can update today, then suddenly tomorrow you're out of date again. The whole security model of being up to date is a flawed one because you're never up to date, there are always going to be patches and more patches. You need to secure things in such a way that even an out of date system is not compromisable. In the case of a workstation that's easy, it should not be facing the internet in first place. for something like a server then yes you should probably try to stay on top of updates to at least the key programs that are internet facing such as Apache or anything that opens a port up.
 
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."

You are correct, let me clarify: I've been using Active Hours since Anniversary. The 1st win10 year, I just told my PC to update at 3AM. If my PC was on, it'd do it then, if I turned it off earlier, it'd apply updates then. That's how I did it with win10, 8, 7, Vista and I can't really remember about XP. Haven't had an update suddenly install, at least since 2005. Because they don't, if you configure your machine correctly.

I still think the article is pure clickbait. If you configure win10 to do what you want, it does it. End of drama. If you're a business that depends on having PCs up and running, get win10pro and use WU for Business: defer updates for months. Fixed.

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.

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.
 
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?
 
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 shut mine down more often now than back then since it is at desktop so quickly now with the better speeds and ssd.
 
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.
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.
 
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?

lol yeah that's kinda sad if people are expected to do that. They obviously don't use their computers for anything important to begin with or have 20+ different things open that they're working on, if they think that's ok. Data saved or not, if all my stuff is open and laid out the way I left it, I want it to be that way when I come back to it the next day. The idea of being forced rebooted any time, even overnight, is just absurd. Especially if you can't control it.

I'm just glad I switched to Linux so I don't have to deal with any of this stuff. :p
 
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.
 
Tell that to the people who ditched Windows long ago... for Linux.

I love that people can do this, it's good news if it can ever really proliferate. I will not be able to leave Windows because my living is using their products really (I am a developer of windows code) but I remember not that long ago (haha I am old) that development was a generic thing and you did Mac, SunOS (yeah I know old) and DOS/Windows development regularly. I yearn for that day again where we have more choices :)

Oh and I personally love Linux, the day we have gaming proliferate on Linux could be the end of the stanglehold. The office substitutes on the Java side are damn good imo.
 
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?

12+ hours for the MSU. It will eventually apply and then updates will flow normally again. I suspect the OEM OS image has a surplus of keys in the registry for various drivers that require parsing as it seems to only drag on laptops (even those equipped with SSDs). Increasing the task priority has no effect and the process manager shows little in the way of activity.
 
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.
 
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.

Because I went through this same issue five years ago, and I gave you my solution to the problem. Again, you are more interested in nursing your grievances than you are in solving your issues. You've been informed of three separate ways to fix your problem--build a stock image for your own use, apply a KB through GPO, and use the Windows 7 Convenience Rollup--but you've fallen back on "management won't help me" and "why should I listen to you?"

You are literal PEBKAC.
 
I've been using Windows 10 on a couple rigs awhile now.

But my Main Rig isn't a business computer I guess, I've been playing Guinea Pig for MS awhile now and update on the insider fast ring.

4R2SMIx.jpg


I just like messing with new stuff, have been using WIN 10 since it was released, far fewer problems on the newer updates. I usually get updates every 4 or 5 days.

For a business computer I think I'd still be a bit wary, but my main rig seems pretty stable with even a lot of the Red Stone things coming out.
 
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.
Have you ever done a computation intensive task that takes 48-72 hours? Just think before you talk shit.
 
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.

It's not that small. Even those of running Enterprise version for home office have issues with WU.

There's a gray area between power users that know what they're doing (majority here on the forums I'd say) and grandma who uses it to stalk the grandkids. Many users can deal with the forced updates and such, never seeing a problem. Others don't like it or find it disruptive to work. Not everyone is a large corporate enterprise with IT staff and deployment services. Many small businesses (like mine) may fall into the annoyed category. If MS wants to cater to the grandma at home with a paint-by-numbers OS, that's fine, make the Home version that way. Allow people with the Pro/Enterprise versions to accept the risks and enable deeper settings to configure the PC in the way they seem fit.

As I previously said above, I got so annoyed last week by WU issues that I disabled them completely with a few hacks. So in MS's forced wisdom to make the OS secure, they've created edge cases where people have to take drastic measures to get the OS to be useable.

Said it before, a lot of issues would be cleared up if they (re)introduced a few key settings.

- Ability to reboot/shutdown without updating.
- Ability to force WU reboots during non-active hours (so you don't have them falling over to non-active hours in the work week).
- Ability to have more control over the scheduling of updates (including once a week). Updates flagged as urgent security could put a note on the notification center that it's recommended to be applied right away.

Windows 8 was far worse in that it'd give you the option to delay an update and then force it upon you. So I can see where people would lose work in that use case. I was a victim of it a few times until I found a hack that allowed me to disable it.
 
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.

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.
 
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?
 
What happened to your backup drive(s)? External? You lost access or data?

I put drives but it was only one. It was there in Disk Management but I wasn't able to assign a drive letter but it showed the drive not having anything on it so I formatted. Thinking I could just use GetDataBack that I bought several years ago or Recuva, most of the data was apparently overwritten even though I hadn't touched the drives. It was my mistake assuming the update would go alright but I also didn't handle it correctly. I should have just restored back to before the Anniversary Update. The system is stable though and oddly very responsive.
 
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.

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.

now of course dont go all extreme, we know that some times doing an update is a good idea. yes its generally a good idea. But its simply not a requirement as many make it out to be. And i've seen no evidence, either in my anecdote nor in the wider information station that its an ACTUAL requirement unless there is some direct fault being rectified in said updates that is effecting your production or usage of your device. With the way MS is going.... adding more telemetry or fixing 'bugs' in telemetry, doesn't sit high on my priority list. especially when they want to force the update on me and/or do things like remove update descriptions etc

Its just plane ridiculous. But hey, its not about user options or user experience or user satisfaction nowadays. its all about what the Corpoeration wants. Every damn one of them nowadays operate in the "do what we want" world. Its getting tiring and its really making it easy for me to spend less money on half ass services. Not that i wasted coin prior.
 
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.
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.
 
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.

Been wondering about this myself. Seems like most of the exploits that have found ways around UAC still require physical access (or a dumb user) to actually be useful. If thats really the case most people here have no need for these updates anyway.
 
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?
 
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?

Privilege escalation is the most important security feature in your operating system. What Microsoft did wrong was not forcing users to enter their password at each administrative prompt like Linux does, or at least made it easier to enable that without having to use the registry editor. UAC also sandboxes programs running in protected directories. UAC isn't a dummy prompt, it's your defense against unknown exploits. The local user has to give software permission to make admin level changes to the system.

It amazes me that there's still a lot of anti-Vista/UAC FUD still floating around out there. The only real alternative to privilige escalation is a closed off app store style environment where the device manufacturer (hopefully) checks all the software they host.
 
OEM 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.
Then
As long as everyone thinks with this kind of prejudice, it will never be unfortunately.
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.
 
Back
Top