I’m going to be honest with you, as often as this has been memed and for as long as I have been using Windows on my work computer, I have never once been forced to restart on the spot by an automatic update.
I’m sure those who have will be quick to reply but at this point I’m 90% confident it’s a loud minority.
I’ve seen an entire factory shut down for hours because two critical Win10 computers tried and failed to update. It’s never an issue until it becomes one.
Plus a failed update is the whole reason I nuked my C: drive and switched to Manjaro (now running Arch, put down the pitchforks).
Neither of those options were available. It was written by a third-party for some old .NET Framework version, and the server and GUI components were written as a single application. Putting it on a server wasn’t an option either because the application’s GUI was constantly used for the management of assembly machines, and other applications were used for monitoring and administrative stuff.
If you had been there, you’d know why this was a low-priority risk. That place was bleeding from a thousand wounds. At least this had some redundancy, for all it was worth in the end…
(edit) I actually contributed to that software, even though it’s not open-source! I managed to nail down an issue where loading a project file using one locale would result in a crash, but not in others. The .NET stack trace was printed to an XHR response’s payload and I used that to locate a float.ToString() call where CurrentCulture was passed as the cultureInfo instead of InvariantCulture, so depending on the computer’s locale, it would try to parse CSV data either using a decimal dot or a decimal comma. I mailed this to the maintainer and the fix was released within the month.
I’m saying it’s never happened to me. Not once. Zero times. Zero is less than one.
Normal Windows updates don’t take an hour long. Give me a break. The ones that do are the version upgrades. That’s like the equivalent of a distro upgrade.
That happened in 2013 with random laptop they gave me. I kid you not it took that long, could have been a bug somewhere in the OEM, never cared enough to find out.
But my experience is just as real as much as yours.
Correct. But who can tell the difference beforehand between a normal update and an abnormal one? The problem is Windows tends to hide those details. I’ve sat on support calls where a server needs to be rebooted for some configuration change, and Windows insists on applying updates because hey, you’re rebooting anyway, so what if it takes 1/2 hour to do this thing that should take 5 minutes…
Sure Windows gives you warning, but after a while it FORCES you to install, even if for whatever reason that new branch bricks your computer. I had a good 6 months of that where every time my computer got shut off, it would force the update and fail like 40 times before it finally let me revert and use my computer. There was no way to tell it to STOP UPDATING
I had almost the same thing for about 2 months before I gave up and switched to linux, only difference is I would get up to go to the bathroom, come back and it’s already trying to up date, that happened to me pretty regularly
Ive not had “must update on the spot right this very second,” but ive had countless, “we will update the second u power off or attempt a restart. If you try and restart into ur linux partition, we will somehow ensure u fail to boot right up until u got thru with our forced update.” Which also sometimes goes hand in hand with, “oops, i was supposed to update, but i shit myself instead. Youre going to need to try again at least once or twice. Dont worry, whether the update goes thru or not, itll only take a maximum of 90 minutes.”
Windows can fuck its facehole thru its ass as far as its auto updates are concerned for all i care.
I’m going to be honest with you, as often as this has been memed and for as long as I have been using Windows on my work computer, I have never once been forced to restart on the spot by an automatic update.
I’m sure those who have will be quick to reply but at this point I’m 90% confident it’s a loud minority.
I’ve seen an entire factory shut down for hours because two critical Win10 computers tried and failed to update. It’s never an issue until it becomes one.
Plus a failed update is the whole reason I nuked my C: drive and switched to Manjaro (now running Arch, put down the pitchforks).
Well, running Windows 10, a consumer user-oriented operating system, to control mission-critical machines is mistake number 1.
This wouldn’t have happened if they had used Windows Server or something actually designed for that task (like Linux!).
Neither of those options were available. It was written by a third-party for some old .NET Framework version, and the server and GUI components were written as a single application. Putting it on a server wasn’t an option either because the application’s GUI was constantly used for the management of assembly machines, and other applications were used for monitoring and administrative stuff.
If you had been there, you’d know why this was a low-priority risk. That place was bleeding from a thousand wounds. At least this had some redundancy, for all it was worth in the end…
(edit) I actually contributed to that software, even though it’s not open-source! I managed to nail down an issue where loading a project file using one locale would result in a crash, but not in others. The .NET stack trace was printed to an XHR response’s payload and I used that to locate a
float.ToString()call whereCurrentCulturewas passed as the cultureInfo instead ofInvariantCulture, so depending on the computer’s locale, it would try to parse CSV data either using a decimal dot or a decimal comma. I mailed this to the maintainer and the fix was released within the month.Yes, because even once is too many.
In a corporate, I spent an hour and half every morning waiting for Windows to update. Then my coworker handed me Fedora DVD and I never looked back.
I’m saying it’s never happened to me. Not once. Zero times. Zero is less than one.
Normal Windows updates don’t take an hour long. Give me a break. The ones that do are the version upgrades. That’s like the equivalent of a distro upgrade.
Sure, your experience may be different.
That happened in 2013 with random laptop they gave me. I kid you not it took that long, could have been a bug somewhere in the OEM, never cared enough to find out.
But my experience is just as real as much as yours.
Correct. But who can tell the difference beforehand between a normal update and an abnormal one? The problem is Windows tends to hide those details. I’ve sat on support calls where a server needs to be rebooted for some configuration change, and Windows insists on applying updates because hey, you’re rebooting anyway, so what if it takes 1/2 hour to do this thing that should take 5 minutes…
Sure Windows gives you warning, but after a while it FORCES you to install, even if for whatever reason that new branch bricks your computer. I had a good 6 months of that where every time my computer got shut off, it would force the update and fail like 40 times before it finally let me revert and use my computer. There was no way to tell it to STOP UPDATING
I had almost the same thing for about 2 months before I gave up and switched to linux, only difference is I would get up to go to the bathroom, come back and it’s already trying to up date, that happened to me pretty regularly
Ive not had “must update on the spot right this very second,” but ive had countless, “we will update the second u power off or attempt a restart. If you try and restart into ur linux partition, we will somehow ensure u fail to boot right up until u got thru with our forced update.” Which also sometimes goes hand in hand with, “oops, i was supposed to update, but i shit myself instead. Youre going to need to try again at least once or twice. Dont worry, whether the update goes thru or not, itll only take a maximum of 90 minutes.”
Windows can fuck its facehole thru its ass as far as its auto updates are concerned for all i care.