I have an interactive service created with this command:
sc create TaskMGR binPath= "%SystemRoot%\System32\cmd.exe /c start /REALTIME
%SystemRoot%\System32\taskmgr.exe" type= own type= interact start= demand
error= ignore obj= LocalSystem
It used to generate an error when I try to run it, but then it would suceed
to start TaskManager as NT Authority\System. Now (probably after my last
visit to windows update) it no longer starts TaskManager.
I need System priviledges from time to time and I usually begin with a
Command Prompt or TaskManager window. How do I revert to the previous
behaviour, when my custom service worked? Or how do I escalate my
priviledges from Administrator to NT Authority\System?
Windows 2003 Enterprise server SP2, up to date, x86 platform.