We all know that Task Scheduler is the in-built Windows utility that helps us to run specified tasks at the scheduled sessions. Recently, we tried to schedule a task with this tool, but unfortunately, we were not able to do so. The task was to run an executable file at some scheduled time but Task Manager refused to accept this task with Access is denied message. Additionally, an error code 0x80070005 also resulted.
After receiving this error code and investigating it a bit, we found that we need to provide the highest privileges to run that task. We applied that, but that did not bring any changes in the situation. Next, we tried to configure the task for the available ranges of various editions, but with no luck.
At last, we realized that we needed to go for a registry manipulation that worked, in order to solve this problem. So if you’re also facing this error, here is how you can suppress it:
Task Scheduler Access is denied, Error code 0x80070005 in Windows 11/10
Making mistakes while editing the Windows Registry could affect your system adversely. So be careful while editing registry entries and create a System Restore point before proceeding.
1. Press Windows Key + R combination, type put regedit in Run dialog box and hit Enter to open the Registry Editor.
2. In the left pane of Registry Editor, navigate here:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
3. Moving on, in the right pane of the above-mentioned registry location, look for the registry DWORD (REG_DWORD) named EnableLinkedConnections and double click on it to get this:
4. Finally, in the above-shown Edit DWORD Value box, put the Value data as 1 and make sure that Base is Hexadecimal. Click OK and close Registry Editor now, reboot the machine.
After restarting the system, try to create a task and it should work fine this time.
Hope this helps, Good luck!
Error 0x80070005 is rather ubiquitous and this code is also displayed in the following scenarios:
What is the root cause though?
^^ When UAC is enabled, network access don’t have highest privileges by default. Registry manipulation assigned highest privileges to network access as well, in addition to task itself :)
Oh ok, ty. This seems like something that should work without needing a registry edit to fix (*hint to Microsoft*) [note to self, bring this up in win 10 feedback app if problem still exsists]