<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Windows on Kuldeep Pisda</title><link>https://kdpisda.in/tag/windows/</link><description>Recent content in Windows on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 17 Oct 2026 08:30:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/windows/index.xml" rel="self" type="application/rss+xml"/><item><title>Windows 11 Now Blocks NTLMv1 Single Sign-On by Default, and an Unset Registry Value Is the Switch</title><link>https://kdpisda.in/windows-ntlmv1-sso-enforce-default-mschapv2/</link><pubDate>Sat, 17 Oct 2026 08:30:00 +0530</pubDate><guid>https://kdpisda.in/windows-ntlmv1-sso-enforce-default-mschapv2/</guid><description>&lt;p&gt;If your Windows 11 fleet signs in to Wi-Fi, wired 802.1X or VPN with an MS-CHAPv2 profile and &amp;ldquo;use my Windows credentials&amp;rdquo;, the October 13, 2026 cumulative update may have changed that behavior. &lt;a href="https://support.microsoft.com/en-us/servicing/os/windows-11/2026/10/kb5127648-windows-11-24h2-25h2-26h2-security-update"&gt;KB5127648&lt;/a&gt; changed the default of a registry value called &lt;code&gt;BlockNtlmv1SSO&lt;/code&gt; from Audit to Enforce. Microsoft added the note to the KB page on October 15, two days after the release.&lt;/p&gt;
&lt;p&gt;I have not tested this on a device. Everything below comes from Microsoft&amp;rsquo;s two pages, and I mark where I am inferring.&lt;/p&gt;</description></item></channel></rss>