For anyone who find themselves in the same situation: I had Scm folder deleted from C:\Windows\System32\Logfiles I recreated the folder and restarted the machine and it solved the issue. Microsoft sure has a funny way of doing things. A folder meant to store the useless logs would break the entire Task Scheduler module 0_o ?|? Who would have thought.