VS 2019/2022 IntelliSense dead after update? Fix here

You installed the latest Visual Studio update, and IntelliSense just stopped.

You open your solution. Code compiles fine. But the little dropdown suggestions? Dead. No syntax highlighting, no squiggly underlines, no autocomplete. It's like the language service went on strike. This happened to a client last month after the 17.8 update for VS 2022 — they spent two hours restarting and reinstalling extensions. None of that works. The fix is simpler, but you gotta know where to look.

Root cause

The update corrupts or invalidates the IntelliSense cache — a hidden folder where VS stores parsed project data. It can also mess up the .suo file (solution user options), or the settings in a local config file. The language service (the part of VS that powers IntelliSense) gets confused and stops responding. You don't need to reinstall VS. You don't need to nuke your whole environment. Just clear the cache, delete the user options file, or reset the user data. Do them in order — start with the least destructive.

Fix it in three steps

1. Clear the IntelliSense cache

This is the most common fix. VS stores cached data here:

%LOCALAPPDATA%\Microsoft\VisualStudio\17.0\ComponentModelCache

For VS 2019, replace 17.0 with 16.0. Close VS first. Then delete everything inside that ComponentModelCache folder. Don't delete the folder itself — just the files. Reopen VS, rebuild your solution, and you should see IntelliSense come back. If not, move to step 2.

2. Delete the .suo file

The .suo file sits in your solution's hidden .vs folder. It stores per-user settings like which files were open and what breakpoints you had. It can also carry corrupted IntelliSense state. Close VS, then navigate to your solution folder. Show hidden items if needed. Delete the entire .vs folder — not just the .suo file inside. Next time you open the solution, VS recreates it fresh. This alone fixed it for a client after the 17.9 preview update.

3. Reset VS user data (last resort)

If neither works, the update may have corrupted your main user data file. Run this command from a Developer Command Prompt (or any cmd as admin):

devenv.exe /ResetUserData

Warning: This wipes all your VS settings — theme, extensions, keybindings, startup project — back to factory defaults. But it's the nuclear option that always works. After running it, you'll have to reconfigure your environment. Back up settings first with Tools > Import and Export Settings > Export if you care about them.

What else to check if it still fails

• Extensions that hook into IntelliSense: Disable third-party extensions one by one (Extensions > Manage Extensions). Resharper, SonarLint, and some snippet tools sometimes conflict after an update. A client had ReSharper completely kill VS's native IntelliSense after the 17.7 update — disabling it fixed it instantly.
• Corrupted project cache: Close VS, delete *.suo and any *.user files from your solution folders, then delete the bin and obj folders. Rebuild from scratch.
• Diagnose the language service: Open the Output window (View > Output) and change the dropdown from "Build" to "Language Service". If you see errors like "Failed to initialize Language Service", that points to a corrupt installation. In that case, run the VS Installer, click "Modify" on your VS version, and choose "Repair". It takes 20 minutes but often fixes deep corruption.
• Check your .editorconfig or .vsconfig: A misconfigured .editorconfig file can silently turn off IntelliSense for certain file types. Temporarily rename it to see if that fixes the issue.

In my experience, step 1 works 70% of the time, step 2 gets another 20%, and step 3 catches the rest. Don't waste time reinstalling extensions or rebooting — that's a trap. The cache and .suo file are almost always the culprit.