Windows 11 applications may eventually care not just whether your PC runs Windows, but whether its security protections are enabled. Microsoft’s Windows baseline protection preview gives developers a shared way to check that state—and decide whether to warn users, limit functionality, or deny access.
According to reporting by Abhijith M B at Windows Latest, the feature is being previewed with Windows Insiders, with general availability planned for 2027. Adobe, Battle.net, 1Password, and Schoolyear are among the companies testing it. That is a reason to review your configuration, not evidence that your everyday apps are about to stop working.
What Windows baseline protection actually changes
Security-sensitive software already checks individual Windows settings. A game might require Secure Boot, while another application might look for a Trusted Platform Module. The new approach consolidates those separate checks into a common security signal.
Windows Latest reports that developers can request a pass-or-fail result, information about missing protections, or a hardware-backed attestation token for verification on their servers. Attestation is intended to provide stronger evidence than simply trusting a local application’s assessment.
The crucial distinction is between measurement and enforcement. Windows supplies the security state; the application developer decides what to do with it. A failed check could produce an explanation, disable a sensitive feature, or prevent the application from running. It does not automatically mean Windows itself blocks every application on the machine.
Nor does passing establish that a computer is malware-free. This is a configuration baseline, not a replacement for patching, endpoint protection, backups, or sensible handling of downloaded software.
Which protections are included?
The report describes eight protections in the initial baseline:
- TPM 2.0: a hardware-backed foundation for protecting sensitive information.
- Secure Boot: protection for the startup process.
- Virtualization-based security: isolation for security-sensitive Windows components.
- Memory integrity: protection against malicious code in sensitive kernel contexts.
- Signed drivers only: restrictions on loading unsigned drivers.
- Windows-certified drivers: additional Windows driver-signing requirements.
- Kernel debugger protection: restrictions intended to prevent debugging mechanisms from undermining security.
- Vulnerable driver protection: blocking drivers with known weaknesses.
There is a documentation nuance: Windows Latest notes that Microsoft’s support material groups the two driver-signing requirements under one test-signing protection entry, producing seven listed checks rather than eight. Treat that as a presentation difference, not proof of two incompatible baselines.
Microsoft also describes the security state as versioned. Administrators should therefore avoid treating today’s passing result as a permanent compatibility guarantee: future versions may set different requirements.
Adobe and Battle.net participation is not a blocking announcement
The names involved make this relevant beyond enterprise security teams. Creative software, games, password management, and online exams all have different reasons to assess the devices running their applications.
However, participation in testing does not establish an enforcement policy. The report explicitly says Adobe and Battle.net have not announced that they will block computers that fail the check. Claims that either company is preparing a blanket lockout go beyond the available information.
Schoolyear provides a more concrete example: its security engineer describes using the API to confirm that a student’s computer meets the required standard before an exam. In that setting, finding an incompatible configuration early could prevent a much more disruptive surprise on exam day.
For users, the meaningful question will be what each application requires, when that requirement takes effect, and what recovery path the developer provides.
Where users will see the result
On supported preview installations, the report places the new page at Settings > Security > Baseline protection. A protected configuration receives a green indicator, while missing protections trigger an attention warning.
A button can enable the protections Windows is able to configure, followed by a restart. Secure Boot remains a separate concern because enabling it requires firmware configuration. The preview includes guidance for restarting into UEFI and viewing instructions on another device.
Do not assume this page is already available on every Windows 11 PC. This remains a preview, and managed computers may have settings controlled by their IT department.
A practical preparation checklist
The sensible response is to document and test, rather than change firmware settings blindly.
- Review intentional exceptions. If you previously disabled Memory Integrity for troubleshooting or gaming, record why. An old workaround may no longer be necessary after driver updates.
- Investigate driver compatibility first. Update affected drivers through trusted vendor channels before trying to force protections on. Test peripherals and essential software afterward.
- Prepare before firmware changes. Back up important data, make sure your disk-encryption recovery key is accessible, and follow your PC manufacturer’s Secure Boot instructions. Dual-boot users should check their specific bootloader configuration rather than assume all Linux setups require Secure Boot to be disabled.
- Pilot on representative devices. IT teams should include older hardware, specialist peripherals, and development workstations. Record both the missing protection and the business reason for any exception.
- Track application policies separately. A device-readiness inventory cannot tell you whether a vendor will warn, restrict, or block. That requires the vendor’s own rollout guidance.