How to Check NTLMv1 Enforce Mode Changes in Windows 11
- 15 steps
- Needs administrator rights
NTLMv1 Single Sign-On blocking on Windows 11 now defaults to Enforce mode (1) when the BlockNtlmv1SSO registry value is not set. Microsoft made the change in update KB5127648, and it replaces the old default, Audit mode (0). This tutorial shows how to check where a PC stands by confirming the update, checking Credential Guard, and looking for that value.
NTLMv1 is the original version of NTLM, an older Windows sign-in protocol. Single Sign-On (SSO) reuses your credentials so you do not sign in again for each resource. Microsoft documents the change in KB5066470.
To check NTLMv1 Enforce mode changes in Windows 11, open Settings Windows Update Update history and look for KB5127648. The update switches a PC with no BlockNtlmv1SSO value from Audit mode (0) to Enforce mode (1), but only where Credential Guard is disabled, so check Credential Guard too.
What changes with the October 13, 2026 update
Here is the short answer to “what does KB5127648 do to NTLMv1 on Windows 11?” A PC with Credential Guard disabled and no BlockNtlmv1SSO value moves from Audit mode (0) to Enforce mode (1). In Enforce mode, Windows blocks NTLMv1-derived credentials for Single Sign-On.
Before the update, Windows uses Audit mode (0) when the BlockNtlmv1SSO registry value is not set. With KB5127648 installed, Windows uses Enforce mode (1) in that same situation. Audit mode lets NTLMv1 Single Sign-On keep working and records events when it is used, while Enforce mode blocks it.
- The update does not touch the registry. It does not create or modify the BlockNtlmv1SSO value. A PC with no value before the update still has no value afterward, but the mode Windows applies is now different.
- The default only applies when the value is not set. If someone has set a value on the PC, that value is what you need to find, because the new default covers only the “not set” case.
- The change applies only where Credential Guard is disabled. Credential Guard is a Windows security feature that isolates sign-in secrets from the rest of the system. If it runs on the PC, the default change does not apply.
That means no single setting gives you the result. You have to read the update status, the Credential Guard status and the registry value together.
Before you start
Gather three things before you open anything.
- An administrator account or its credentials. Registry Editor asks for administrator approval when it opens. Reading a value does not change anything, but the approval prompt still appears.
- A PC running a currently supported Windows 11 version (25H2 or 26H2) that receives security updates. The default changes only after KB5127648 installs. Before then, Audit mode (0) remains the default when the value is not set.
- A few minutes. Searching the whole registry by value name takes longer than opening a known path.
The exact registry key that holds BlockNtlmv1SSO is not confirmed here.
[Registry method: to be verified]For that reason, the steps below search for the value by name instead of browsing to a path. A search finds the value wherever it is stored, so you do not need to know the key in advance.
How to check NTLMv1 Enforce mode changes in Windows 11
The steps below test the three conditions that decide the mode: the update, Credential Guard and the registry value. Run them in order and write down what you see at each stage. Nothing here changes a setting, so no restart is needed.
- Press Win+I to open Settings. The Settings window opens.
- Go to Settings Windows Update Update history. The page lists installed updates by date under headings such as Quality Updates.
- Look for KB5127648 in the list. If it does not appear, the new default has not reached this PC yet, and you can stop here. Windows 11 security updates are cumulative, so a later monthly update should carry the change as well.
- Press Win+R, type
msinfo32, and press Enter. The System Information window opens. - Select System Summary, the first item in the left pane. The right pane lists system details.
- Scroll the right pane to the row named Virtualization-based security Services Running. If it lists Credential Guard, the feature is running and the default change does not apply. If the row is empty or does not list Credential Guard, the feature is disabled.
- Press Win+R, type
regedit, and press Enter. Registry Editor needs administrator approval, so select Yes on the User Account Control prompt, or enter administrator credentials. - Click Computer, the top item in the left pane, so the search covers the whole registry.
- Press Ctrl+F. A small Find dialog appears.
- Type BlockNtlmv1SSO in the Find what field, exactly as written.
- Under Look at, clear Keys and Data and leave Values ticked. Then tick Match whole string only.
- Select Find Next. Registry Editor scans the registry. This can take a few minutes, and the window may look idle while it works.
- Read the result. If Registry Editor stops on a value named BlockNtlmv1SSO, look at its data in the right pane. If a message says the search is finished and nothing was found, the value is not set on this PC.
- Press F3 to look for more matches. The value can exist in more than one place, so keep pressing F3 until the search reports that it has finished.
- Close Registry Editor. Do not change anything you found while you are only checking.
That’s it. You now have the three facts for this PC: whether KB5127648 is installed, whether Credential Guard is running, and whether a BlockNtlmv1SSO value exists. Nothing was modified, so there is nothing to undo.
What to do if the search finds nothing
A missing value is a normal result, not an error. It means nobody has set BlockNtlmv1SSO on this PC. In that case the default applies: Audit mode (0) before KB5127648 and Enforce mode (1) after it, as long as Credential Guard is disabled.
If Find Next seems to do nothing, check that Values is the only item ticked under Look at. A search that includes Data can stop on unrelated entries that happen to contain the same text.
How to read your results
Combine what you saw in the three checks. Find the row in the table that matches your three results.
| Security update installed? | Credential Guard running? | BlockNtlmv1SSO set? | Result |
|---|---|---|---|
| No | No | Not set | Audit mode (0) applies. |
| Yes | No | Not set | Enforce mode (1) applies. The update changed the default. |
| Yes | Yes | Not set | The default change does not apply, because Credential Guard is running. |
| Yes | No | Set to a value | The value on the PC applies, not the new default. Read its data: 1 is Enforce mode and 0 is Audit mode. |
The second row is the one that matters for most unmanaged PCs. The registry looks identical before and after the update, but the behavior is different. If a Wi-Fi, Ethernet or VPN connection that uses MS-CHAPv2-based authentication fails on a PC that matches this row, the new Enforce mode might be the cause.
Confirm the Credential Guard status with PowerShell
The quickest check is the Credential Guard status in System Information. PowerShell gives the same answer as text you can copy into a script or a support request. This command reads which virtualization-based security (VBS) services are running. VBS is a Windows feature that runs security services apart from the main system. The command only reads data and changes nothing.
Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard | Select-Object SecurityServicesRunningA 1 in the SecurityServicesRunning list means Credential Guard is running. An empty list means it is not. If the command returns an error or nothing at all, rely on the System Information check instead.
Home, Pro and managed PCs
Credential Guard is aimed at Enterprise and Education editions, so PCs on Home and Pro editions of a currently supported Windows 11 version (25H2 or 26H2) normally do not run it. On those PCs, expect the Credential Guard row in System Information to be empty. That makes the Enforce mode default from KB5127648 more likely to apply when no value is set.
On a work or school PC, an administrator may already have set BlockNtlmv1SSO through management tools. If your search finds the value, it may reappear after you change it, because management tools reapply their settings. Ask whoever manages the device before you edit it.
Check a PC you do not sit at
The same three facts apply to any PC: the update status, the Credential Guard status and the value. The PowerShell command above works in a remote session with the same meaning. For the registry value, repeat the search by name on that PC. A saved list of results per PC keeps you from rechecking the same machines.
Changing the mode on a PC
For that reason, do not create the value from memory.
Read the full details in Microsoft’s KB5066470 before you set anything. What the update does and does not do is already clear: it leaves the registry alone and changes only the default when no value exists.
What to do next
Run the check again on any PC that did not have KB5127648 yet, because until it installs, Audit mode (0) still applies when the value is not set. If a PC shows a value you did not expect, find out who set it before you change it, since policy-managed settings often work this way. For another example of a setting that behaves like this, read controlling desktop background changes in Windows 11.
For other security settings that you can require rather than leave optional, see how to enforce BitLocker encryption types on Windows 11 drives. See also how to enforce BitLocker encryption on removable drives.
Have a question about this guide?
Answered by AI from this guide. Good questions may be added to this page — please don't include personal details.
Did this guide fix your problem?
About the Author
Richard
Tech Writer, IT Professional
Richard is a writer at Geek Rewind who turns complex IT tasks into clear, step-by-step guides. He draws on years of hands-on experience in system administration and enterprise IT operations, focusing on Windows, Linux and WordPress: the problems people actually run into, and the fixes that work. His server and WordPress guides come from systems he runs himself. Richard builds and maintains the platform behind Geek Rewind, from its Ubuntu servers and Nginx configuration to its custom WordPress plugins. Many new tutorials start with readers' questions, and he's always glad to answer them in the comments.
No comments yet — be the first to share your thoughts!