Microsoft Planning Major Windows 10 UI Refresh for 2021

I usually just bite the bullet on these things. I want to make sure I get all of the security patches. That is a far higher priority than having to put up with UI or other changes I don't like.

Yeah I take my chances on the "security" patches that I receive. I've had way more issues with Windows 10 breaking things with every forced update (more than I can remember) than I have security breaches (0).

Back in the days before Windows 10 (well up until at least Windows 7) you had the option to pick and choose your updates. Security updates. Check. Everything else. Uncheck. Until they started hiding malware crap in the security updates. Now they just force all updates on you.
 
I usually just bite the bullet on these things. I want to make sure I get all of the security patches. That is a far higher priority than having to put up with UI or other changes I don't like.
You ever consider Win10 LTSB/LTSC? If I recall correctly, you still get the security updates, but none of the feature updates and other nonsense you probably don't want. Then again, maybe it doesn't matter, cuz if I recall correctly, your Win10 system is just a side-system you have mostly for gaming. So less risk involved.

Back in the days before Windows 10 (well up until at least Windows 7) you had the option to pick and choose your updates. Security updates. Check. Everything else. Uncheck.
I really ****ing miss this. Picking and choosing only the Windows updates that you wanted. For Win7 I kept a list of the bad/unwanted updates, in case they re-appeared (and sometimes they came back with a different KB number), and cuz I could not possibly remember them all. There were a good number of them. Every time Patch Tuesday rolled around, I would scan through the updates and check against my list to make sure any *******s weren't trying to sneak on, and add to the list as needed. Towards the end of Win7's life, Microsoft started throwing out those cumulative updates, where one update would contain many, so you still couldn't pick and choose. At least not with the granularity you could before.

With Win10 my general rule is wait at least a week (if not longer) for regular Patch Tuesday updates and such, wait months for each of the major updates, the ones that come twice a year (and test on another machine first if possible).
 
You ever consider Win10 LTSB/LTSC? If I recall correctly, you still get the security updates, but none of the feature updates and other nonsense you probably don't want. Then again, maybe it doesn't matter, cuz if I recall correctly, your Win10 system is just a side-system you have mostly for gaming. So less risk involved.

I'd jump on LTSB if I could buy it, but I can't. Unless you are a corporate or educational volume license buyer there is absolutely no way to get it. At least not legally.

But yeah. I use windows for two things. Games, and I also have a Win10 VM on my linux desktop for when I work from home (which granted, is all the time these days)
 
I'd jump on LTSB if I could buy it, but I can't. Unless you are a corporate or educational volume license buyer there is absolutely no way to get it. At least not legally.

But yeah. I use windows for two things. Games, and I also have a Win10 VM on my linux desktop for when I work from home (which granted, is all the time these days)

Well your comment makes more sense now if you don't use Windows primarily nor do you run it on more than one system. For my BOINC farm I run Windows 10 on multiple computers and it never fails for Windows Update to break them across the board. I then have to go into each one and manually fix them so the work continues.
 
Well your comment makes more sense now if you don't use Windows primarily nor do you run it on more than one system. For my BOINC farm I run Windows 10 on multiple computers and it never fails for Windows Update to break them across the board. I then have to go into each one and manually fix them so the work continues.

If it's just a BOINC farm, have you considered using the Linux BOINC client?

I've often considered running BOINC, but... you know... power bill...

So I keep my idle power cycles as idle power cycles, and shut down everything that is not a server when not in use.
 
If it's just a BOINC farm, have you considered using the Linux BOINC client?

I've often considered running BOINC, but... you know... power bill...

So I keep my idle power cycles as idle power cycles, and shut down everything that is not a server when not in use.

Not all projects run on Linux. All projects, except 1, run on Windows. So I only run the Linux client on two rigs, then run VMs if I need to hit the Linux only project hard.
 
I can't say I'm challenged by UI changes much; I also distro hop quite a bit, as well as use distros for work that have older UIs.

If you can find your way around different versions of Linux OSs with different DEs, you can find your way around Windows 10.

Assuming that you don't want to search for something, you at least know that it's either a legacy control app or in the settings app. I've had significantly more trouble with Linux distros that try to be 'creative', and you have no idea where they put a particular setting.


As for the voice stuff, I pity those that don't turn it off on the outset.

I'd jump on LTSB if I could buy it, but I can't. Unless you are a corporate or educational volume license buyer there is absolutely no way to get it. At least not legally.
I looked into this really, really hard. Good luck even getting it less than legally (but still in an activatable state). And realistically, while it'd likely be a fine 'work' OS, you really don't want to be missing feature updates on a gaming system. That could come back to bite you.

One other thing I've tried is using scripts to 'strip' Windows before you start using it, i.e., right after install. Used to be called something like 'decrapifier', and seemed to work well when I did the process a few years back, but obviously this is a limited solution.
 
I can't say I'm challenged by UI changes much; I also distro hop quite a bit, as well as use distros for work that have older UIs.

If you can find your way around different versions of Linux OSs with different DEs, you can find your way around Windows 10.
To some extent.

I think what is more frustrating is the lack of consistency. I mean, it's all slowly migrating to the new flat UI (which is a subjective design opinion)... but for the longest time, Win10 has been some Frankenstein of MMC panels, Control Panels, and new Settings screens. And each update moves things ... so for years it was in an MMC panel, then next update the MMC panel is gone and it's in a Settings screen, then next update that Settings screen gets split into 4 different Screens, and what you are looking for is in the wind.

It's not all that different than bouncing between different distros on Linux.. but at least changing distros is a conscious decision on your part, or is a difference between two systems that you are accessing. This from Microsoft is a forced change on a system that otherwise would be perfectly stable, all in the name of .. I'm not really sure. They have been so inconsistent for so long with their UI Design, that in trying to unify it finally they have introduced even more disorder and chaos.

I think the ultimate fix is that they need to just stop monkeying with the UI stuff... new UI = new release. Then people can migrate if/when they want to the new UI stuff. I know that goes against the new "Win104Ever" philosophy, but that's how it was done prior to WIn10, and people could jump or skip releases as they saw fit.
 
Try doing a remote desktop to Server 2016 (retains the full-screen menu) on another continent, and from that server, to one on a third...

I'm pretty sure you're talking about 2012 server not 2016. But the point stands. I manage several hundred servers remotely so I get it.
 
Not all projects run on Linux. All projects, except 1, run on Windows. So I only run the Linux client on two rigs, then run VMs if I need to hit the Linux only project hard.

Ah, I just assumed it was some sort of virtual environment such that all projects ran on all platforms.
 
To some extent.

I think what is more frustrating is the lack of consistency. I mean, it's all slowly migrating to the new flat UI (which is a subjective design opinion)... but for the longest time, Win10 has been some Frankenstein of MMC panels, Control Panels, and new Settings screens. And each update moves things ... so for years it was in an MMC panel, then next update the MMC panel is gone and it's in a Settings screen, then next update that Settings screen gets split into 4 different Screens, and what you are looking for is in the wind.

It's not all that different than bouncing between different distros on Linux.. but at least changing distros is a conscious decision on your part, or is a difference between two systems that you are accessing. This from Microsoft is a forced change on a system that otherwise would be perfectly stable, all in the name of .. I'm not really sure. They have been so inconsistent for so long with their UI Design, that in trying to unify it finally they have introduced even more disorder and chaos.

I think the ultimate fix is that they need to just stop monkeying with the UI stuff... new UI = new release. Then people can migrate if/when they want to the new UI stuff. I know that goes against the new "Win104Ever" philosophy, but that's how it was done prior to WIn10, and people could jump or skip releases as they saw fit.

In Linux it is easy though. Want to configure something? Look for a text config file in /etc

They are even searchable with find and grep!

In windows 10, I have on occasion wanted to tear my hair out looking for where they moved the **** config menu I remember.
 
In Linux it is easy though. Want to configure something? Look for a text config file in /etc

They are even searchable with find and grep!

In windows 10, I have on occasion wanted to tear my hair out looking for where they moved the **** config menu I remember.
Could not agree more.
 
In windows 10, I have on occasion wanted to tear my hair out looking for where they moved the **** config menu I remember.

Wow. The profanity censor makes it look like I have a WAY more foul mouth than I actually do. That was just a four letter word beginning in D and ending in N. :p
 
Ah, I just assumed it was some sort of virtual environment such that all projects ran on all platforms.

Some projects do utilize VMs to run their projects on any platform, but those projects, for the most part, suck. VB creates all sorts of other problems.
 
view-dam-hydroelectric-power-station-260nw-1166660776.jpg
 
I also hate the forced updates. I wish it would go back to spaced out (and OPTIONAL) service packs for UI enhancements, and something resembling a regular schedule for security updates via windows update. Right now they just push updates whenever MS feels like it. Hate it. And their QA/testing has gone in the sh!tter the last couple years.
 
I also hate the forced updates. I wish it would go back to spaced out (and OPTIONAL) service packs for UI enhancements, and something resembling a regular schedule for security updates via windows update. Right now they just push updates whenever MS feels like it. Hate it. And their QA/testing has gone in the sh!tter the last couple years.

So, I'm torn.

I'll be clear. I am a security patch extremist. I firmly believe everything should be patched for security as soon as a patch is available. Every second of delay leaves you vulnerable, and a breach is always much worse than a little downtime. I am completely unsympathetic to wanting to validate security patches before implementation.

That said, there should be no reason feature patches should be forced on people.

The problem becomes, as soon as you have many different versions of feature patches live in the field, you wind up with an unmanageable mess of different combinations and permutations in the field to patch for security.

So as much as I am annoyed by this ****, I can understand why it happens.
 
Become a Patron!
Back
Top