Wednesday, April 6th 2022
Microsoft Readies Security Feature-Update for Windows 11 Needing an OS Reinstall to Use
Microsoft is giving final touches to a what it refers to as a groundbreaking new security feature update for the Windows 11 operating system, which should significantly improve application-level security, and safeguard you from malicious apps based on the way they behave. Trouble is, to use the feature, you will have to reinstall your operating system (i.e. a clean reinstall), if you're on the current release of Windows 11, or any build that's older than the one that carries this update.
The Smart App Control feature by default blocks untrusted or uncertified applications from running on your PC, and unlike browser-level protections such as Smart Screen, is baked directly into the OS, and monitors application code at a process level, to detect potentially malicious application behavior. It does this using a combination of code-signing by the application publisher and an AI model for trust within the Microsoft cloud. The OS keeps in touch with the cloud 24x7 (whenever the PC is up), to receive the latest threat intelligence and AI model updates from the cloud. It's very likely that Smart App Control will be part of the next significant version milestone of Windows 11 (such as "22H2"), which means everyone on 22H1 or older will be made to reinstall to use it.
Sources:
Microsoft, PC World
The Smart App Control feature by default blocks untrusted or uncertified applications from running on your PC, and unlike browser-level protections such as Smart Screen, is baked directly into the OS, and monitors application code at a process level, to detect potentially malicious application behavior. It does this using a combination of code-signing by the application publisher and an AI model for trust within the Microsoft cloud. The OS keeps in touch with the cloud 24x7 (whenever the PC is up), to receive the latest threat intelligence and AI model updates from the cloud. It's very likely that Smart App Control will be part of the next significant version milestone of Windows 11 (such as "22H2"), which means everyone on 22H1 or older will be made to reinstall to use it.

115 Comments on Microsoft Readies Security Feature-Update for Windows 11 Needing an OS Reinstall to Use
I know, a novel idea.
Granted its not exactly the same but on a basic principle Applocker (and SRP) can be configured to only allow trusted signed binaries to run from specific locations, the features have been available for a decade plus now but never enabled on consumer windows.
I don't understand how "lol there's an opt out button" is a counter to "keep Enterprise stuff out of home (and not work) out of it".
An "opt out" is only an option until there isn't one and we all know how trust worthy MS has been over the years with opt out options. Kind of like being able to opt out of certain updates until you can't (ala W11).
It's not something they'll force on people, unless they hate existing
I'm so tired of all this FUD. We all hate Windows but we can't live without it, so bitterness and conspiracy theories keeps growing. Still, TPU is nowhere as bad as NBR forums back in the day lol..
but I'm with you on the work machine for work.
Home machines for not work, and hence this might be a stretch too far for homes, that said since I do keep more than one home pc I do like one of them to be as safe as possible for online banking, etc so it would get put on 1 of 3 of mine plus the 1 laptop I have from work will definitely get this, my IT guy in work is going to f$%$£in LOOOOOve this , not.
I'd say kick 11 business/ enterprise off 11 pro version
First thing businesses would do is remove any gaming/ social apps off their installs so pro is the wrong version for them bottom line.
What are you doing Micro$oft?! First you blocked people now you want them to reinstall, reinstall really? That settles it i am going Linux the moment it can run all my games you can go downhill for all i care.
Enterprise is more tricky, but most medium/big-sized companies likely order prebuilts and laptops with exact same configuration in the dozens, hundreds or thousands. Just make a disk image and clone it.
And both large enterprise and small businesses don't want to get into the new stuff right off the bat. Enterprise would only do so for security reasons, and small businesses straight out stay away from it if not needed.
The only backlash I'd expect is what was mentioned before, EU or FTC. And even then, between the clean install requirement and the switch to toggle it off, Microsoft is probably in the clean.They're a corporation, they're in it for the money. Writing "Micro$oft" is stating the obvious.And yet here almost everyone is complaining about how this is turning into 1984. Which, yeah, I can see the logic for people to think that.
So, no, I doubt the reinstall is gonna be a real issue. If anything, I think most here are quite happy that they need to do that before Smart App Control even works.Yeah, sure, whatever. You do you. :rolleyes:
Of course that is just the logistics of getting the update out, the intent of the update will of course lead to contention amongst everyone, not just those of us here.
I'm so out of compliance from just the new 11 requirements "even on a couple machines that can be compliant" this update has zero chance of being installed :laugh:
You need a clean install (either build 22593 or later for Windows Insiders, or whatever build ends up being the RTM/GA for the stable channel) to use Smart App Control. If you don't do a clean install you don't get Smart App Control. That's it. You'll continue to receive updates normally regardless of whether your install is clean or if it comes from upgrades from Windows 98 (all the TPM and spec requirements bullshit aside).Most normal consumers don't really care much for the feature (in fact, I'd bet it will have growing pains that will make it as hated as UAC was back with Windows Vista), don't really care for knowing how to install Windows at all, and they will get a new Windows install the moment they get a new device.And on that, I'll agree completely.
Features update guess I should of said
I look forward to the reg file to kill the annoying "activate smart app control messages" think @brink is on it like the green hornet :laugh:
support.microsoft.com/en-us/topic/what-is-smart-app-control-285ea03d-fa88-4d56-882e-6698afdb7003
There's a bit more depth of an explanation there, but the TLDR of it is:
1-For developers, this feature, once it's enabled rather massively, will encourage them to sign their software (software signing also means that it's possible to identify a developer in the real world)
2-The order of priorities is like this:
2.1: Check if the app is popular or well-known, if that's the case let it run (my understanding is that by this point Windows Defender or your antimalware of choice already said it's clean)
2.2: if the app isn't popular, check for a signature, if it's digitally signed it can still run, otherwise it's considered not trustworthy.
3-Smart App Control has an "evaluation" mode. In Microsoft's words:4-Regarding manual whitelisting, there's none. It's turned on or off for everything, no exceptions.
5-About why Microsoft wants a clean install, I quote:
Microsoft has been removing or reducing users choice on enabling/disabling or using/skipping "features" for a while now. The telemetry fiasco is an example, coming from the optional, CEIP enrolment pre-10. More examples: Edge removal using GUI (compared to IE) and the rest of MS bloat that have been "integrated" into the OS, the ability to open system-related web links in non-MS browsers (e.g. start menu web results. AND locking it down even against third party mods), setting up Win Home with local accounts, the update package/patch selector in wupdate GUI and the ability to disable automatic updates (from GUI) in Home editions, etc.
And at the very least, you have the plethora of dark patterns Microsoft have been implementing that reduce and practically eliminate choice for all but the most savvy users. The case of removing local account option began its life as one, and then you have the recent drama with default browser change, which most likely wouldn't have been "fixed" if not for the strong backlash from other browser devs.
And to spare anyone the apologism, whether or not there exists some third party hack or obscure set of powershell commands that still carry out the task is irrelevant. The point is that there were accessible and clear interfaces to do something, and then Microsoft removed them. Respecting user choice was not part of their agenda for the last 7 years.