<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: iqan1996</title>
    <description>The latest articles on DEV Community by iqan1996 (@iqan1996).</description>
    <link>https://dev.to/iqan1996</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3951415%2Fcc6f665a-c1a1-4ffe-998c-b1c61b8d1bdc.png</url>
      <title>DEV Community: iqan1996</title>
      <link>https://dev.to/iqan1996</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/iqan1996"/>
    <language>en</language>
    <item>
      <title>Windows 11 Microsoft Account Login Recovery During Internet Restrictions</title>
      <dc:creator>iqan1996</dc:creator>
      <pubDate>Mon, 25 May 2026 21:31:02 +0000</pubDate>
      <link>https://dev.to/iqan1996/windows-11-microsoft-account-login-recovery-during-internet-restrictions-2dh2</link>
      <guid>https://dev.to/iqan1996/windows-11-microsoft-account-login-recovery-during-internet-restrictions-2dh2</guid>
      <description>&lt;p&gt;Windows 11 locked me out of my own Microsoft account during an internet blackout.&lt;/p&gt;

&lt;p&gt;Not because the password was wrong.&lt;br&gt;
Not because the account was compromised.&lt;br&gt;
Because Windows Hello + Microsoft auth decided they needed proper connectivity again.&lt;/p&gt;

&lt;p&gt;What made this worse:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;International internet access was partially blocked&lt;/li&gt;
&lt;li&gt;VPN only worked inside a secondary local admin account&lt;/li&gt;
&lt;li&gt;Switching users killed the VPN tunnel&lt;/li&gt;
&lt;li&gt;Microsoft login traffic was not respecting normal proxy routing&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;After a lot of testing, this is what finally worked:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Logged into a local admin account&lt;/li&gt;
&lt;li&gt;Ran v2rayN as administrator&lt;/li&gt;
&lt;li&gt;Enabled TUN mode (critical part)&lt;/li&gt;
&lt;li&gt;Connected VPN successfully&lt;/li&gt;
&lt;li&gt;Instead of “Switch User”, used:
Win + L&lt;/li&gt;
&lt;li&gt;Logged into the main Microsoft account from the lock screen&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;That combination preserved the tunnel long enough for Windows auth services to reach Microsoft again.&lt;/p&gt;

&lt;p&gt;Interesting detail:&lt;br&gt;
Normal system proxy was NOT enough.&lt;br&gt;
Windows login/auth traffic was bypassing it.&lt;br&gt;
TUN mode fixed the routing at the network stack level.&lt;/p&gt;

&lt;p&gt;Also discovered:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Microsoft Store failures were related to the same routing issue&lt;/li&gt;
&lt;li&gt;Lock Screen behaves differently from Switch User regarding session/network persistence&lt;/li&gt;
&lt;li&gt;VPN behavior across Windows sessions is extremely inconsistent depending on implementation&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is one of those edge-case debugging sessions where official documentation is almost useless and you end up reverse-engineering Windows behavior live.&lt;/p&gt;

&lt;p&gt;Maybe this helps someone else avoid a few hours of panic.&lt;/p&gt;

</description>
      <category>microsoft</category>
      <category>networking</category>
      <category>systems</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
