New
#11
Try:
@echo off
RUNAS taskkill /im Atom.SDK.WindowsService.exe /t /f
echo
exit
I don't get why you want to kill it.
Try:
@echo off
RUNAS taskkill /im Atom.SDK.WindowsService.exe /t /f
echo
exit
I don't get why you want to kill it.
More generic version to support random commands with arguments.
Code:$whitelist = @{ "Script 1" = @{ Command = "cmd.exe" Argument = "/c C:\Users\GARLIN\batch.cmd" } "Kill AtomSDK" = @{ Command = "taskkill.exe" Argument = "/im Atom.SDK.WindowsService.exe /t /f" } } $tasksPath = "\UAC Whitelist" $shortcutsDir = "$env:USERPROFILE\Desktop" $user = [System.Security.Principal.WindowsIdentity]::GetCurrent().Name $principal = New-ScheduledTaskPrincipal -UserId $user -LogonType Interactive -RunLevel Highest $whitelist.GetEnumerator() | ForEach-Object { $name = $_.Name $command = $_.Value.Command $argument = $_.Value.Argument # Create "scheduled" task $action = New-ScheduledTaskAction -Execute $command -Argument $argument $task = New-ScheduledTask -Action $action -Principal $principal Register-ScheduledTask -Force -InputObject $task -TaskPath $tasksPath -TaskName $name # Create shortcut to run the above task $WshShell = New-Object -ComObject WScript.Shell $shortcut = $WshShell.CreateShortcut("$($shortcutsDir)\$($name).lnk") $shortcut.TargetPath = "C:\Windows\System32\schtasks.exe" $shortcut.Arguments = "/RUN /TN `"$($tasksPath)\$($name)`"" $shortcut.IconLocation = "C:\Windows\System32\cmd.exe,0" $shortcut.WorkingDirectory = "C:\Windows\System32" $shortcut.Save() }
no joy (cmd window displays RUNAS Usage help)
Installed a vpn and (unknown to me) it also installed Atom. So, I assumed this service was required for the vpn as I had never seen it before. Began to notice that when I shutdown the vpn app, atom was not shutting down along with it, which I assumed it should and I decided to create a batch shutdown for the vpn. The batch worked fine until recently when I noticed that the atom taskkill was failing due to 'access denied' error (other topic on this in General forum) .
You can try preventing it from running:
If that causes problems just delete the registry entry.Code:reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\Atom.SDK.WindowsService.exe" /v Debugger /t REG_SZ /d "%windir%\System32\taskkill.exe" /f
Also I don't know which VPN you're using but I can see posts elsewhere that suggest that this runs if using Pure VPN with wireguard protocol. If that's the case (I know that it might not be) try another configuration. (Protocol).
Anyway it's possible that the service needs to be running in the background after boot for the VPN to work.
ok - Not a showstopper so I will shelf the issue for now, thanks to all
Thanks again -
Last question. Is it possible to prevent this service from starting at boot? In addition to the taskkill 'no longer working' w/o admin credentials, this task is now starting at boot. I know the vpn uses this service but the app will start it when the app is invoked, thus my assumption and surprise that closing the app did not end the task. I still suspect the latest windows update did something based on the timing of this behavior.