This was a huge problem, for me. Some multiaxis CNC toolpaths require days to generate. I missed a critical deadline as a result of Windows 10 deciding to update itself, which finally prompted me to install ShutUp10 from O&O.
I use the maximum shit-disabling mode in ShutUp10. It works. Once or twice a year, I run Windows Update and get updates, then I run ShutUp10 again and disable all the trash Microsoft re-enables.
https://www.majorgeeks.com/files/details/windows_update_mini...
I'd rather describe this as a mail-in-rebate for the costs of running Windows 10.
We sort of implicitly know there is this need to make the Windows lifestyle more sane, and can rely on tools like these existing.
But the time it takes to research this, track down the best binary for the job (examining the source code is not always easy), makes me conclude that there's a real hidden cost to being a Windows user.
The most impressive thing about Microsoft as a company is the way it single-handedly lowered user expectations to the point where ads, security issues, and critical time-wasting failures are somehow considered an acceptable price of entry, and not evidence of an unacceptably shoddy, incompetent, and user-hostile product culture.
The relevant dichotomy is more like: people who run Windows aren't the buyers. One-off personal licenses for home PCs are more than a rounding error but are certainly not what made Microsoft what it is.
Governments and F500 companies buy Windows and Office for X00,000 machines for X0 years of support at a time. Enterprise procurement teams are the actual buyers whose opinions matter to product managers.
Does MS sell their telemetry data?
> I paid $200 for a Windows 10 pro license because I needed to run a Windows application in a virtual machine.
I think if someone is willing to cheat on the licensing cost 4hey might just as well go with a pirated XP?
Remember that time Microsoft let FTDI brick a bunch of knockoffs through the first party update mechanism? Remember when they locked up a bunch of embedded devices with Windows 7 support nags? Remember when they dropped Candy Crush in your start menu, when they decided local accounts now had to be cloud linked, and when they enabled Cortana by default and made it increasingly difficult to opt-out? When they decided to take 30 minutes of your morning without asking (hope you weren't planning on using the computer for anything important)?
When it comes to high-reliability embedded OSes, Microsoft is a case study in inept paternalism. Updates regularly cause problems. Between updates and malware spreading behind a NAT, I'm not at all convinced updates are the lesser of two evils. Ideally, these applications wouldn't run windows, but since they often do, IMO the best approach is to isolate them to the greatest degree possible which includes blocking auto-update (note: not turning it off, blocking it, along with everything else you can get away with).
I've also rebooted to find out about Microsoft Edge, the new browser that's now pinned to my taskbar, even after removing Edge several times.
MS finished making Windows into a stable, usable OS and then promptly began turning it into adware.
I just installed a new Windows 10 VM last week and there was no option to use a local account anymore. None. No dark pattern menu link somewhere hidden in a corner of the screen with low contrast, only the choice between logging in or creating a new Microsoft account. Which took me longer than the whole rest of the installation, because as it turns out generic addresses like "[email protected]" are already taken and Microsoft seems very anal about certain choice words.
But at the same time they don't seem to mind if I enter a date from 2018 as my birthdate and the calendar dialog includes decades of future dates, but at least they got the forced online account working...
> Between updates and malware spreading behind a NAT, I'm not at all convinced updates are the lesser of two evils.
You can get your answer looking back to events like Nimda and Code Red.
Now I run a rolling distro since 2018. Development got a whole lot simpler, everything is more enjoyable and to date there's been exactly one noteworthy issue which was resolved after a quick search and 10 minutes.
And since then I've never seen a "new update available" popup dialog, no ads, no Cortana, no "smart" features, and most definitely no need to install third-party software to actually have a usable file search. I even update much more frequently than Windows 10 every forced me to, because for some reason I just never have any issues and I can just do it in the background.
I wish Windows would let me treat it like a car.
* I log in.
* I start setting things up so I can start work.
* I'm notified about critical updates. There will be a forced reboot soon...
* I'm watching out in case something pops up while I'm typing and whatever key I was about to press causes the 'reboot' question to be answered - and I wait several minutes and lose flow entirely.
* I log in.
* I start setting things up again as they were so I can start work again.
* There are more critical updates...
Turning off auto-update is not an option, because there are so many security holes and I don't want to end up a victim. I also don't like having to fight to try and keep the OS from doing something it will push against, so trying to creep around letting it do updates when I'm not busy and reboots when I want it to but not asking me - waiting to be told - it's hard work and stressful.
Windows is an amazing piece of tech and gets better all the time, but I find myself much more able to stay in the 'flow' and avoid stress in MacOS or Linux.
I think I get it why it wants to reboot: not only is it probably somewhat safer in terms of not screwing anything up in running session, but you can't be sure some running application or service isn't still using an outdated version of a library until you've restarted it. (Not to mention that the Linux kernel updates every week or so nowadays, but those are definitely not the only ones that trigger an update [edit: by which I of course mean "trigger a reboot"].)
I tend to not use the graphical software updater and just ignore its notifications instead, and just update from the command line and reboot when it suits me. That does allow me to not have my workflow interrupted but it doesn't change the fact that I still do get notified of updates that require some kind of action pretty often.
On the other hand, checking for those updates doesn't burn minutes on end of CPU time every time the OS is booted, as it seems to do on Windows 10.
But no, obviously Fedora doesn't force a reboot, nor does it give a prompt you can accidentally reboot through.
However, a part of the complaints (which I fully understand) seemed to be about the frequency of the updates, and in the name of honesty I just wanted to point out that's not really just a Windows issue.
I have said it before, but around half of the machines in my estate are macs, and I have many more reported update problems from them. I think a lot of it is caused by inconsistent updates.
I've been running one at home since the first TP in 2006, and I don't spend any time thinking about or maintaining them (running on Debian)
I wish that was the case.
It may not be a perfect situation but I don't find it to be quite as dreadful as many make it out to be. FreeBSD is my other OS and I'll be honest, I dread doing those updates much more.
Windows 10 hasn't always warned you about an update. Once I lost a half days work while visiting family. I had been doing some genealogy work, when some small kids come over, so I put my laptop asleep (shut the lid) and went about my day, not thinking to save. The next day, opened my laptop and was greeted with the "Hi! We are setting things up for you" screen. Was very upset to have to redo the previous days work.
You may not always be at the computer if you're waiting for some kind of a long-term process to finish.
No store, no advertisements, no telemetry, Edge optional, all Enterprise features enabled, security updates only (defer fully configurable), out of the box.
I use it at home and with my family members.
We have to trick our immune systems because we didn't design them.
An OS is, obviously, designed by humans. So we shouldn't have to trick it.
Of course, you're not the only one with this issue. There used to be an option in "gpedit" to disable this, but I can't find it anymore. I suspect that this is because there is now an option in the "advanced options" of the "Windows update" menu, called "restart this device as soon as possible".
It's very SV-bubble to assume that Microsoft's security needs are more important than him getting his work done.
As he stated, he missed a critical deadline. What if the client cancelled the contract because of that, causing him to go out of business? How does trying to sympathize with Microsoft feed his family?
No, the tech bubble is not more important than things that happen in the real world. Windows has security problems? Sure, all operating systems do. But Microsoft shouldn't shift its problems onto the users. That's just bad business, and bad ethics.
I don't like the automatic reboots, and I'd agree it's not a good solution and I probably wouldn't have implemented it if I were making the decision, but I don't really see how finding reasons for why MS might reasonably want to do it is a SV bubble thing.
The bubble isn't a geography, it's a mindset.
Once a month I update my work PC and three home PCs, all on the same day. Easy to remember, saves surprise updates and reboots.
Similar to how getting a vacination is not only good for you, but also for the rest of society.
Mind you, I'm saying this from a perspective of someone who uses his machine to perform nightly jobs (learning models, ontology alignment, etc) So it's not like I haven't shared your pain =)
Thanks for the explanation, but I'm well aware of malware. I wrote my own boot sector viruses back in 8-bit days.
But the point still stands: Microsoft's practices stop him from doing his work, and could cost him his livelihood because it assumes that fixing its failures are more important than his work. What's the point of even having the computer if it can't be relied upon to do complex tasks?
I tend to agree, but I have difficulty when you scale the problem. No individual person benefits from having their computer rebooted enough to counteract the issues, but might everyone collectively? The utilitarian calculus becomes difficult.
Though parallel solutions: better security testing or a capacity for live updates without a reboot, may be an answer.
Same as you, I periodically turn off the metered connection toggle and then run updates. It saves me a heap of angst.
And this is why I tend to ignore most commentary on Operating Systems. You know the moment that Windows releases a centralized repository, there will be a thousand cries of "walled garden!" and "embrace, extend, and extinguish". It's literally impossible to satisfy everyone, given how many mutually exclusive needs exist out there.
- You can still install applications manually, and there are no special permissions lost for doing so.
- You can access it using your choice of application, instead of only the MS-approved tool
- You can add 3rd party repositories
If that's what the "Windows store" was, I'd absolutely use it (if I still used Windows). If it comes along with a bunch of other crap, then yeah, there will be pitchforks.
What does seem to work is the certificate and code reputation. It does actually prevent users from running things but is easy enough to click through if you really know better.
Yes, that's the "other crap" I was referring to [edit: specifically "special permissions lost for doing so". I was a little vague because I knew there were some additional restrictions for using the Windows store but wasn't sure what they were.]
I didn't spend enough time to verify if it satisfies the "can use other clients" and "can add 3rd party repositories" criteria. But assuming it does, I bet tons of people would happily use it, if Microsoft blessed it as the official standard for managing Windows applications / installed it by default.
https://github.com/microsoft/winget-cli
I like scoop though personally.
This is only true when the centralized store is the only way of installing software. That's why iOS is called a walled garden, but not Android.
I think, though, I've come to realize why: backwards compatibility. I've seen videos where people have installed Windows 3.1 and then upgraded the OS from there and pretty much everything continues to work. I think in one video I saw, Quake or Doom stopped working after one upgrade (probably Vista) and then started working again after a patch release or something.
I have to hand it to Microsoft that they honor backwards compatibility as well as they do. However, at some point, you have to just make a clean break. You have to acknowledge that what you have is bad and broken and should no longer exist in this world. Microsoft finally did just that with Internet Explorer and then (to a lesser degree) with replacing Edge's rendering engine.
For Apple, backwards compatibility isn't a sacred cow. They're more than willing to throw something out that is old and/or doesn't work as well as it should. They handle breaking that fairly well, all things considered. They give plenty of notice (sometimes not as much as they probably should have -- https://arstechnica.com/gadgets/2018/01/apple-prepares-macos...) so average and power users alike have the time to transition. Sure, it's never as smooth as we would like but what transition ever is? Still, Apple users don't have to deal with things like Windows users do.
Microsoft needs to start making a clean cut with Windows, probably starting with the Explorer shell. It's old. It's obnoxious. It actively gets in the way and makes me less productive. They can do this if they just put their shoulders into it a little. (Christ almighty why does the scroll bar have to jump back to where it was if my mouse veers away from while scrolling? "Because that's how we've always done it!" is easily the worst answer to any question ever asked)
Also, for the love of all that is holy they need to reverse the decision to have ads built into the OS. How can they not see how bad an ad-centric model is becoming for Google and Facebook? Having a whole OS where the user is the product? That's a privacy nightmare that makes Google and Facebook look like little league.
But Microsoft then throws a bunch of stupid crap on top of it like Candy Crush ads for a piece of software that costs $200 and kinda ruins it. Or with all the deep hooks for Windows Defender & friends that just cripple process launching & file creation performance.
Can't the same be said with Linux too? Major distros has Linux with KVM kernel module built-in. I never had to do anything rocket science to run KVM, for example.
I use it to model and test code that will take hours to fold into a build for our embedded target. On the last feature I completed, I wrote 2500 lines of pthread / Unix domain socket server code, and it ran on my WSL/Ubuntu target with only lightweight text file based shims to replace drivers on the embedded target. When I slid it over into the embedded build flow, it ran on the first try, no changes.
Compiled as a unit test harness in about 3 seconds on my WSL instance. Our full embedded target takes 30 minutes to build. So the WSL/Ubuntu instance is a huge time saver.
Linux is a different and somewhat distant version of UNIX.
-On Windows Home however, it comes with Candy Rush and a bunch of nonsense that show up in the Start menu tiles. I just uninstalled them and call it a day.
-Yeah this is my biggest issue.
-Indeed but I have not even thought about it.
You can turn off advertisement during installation, and set up privacy measures like don't give up hardware id for advertising.
I had no problem with windows restarting itself during work hours. After you install all drivers, it would only restart during night time while I was sleeping.
About central repository, is true. You have windows stores, but is very incomplete. The best tool I found to help me was chocolatey, and it saved me a few hours. https://chocolatey.org/
What? Where? How do you tell it not to advertise the new Edge or Candy Crush in the Start Menu during installation?
> and set up privacy measures like don't give up hardware id for advertising.
some privacy measures. For others, you still need to manually turn them off via gpedit or using a 3rd-party-tool like OO Shutup.
Source: Have installed win10 more times than is healthy.
ShutUp10 is probably your best bet, or something like this: https://gist.github.com/alirobe/7f3b34ad89a159e6daa1
Edit: If you don't mind a little up front prep time, you could probably create install media for windows that would run one of the above programs immediately after finishing the install. If you have to do it multiple times quickly that may save some time.
The fact that these are required at all is ridiculous, and (part of) why I run Linux/BSD these days.
On something you paid $200 for? WHAT? What is this world coming to?
Use https://www.microsoft.com/en-us/solution-providers/ and pick one of the companies in your area. It largely doesn't matter.
Shoot them an email explaining what you want and they'll have you meet the 5 license minimum for volume licensing by buying a Windows Pro License a Windows Enterprise Upgrade license, and 3 user cals which are cheap. They'll put your name down as the business and then you're done.
If the OP indeed meant "Windows LTSC", then I'm not following along with their point.
You can't. It asks you if you want to not share data, but warns you that this will result in less personal ads.
So you can opt for non-personalized ads, but you can't turn off ads altogether during the install.
- half of the things are for stuff you shouldn't have to opt out of in the first place in any reasonable OS
- that's if you can even opt out of them
- the settings/ways to do so are often obscure/ obscured
- come next update, your settings are never safe, and you can't have faith they didn't add more bullshit that you have to research and find ways of turning off
Server does require initial tweaks to run smoothly on a desktop machine. Some security and telemetry policies need relaxed, audio service doesn't run by default, Internet Explorer Enhanced Security Configuration needs disabled so you can grab an installer for your preferred browser, and other minor things like disabling Ctrl+Alt+Del on the login screen.
The result, though, is that you get an OS that acts like regular old Windows 10, with _zero_ ads and (I think?) less telemetry. I have not seen anything Pro can do that Server cannot, even gaming (Steam, AMD graphics drivers) works fine. As a bonus, you're not subject to any of the restrictions that Pro has for advanced workloads like virtualization. Server Manager along with all the extra utilities not found on Pro are also nice to have.
Updates are still downloaded/installed automatically, but servers can't reboot whenever they feel like it, so I'm not ever interrupted by unwanted reboots like on Pro.
Just set 'active hours', turn off everything under 'Advanced', and if you really want to not do any updates for a while, you can select a date a date 35 days in the future to restart updates.
Three very simple things built into the update tool.
If you are on a corporate machine, they may limit what you can block based on their internal rules, but that is an IT problem, not Microsoft.
Windows 10 never updates or reboots during my active hours. I always defer updates to a long time out, then manually update at a point where I want to. Problem solved.
[2] https://docs.microsoft.com/en-us/windows/package-manager/win...
2. There's an option to disable automatic restart for updates
3. There's the winget package manager, but it's still in preview. There's also chocolatey and scoop, which are community run, but that's similar to homebrew on macOS.
Where? I've been able to defer reboot, but not disable it completely. ShutUp10 seems to (mostly) work, but automatic updates/reboots somehow get re-enabled sometimes.
With Group Policy: if you are logged in, Windows will pop a modal dialog in your face and you can preempt it there, but just leaving an application running and being AFK will not prevent reboot if Windows has decided it has waited long enough. The amount of time I can ignore the "restart" request in Windows Updates varies from days to weeks for me.
I hate the behavior with a passion, but I can see why Microsoft wants to force reboots eventually. Having un-updated Windows is not good for 90% of the people out there.
Honestly speaking, Windows 10 is as far from the spirit of the "I'm a PC" and "Windows 7 was my idea" ad campaigns as you can get. Now it's just "You will bend over and take what we give you, for the greater good"
If you want full control of your OS, you need to switch to a BSD or Linux, with appropriate expectations about the applications you will or won't find there.
Edit: fix grammar/punctuation a bit
Stop spreading lies. It does work. (I also have hot had ads in Windows on all Windows machines I own. But this is a Microsoft product, which always raises these long list of myths.)
Instead of name-calling, maybe post the group policy here that allows you to never reboot after updating.
So the solution, as I said, is to not install these updates. (Or reboot, but you say you don't want reboots.)
https://developer.microsoft.com/en-us/windows/downloads/virt...
Sounds like you have problems with reading or clicking links, it's a: Windows 10 Enterprise
>Likely nix23 upgraded to Win10 Pro from Win10 Home for this reason.
WHAT? I run freebsd and develop/maintain sometimes Windows "Apps" with the virtual machine.
This works for my web testing purposes, but probably isn't practical for a CNC machine.
Since the CNC maschine/controler should no be connected to the internet anyway it's not important...and even then, you still get sec-updates.
>Get a Windows 10 development environment
>Start building Windows applications quickly by using a virtual machine >with the latest versions of Windows, the developer tools, SDKs, and >samples ready to go
So i say thank you very much Microsoft.
> You may use the software in the virtual hard disk image only to demonstrate and internally evaluate it. You may not use the software for commercial purposes. You may not use the software in a live operating environment.
I think the heading Get a Windows 10 development environment is referring to downloading the image, rather than to licensing. I agree it's not very clear.
I’ve also had forced restarts while a directX application was in full screen and I didn’t see the windows pop up.
I paid $200 for a Windows 10 pro license because I needed to run a Windows application in a virtual machine. I was very unsatisfied with my purchase. I would describe Windows as “a nightmare”. Here are my top three complaints about Windows.
* There are advertisements built into the operating system.
* The operating system often restarts itself, without the users permission. It will restart itself even if a user launched application is running.
* There is still no central repository for useful applications. Managing and keeping all software updated takes a lot of manual work.