VPN When Switching Windows User: Same PC, New Login

A Windows reinstall of a PC you kept is a different leftover. Win32 is gone. The TAP or Wintun-class adapter the installer added is gone. First-run Windows does not remember that you paid for a year. That essay already owns the empty disk. Switching the signed-in Windows user leaves the OS standing. The other profile can still have a Start tile. The new profile can still be missing the client. Farms skip that sentence because the keyword is privacy. Privacy after you meant a new login is a matching .exe under that user plus a seat, not a screenshot of Fastest server.

A borrowed laptop is outbound by dinner. You ask. You uninstall. You hand the chassis back. You are not handing this PC to anyone in this article. If you are, stop. That is the borrowed-laptop URL. Mixing those in one sentence is how farms sell best VPN for Windows until the cookie expires. A shared family PC is several humans you live with taking turns at one chair. OS profiles there are household furniture. This URL is you, alone, moving from one Windows account to another on hardware you kept. The leftover is per-user. The seat is still the machine while Connect is up.

I will not walk packet sniffing. The public Wi-Fi how-to already did. I will not pack your chargers. The travel checklist exists for install-before-you-fly. Here the PC is already on the desk, same Windows, new login. The download page is the next job if this account cannot see the app. The seat is the job after that.

Klox is a consumer tunnel to an exit you picked. It is not Microsoft's user accounts. It is not Fast User Switching. Microsoft's create a local user or administrator account page is the vendor novel. I will stay at overview height. I will not paste a 40-click path that rots when Windows 11 moves Accounts. Farms skip that sentence because the keyword is new user. A new Windows user is Microsoft's product. Installing Klox under that user is ours.

Windows stores a lot of what you think of as the app inside the user profile. Start menu pins. Desktop shortcuts. AppData. Tokens the tray used last week. Switch user and those objects stay with the old login. The new desktop can look like first-run Windows even though the disk still has yesterday. People then decide the VPN vanished. It did not vanish. It stayed with the other account. Look before you download twice so two trays fight.

Fast User Switching can keep processes alive. You switch to the new account and the old session is still parked. A tunnel started under Dad can still be up when you land on the new profile, or the other way around, depending on how the helper is scoped. Machine-wide helper versus per-user tray is a client fact. Confirm it. Then write it. If the VPN is per-user, the new login does not inherit the tray. If it is machine-wide, the hop can still be up and the household is still spending a seat. Look at the icon. Do not assume.

I will not invent a per-user Klox dashboard so this article matches a competitor screenshot. Klox is one consumer account you sign into on a machine. Windows users are OS profiles. They have their own desktops. They are not extra Klox seats by themselves. They are also not a free extra install if the binary never landed in this profile. Split those two sentences. Farms mash them because the keyword is user.

Sign out of Windows is not a Klox disconnect. Closing the session can drop a per-user helper. It can also leave a peer sitting until the handshake dies. Prefer looking in the live app. A leftover row is a corpse, not a second laptop. Remove it there. I will not mint a portal path. A screenshot from a farm is not our admin.

Do not copy files from the old user's Desktop into the new one and call that an install. Shortcuts break. Tokens stay behind. The honest path is /download under the account you now type in. Run as administrator. Sign into the same email. That is boring. Boring is the point.

The new profile returns you to a clean Start menu. Browser bookmarks are gone unless you signed into a browser profile. The old Klox shortcut is on the other desktop. Open a browser you trust while you are this user. Type klox.app/download. Do not search Klox VPN installer and click the first ad. Ads impersonate download pages. Bookmark download after the first honest visit.

Windows 10 and Windows 11 both exist. Pick the architecture. AMD64 for Intel and AMD CPUs. ARM64 for ARM processors: Snapdragon, some Surface models, Copilot+ boxes. Settings, System, About, System type. ARM-based processor means ARM. x64-based processor means AMD64. Wrong arch fails to install or fails to launch. That story in full is VPN on Windows ARM: Pick the ARM64 Installer, Not AMD64. Here the user-switch line is: the new profile forgot which file you used last year, even if the old profile still has it. Look again. Do not grab last year's USB stick with a renamed .exe because the filename felt lucky. Do not copy the old user's Downloads folder and run that file as a personality.

Right-click. Run as administrator. Follow the wizard. Launch. Sign into the same email you already paid on. A second Klox account is how you lose the year you already bought and then hit a seat error on the old login you forgot. System requirements on that page: 2 GB RAM, 100 MB disk, internet, administrator privileges. Trust it. I will not invent a Store tile because a new Microsoft account would have preferred one.

SmartScreen may appear on a publisher you have not seen under this profile. That is not automatically malware. It is also not automatically fine. The test is the URL you typed. klox.app/download. More info. Run anyway only if you typed that URL. Do not disable SmartScreen as a lifestyle. The White-Label VPN and Windows Smartscreen post is for brands writing macros. You are not writing macros. You are installing one consumer EXE after a login you meant.

If the old Windows user still has the client and you can still sign into it, you can uninstall there after this account works. Do not leave two signed-in trays on one chassis unless you like support tickets that start with I switched user and nothing works. One honest install under the account you live in. Then clean the leftover on the account you left.

Some Windows installs land in Program Files and show up for every local user. Some land in the profile and do not. Klox's consumer Windows client is an .exe from /download that needs administrator privileges. After an admin install, another user on the same PC can often launch it. After a per-user leftover, they often cannot. Look. If this account has no Start tile and no tray, install from /download under this account. If this account already has the tray, skip the second copy. Two copies is how Connect looks haunted.

I will not invent a Program Files versus AppData picker as a consumer protocol. The Download page does not offer that as a toggle. The practical test is: signed into this Windows user, can you open Klox? Yes: sign in, allow adapter if asked, look at the seat. No: type klox.app/download, matching arch, run as administrator. Do not export a zip of the old user's AppData. Do not robocopy a profile because a forum said roaming was privacy. Roaming is Microsoft's noun. It is not our installer.

A Microsoft account you just created is still a Windows user. It is not a Klox SKU. Signing into Microsoft does not sign you into Klox. Signing into Klox does not create a Microsoft account. Keep those buttons apart. People mash them because both say account. One is the OS. One is the tunnel you paid for.

Local account to Microsoft account on the same profile can keep the same user folder. That is Microsoft converting the login, not creating a second human. If you still see the same desktop, the same Start pins, and the same tray, this checklist may be the wrong URL. You already have the client. Sign in if the token died. Do not download a second copy so two trays fight. If you created a brand-new local user and left the old one sitting, you are on this page. Two folders. Two Start menus. Maybe one Program Files. Look before you assume the hop followed you.

Do not copy the shortcut from the other desktop. A shortcut that points at a path the new user cannot read is a blank icon and a ticket. The installer writes the right ACLs. Your drag-and-drop does not. I have watched people duplicate a .lnk, decide VPNs are broken, and then install a forum EXE. The shortcut was the whole bug.

Timeout is the boring failure. You switched Windows user. You did not disconnect first. The account still shows this laptop for a while. You install under the new login, you connect, and you are at five, or you think you were robbed of a slot. You were not robbed. You left a corpse. Remove it in the live app. I will not invent a web portal URL for that tap. Confirm the client you already signed into. If the row is gone on its own, good. If it sits, disconnect that device from a logged-in client. A label is not a logout. Kick is a logout of that seat. It is still not a second PC. It is still not a reinstall. The chassis is the same radio wearing two Windows names.

Two Windows accounts are not two Klox seats by themselves. A seat is a live handshake. If the tunnel stays up across Fast User Switching, the household still spent one seat. If the tunnel drops when the first person signs out, the next login has to Connect again. Look at the app. Do not assume. I will not invent a per-user Klox dashboard so this article matches a competitor screenshot. We did not ship that screen on the desktop app.

I will not print a minutes-and-seconds figure for when a dead peer drops. Networks fail closed, fail open, retry. Prefer in-app disconnect before a user switch you plan, so you are not guessing. If you already switched, open Klox on this PC after install, or on a phone that still has the app, and remove the leftover row. Change the password if you are not sure who held the old Windows login. Password reset is not this article's novel. It is the obvious next move when a machine sat unlocked with two accounts.

Family math lives in the five-device article. I will not rebuild the household spreadsheet. PC you still own plus phone is the common kit for this URL. After a clean remove, you are back to the ones that are actually tunneled. Ghost sessions are how people think a Windows user switch uses extra licenses. There are no extra licenses. There are leftover peers. Five means five connected at once. You can install in more places.

Yearly from $2.83 a month does not buy a sixth seat while a second Windows login retries a name the server still holds. Seven-day first purchase if you only bought to try a tunnel and you are inside the clock. Refunds: /refund. A user switch is not a refund reason by itself. A user switch is not a first-purchase coupon. If you already had a year, a new local account does not restart that clock.

The installer adds a virtual adapter. A reinstall of Windows deletes it. A user switch often does not. The NIC can still sit in the adapter list from the old install. First Connect under the new profile may still ask. Allow it. Cancel is how people decide a new Microsoft account hated VPNs. The product did not hate them. They denied the NIC.

I will not invent a TAP versus Wintun picker. The Download page does not offer that as a consumer protocol. Protocols remain WireGuard, OpenVPN, OpenConnect, and Shadowsocks. WireGuard first. OpenVPN when UDP is rude. Do not add a VPN in Windows Settings and pick IKEv2. That built-in row is not Klox. Two tunnels is how you get none. The Windows VPN Setup Checklist (2026) owns that order once the binary actually runs under this user. This page exists so you remember the leftover is the profile, not the disk.

Another VPN leftover can own the NIC if you installed a trial from a banner during first-run of the new account. Uninstall that. Then ours. Two privileged adapters fighting is a support ticket that starts with I switched user and nothing works. Split the jobs. Windows user is Microsoft. Binary is /download under this login. Adapter is Allow. Protocol is WireGuard unless the cafe is rude.

Windows Firewall stays on. The VPN and Windows Firewall: Do They Work Together? is the shield-plus-tunnel coexistence. I will tell you to keep it on and send fights there. Turning the shield off to make VPN work is how a new profile becomes a hobbyist lab. You wanted a hop. You did not want an open inbound day.

If Connect works on the old Windows user and fails on the new one, the usual miss is the adapter prompt this profile has not seen, or the .exe this profile does not have. Run the installer as administrator if Windows never asked. Then Connect. Approve the sheet. First handshake on a network you already trust. Do not debug both logins at once in a cafe.

A new Microsoft account can land you looking at Store-only if this PC was always S mode and you never left. Education SKUs and cheap laptops ship that way. S mode is Store-only. Our Windows client is an .exe from /download. There is not a Microsoft Store listing on that page. I will not invent one. If Settings still says S mode, the VPN on Windows S Mode: Store-Only, No Sideload .exe owns the gate. Switch out using Microsoft's docs if you meant the desktop app and policy allows it. Then come back for the user-switch leftovers: per-user install, adapter, seat, same email.

Architecture still matters after you create a local user. Snapdragon still wants ARM64. Intel and AMD still want AMD64. A new Microsoft account does not pick your CPU. People who just escaped a login wizard grab the first Windows button they see and then decide VPNs are broken. They grabbed AMD64 on ARM, or the reverse. The VPN on Windows ARM: Pick the ARM64 Installer, Not AMD64 article owns that picker. I will point. I will not reprint the About screenshot so three URLs compete.

The Chrome extension is on Download as browser-only traffic. After a new Windows user you may only have Edge or a fresh Chrome. The extension is not a NIC. Slack and the mail app stay in the clear. If you truly only needed that browser, install the extension and be honest about the leftover. For a system tunnel on this PC, you still need the .exe, admin, adapter. Do not treat the extension as a user-switch recovery SKU.

A borrowed laptop is still not this page. If the chassis is not yours, ask, uninstall, leave. Do not create a second Windows user on a machine you will give back so you can hide a VPN from the owner. That is a different product surface and I will not coach it. A wipe you ran is the reinstall article. If you Reset this PC and then created a Microsoft account, you have two articles. Read both. Do not paste one checklist into both days.

Linux ARM packages are a different OS. If this laptop dual-boots after you created a Windows user, that is two articles. Do not grab Klox-linux-arm.deb because you just read ARM in a forum. You are on Windows until you are not. Mac is a different family. Universal .dmg. Not this page.

Do not switch a Windows user you do not own. Work laptop. School image. A friend's PC you are fixing without asking. Stop. I will not coach a new local admin on a disk that is not yours. I will not coach bypassing BitLocker. I will not coach skipping a work or school account. I will not coach a VPN as a cloak for that. If it is employer property, IT owns the accounts. If it is a school device, the AUP still exists. If it is not yours, it is not yours.

First handshake should happen on home Wi-Fi or Ethernet in the kitchen. Confirm WireGuard comes up. Open a boring site. Then pack. A hotel splash plus a first-ever adapter prompt on a new Windows user is how people decide the login hated VPNs. The product did not hate them. The garden raced the tunnel.

Once the .exe actually runs under this account, the order is the Windows VPN Setup Checklist (2026): official file, adapter prompt, WireGuard first, OpenVPN if the network is rude, firewall on, hotel portal before panic, this PC is one of five. I will not reprint that list so two URLs compete. This page exists so you remember why you are doing the list again: the profile forgot the binary, or never had it.

Smart Connect, if the app shows the row, means connect on untrusted Wi-Fi. A cafe SSID is untrusted. A house SSID you run can be marked however the app lets you. I will not invent a toggle named On Demand. If the row is missing, you have a Connect button. Use the button after the splash, same as any other day. A new Windows user does not mint a special auto-connect.

Do not skip because the app felt slow once. Switch protocol. WireGuard first. OpenVPN when UDP is rude. If both fail on a network you trust, wait. A cafe is not the spare tire for a rude first handshake. A rude first handshake is a reason to stay in the kitchen until a boring site loads through the hop. Cookies on klox.app remain at /cookie. A Windows user switch is not a cookie. A leftover seat is not a cookie. Do not file a cookie ticket because a new profile still showed a peer. That peer is this article. ExpressVPN's Windows download ranking is not your leftover. Download the matching .exe under the account you live in. Count the seats. Leave Windows users you do not own alone.

The old Windows user can stay on the disk. That is allowed. Uninstall Klox there if you will not sign into it again, so the tray does not surprise the next person who still uses that login. If nobody uses that login, Microsoft's account list is their product. I will not write a delete-user novel. I will tell you not to delete a profile that still holds files you need. Look at Documents on that user before you feel brave.

Seven days is not a user-switch coupon. First purchase, seven days, /refund. If you already had a year, a new local account does not restart that clock. Same email. Same five seats. Yearly from $2.83 a month on the seats that remain. No city count. No portal URL. Cookie policy at /cookie.