you either have a bad image/install of windows 10 or some software that was being installed is not working right with windows 10 which likely isn't MS's fault.
- - - Updated - - -
you can control when you update in win 10.... granted it's best to configure working hours and let it updates itself when it wants to imo. And yeah fine using a no longer supported/updated/patched OS.... not so much.
Member: Dragon Flight Alpha Club, Member since 7/20/22
May be, but OpenShell also allows you to have almost 7-like Aero Start menu (default skin is flat 8-like), it also allows you to have task bar, looking similar to Aero one. What OpenShell can't - to change that stupid ugly flat theme. And list of such small changes goes and goes on. And it brings simple question. Why should I bother about that all that crap, if I have fully functional OS with perfect visual theme?
It's same crap, that happens with Wow now. Wow loses subs due to wrong game design, players tell Blizzard, what is wrong with their game, even FF starts to be more popular, but nothing is done to fix it. Instead, Blizzard go further and further along that road of terrible design, like if they would have some intentional plan about it.
For example M$ failed to conquer mobile market and now they try to abuse their core desktop auditory in order to make them become used to Windows-specific design and then push them towards M$'s devices with mobile Windows. But, as in case of relying on TBCC and killing retail - they risk to lose both sides at the same time.
Last edited by WowIsDead64; 2021-06-16 at 03:34 PM.
I don't care about Wow 11.0, if it's not solo-MMO. No half-measures - just perfect xpack.
But can you choose not to update? And never be asked about it? And of course win 7 is fine. I don't need support. I did not update windows 7 when it was still supported, I do not update it now. Because it just works as it is (just the IE does not work, but who cares about IE?). And everytime I updated Windows a different thing I installed broke, be it an old game, java, some application I installed, whatever. So I go by "don't fix what's not broken" and will continue to use my unupgraded system until I get new hardware that demands a newer operating system. Because what value does a new/updated OS have for me, if 50% of all the stuff I installed ceases to function properly?
I acknowledge that win 10 is better. But it is not so much better that I can be assed to build my setup anew, which would be required.
Technically, yes, but you have to disable the TrustedInstaller service to kill feature updates forever, but let me give you some context to this.
1. TrustedInstaller (tiworker) does much more than just feature updates, it handles any Windows Modules installs including driver registration
2. Windows 10 feature updates are treated as different OSes in the same way that we treat Windows 8 and Windows 8.1 as separate OSes (same with 2012 and 2012R2)
3. So if you choose to remain on 1803 instead of coming to 20H2, etc... you are choosing to remain in an OS that is no longer supported
If you do not want to kill TrustedInstaller on startup, there are other things you can do delay the feature updates of Windows 10
1. You can set a defer registry flag for 365 days to block all feature updates. 365 days is the maximum, after that time has expired, we will no longer honor the values set in this key, even if you keep on resetting them.
2. You can force compatblocks to have WUSA (Windows Update) see your machine as "not compatible for feature updates". I wont go into too much detail on this because its technically not supported and I shouldn't be giving you advice on how to make your system unsupported.
3. You can block WUSA via firewall rules, setting up a fake WSUS server (point to localhost), etc etc
I'm just letting you know that is possible to stop feature updates on Windows 10, just harder than it was on Windows 7
EDIT: Just to add... the defer key is not honored if your current feature version of Windows 10 is End of Support.
Currently all Windows 10 versions 1809 and lower are end of support except for LTSB (1607)
You can check your feature version with the Winver command
Last edited by Wavebossa; 2021-06-16 at 03:40 PM.
yes you can (https://www.windowscentral.com/how-s...lly-windows-10) but an OS that is no longer support is a wide-open target, click on bad link in email and up in smoke, it goes for example. the mantra of "if it's not broken don't fix it" just doesn't work in IT and is the hardest thing I battle at work forcing upgrades. Even the new MS edge is good (queue browser haters). Most software should run under win 10, esp if its patched to the latest version. If the software is old, outdated, or from a now-defunct company it could be an issue I guess.
Member: Dragon Flight Alpha Club, Member since 7/20/22
I know registry editing can achieve this. But that's very inconvenient. It must be a built in feature to give your customers the option not to update. If I wanted to be patronized I would use Mac OS.
And I simply know what to click and whatnot. I've never had a virus/adware/whatelse and I never activated the Windows Firewall anyways (since that thing was such a nuissance when playing over LAN).
Yes, for business and unexperienced users having updates applied automatically is a wonderful thing. But I am neither. The fact that win 10 does not even want to give me the option to choose whether to update or not combined with the fact, that Microsoft repeatedly put forth "updates" that broke win10 for many users, does not entice me to upgrade when I don't need to.
XP was great at the time.
7 was great at the time.
10 is great now.
Time to move on.
OOSU10 installed for privacy, and some other minor tweaks and im good. Yes Windows 10, windows in general, could be a lot better, but Im not gonna play on some ancient software...
Youtube channel: https://www.youtube.com/c/djuntas ARPG - RTS - MMO
Gaming: Dual Intel Pentium III Coppermine @ 1400mhz + Blue Orb | Asus CUV266-D | GeForce 2 Ti + ZF700-Cu | 1024mb Crucial PC-133 | Whistler Build 2267
Media: Dual Intel Drake Xeon @ 600mhz | Intel Marlinspike MS440GX | Matrox G440 | 1024mb Crucial PC-133 @ 166mhz | Windows 2000 Pro
IT'S ALWAYS BEEN WANKERSHIM | Did you mean: Fhqwhgads"Three days on a tree. Hardly enough time for a prelude. When it came to visiting agony, the Romans were hobbyists." -Mab
If you are on home Pro or Enterprise (wont work on home), you can make a local GPO to point a nonexistent WSUS server for updates, which will effectively do what you are asking for, and it is the closest thing to a "UI option" for this without manually altering registry flags. If you are genuinely interested in how to do this, i can show you. Its a very quick process, will take you less than 1 minute. Its not future proof though, we may decide to ignore it in the future.
However, I think people (not necessarily you) are conflating 2 different things.
Windows 10 is not 1 OS, at least that's not how we at Microsoft intend it to be. Windows 10 is many different OSes, and the feature set is the OS you are on. We dont say "are you running Windows 10?" We say "are you running 1803, 20H1? 1607?". The reason why is because these are separate branches that get updated concurrently. These are not really the same OS, the same way that 2012 and 2012R2 are not the same OS. Or 8 and 8.1 are not the same OS.
So I think you are talking about feature updates, and not the cumulative security updates that we roll up monthly. I think you are talking about going from 1803 to 1809 vs going from May monthly rollup.
I do agree that it would be nice for SOME users if we gave them an option to remain on their feature set indefinitely (like we did previously), but it would be absolute hell for us from a support side. Instead of supporting 8 and 8.1 (two separate OSes), we would need separate support for over 10 versions of Windows 10.
That's why we sunset older versions, it has to do more with support than anything else.
Even I disable automatic feature updates on my lab machines, because I have to have them remain at their unsupported version numbers to troubleshoot certain issues that only occur on certain versions.
I have an entire HyperV Cluster (3 hypervisors, 21 nodes) of Windows 10 machines just so I can bounce around versions quickly for testing.
Troubleshooting outdated versions sucks us haha.
That's a generous offer, but as I said: I will stay with win 7 on my current PC. When I upgrade to a new PC I will upgrade to win 10 (or it's successor), but I think until then I will have forgotten how to setup what you're suggesting, because considering the current prices for hardware I will probably have to wait at least one or two years until I get a new computer
Thank you for the insight! I can imagine that it's hard to support many different versions simultaniously and imo it would be completely fine to only support the newest feature set. But why not simply give the users the option to stay on an old, unsupported feature set? If it stops working for them, then they can still choose to update. Is it because the security updates are specifically designed for one feature set?However, I think people (not necessarily you) are conflating 2 different things.
Windows 10 is not 1 OS, at least that's not how we at Microsoft intend it to be. Windows 10 is many different OSes, and the feature set is the OS you are on. We dont say "are you running Windows 10?" We say "are you running 1803, 20H1? 1607?". The reason why is because these are separate branches that get updated concurrently. These are not really the same OS, the same way that 2012 and 2012R2 are not the same OS. Or 8 and 8.1 are not the same OS.
So I think you are talking about feature updates, and not the cumulative security updates that we roll up monthly. I think you are talking about going from 1803 to 1809 vs going from May monthly rollup.
I do agree that it would be nice for SOME users if we gave them an option to remain on their feature set indefinitely (like we did previously), but it would be absolute hell for us from a support side. Instead of supporting 8 and 8.1 (two separate OSes), we would need separate support for over 10 versions of Windows 10.
That's why we sunset older versions, it has to do more with support than anything else.
Even I disable automatic feature updates on my lab machines, because I have to have them remain at their unsupported version numbers to troubleshoot certain issues that only occur on certain versions.
I have an entire HyperV Cluster (3 hypervisors, 21 nodes) of Windows 10 machines just so I can bounce around versions quickly for testing.
Troubleshooting outdated versions sucks us haha.
What I'm essentially asking is: Why am I able to work and game on my win 7 professional service pack 1 without many problems, even though I ignored any support for it since I installed it and why is there no such option (so the option to just stay on a specific feature set, acknowleding that it is not supported anymore) for windows 10 without having to resort to "unintended" user behavior?
Effectively.
it is more expensive for microsoft to support old stuff, and more expensive for most users to continue using old stuff.
I cannot begin to count (lets start at five hundred and go from there) how many times people have had to pay a ton of money, anywhere from $500 for regular users (which, hey, for people living check to check is life changing), to $100,000 for some businesses, because they insisted on staying with old stuff instead up upgrading. They either end up with no upgrade path and having to start from scratch on new software, or they got whammied by some security flaw.
Luck, pretty much. You drew the 'conveniently didn't have problems' card.What I'm essentially asking is: Why am I able to work and game on my win 7 professional service pack 1 without many problems, even though I ignored any support for it since I installed it and why is there no such option (so the option to just stay on a specific feature set, acknowleding that it is not supported anymore) for windows 10 without having to resort to "unintended" user behavior?
Gaming: Dual Intel Pentium III Coppermine @ 1400mhz + Blue Orb | Asus CUV266-D | GeForce 2 Ti + ZF700-Cu | 1024mb Crucial PC-133 | Whistler Build 2267
Media: Dual Intel Drake Xeon @ 600mhz | Intel Marlinspike MS440GX | Matrox G440 | 1024mb Crucial PC-133 @ 166mhz | Windows 2000 Pro
IT'S ALWAYS BEEN WANKERSHIM | Did you mean: Fhqwhgads"Three days on a tree. Hardly enough time for a prelude. When it came to visiting agony, the Romans were hobbyists." -Mab