Task Scheduler service is not available. Network condition issue.

I am having the same issue David_882 had after installing the Anniversary Update. Follow the link bellow
http://answers.microsoft.com/en-us/windows/forum/windows_10-performance/anniversary-update-version-1607-build14393-breaks/d034ab52-5d49-4b92-976a-a1355b5a6e6d?page=2&auth=1

"If your task contains a specific network connection as a condition, the task won't run. If you try to start it manually, you'll get an error like this:

"Task Scheduler service is not available. Task Scheduler will attempt to reconnect to it." "

Windows 10 Home (Core).

Version 1607

On my laptop, I disabled some applications at startup in Task Manager and enabled them in Task Scheduler to start only when my device is connected to my home Wi-Fi hotspot. So, in my university, where, usually, I would prefer more battery life than some apps in background, they shouldn't start automatically and consume resources.

This option was very useful before the update.

This happens not only on my laptop (as you can see on the bottom link).

Is there any solution? Are Microsoft going to fix this issue?

P.S. Sorry for my English.

 

Question Info


Last updated June 25, 2019 Views 3,483 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

I am having the same issue David_882 had after installing the Anniversary Update. Follow the link bellow
http://answers.microsoft.com/en-us/windows/forum/windows_10-performance/anniversary-update-version-1607-build14393-breaks/d034ab52-5d49-4b92-976a-a1355b5a6e6d?page=2&auth=1

"If your task contains a specific network connection as a condition, the task won't run. If you try to start it manually, you'll get an error like this:

"Task Scheduler service is not available. Task Scheduler will attempt to reconnect to it." "

Windows 10 Home (Core).

Version 1607

On my laptop, I disabled some applications at startup in Task Manager and enabled them in Task Scheduler to start only when my device is connected to my home Wi-Fi hotspot. So, in my university, where, usually, I would prefer more battery life than some apps in background, they shouldn't start automatically and consume resources.

This option was very useful before the update.

This happens not only on my laptop (as you can see on the bottom link).

Is there any solution? Are Microsoft going to fix this issue?

P.S. Sorry for my English.

Hi Moris,

To assist you better with your concern regarding the error message that you're getting, we suggest you follow the troubleshooting steps provided by Sumit Dhiman2 on this link.

For more information regarding the process, visit this link.

Let us know if you need further help.

Thank you.

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I may test it later, but for now I don't think that's a good idea.
I am not ready to lose my custom fonts, some registry edits and a lot of other settings that Windows is not synchronizing.
There must be another way to fix it. Maybe I would try clean Windows 10 ver.1607 install on another disk partition later, but if it will not work, then there is no reason in using system repair tool.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I may test it later, but for now I don't think that's a good idea.
I am not ready to lose my custom fonts, some registry edits and a lot of other settings that Windows is not synchronizing.
There must be another way to fix it. Maybe I would try clean Windows 10 ver.1607 install on another disk partition later, but if it will not work, then there is no reason in using system repair tool.

Nothing has changed after clean install. The issue still persist. This is a bug, not affected by installed programms or previous system settings. Normal user can't fix it by himself, there must be pushed a fix through Windows Update.

7 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I have had exactly the same since the Anniversay update. The same workaround also works - turning off the network condition. That's fine for a short period of time but Microsoft - you broke it, you fix it.

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Same behavoir on my Notebook.

Before doing an unnessecary new installation i tested with a fresh installed Windows 10 1607 (German Language) in a virtual Machine: Same behavoir as reportet by Moris Shalon.

I already made a report with Feedbackhub (1 week after release of Windows 10 1607) but nothing happened!

@Microsoft: It's not good to break such a basic feature and not fixing it in a short time period!!

I'm a troubleshooter - If i see a trouble: I SHOOT!!!

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Same problem on my laptop. Disabling a feature that used to work just because it no longer works is not a reasonable option.

Please fix ASAP.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Is this still not fixed? I totally agree that the solution to stop using the network condition is not acceptable. Updates are not supposed to break existing functionality...

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Is this still not fixed? I totally agree that the solution to stop using the network condition is not acceptable. Updates are not supposed to break existing functionality...

Yes, it is still not fixed!

I'm a troubleshooter - If i see a trouble: I SHOOT!!!

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I came up with a workaround that sort of accomplishes the original intent of the functionality. The workaround is to, from the Task Schedule task, call an intermediate .bat script which, in turn, calls the target task once the .bat script determines that the system is connected to the desired network.

REM Determine if connected to the network
NETSH WLAN SHOW INTERFACE | FINDSTR /r SSID | FINDSTR /r NetworkName
IF %ERRORLEVEL% == 0 (
    SET "ConnectedToNetwork=True"
) ELSE (
    SET "ConnectedToNetwork=False"
)

REM Run tasks that require a connection to the server
IF %ConnectedToNetwork% == True (
    [Run original task requiring network connection]
)

One advantage to this technique is that you can use it to check for multiple network names without having to create multiple Task Scheduler tasks. For example, if connecting to a wireless network and there are two or more network names that all start with "MyNetwork" such as "MyNetwork" and "MyNetwork 5G", then searching for "MyNetwork" will return an "ERRORLEVEL" of 0 in both cases.

The disadvantage is that we can't tell from the Task Scheduler logs when the target task was run and not run based on the status of the environment.

All in all, Microsoft's testing department needs an interjection of some best practices such as incorporating better and more complete automated regression testing to ensure nothing gets broken when changes are made to the system.

Kevin

14 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Installed the Final Creators Update:

Nothing changed, it still doesn't work!

It's a shame @Microsoft!

@zorvek

Thanks for your workaround!

I'm a troubleshooter - If i see a trouble: I SHOOT!!!

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.