-
Not necessary, if you let the installer overwrite the policy.xml.
I'm sure this problem has nothing to do with RAA. It's some kind of privilege problem of the windows shell.
Couldn't you find anything in the event log about a shell startup error!?
Try to revoke your admin rights (be a normal user) when RAA is uninstalled, will the windows shell startup normally in that case!?.
2009-09-29 11:57:09 UTC in RunAsAdmin Explorer Shim
-
You mean, when uninstalled RAA (and/or deleted registry entries and %SYSTEMROOT%\Shim directory) everything got back to normal, than after reinstalled the program the same taskbar problem occures at the first (re)login!?.
2009-09-29 10:27:54 UTC in RunAsAdmin Explorer Shim
-
Please try to uninstall than reinstall RAA, that should delete all registry settings.
Alternatively you can manually delete RAA registry settings under HKEY_LOCAL_MACHINE\SOFTWARE\RunAsAdmin.
Let me know please if it fixed the problem.
Thanks!
2009-09-28 12:46:16 UTC in RunAsAdmin Explorer Shim
-
If the shell, in our case RunAsAdmin explorer.exe can not start correctly and it could not start the real (windows) explorer.exe, you will not see a taskbar either.
To fix this change back the shell registry entry to it's original value like suggested here: https://sourceforge.net/projects/runasadmin/forums/forum/543633/topic/1706114.
2009-09-24 07:50:47 UTC in RunAsAdmin Explorer Shim
-
Unfortunately we heard that in some cases the task manager could not be started either.
In that case try to login as a different user or to edit the registry remotely.
RAA hijacks the task manager execution also if selected from settings.
You can revert that setting manually also if you delete the "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution...
2009-09-24 07:48:57 UTC in RunAsAdmin Explorer Shim
-
Please see F.A.Q. entry
https://sourceforge.net/forum/forum.php?thread_id=1706114&forum_id=543633.
2009-03-18 14:06:12 UTC in RunAsAdmin Explorer Shim
-
More about how to start programs as unrestricted can be found here https://sourceforge.net/forum/forum.php?thread_id=1833303&forum_id=543633.
2009-03-01 13:55:59 UTC in RunAsAdmin Explorer Shim
-
Currently there's no such possibility. You can only revoke admin privileges for a user than he/she won't be able to override levels defined in the policy.
2009-03-01 13:37:45 UTC in RunAsAdmin Explorer Shim
-
Because only way 1 and 4 goes through signaling only that 2 CAN (now) lead to policy evaluation.
To make every kind of file open go through that process, to behave the same way, we have to add signaling to 2 and 3 instead of the direct call of internal CreateNewProcess.
This might require the current user policies modification.
2008-11-28 09:56:12 UTC in RunAsAdmin Explorer Shim
-
Revising the release we found the reported bug is a by design behavior.
Version beta9 and later does not evaluate (therefore not calling annoying rules) just check the policy if the privileged open signal came from the shell extension.
We handle 4 ways of file open
1. Open from external source (via shell execute hook and a signal to RunAsAdmin)
2. Open via our command dialog (directly by...
2008-11-27 00:48:11 UTC in RunAsAdmin Explorer Shim
