Every Windows 10 Update is a New Disaster

[XavierMace]

I couldn't even tell you how many Windows 10 systems we manage beyond it being many thousands. I'd say the number of systems that have had issues caused directly by updates is less than 50.

 

[lxskllr]

I don't hear complaints about the Win10 system I setup for the secretary at work. So far, the only issue I've had was Defender put one of the executables for the accounting software in quarantine. I usually check the computer every other day or so, and just happened to see it. That could have been an issue if she tried to use the system.

Other than that, it seems fine. I don't use Windows at all, so I may miss aggravations regular users have, but as far as Windows goes, I like it about as well as other versions.

 

[Greenman]

I swear people on this board seem to have more issues with Win10. I've been running Win10 since it was in beta and haven't had any issues with it. Did the free upgrade a few years ago on all the pc's in the house and never have issues. Five pc's all humming along fine with Win10 at the helm.

And for the record I would recommend against installing Linux or any of its variants on your moms computer. I can't even in good faith recommend Linux Mint which is the pride of the fleet. Sudo this and sudo that and adding ppa's to get programs that aren't in the official libraries which are horribly outdated btw. Googling an issue only to think you have found a solution but when you copy and paste the syntax into the terminal it does something but not what you wanted. Good luck trying to find out how to undo what you just did.
Uggg...putting Linux on a moms pc is a terrible idea.

My MIL doesn't google issues, she doesn't install applications, and there is no way on earth she could even find the terminal. She can turn her computer on, open chrome, and get to her email. She knows how to print which she's done two or three times over the last few years.
Mint was a godsend for me as she had never ending issues with windows. Mint works day in day out, it doesn't crash, it doesn't lock up, it just hums along doing the few things she needs a computer for.
Given the choice of running win10 on her machine for free, or having to pay $300 for Mint, I'd pay for Mint without a second thought.

 

[paperfist]

I just built my mom a new windows 10 pc last week and it works like a charm and we haven't had a bad update since the original version was released. Have you tried running the windows file checker to see if any system files are corrupted? Next would be use a registry repair utility to clear out bad entries.

Penguins belong in their native habitat not on any of my desktops.

Wait till one of those Creator updates come knocking

 

[shortylickens]

Solitaire has ads.


VIDEO ADS!

 

[BonzaiDuck]

I really understand the frustration.

In my own case, I can almost be sure that another feature or Creators update will bork my dual-boot system (Win7/Win10). I'm also fairly confident that a routine application of a self-booting Macrium Repair disc will set it straight. At least, that's what I get from the small sample of two updates (#1703 and #1709) both resolved and fixed the same way.

I can also imagine some variety or range of hardware that offers some fateful combination that causes these problems with the feature updates. Somebody above mentioned a C2 Quad system, perhaps a laptop, that was cause of much troubles. I have a C2D laptop which never seems to miss a lick with these updates, but it is so slow compared to my other systems. I use it with our surveillance software -- it works fine. But I've got in mind to purchase a new laptop in the next year.

It seems that we welcomed computers into our lives to save us time. I only wanted to do statistical analysis of Box Jenkins time-series models. I didn't want to "friend" people on Facebook. But I began to embrace the challenge of "fixing windows" with my hardware, investing more and more time in the experience. I could also say that it is some sort of perverse hobby right now.

But I feel your pain. I have FELT your pain. But to the end of suffering it, I make sure I've got at least one reliable computer running Windows 7. I have to have multiple computers as insurance that some incident posters have described above doesn't cripple my life!!

 

[Markfw]

Well, there are several problems with the fall creators update. First, every computer that I have seen that completed successfully, has had printer driver problems, only some of which have been fixed. I personally have 2 different socket 1366 systems that end up with a black screen, and the only way to fix it, is to roll back. But then windows borks the computer by updating again ! So now I have a useless Xeon X5570 computer with 18 gig of ram ! And a useless I7 950

 

[DAPUNISHER]

I personally have 2 different socket 1366 systems that end up with a black screen, and the only way to fix it, is to roll back. But then windows borks the computer by updating again ! So now I have a useless Xeon X5570 computer with 18 gig of ram ! And a useless I7 950

The only way I have been able to resolve the issue on affected systems, is a clean install of 1709. PITA when you have a bunch of programs and such you do not want to reinstall, but at least the system gets back up and running.

 

[Ketchup]

I have run into driver issues here and there, and I believe that is what Microsoft is trying to fix with their Device Installation Setting feature (btw, they need to be trying a lot harder with this one). I think the majority of issues come from users (myself included) running 10 as an upgrade on older hardware. It seems that for new hardware, it does fine. But since Microsoft pushed so hard to have people upgrade (anyone using 7 and up), we are seeing a lot more "issues" this time around than we have in the past.

 

[Markfw]

The only way I have been able to resolve the issue on affected systems, is a clean install of 1709. PITA when you have a bunch of programs and such you do not want to reinstall, but at least the system gets back up and running.

I did a download of the win 10 iso, how would I know what version that is ?

 

[Markfw]

I have run into driver issues here and there, and I believe that is what Microsoft is trying to fix with their Device Installation Setting feature (btw, they need to be trying a lot harder with this one). I think the majority of issues come from users (myself included) running 10 as an upgrade on older hardware. It seems that for new hardware, it does fine. But since Microsoft pushed so hard to have people upgrade (anyone using 7 and up), we are seeing a lot more "issues" this time around than we have in the past.

MY problem is that it already had win 10 on it, the computer won't even complete a boot in safe mode under 1709. The previous version of win 10 works fine.

 

[mxnerd]

I used to be able to use my Brother 2270DW for duplex printing on Windows 10 using Win10 native driver.

Yesterday when I try to print document using the duplex feature, I found that I could not find the option any more!

Don't know which update caused this.

I had to download driver from Brother website to fix this.

 

[DAPUNISHER]

I did a download of the win 10 iso, how would I know what version that is ?

Sorry I took so long to answer; surfing with my son, since it was senior skip day. The latest iso will be 1709 so you are good to go.

 

[Markfw]

Sorry I took so long to answer; surfing with my son, since it was senior skip day. The latest iso will be 1709 so you are good to go.

Dated last sept ? thats when I made the USB I think.

 

[BonzaiDuck]

Well, there are several problems with the fall creators update. First, every computer that I have seen that completed successfully, has had printer driver problems, only some of which have been fixed. I personally have 2 different socket 1366 systems that end up with a black screen, and the only way to fix it, is to roll back. But then windows borks the computer by updating again ! So now I have a useless Xeon X5570 computer with 18 gig of ram ! And a useless I7 950

Do the installations go to completion? Or do they fail to complete? If they finish, and a reboot shows no system post, I'd try and repair them with a boot-sector/boot-record repair utility -- like Macrium. I had the "blank screen" failure to post appear soon after updating to 1709. I was developing a plan to pull hardware, one item at a time. I was lucky for being inquisitive enough to suspect a boot-disk problem.

 

[Markfw]

Do the installations go to completion? Or do they fail to complete? If they finish, and a reboot shows no system post, I'd try and repair them with a boot-sector/boot-record repair utility -- like Macrium. I had the "blank screen" failure to post appear soon after updating to 1709. I was developing a plan to pull hardware, one item at a time. I was lucky for being inquisitive enough to suspect a boot-disk problem.

Nope, all the installations go fine. After a reboot its a black screen and a perfect mouse cursor that works AND if I crtl-alt-del, I get a menu (in blue solid background) ! Task manager, change user something like that. But if I follow the instructions to get to safe mode, it will lockup right when you see a blue background with the version in the 4 corners.. Clicking in the start button gets a blue swirling circle, and a box that says something is not responding. Its locked up. And I waited, it just says not responding, shut down app, then repeats.

 

[DAPUNISHER]

Dated last sept ? thats when I made the USB I think.

that is too old, make a fresh one tonight.

 

[Markfw]

that is too old, make a fresh one tonight.

Well, thanks to Microsoft jerks, my son will now loose all his software. It will all have to be reinstalled, and some may have to be paid for again ! (CAD software)

 

[VirtualLarry]

Well, thanks to Microsoft jerks, my son will now loose all his software. It will all have to be reinstalled, and some may have to be paid for again ! (CAD software)

Well, technically, blaming Microsoft would be incorrect. It's the vendors of the CAD software that should be complained to.

 

[Markfw]

Well, technically, blaming Microsoft would be incorrect. It's the vendors of the CAD software that should be complained to.

So whether I have to pay for the software or not, because Microsoft forced the update, and my sons computer for WORK is down indefinitely, and best case scenario is that I spend days reinstalling everything, its not their fault ? Come on Larry....

 

[homebrew2ny]

Been using 10 on multiple computers since day 1 including laptops, never had a single issue. Can't help but feel most issues are user error (knowingly or otherwise).

 

[Markfw]

Been using 10 on multiple computers since day 1 including laptops, never had a single issue. Can't help but feel most issues are user error (knowingly or otherwise).

Have you read my posts ? System works perfectly on win10 version previous to 1709. Windows forces an update to 1709. Computer is not function afterwards. I didn't even though anything, Microsoft did.

And you say its user error ? How is that possible. ??????

Oh, and all the drivers that it breaks with no intervention, those are user faults also ?

 

[mindless1]

And you say its user error ? How is that possible. ??????

Tell us again what OS you're running. That's how it's possible. Win10 was known to be a time bomb.

 

[BonzaiDuck]

Nope, all the installations go fine. After a reboot its a black screen and a perfect mouse cursor that works AND if I crtl-alt-del, I get a menu (in blue solid background) ! Task manager, change user something like that. But if I follow the instructions to get to safe mode, it will lockup right when you see a blue background with the version in the 4 corners.. Clicking in the start button gets a blue swirling circle, and a box that says something is not responding. Its locked up. And I waited, it just says not responding, shut down app, then repeats.

The symptoms are a slight variation with differences from mine. First time around, with #1703, the system wouldn't present my dual-boot menu, or it wouldn't operate properly. Even so, I could still eventually get "into" either OS. Fixing the boot record with a bootable Macrium, EaseUS or MiniTool disc fixed it. Second time, system would not post, and I feared hardware failure. RAM? PSU? graphics card? I pondered all these things, but decided to see whether it would boot from the repair CD. That was lucky.

Even so, with the dual-boot system, the CD would show the system could boot, but it couldn't "see" the OS versions to fix. I'd go through about five or six resets and get it to boot to Win 10, assigning drive letters to the Win 7 partitions. Then, the repair disc program would show the win 7 partitions. I could eventually get into Win 7 and made sure to assign drive letters to the Win 10 partitions, and rebooting to the CD would now show both OSes -- so the repair proceeded speedily.

It's nice to have a stellar backup imaging system that is updated daily excepting weekends . . .

Someone else recently-posted was mystified that "somebody didn't do something properly." I don't think MS much considered or cared for dual-boot installations with Win 7. I intend to suffer through these feature updates, and simply run the repair disc as a routine after completing them. And I'm lucky enough to be able to return the system to pristine operation in maybe an hour's time, if the same remedy continues to work.

 

[homebrew2ny]

Have you read my posts ? System works perfectly on win10 version previous to 1709. Windows forces an update to 1709. Computer is not function afterwards. I didn't even though anything, Microsoft did.

And you say its user error ? How is that possible. ??????

Oh, and all the drivers that it breaks with no intervention, those are user faults also ?

I have been reading, and I understand you are frustrated pointing blame outward. However, seeing how windows update works perfectly on the vast, VAST majority of everyone else's computers working windows 10, I am nudged to believe it is a conflict to something specific to your machine(s), or those close to you. Perhaps its conflicting with an unusual setting manipulation you did, or some piece of software not fully supported in windows 10 that you install. Perhaps its a registry error that went unnoticed until the update.. The possibilities are almost endless as to why it might of happened, but (and again) I cant help but think fault is at the user end or at the very least, attributable to some piece of non windows 10 software installed causing the conflict, that will inadvertently also fall on the users shoulders.

The bottom line is, is if windows 10 updates were actually killing perfectly working machines with nothing but supported software installed, then the internet would melt down with all the complaints. as it is, its a teeny tiny fraction of a percent of users who have problems and that usually spells user error. Sorry, but good luck!