Security

Download PROCMON from Microsoft (http://technet.microsoft.com/en-gb/sysinternals/bb896645.aspx). Run this as the std user (on Win7 do a right-click Runas as it needs admin permissions). Run the app and when you get the error stop procmon from recording by clicking on the magnifying glass icon). Starting at the top search for ACCESS DENIED. Hopefully you will find one or more which will indicate a reg key or file that a std user cannot access. Change the permissions and then retest. If this doesn't fix it try running the app in XP mode if you are on Win7. If this still doesn't work try making a compatibility shim with the compatibility toolkit from Microsoft.

If you post some details after you've tried this I'll try and help.

If you're still having an issue with this, take a look at LUA Buglite - http://blogs.msdn.com/b/aaron_margosis/archive/2012/11/28/lua-buglight-2-2-with-support-for-windows-8.aspx

Basically, LUA Buglight runs the application as a standard user, but when some aspect of it fails, it runs it again with admin credentials (that you've provided), and then tells you explicitly what file/registry areas required permission.

It might shed some light on this issue and help.

Dunnpy

If you do run ProcMon to find it you can also search for the Ding.wav (or equivelent). When the stop occurs it sounds a "Ding". By looking for this in procmon you can narrow your field down.

There are several solutions from RES, AppSense, and others that allow for running individual apps in elevated rights mode instead of a wild west all rights allowed model.