[SOLVED] Task Scheduler: Remote Computer Not Found AGAIN

Anonymous
2020-12-08T13:45:24+00:00

Updating to 2004 left me with broken task scheduler. I was able somehow to get it back by updating to 20H2 and running the last (after dozen of times before updating) sfc /scannow by miracle. I had no idea what fixed it but hey it was working so ok. NOW all of a sudden task scheduler is givin the SAME ERROR as before, AGAIN. It's unbelievable.

The last thing my PC has done that I can associate to this problem is a quality update for 20H2. I can't find absolutely nothing on the internet. I have performed all the scannow and DISM stuff many times now. No issues have been found. I have also used a restore point previous the last couple windows updates but it didn't work.

Initially, by trying to start the "schedule" service it reported the "1067: the process terminated unexpectedly" error, so the service won't start. Now the service starts but when openin task scheduler the "remote computer not found" message appears, and task scheduler won't be able to read anything from my PC. (The remote computer of course is the local one).

Startup for the "schedule" service is set to automatic and has never been changed.

Task scheduler is inaccessible even through elevated CMD, as typing "schtasks" or "schtasks /query" do both result in "wrong network address".

This is RIDICULOUS. I really hope Microsoft can do something about this and stop messing up with my PC.

[SOLUTION] Recap: my Task Scheduler service wouldn't automatically start even though the service startup was set to automatic both in Services and Registry. If I tried manually starting it I would get either errors (see above) or fake starts (the service resulted as running but would not be picked up as such by e.g. Disk Defragmentation Utility).

While a commonly proposed solution was adding a "start" key in the registry to set the automatic service startup [value: 2] (in my case it was already present), I edited the value to 3 [manual startup] (since the option to change the startup behaviour is greyed out in Services). So now my Task Scheduler service is set to manual startup and it starts up at boot and everything related to it works as intended (at least for now).

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes

13 answers

Sort by: Most helpful
  1. Anonymous
    2020-12-08T14:05:25+00:00

    Hello fra.carol, welcome to the Microsoft community, my name is Luiz Cruz, an independent consultant and I would be happy to help you.

    To activate the task scheduler, I suggest you use the steps below:

    1. Click on the Start Menu and in the Search field type “CMD”;
    2. Right-click on the Command Prompt item;
    3. Then click Run as Administrator;
    4. At the Command Prompt, type the commands listed below and press Enter after each line:

    Net start Schedule

    Reg add "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Schedule" /v Start /t REG_DWORD /D 2 /f

    1. Restart the system.

    Hope this helps. If it was resolved, please click Yes to the question. Did that solve your problem? Because other people may be having the same difficulty and so you can help them.

    If the error still occurs, feel free to post again. We will be ready to help!

    11 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2020-12-08T15:10:35+00:00

    I tried to perform (again) the actions you suggested but unfortunately the result is the same. I was able to get the service running but the remote computer not found error is still there.

    I wonder if there is some sort of way to reset task scheduler to default, at least for the microsoft stuff; I don't really know if it would matter though.

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-12-08T14:26:18+00:00

    Hi, thank you for your answer. Before proceeding as you suggested, I've noticed that the "start" key is already present and set to "2" in the registry location suggested, so I'd like to ask if it would create any issue.

    Also, the net start command gives "system error 1607".

    Thank you for your time.

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2020-12-08T14:34:02+00:00

    Dear fra.carol,In case I recommend using the Windows 10 repair tools, please follow the steps below.

    Press the Windows + X keys, select Command Prompt (Admin), copy and paste the commands below and press enter after each command.

    Dism /Online /Cleanup-image /RestoreHealth

    Sfc /ScanNow

    Restart the pc.

    I hope this helps, even more!

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2020-12-08T14:35:26+00:00

    Correcting the commands above that left "space".

    Sfc /ScanNow

    Dism /Online /Cleanup-image /RestoreHealth

    See you!

    0 comments No comments