Disable scheduled tasks instead of remove

[404]

I'd like the ability to disable scheduled tasks instead of remove them in NTLite

 

[garlin]

That's not possible with any Windows image editing tool. Scheduled tasks are stored in the registry, and protected by a security hash. When you modify any task (including to disable), the hash is required to be updated. For obvious security reasons, MS doesn't reveal how it works.

The only way is to sysprep an image, disable your tasks, and capture it to WIM.

 

[aviv00]

u can import them from ..system32\tasks

 

[garlin]

u can import them from ..system32\tasks

Except that doesn't work, editing the task file creates a scheduler error:
Task [Name]: The task image is corrupt or has been tampered with.

Your edited task will be skipped (same result as disabled), but you can no longer edit it from Task Scheduler or schtasks. It's possible to run a disable command in Post-Setup, but it won't stop any task which is triggered before Post-Setup.

schtasks /change /tn MyTaskName /disable

 

[nuhi]

I'd like the ability to disable scheduled tasks instead of remove them in NTLite

Would you be ok if it's just adding a command as garlin suggested?

 

[aviv00]

Except that doesn't work, editing the task file creates a scheduler error:

i do it all the time
i remove all the tasks
and add back

with this ps

Register-ScheduledTask -Xml (Get-Content ("C:\Windows\System32\Tasks\Microsoft\Windows\TextServicesFramework\MsCtfMonitor") | Out-String ) -TaskName "MsCtfMonitor"

and the typing password into wifi works also search in cortana

 

[garlin]

That doesn't update offline images. You're ignoring the possibility your task needs to be triggered before the import command is run.

 

[nuhi]

That doesn't update offline images. You're ignoring the possibility your task needs to be triggered before the import command is run.

Regarding disabling via command-line at the end of setup via the post-setup machine section, before any users are created.
Would that be early enough to warrant a separate option? I believe most will be satisfied if the task is disabled whenever during setup, and those that need it guaranteed not ran, can remove it.

Basically I'm asking for your opinion to add a disable command support or not. I prefer to avoid scripting, potentially would be fine if added to the post-setup page and people can edit/remove them at will, just use the Scheduled Tasks page to easily enqueue them?

 

[garlin]

Disabling tasks under the Scheduled Tasks page would be my preference. NTLite should probably check the trigger and if any condition is run on startup -- provide you a warning dialog so you know this change doesn't take effect until the next reboot.

 

[chrcol]

I have always been ok with disabling post install using commands in a post install script.

But I like the idea of adding a means to disable within ntlite, with the warning of course the tasks may still get ran prior to them being disabled.

 

[Random Bit]

import winreg
from hashlib import sha256
from pathlib import Path
from winreg import HKEY_LOCAL_MACHINE

with winreg.OpenKey(HKEY_LOCAL_MACHINE, r'SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Test') as key:
    task_id, _ = winreg.QueryValueEx(key, 'Id')

with winreg.OpenKey(HKEY_LOCAL_MACHINE, fr'SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tasks\{task_id}') as key:
    task_hash, _ = winreg.QueryValueEx(key, 'Hash')
    task_file, _ = winreg.QueryValueEx(key, 'Path')

task_path = Path(rf'C:\Windows\System32\Tasks{task_file}')
task_xml = task_path.read_bytes()[2:]
super_secret_hash = sha256(task_xml).hexdigest()

print(f'Task GUID: {task_id}')
print(f'Task path: {task_path}')
print(f'Task hash: {task_hash.hex()}')
print(f'Calc hash: {super_secret_hash}')