Windows 10 task scheduler stopped working

Hello, I have a weird problem on a Windows 10 machine. Task scheduler just won't work anymore, so I can't schedule backups.
The service is correctly set to automatic and it starts at boot but it shuts down immediately with no error whatsoever. I also enabled all Task Scheduler event logging but I don't get any errors, it just says that the service is shutting down.

When I try to open the scheduler, I get a "Remote computer not found" error. Since this error is fairly common, I tried tons and tons of suggestions found on forums (check file integrity, delete a registry key which actually wasn't there and more). I also tried out a third party tool made especially for fixing tasks, but it doesn't work (although for each task it says there is an error, "invalid network address", but it can't fix them).

I also tried the usual malware and rootkit scans, with no luck (meaning, there's nothing of note).

So I'm at a loss, I'd like to avoid a complete restore since it would take too long. I was wondering if any of you guys has some insight on this. Thanks.
Daniele BrunengoIT Consultant, Web DesignerAsked:
Who is Participating?
 
JohnConnect With a Mentor Business Consultant (Owner)Commented:
Open cmd.exe with Run as Administrator and run DISM.

dism.exe /online /cleanup-image /restorehealth  .  Restart and test.

If DISM does not resolve the issue, you can run a Windows 10 Repair Install and keep everything.

https://www.microsoft.com/en-us/software-download/windows10

Windows 10 is running, so click on the Download button (not Upgrade Button, select Open (Run) but NOT Save. Allow the program to run. Allow drivers to update. Then select Keep Everything.
0
 
Daniele BrunengoIT Consultant, Web DesignerAuthor Commented:
DISM didn't work. Will the repair install keep installed software too?
0
 
JohnBusiness Consultant (Owner)Commented:
Yes, the default is Keep Everything and if that is selected, all will be kept
0
 
Daniele BrunengoIT Consultant, Web DesignerAuthor Commented:
The latest Windows update 1803 fixed the problem. Guess it was like a repair install after all, gladly I waited.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.