Access runtime 2003 will not start on Windows 10 Enterprise
It turned out to be linked to EMET and DEP. We have version 5.51 of EMET
By starting the EMET Notification gui (as Admin) and then starting Access I got a notification on the taskbar:
"EMET detected DEP mitigation and will close the application MSAccess.exe"
This is also logged in the Application log (it was not before).
When I reran sysinternals procmon I could see that EMET had been triggered when MSAccess started to run.
There are options with DEP and within EMET.
However, it turned out that we have DEP protection enabled at all times. OptOut and OptIn have no effect, Emet still starts. and this can only be changed by altering Secure Boot policy
4 values:
bcdedit /set {current} nx AlwaysOn - our default setting
bcdedit /set {current} nx OptOut - able to set this but EMET still came on
bcdedit /set {current} nx OptIn - able to set this but EMET still came on
bcdedit /set {current} nx AlwaysOff
An error has occurred setting the element data. The value is protected by Secure Boot policy and cannot be modified or deleted
-