Windows Baseline Protection lets apps check eight settings
Key takeaways
- Baseline Protection checks eight items at startup and hands the result to apps and local admins, with more checks promised
- Checks are auditable by third parties rather than Windows alone, so apps can trust the result
- It is in preview now and generally available next year, so IT teams have time to audit their fleets
- Machines without Secure Boot, memory integrity or a security processor may find apps refusing to run
Microsoft is giving apps the power to refuse to run on Windows machines that do not meet a security baseline. The feature, Windows Baseline Protection, checks eight security settings at startup and passes the verdict to applications and local administrators. It is in preview now and will be generally available to all users next year.
The practical consequence is simple. If a banking app, password manager or exam proctoring tool decides your configuration is not good enough, it can stop working, switch off some of its own features, or ask the user to change their OS settings first.
The headline numbers
Baseline Protection currently tests eight items, and Microsoft says more will follow.
| Check | What it confirms |
|---|---|
| Secure Boot | Enabled |
| Security processor | Present |
| Drivers | Signed or Windows-certified |
| Memory integrity | On |
| Virtualization-based security | On |
| Kernel debugger protection | Enabled |
| Vulnerable driver protections | Enabled |
The source lists seven named items against a count of eight, so the full set is not itemised here. Microsoft's own documentation should be treated as the authority on the complete list.
What the data actually shows
The notable detail is not the list of checks, since several already exist in Windows and feed the Security settings panel. The difference is who can verify them. Under Baseline Protection the results are auditable by third parties, not just by Windows itself. That turns a self-reported status into an attestation, a signed statement about system state that another party can rely on.
That matters because of how developers work today. Many apps ship their own scripts to probe for security features, and the source describes those scripts as often buggy and capable of crashing Windows systems. A single, supported check could replace the home-grown ones. Microsoft hopes for better security and better OS stability at once.
The named use cases show where the pressure will land first: password managers, banking and document e-signing, gaming anti-cheats and exam proctoring software. These are all categories where an attacker, or a cheater, gains from running on a weakened machine. An anti-cheat vendor, for example, can demand that memory integrity and kernel debugger protection are on and trust the answer, rather than guessing from the outside.
What the data does not tell us
Several questions are open. One banking app may block entirely; another may merely warn. Users could therefore meet wildly inconsistent responses on the same laptop.
Nor is there any figure for how many existing Windows PCs would pass all eight checks today. Older hardware without a security processor, or machines running unsigned legacy drivers, are the obvious candidates for failure, but the scale is unknown. The same applies to specialist and industrial software that relies on older drivers.
It is also unclear how the attestation is protected against tampering on a compromised device, or how local admins will see and act on results at fleet scale. Those details will decide whether this is a useful control or a compliance checkbox.
How this compares
Phone users will recognise the model. Baseline Protection moves Windows towards that mobile-style trust model, with the OS vouching for its own state.
None of these incidents is tied to Baseline Protection in the source. Microsoft says the feature is meant to make apps more secure while keeping the operating system stable.
So what?
For IT teams the action is clear. The feature is in preview now, with general availability due next year. Administrators can audit their estates against the named items: Secure Boot status, security processor presence, driver signing, memory integrity, virtualisation-based security, kernel debugger protection and vulnerable driver protections. Any device failing those checks is a candidate for remediation before an app locks users out. Where hardware cannot meet the baseline, that is a procurement conversation, not a support ticket.
Developers of internal tools have a different decision: retire homemade check scripts in favour of the supported attestation, and decide in advance what each failure should do.
The single most important point: treat the preview period as an audit window, because next year apps will be able to check these settings and may refuse to run if they fail.
Frequently asked questions
What is Windows Baseline Protection?
It is an attestation process in which Windows checks which security features are enabled at startup and reports the result to apps and local admins. Apps can then refuse to run, disable features or ask users to change settings.
When will Windows Baseline Protection be available?
It is in preview now and will be generally available for all users next year, according to Microsoft.