Your screen freezes, the cursor spins, and the Task Manager shows lsalso.exe eating up your CPU. Before you panic and assume malware, know this: there are proven fixes. I've walked dozens of users through this exact scenario over the years, and in most cases, the solution is simpler than you'd think. This guide covers everything from quick safety checks to advanced registry edits—so you can get your system back to normal without the guesswork.
What Is lsalso.exe and Why Does It Stop Responding?
Let's clear up a common point of confusion right away: lsalso.exe is almost always a misspelling of LsaIso.exe (short for LSA Isolated). If you're seeing "lsalso" in Task Manager or in an error dialog, you're dealing with the same legitimate Windows security process that Microsoft documents as LsaIso.exe.
This process is a "trustlet"—a small, specialized program that runs inside Virtual Secure Mode (VSM), a hardware-isolated environment in Windows 10 and 11. Its job is to protect your credentials (passwords, Kerberos keys, and other sensitive authentication data) from being accessed by malicious code running in the normal operating system. Think of it as a vault within a vault: even if malware compromises the main OS, it can't reach the credentials locked inside VSM.
Lsalso.exe vs. LsaIso.exe: Clearing Up the Confusion
| Name | What It Is | Where It Lives |
|---|---|---|
| LsaIso.exe | The correct filename (LSA Isolated) | C:\Windows\System32 |
| lsalso.exe | Common misspelling of LsaIso.exe | Same location |
| The misspelling is so widespread that Microsoft's own support forums see users searching for "lsalso" when they mean "LsaIso." If you're troubleshooting, use both terms when searching—you'll find more relevant results that way. |
Common Causes of the 'Lsalso Not Responding' Error
Through my years of troubleshooting Windows systems, I've seen the "not responding" state trace back to a handful of recurring culprits:
- Outdated or faulty drivers — Graphics and chipset drivers are the usual suspects. When they try to load DLL files into the LSA process, things can destabilize.
- Corrupted system files — A botched Windows update or a failing hard drive can leave system files in a broken state.
- Third-party software conflicts — Security tools, VPN clients, and even some gaming overlays have been known to interfere with VSM processes.
- Malware masquerading as the process — Hackers sometimes name their payloads after legitimate system files. This is rare, but it happens.
- Windows updates gone wrong — A recent feature update can introduce regressions that affect LsaIso.exe behavior.
One thing worth noting: high CPU usage and "not responding" are related but distinct problems. High CPU usage means the process is actively working (too hard); "not responding" means it's hung or frozen. I'll dig into that distinction later in this guide.
How to Fix Lsalso Not Responding: A Step-by-Step Troubleshooting Guide
I've organized these fixes in order of complexity—start with the safety check, then work your way down. In my experience, most users resolve the issue by Step 3 or 4. The later steps are for stubborn cases.
Step 1: Verify the Process Is Legitimate (Safety Check)
Before you do anything else, confirm you're dealing with the real LsaIso.exe and not malware wearing its name.
- Press Ctrl + Shift + Esc to open Task Manager.
- Right-click lsalso.exe (or LsaIso.exe) and select Properties.
- Go to the Details tab and check the Copyright field. It should read "Microsoft Corporation. All Rights Reserved."
- Verify the file location is C:\Windows\System32. If it's anywhere else—especially in AppData or Temp folders—that's a red flag.
Even if everything checks out, run a quick scan with Windows Defender or your preferred antivirus. For extra peace of mind, upload the file to VirusTotal—it runs the file through 70+ antivirus engines and gives you a second opinion in under a minute.
Step 2: Run the Built-In Windows Troubleshooters
Windows ships with automated troubleshooters that can fix common issues without you needing to touch anything technical.
- Open Settings > Update & Security > Troubleshoot (Windows 10) or Settings > System > Troubleshoot (Windows 11).
- Run the Program Compatibility Troubleshooter.
- Run the System Maintenance troubleshooter.
These tools scan for common problems—like misconfigured settings or corrupted caches—and apply fixes automatically. It's worth trying before you dive into more invasive solutions.
Step 3: Perform a Clean Boot to Isolate the Problem
A clean boot starts Windows with only the essential drivers and services running. If lsalso.exe behaves normally in this state, you know a third-party program is causing the conflict.
Here's how to do it:
- Press Win + R, type
msconfig, and press Enter. - Go to the Services tab, check Hide all Microsoft services, then click Disable all.
- Go to the Startup tab and click Open Task Manager.
- Disable all startup items.
- Restart your PC.
If the problem disappears, re-enable services and startup items one by one until you find the culprit. It's tedious, but it works. In my experience, the usual offenders are security suites (especially ones with their own credential protection) and hardware monitoring tools.
Step 4: Update or Roll Back Problematic Drivers
Outdated drivers are one of the most common triggers for lsalso.exe issues. Here's how to tackle them:
- Press Win + R, type
devmgmt.msc, and press Enter to open Device Manager. - Expand categories like Display adapters, System devices, and Firmware.
- Right-click each device and select Update driver > Search automatically for drivers.
If the issue started after a recent driver update, try rolling back instead:
- Right-click the device and select Properties.
- Go to the Driver tab and click Roll Back Driver.
Pay special attention to graphics and chipset drivers—they're the ones I've seen cause LsaIso.exe problems most frequently.
Step 5: Repair Corrupted System Files with SFC and DISM
Corrupted system files can cause all sorts of strange behavior, including lsalso.exe freezing. Windows has built-in tools to find and repair them.
Open Command Prompt as administrator and run these commands in order:
sfc /scannow
This scans protected system files and replaces corrupted ones. If it finds issues it can't fix, follow up with:
DISM /Online /Cleanup-Image /RestoreHealth
DISM repairs the Windows image itself, which gives SFC a clean foundation to work from. After both scans complete, restart your PC.
Step 6: Disable or Reconfigure Credential Guard / VBS
This is the nuclear option—and I want to be clear about the trade-offs before you proceed.
LsaIso.exe is integral to Credential Guard and Virtualization-Based Security (VBS). Disabling these features reduces your system's security posture. Malware that steals credentials becomes more dangerous without the isolation VBS provides.
Only do this if you've exhausted the other options and you understand the risks.
If you're still reading, here's how to disable VBS via the registry:
- Press Win + R, type
regedit, and press Enter. - Navigate to:
HKLM\SYSTEM\CurrentControlSet\Control\Lsa - Find the LsaCfgFlags value. Set it to 0 to disable Credential Guard.
- Restart your PC.
Alternatively, you can disable VBS entirely via Group Policy:
- Press Win + R, type
gpedit.msc, and press Enter. - Navigate to Computer Configuration > Administrative Templates > System > Device Guard.
- Open Turn On Virtualization Based Security and set it to Disabled.
- Restart your PC.
Warning: Disabling VBS or Credential Guard weakens your system's defenses against credential theft. This should be a last resort, not a first response.
Lsalso Not Responding on Mac, iPhone, or Android?
Here's something that surprises a lot of people: lsalso.exe doesn't exist on Mac, iPhone, or Android. It's a Windows-specific system process tied to Microsoft's security architecture.
If you're seeing "lsalso not responding" on a non-Windows device, you're dealing with something else entirely—likely a third-party app or browser extension that happens to share a similar name.
Is lsalso a Cross-Platform App?
No. The LsaIso.exe process is deeply integrated into Windows' security model. It doesn't have a macOS, iOS, or Android equivalent. When users search for "lsalso not responding on mac," they're almost always encountering a different application—often a utility or a browser extension that's using a confusingly similar name.
Check your installed applications and browser extensions for anything named "lsalso" or similar. If you find one, that's your culprit.
Troubleshooting Similar Issues in Browsers (Chrome, Safari, Firefox, Edge)
If you're seeing "lsalso not responding" in a browser context, it's likely a rogue extension or a website script gone wrong. Here's how to clean things up:
- Disable all extensions — Go to your browser's extensions page and disable everything, then re-enable them one by one.
- Clear your cache — In Chrome: Settings > Privacy and security > Clear browsing data. Similar paths exist in Safari, Firefox, and Edge.
- Reset browser settings — This restores default configurations and removes most malicious extensions.
One more thing: if a pop-up says "lsalso is not responding" while you're browsing, treat it with suspicion. Legitimate system processes don't generate browser pop-ups. This could be a phishing attempt designed to trick you into downloading malware.
Lsalso High CPU Usage vs. Not Responding: What's the Difference?
These two problems get conflated all the time, but they're distinct—and they need different fixes.
| Symptom | What It Means | Common Cause | Typical Fix |
|---|---|---|---|
| High CPU usage | Process is actively consuming resources | Driver conflicts, overloaded system | Update drivers, end conflicting processes |
| Not responding | Process is frozen or hung | Software conflicts, corrupted files | Clean boot, SFC/DISM scans |
| High CPU usage can sometimes lead to a "not responding" state if the system becomes overwhelmed. But they're not the same thing, and treating them identically will waste your time. |
In my experience, high CPU usage is usually a driver issue—something is trying to load a DLL into the LSA process and causing a bottleneck. "Not responding" is more often a software conflict or file corruption problem.
Lsalso Not Responding After an Update: Special Cases
Updates can be a double-edged sword. They bring new features and security patches, but they can also introduce regressions.
Windows 11 vs. Windows 10: Different Behaviors
Windows 11 has tighter integration with VBS and Credential Guard, which means LsaIso.exe issues can be more prevalent. Microsoft enabled VBS by default on many Windows 11 systems, and while that's good for security, it also means more opportunities for something to go wrong.
Windows 10 users tend to see this issue after feature updates—the kind that arrive twice a year and bring major changes under the hood.
If you're experiencing lsalso.exe problems after an update, check for pending Windows updates and install them. Microsoft frequently releases patches for known issues, and the fix for your specific problem might already be available.
FAQ
Is LsaIso.exe safe?
Yes, the legitimate LsaIso.exe (lsalso.exe) is a safe Microsoft process. It's a core component of Windows security, protecting your credentials from malware. However, malware can disguise itself with the same name. To verify authenticity: check that the file is in C:\Windows\System32, confirm the copyright field says "Microsoft Corporation," and run a scan with your antivirus or upload the file to VirusTotal for a second opinion.
What is lsalso?
Lsalso.exe is a common misspelling of LsaIso.exe (LSA Isolated), a legitimate Windows security process. It runs in Virtual Secure Mode (VSM) as part of Credential Guard and KeyGuard, protecting sensitive authentication data like password hashes and Kerberos keys. The file is located at C:\Windows\System32 and is signed by Microsoft.
How do I fix lsalso not responding?
Start with these three quick fixes: 1) Run SFC and DISM to repair corrupted system files. 2) Perform a clean boot to isolate software conflicts. 3) Update or roll back problematic drivers. If none of these work, work through the full guide above—the registry edit to disable Credential Guard is the last resort.
Why does lsalso keep crashing on startup?
Startup crashes are often caused by a corrupted driver or a conflicting startup program. Perform a clean boot to identify the culprit, update your drivers, and check the Windows Event Viewer for specific error codes related to lsalso.exe. The Event Viewer logs will give you more detail than the generic error message.
Final Thoughts
Dealing with lsalso.exe not responding can feel like chasing a ghost—the process is obscure, the error messages are vague, and the forum advice is all over the place. But in my experience, the fixes above resolve the issue in the vast majority of cases.
Start with the simplest solutions: verify the process is legitimate, run the built-in troubleshooters, and perform a clean boot. Work your way up to the more advanced steps only if needed. And remember, disabling Credential Guard should be your absolute last resort—the security trade-off isn't worth it unless you've exhausted every other option.
If all else fails, a system restore or Windows reset will give you a clean slate. It's not elegant, but it works.
Did one of these methods fix your 'lsalso not responding' issue? If you found a different solution, share it in the comments below to help other users. If you're still stuck, let us know your specific error message and system specs for personalized assistance.