Bill Roper (billroper) wrote,
Bill Roper
billroper

Putting the Fault Tolerant Heap In Its Place

If you've been following my little battle against Microsoft's Fault Tolerant Heap which happily enabled itself on a development system in such a way to make actual development use impossible, you may be amused to find out that I now have a solution to the problem and am able to go back to normal debugging with Visual Studio. More or less. :)

It turns out that you can disable the Fault Tolerant Heap by renaming the DLL that it uses: Windows\AppPatch\AcXtrnal.dll. I had tried this before without success, because on Windows Server 2008 R2, the file belongs to "Trusted Installer", which prevents anyone except an installation program from deleting or renaming the file.

If you go to the advanced options in the file properties, you can take ownership of the file away from Trusted Installer and give it to yourself. Then you can add yourself (or just Administrators) to the list of people with Full Control of the DLL.

And then you can rename it.

This will prevent the Fault Tolerant Heap from running on the system at all, at least until you get an OS update that reinstalls it, at which point you'll have to do all this again.

But -- for the time being, at least! -- the Fault Tolerant Heap has been moved to the correct location.

The trash heap.

"Hi! We're from Microsoft and we're here to help you!"
Tags: computers, microsoft, musings, work
Subscribe
  • Post a new comment

    Error

    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded 

  • 5 comments