VS C++ IntelliSense Crashes: Fix in 30 Seconds to 15 Minutes

First, the 30-second fix: give IntelliSense more memory

Most of the time, IntelliSense dies because it runs out of RAM. The default limit is 4 GB, which sounds like a lot but gets eaten fast when you have a few thousand files and heavy template code. You can raise that cap in under a minute.

1. In Visual Studio, open Tools → Options.
2. Go to Text Editor → C/C++ → Advanced.
3. Look for “Disable IntelliSense” – set it to False if it's not already.
4. Scroll down to “Fallback Location” and set it to a local folder like C:\IntelliSenseCache – don't use a network drive.
5. Then find “Maximum File Size” – bump it to 10000 (KB).
6. Click OK and restart VS.

After you restart, open your project and see if the red squiggles still freeze the editor. You should notice the CPU spike settles within 10 seconds of opening a file. If it still crashes, move on.

The 5-minute fix: clear the IntelliSense cache and re-scan

If the memory bump didn't stop the crashing, the cache is probably corrupted or stale. IntelliSense keeps a local database of your symbols, and when that database gets out of sync with your actual code, it goes into a loop and dies. Wipe it clean.

1. Close Visual Studio completely. Make sure no devenv.exe process is running in Task Manager.
2. Open a command prompt as administrator.
3. Run this command:

cd %LOCALAPPDATA%\Microsoft\VisualStudio\17.0_xxxx\ComponentModelCache

Replace 17.0_xxxx with your actual VS version folder – you'll see a bunch of them, pick the highest number.

4. Delete everything inside that folder. Don't worry, VS rebuilds it automatically.
5. Also delete the %LOCALAPPDATA%\Microsoft\VisualStudio\17.0_xxxx\ folder called IntelliSense if it exists – that's the actual database.
6. Restart VS. It will take 1–2 minutes to rebuild the index, but it won't crash while doing it.

If you're using VS 2019, the path is 16.0_xxxx instead. The process is identical.

This clears the stale data that's causing the freeze. You should see IntelliSense working again after the rebuild. If it still crashes, there's one more thing to try.

The 15+ minute fix: switch to the 64-bit version of Visual Studio

Here's the real deal: Visual Studio 2022 is 64-bit, but many devs still run the 32-bit version out of habit. The 32-bit process can't address more than 4 GB of RAM, period. No matter how much you raise the IntelliSense limit, it'll hit a wall. The fix is to install the 64-bit edition.

1. Open the Visual Studio Installer.
2. If you have VS 2022 installed, check the version under Installed – if it says 32-bit, you need to change it.
3. Click Modify on your installation.
4. In the Workloads tab, you'll see a checkbox near the bottom: “Install 64-bit tools”. Check it.
5. Click Modify and wait for the install to finish (takes 5–10 minutes).
6. Restart your machine, then open VS again.

After that, VS will run as a 64-bit process. You can verify by going to Help → About – it'll say “Visual Studio 2022 (64-bit)”. This change alone fixed my crash on a project with 1,200 files and heavy template metaprogramming.

If you're on VS 2019, you're out of luck – there's no 64-bit version. You'll need to upgrade to VS 2022. It's worth it.

What actually causes the crash in real projects

Here's a concrete scenario: you've got a Unity or Unreal project with a large generated header file, like GeneratedCpp.inc that's 5 MB. IntelliSense tries to parse that file in a single pass, and the parser eats all available RAM. The 32-bit process hits the 4 GB ceiling, throws an out-of-memory exception, and the whole UI freezes. The memory cap fix helps, but the 64-bit switch is the permanent solution.

Another common trigger: a file that includes a lot of headers via a precompiled header (PCH). If your PCH is huge, IntelliSense re-parses it every time you edit a file, which hammers the CPU and memory. The cache clean helps because it forces a fresh parse, but the real fix is to limit what's in the PCH.

One more tip: disable IntelliSense for specific files

If you're still stuck after all that, you can exclude certain files from IntelliSense parsing. It's not ideal, but it beats crashing. Right-click on a file in Solution Explorer, go to Properties, then C/C++ → Advanced, and set “Disable IntelliSense” to True. Do this for your generated files or any huge file that never needs autocomplete.

That's the full flow. Start with the 30-second memory bump, then the 5-minute cache clean, then the 15-minute 64-bit install. Most people stop at step 2 and never look back. If you've done all three and still get crashes, you might have a corrupt VS installation – in that case, run the installer again and choose Repair. But honestly, that's rare.