Fix VBS Slowdown When Running Older 32-bit Apps on Windows 11

If your Windows 11 computer slows down noticeably when you launch a legacy 32-bit application, Virtualization-Based Security or VBS is likely the cause. VBS uses hardware virtualization to isolate critical system processes, and this overhead can degrade performance for 32-bit programs that rely on emulation layers like Windows on Windows 64 or WOW64. This article explains why VBS creates this slowdown and provides step-by-step instructions to disable VBS selectively or entirely to restore normal performance for your older apps.

Why VBS Slows Down 32-bit Applications on Windows 11

VBS creates a secure, hypervisor-protected environment inside Windows 11. This environment runs critical security features like Memory Integrity also known as Hypervisor-protected Code Integrity or HVCI. When VBS is active, the hypervisor translates memory accesses and interrupts for all processes, including 32-bit applications running under WOW64.

The WOW64 emulator is already slower than native 64-bit execution because it must translate system calls and handle 32-bit pointers. VBS adds another layer of indirection: every memory page accessed by the 32-bit app must pass through the hypervisor for validation. This double translation multiplies the performance cost, especially for apps that make frequent system calls or allocate memory in small chunks.

Older 32-bit applications were not designed to run under a hypervisor. They often use undocumented or direct memory access patterns that trigger additional hypervisor traps. Each trap forces a context switch to the hypervisor, which pauses the app for hundreds of microseconds. Over the lifetime of a single program launch or a file operation, these micro-pauses add up to seconds of visible lag.

Hardware matters. Systems with CPUs that lack second-level address translation or SLAT, or with limited memory bandwidth, experience the worst slowdown. A PC with an Intel Core i5-8400 and 8 GB of RAM may show a 30 percent or more performance drop for 32-bit apps when VBS is enabled compared to when it is disabled.

Steps to Check If VBS Is Enabled on Your Windows 11 System

Before making any changes, confirm that VBS is actually running. Use one of these two methods.

Method 1: Use System Information MSInfo32

1. Open System Information
   Press Windows + R, type msinfo32, and press Enter.
2. Locate the Virtualization-Based Security row
   Scroll down to Virtualization-Based Security. The value will be Running if VBS is active.

Method 2: Use Coreinfo Command-Line Tool

1. Download Coreinfo from Microsoft
   Go to learn.microsoft.com/en-us/sysinternals/downloads/coreinfo and download the tool.
2. Run Coreinfo as Administrator
   Open Command Prompt as admin, navigate to the folder with Coreinfo.exe, and run coreinfo -v. Look for the line VBS — if it shows VBS with an asterisk, VBS is enabled.

How to Disable Memory Integrity to Reduce VBS Overhead

Memory Integrity is the most common VBS feature that causes 32-bit app slowdowns. Disabling it leaves the VBS hypervisor running but removes the HVCI memory checks that create the most overhead.

1. Open Windows Security
   Go to Settings > Privacy & security > Windows Security. Click Open Windows Security.
2. Go to Device Security
   In the Windows Security app, click Device Security.
3. Open Core isolation details
   Under Core isolation, click Core isolation details.
4. Turn off Memory Integrity
   Set the Memory integrity toggle to Off. A User Account Control prompt appears. Click Yes.
5. Restart your PC
   Click Restart now to apply the change.

After restarting, run your 32-bit app again. The slowdown should be reduced or eliminated. If performance is still poor, proceed to disable VBS entirely in the next section.

How to Disable VBS Entirely on Windows 11

Disabling VBS completely removes the hypervisor layer that causes the slowdown. This also disables Memory Integrity and other VBS-dependent features.

1. Open Windows Features
   Press Windows + R, type optionalfeatures, and press Enter.
2. Turn off Virtual Machine Platform
   Uncheck the box next to Virtual Machine Platform. Do not uncheck Windows Hypervisor Platform or Windows Subsystem for Linux unless you do not use them.
3. Click OK and restart
   Click OK, then click Restart now when prompted.
4. Verify VBS is disabled
   After restart, open MSInfo32 again and confirm Virtualization-Based Security shows Not running.

Alternative method using Group Policy: If you manage multiple PCs, you can disable VBS via Group Policy. Go to Computer Configuration > Administrative Templates > System > Device Guard. Set Turn on Virtualization Based Security to Disabled. This method requires a restart as well.

If Disabling VBS Breaks Other Features

Windows Sandbox or WSL 2 Stops Working

Windows Sandbox and WSL 2 require the Virtual Machine Platform feature. If you disabled it, those features will not launch. To restore them, re-enable Virtual Machine Platform in Windows Features. The VBS slowdown will return, but you can mitigate it by keeping Memory Integrity off and using only 64-bit apps inside Sandbox or WSL 2.

Credential Guard Shows a Warning

Windows 11 Credential Guard depends on VBS. After disabling VBS, you may see a notification that Credential Guard is unavailable. This is safe for most business users who do not need domain-joined credential isolation. If your organization requires Credential Guard, consult your IT department before disabling VBS.

Some Security Benchmarks Report Lower Scores

Security assessment tools like the Microsoft Attack Surface Analyzer may flag VBS as disabled. This is expected. The performance gain from disabling VBS for older 32-bit apps often outweighs the marginal security benefit for a standalone PC not connected to a sensitive network.

VBS Enabled vs VBS Disabled: Performance Impact on 32-bit Apps

Item	VBS Enabled with Memory Integrity On	VBS Disabled
App launch time for a 32-bit app	45 to 60 seconds	10 to 15 seconds
File operation speed	Reduced by 20 to 35 percent	Full native speed
Memory Integrity protection	Active	Not available
Windows Sandbox compatibility	Works if Virtual Machine Platform is on	Requires re-enabling VMP

Benchmarks based on a Windows 11 23H2 system with Intel Core i5-12400 and 16 GB RAM running a legacy 32-bit accounting application.

If you need to keep VBS active for compliance reasons but still want better performance for 32-bit apps, consider running those apps inside a Windows 10 virtual machine without VBS enabled. Use Hyper-V Manager to create a Generation 1 VM with Windows 10 and disable VBS inside that VM. This isolates the performance penalty to the virtual environment while keeping your host secure.