Quitch

Seems to work like a charm, thanks!

I searched the topic but didn't find any reference to the arstechnica review of this product which brought me here.

Whoops, sorry that was bad of me: Windows 8 Pro 64-bit System-wide Always-on DEP enabled through EMET 3.5. Log Name: Application Source: Application Error Date: 15/01/2013 23:40:36 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: FurryGopher Description: Faulting application name: StartIsBackCfg.exe, version: 1.3.2.0, time stamp: 0x50ef3ed3 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc00001a5 Fault offset: 0x022dfdec Faulting process ID: 0x1164 Faulting application start time: 0x01cdf379b667fbff Faulting application path: C:\Users\Quitch\AppData\Local\Temp\7zS8B460053\StartIsBackCfg.exe Faulting module path: unknown Report ID: f540b7d8-5f6c-11e2-be82-001fd08a0b28 Faulting package full name: Faulting package-relative application ID: Log Name: Application Source: Application Error Date: 15/01/2013 23:40:39 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: FurryGopher Description: Faulting application name: StartIsBackCfg.exe, version: 1.3.2.0, time stamp: 0x50ef3ed3 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x022dfdde Faulting process ID: 0x1164 Faulting application start time: 0x01cdf379b667fbff Faulting application path: C:\Users\Quitch\AppData\Local\Temp\7zS8B460053\StartIsBackCfg.exe Faulting module path: unknown Report ID: f7853490-5f6c-11e2-be82-001fd08a0b28 Faulting package full name: Faulting package-relative application ID: It was my understanding that EMET 3.5 was using the OS implementation of DEP. Perhaps this is incorrect.

If you have DEP selected for "all programs and services" (not the default), then you might have to exclude StartIsBackCfg.exe from it. I believe this was mentioned early in the development, but as users have to manually change from the default DEP setting to this, it would probably be considered "normal" behavior to have to exclude it from DEP if DEP isn't set to the default "for essential Windows programs and services only". It just strikes me as odd for any program developed in this day-and-age to crash when subject to DEP. I mean, as you say, I can exclude it, but it's a really bad coding habit to slide into. Check DEP. Check ASLR. This stuff should be enabled on everything you do as of at least five years ago.

StartIsBackCfg.exe doesn't play nicely with DEP unfortunately, it crashes.