Worship LIVE! and Windows "Data Execution Protection" (DEP) compatibility

Brandon Munday
2017-10-29 23:18

Windows XP and newer versions of Windows all include an anti-malware system called "Data Execution Protection". It's designed to catch attempts by rogue software to execute code outside of Windows' security system. However, it is known to work TOO WELL in some cases, flagging legitimate programs and activity and instantly terminating those programs.

With Windows XP, this mode was optional and was turned off by default. With Vista and Windows 7 it became more common, and in Windows Server and all 64-bit editions of Windows, it is turned on by default.

Unfortunately, this DEP system can trip up the Worship LIVE! and other software, and cause it to quit unexpectedly and instantly, with no chance to save your work, and without even allowing the software to report the problem properly. You will get a generic Windows error but if you look closely you'll see the DEP warning at the bottom:

http://www.fabriceroux.com/images/blogs/070208_dep_us_crash.png

Fortunately, it is possible to turn off this DEP feature, either for ALL software (we don't recommend this) or for just the Worship LIVE! software (this is the best choice).

How to turn on/off DEP in Windows XP or Windows Vista?

 

In windows XP,

 

  • Log in as administrator
  • Open the Start menu, right-click on My Computer and Choose “Properties” from the context menu.
  • On the “System Properties” window, click the “Advanced” tab .
  • Click the Settings button under Performance
  • Click the “Data Execution Prevention” tab
  • Choose either “Turn on DEP for all programs and services except those I select:” or “Turn on DEP for essential Windows programs and services only to select the OptIn policy
  • If you choose “Turn on DEP for all programs and services except those I select:“, click Add to add the programs that you do not want to use the DEP feature.
  • Click OK twice
  • Restart the computer for the changes to take effect

 

In Windows Vista,

 

  • Log in as administrator
  • Open the Start menu and right-click “Computer
  • Choose “Properties” from the context menu.
  • Choose “Advanced system settings” from under “Tasks” in the left pane.
  • Approve the User Account Control query (You will have to be an administrator to do it).
  • Click the button “Settings” in the Performance section.
  • Click the tab “Data Execution Prevention
  • Choose either “Turn on DEP for all programs and services except those I select:” or “Turn on DEP for essential Windows programs and services only to select the OptIn policy
  • If you choose “Turn on DEP for all programs and services except those I select:”, click Add to add the programs that you do not want to use the DEP feature.
  • Click OK twice
  • Restart the computer for the changes to take effect

 

Note that 64-bit versions of Windows automatically enforce DEP for all programs.

 

DEP Configuration, DEP in Vista, DEP in XP, windows xp dep, xp dep, boot.ini dep, disable dep

 

If you want to define policy_level as AlwaysOn or AlwaysOff, you must do it directly via Boot.ini file as detailed below:

 

  • Log in as administrator
  • Click Start, right-click My Computer, and then click Properties.
  • Click the Advanced tab, and then click Settings under the Startup and Recovery field.
  • In the System startup field, click Edit. The Boot.ini file opens in Notepad.
  • In Notepad, click Find on the Edit menu.
  • In the Find what box, type /noexecute, and then click Find Next.
  • In the Find dialog box, click Cancel.
  • Replace policy_level with AlwaysOn or AlwaysOff, as you may want. But make sure that you enter the text accurately. For eg., if you want to set it as AlwaysOn, Boot.ini file switch should read as /noexecute=AlwaysOn
  • Click Save on the File menu in Notepad to save the configuration
  • Restart the computer for the changes to take effect

For more information:
http://support.microsoft.com/kb/875352
http://techblissonline.com/enable-disable-dep-in-windows-xp-vista/

Average rating: 0 (0 Votes)

You cannot comment on this entry