Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, January 7, 2020 7:23 PM
I have created a task in Windows 10 to be triggered on event Windows kernel boot, Event ID 27 , but it isn't triggered on this event.
The reason I'm doing this is to trigger the task every time that system boots, and since At Startup trigger doesn't work with fast startup I tried to use this approach.
Am I doing something wrong?
Thanks
All replies (12)
Wednesday, January 8, 2020 8:25 AM
Hi,
When creating task, on New Triger windows, please select Custom -> New Event Filter, configuration as below:
Besides, on General tab, please select below options:
Best Regards,
Eve Wang
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, January 10, 2020 7:24 AM
Hi;
Thank you for your answer.
I tried your solution but it didn't work (according to last runtime column). Also "Run whether user …" and "Run with highest privileges" were already set.
Friday, January 10, 2020 6:54 PM
I could not get a task triggered on event id 27 either. I assume it is due to the fact that is being generated at boot time and as part of kernel processing. That is an educated guess.
But I do not have problems running tasks At System Startup. For both normal and fast boot. My tasks run as the system account. I am running version 1909.
This thread says that the problem is fixed in 1809.
If you can't upgrade, then have you measured how much time fast startup saves your users? Just turn that off.
Saturday, January 11, 2020 7:03 PM
I could not get a task triggered on event id 27 either. I assume it is due to the fact that is being generated at boot time and as part of kernel processing. That is an educated guess.
Yes, my guess is that task scheduler somewhat misses the event as it loads later than it.
But I do not have problems running tasks At System Startup. For both normal and fast boot. My tasks run as the system account. I am running version 1909.
This thread says that the problem is fixed in 1809.
If you can't upgrade, then have you measured how much time fast startup saves your users? Just turn that off.
I'm also on version 1909 with latest updates, but my task (with At System Startup trigger) only runs on cold boot.
In Windows 10 disabling fast startup affects startup time significantly for me.
Sunday, January 12, 2020 4:34 PM
I'm also on version 1909 with latest updates, but my task (with At System Startup trigger) only runs on cold boot.
I'm sure that you've looked at some of these, but I'd suggest... configure the task for Windows 10 and run as system.
Try setting it to run if start is missed.
Check the task history and see if there are any relevant entries at boot time.
Create a new trivial task that runs at startup and see if that runs. Just run cmd.exe with a parameter of 'exit".
In Windows 10 disabling fast startup affects startup time significantly for me.
Do you know what is causing the delay? Check the Microsoft-Windows-Diagnostics-Performance/Operational eventlog.
Thursday, January 16, 2020 8:15 AM
Hi,
How things are going there on this issue?
Please let me know if you would like further assistance.
Best Regards,
Eve Wang
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Saturday, January 18, 2020 8:00 AM
Create a new trivial task that runs at startup and see if that runs. Just run cmd.exe with a parameter of 'exit".
I Tried it, it didn't run.
Hi,
How things are going there on this issue?
Please let me know if you would like further assistance.
Best Regards,
Eve WangPlease remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
I'm still waiting for a solution.
Thanks
Saturday, January 18, 2020 3:56 PM
I'm still waiting for a solution.
Can you please export the task definition as XML and post it back here so that we can examine the settings?
Saturday, January 18, 2020 4:34 PM
Sure, here you are:
<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.4" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
<RegistrationInfo>
<Date>2019-11-16T15:07:09.2665175</Date>
<Author>DESKTOP-QOHJ6SD\mtasn</Author>
<URI>\Kill Startup Bloats</URI>
</RegistrationInfo>
<Triggers>
<BootTrigger>
<Enabled>true</Enabled>
<Delay>PT30S</Delay>
</BootTrigger>
<EventTrigger>
<Enabled>true</Enabled>
<Subscription><QueryList><Query Id="0" Path="Microsoft-Windows-Kernel-Boot/Operational"><Select Path="Microsoft-Windows-Kernel-Boot/Operational">*[System[(EventID=27)]]</Select></Query></QueryList></Subscription>
</EventTrigger>
</Triggers>
<Principals>
<Principal id="Author">
<UserId>S-1-5-18</UserId>
<RunLevel>HighestAvailable</RunLevel>
</Principal>
</Principals>
<Settings>
<MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
<DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
<StopIfGoingOnBatteries>false</StopIfGoingOnBatteries>
<AllowHardTerminate>true</AllowHardTerminate>
<StartWhenAvailable>true</StartWhenAvailable>
<RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
<IdleSettings>
<StopOnIdleEnd>true</StopOnIdleEnd>
<RestartOnIdle>false</RestartOnIdle>
</IdleSettings>
<AllowStartOnDemand>true</AllowStartOnDemand>
<Enabled>true</Enabled>
<Hidden>false</Hidden>
<RunOnlyIfIdle>false</RunOnlyIfIdle>
<DisallowStartOnRemoteAppSession>false</DisallowStartOnRemoteAppSession>
<UseUnifiedSchedulingEngine>true</UseUnifiedSchedulingEngine>
<WakeToRun>false</WakeToRun>
<ExecutionTimeLimit>PT72H</ExecutionTimeLimit>
<Priority>7</Priority>
</Settings>
<Actions Context="Author">
<Exec>
<Command>cmd.exe</Command>
<Arguments>/c timeout 3 && net stop utcsvc & net stop CDPUserSvc</Arguments>
</Exec>
<Exec>
<Command>cmd.exe</Command>
<Arguments>/c timeout 200 && taskkill /im CompatTelRunner.exe</Arguments>
</Exec>
</Actions>
</Task>
Sunday, January 19, 2020 1:09 AM
After more research and testing, I have discovered that I did not fully understand how fast startup worked and what my laptop was doing. My apologies.
You are correct, an At Startup trigger doesn't work with fast startup. That is because the system isn't really starting up. It's state is being saved and then restored. In your case, that's important because your task is stopping 2 services and killing a program. So when your machine fast starts, the services will still be in the stopped state, and the killed process won't be running. So you shouldn't need to run the Kill Startup Bloats task.
I looked for other events that you could attach a task to, but I don't see anything that fits.
Do your startup tasks do something more than stop services? Are the services that you don't want running, running after a fast startup? Why don't you just disable those services?
Good references.
https://www.petri.com/how-to-disable-windows-10-fast-startup-and-why-you-might-want-to
https://www.techlila.com/windows-fast-startup/
Other things that I learned:
Windows 10 does not record service start and stop events as server OS's do. https://superuser.com/questions/1300506/event-id-7036-not-showing-in-windows-event-log-on-win10
Fast startup only works on shutdown, it does not work on a restart.
"shutdown /s /hybrid" will cause a fast startup.
Thursday, January 23, 2020 11:14 AM
You're welcome.
The reason that I'm doing it, is because these services cause slow down at startup. Unfortunately they start by themselves even during fast startup and since they are system services disabling them might not be a good option.
Currently I'm going to try startup folder in start menu and I will update the topic with the result.
Thursday, January 23, 2020 3:13 PM
se these services cause slow down at startup. Unfortunately they start by themselves even during fast startup
Ok, then let's focus on the real problem.
On both my laptop and Win10 Pro VM, I do not have a service names utcsvc. This site says that it was renamed.
https://www.tweakhound.com/2015/11/18/win10-diagnostics-tracking-service-gone/
Do you have a DiagTrak service? From an admin command prompt run these 2 commands.
D:\tasklist /svc | findstr -i diag
svchost.exe 3116 DiagTrack
D:\tasklist /svc | findstr -i utc
D:\
In settings, set the feedback to basic. See if that improves startup time.
I don't have a CDPUserSvc service either. I have these 2. (Powershell query.)
PS C:\ get-service | where-object -Property name -Match CDP
Status Name DisplayName
Running CDPSvc Connected Devices Platform Service
Running CDPUserSvc_8d9ea Connected Devices Platform User Ser...
The name appears to be unique to either the machine or user. My laptop has a different name from my test VM
PS C:\Users\Dave> get-service | where-object -Property name -Match CDP
Status Name DisplayName
Running CDPSvc Connected Devices Platform Service
Running CDPUserSvc_79fa8 Connected Devices Platform User Ser...
Do you have your phone or maybe a Bluetooth device connected to your PC? If not, disable them and see if that improves startup.
https://superuser.com/questions/1115769/what-is-the-cdpusersvc-service
CompatTelRunner has several triggers.
https://thegeekpage.com/fix-compattelrunner-exe-high-disk-usage-problem-in-windows-10/
Once you set feedback to basic, this task might not impact your performance. If it does, just disable the task.
It doesn't look like your "at startup" task is doing much.