Windows 11 26H2 EmulateHeap: Windows 95 Heap Compatibility Shim Explained

What was actually found​

Windows Latest reported on Oct. 19, 2026 that it found EmulateHeap listed in Compatibility Administrator on one Windows 11 26H2 PC. That is a single reporter's observation on one machine. It is not a Microsoft statement that every Windows 11 install contains the fix.

The "31 years" figure refers to the age of the Windows 95 code, not to a Windows 11 feature that has run continuously since 1995. The EmulateHeap shim has been documented for years. Raymond Chen described it in a 2010 Windows Confidential column.

What EmulateHeap does​

Chen's column explains the mechanism. If the fix is enabled on a process, the OS-level heap functions, from HeapCreate to LocalLock to GlobalReAlloc, are redirected to replacement functions that emulate the Windows 95 heap down to the last detail.

The way Microsoft built it is the part that surprises people. The developers took a copy of the Windows 95 Heap Manager source code, recompiled it, and added it to the compatibility infrastructure. Chen's conclusion was that a significant chunk of the Windows 95 kernel sits inside the compatibility framework.

Why would anyone need this? Chen says older programs carried small mistakes that went unnoticed on Windows 95. Those programs got away with the mistakes only because of how the Windows 95 Heap Manager behaved, and they crash on other Windows versions that have a different Heap Manager. The mistakes include:

• Reading memory after it has been freed.
• Expecting a new allocation to reuse a freed block's address.
• Overflowing a buffer in a way that happened to be harmless on the old layout.

Chen also doesn't treat the old manager as superior. He says it doesn't make the Windows 95 Heap Manager "better" or "more robust". It's just different.

Not always on, and not a background Windows 95​

The scariest reading of the headline is that a 1995 memory manager runs under your desktop right now. The evidence doesn't support that. Windows Latest, relaying Chen, says the old code loads only when EmulateHeap is enabled for an app. Chen says the old code loads from disk only when EmulateHeap is turned on for a specific application. Neither source claims the fix is enabled by default.

Compatibility shims also work within a process. In a 2017 post, Chen noted that shims work only inside the app's own process, so they don't change the security boundaries between the program and the rest of the system. His broader warning applies to shims generally: they should be applied only to solve real compatibility problems. Some of them weaken security on purpose, because the old program depends on the old behavior. The sources don't show that EmulateHeap in particular carries a security weakness, so treat that as a general caution, not a finding.

The SimCity detour is a separate fix​

The SimCity story is the famous part, and it is easy to conflate with EmulateHeap. The Windows 3.x version of SimCity read memory after freeing it. Microsoft added code to Windows 95 that detected the game and delayed freeing memory. Windows Latest says explicitly that EmulateHeap is not the code written for SimCity. Both come from the same compatibility mindset, but they are separate fixes. SimCity is the origin story of Microsoft bending Windows around an app's bugs. It isn't evidence of how EmulateHeap works.

How to see EmulateHeap yourself​

Windows Latest describes this procedure on a 26H2 PC. It only lists the fix and doesn't enable anything.

1. Download the Windows Assessment and Deployment Kit (ADK) from Microsoft and run the installer.
2. Select only Application Compatibility Tools in the feature list and finish the install.
3. Search Start for Compatibility Administrator and open the 32-bit version, since most Windows 95-era apps are 32-bit.
4. Under Custom Databases, right-click New Database, then choose Create New > Compatibility Mode.
5. Scroll the list of available compatibility fixes down to EmulateHeap.

Microsoft's ADK documentation confirms the context. The ADK includes the Compatibility Administrator and the Standard User Analyzer tool. The September 2026 release, version 10.1.26100.9457, supports Windows 11 versions 26H2, 25H2 and 24H2. This confirms the tool and its supported versions. It does not independently confirm that EmulateHeap appears on every one of them.

Should you turn it on?​

Probably not, unless you have a specific legacy app that fails in a way that points to heap behavior. Seeing a fix in a list doesn't mean it works. Windows Latest notes that users reported that games such as GTA Vice City lost sound and Need for Speed: Most Wanted crashed with the shim enabled after the Windows 11 22H2 update. The report gives no tested application and no before-and-after results. Neither does this article, so don't treat it as a tuning tip.

Some practical rules for admins:

• Use compatibility fixes narrowly, on a named executable, and only after a real failure.
• Test the fix on a non-production machine first.
• Prefer a vendor update, or virtualization, when one is available.
• Document every custom shim database you deploy so it can be audited later.

The bigger picture​

Windows is redesigning a lot of its interface. Windows Latest points out the irony of Microsoft replacing the Windows 95-era Properties dialog with WinUI 3 while keeping the 1995 heap manager available for a handful of old apps. That isn't laziness. Microsoft treats compatibility as a product feature. The company bends the OS around specific apps, as it did for SimCity, and it keeps a preserved fragment of old code around for programs that can't be fixed.

The cost is a growing pile of legacy code. The benefit is that a program written in the mid-1990s can still have a way to run on a 2026 operating system. The accurate headline is that Windows 11's compatibility tooling can still reproduce Windows 95 heap behavior for one app on request. It does not mean Windows 11 secretly runs on Windows 95.