I have found sudowin to be dependent on the Secondary Logon or seclogon logon service. Many of the Microsoft security templates will disable the Secondary Logon service. When Secondary Logon service is disabled, sudowin will appear to run correctly but the process will not spawn. It would be easier for someone to catch this problem if sudowin had a dependency set for seclogon. Once recognized they could easily modify their security templates so that Seconday Logon is no longer disabled so that sudowin will work correctly again.
mmiko@rci.rutgers.edu
