Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

SHUTDOWN.EXE Task Schedule Error: Access is Denied

Nov 7, 2010 5:47AM PST

I keep getting a 0x80070005: Access is Denied error when trying to schedule SHUTDOWN.EXE. Other scheduled tasks run fine. I even tried creating it under a different admin account I newly created to no avail. I verified in my security settings that every *.exe in my System32 directory was ENABLED. I dont know where else to check on this. I know others must have tried to schedule shutdown but web searches provide no tips on this specific security error.

Discussion is locked

- Collapse -
Not sure I can help
Nov 7, 2010 8:14PM PST

but when I Googled 0x80070005: Access is Denied I found a number of hits. However it seems these relate to a Windows Server 2003 based system and not to XP.

In case they help you narrow down the problem, below are two links to articles that mention this error and the resolution methods;

Microsoft's "Access is denied" error message when you run a batch job on a Windows Server 2003-based computer, and

Scheduled tasks; 0x80070005 Access is denied if I click "Apply", but fine if "Okay".

I hope they help, or a Google search for the term above gives you more options.

Mark

- Collapse -
Here's what Microsoft writes about this.
Nov 8, 2010 12:44AM PST
- Collapse -
Task Scheduler Problem is Specific to SHUTDOWN.EXE
Nov 8, 2010 9:58AM PST

Proffitt & Flax (a law firm) didn't read my post closely enough. But to further clarify, Im using Win XP Pro (Version 2002) SP3. The SHUTDOWN.EXE that Im running is 19k, CrDt: 8/4/04, Mod: 4/13/08. I have in possession another one 19k, Mod.8/4/04. Im running the former executable under Administrator and yes, I use a password which is required in the scheduler.

But I previously stated that all other Task Scheduler files work fine, meaning its something inherent in SHUTDOWN.EXE and no other programs. Also both replies are for Win 2003 systems and do not refer to the SHUTDOWN.EXE specific problem. The AT command the latter reply refers to was from pre-XP days which was a kernel-version of XP's Task Scheduler that XP auto-migrates the code and then no longer uses, so the information is obsolete and inapplicable. I did try to do the "OK" thing instead of "APPLY" just for the hell of it and it didnt work, same message. I used Yahoo for searching cus Google often gives me too many results and many of those redirect to Ads. Yes, I did start with Microsoft KB Support and got about as far as you guys did.

I did some hunting around in Computer Management and Enabled two Object Security places that refered to "Allow User to Remotely Shutdown Computer" and "Allow Shutdown." Afterwards I rebooted and unsuccessfully retried the scheduled operation.

I also tried setting it up on a different XP machine to no avail. Same message. These two different XP systems are installed and configured on different networks by different people, so it strongly points to a basic issue within XP across the board.

Wherever the problem lies, it appears to be buried deep within XP's settings on more than one different computer.

Have any of you tried to run SHUTDOWN.exe within the Task Scheduler? Try the following in Task Scheduler: shutdown.exe -s -f

Thanks again.

- Collapse -
Footnote: Hotfix only installs on SP1
Nov 8, 2010 10:47AM PST

I thought just for the heck of it to try running the mentioned KB 814761 hotfix. It detected SP3 and said it wouldnt install unless Im on SP1 !!! Those ********!!!

If anyone has the SHUTDOWN.EXE file from that hotfix please email it to me. Thanks.

- Collapse -
I read your first post again.
Nov 8, 2010 11:50PM PST

I think I upset you and apologize. To avoid any further angst I have unsubscribed.
Bob

- Collapse -
Try this ...
Nov 9, 2010 12:20AM PST

Click Start, Run and type Gpedit.msc to bring up the Group Policy editor. In the Local Computer Policy list, expand Computer Configuration, Windows Settings, Security Settings, Local Policies.

Click on "User Rights Assignment" and double click "Access this computer from the network" and then click Add User or Group. Add the the user name or the group name in the Enter the object names to select area.

Click Check Names to verify what you selected and click OK twice to exit.

This will allow you program access in scheduled tasks.

- Collapse -
Shutdown in Scheduler, Microsoft Extractor Not Addressed
Nov 10, 2010 8:12AM PST

Ed you didnt point out how this security setting applies in any way to the issues at hand. Im trying to run Shutdown.exe from the self-same computer. The fact that Shutdown can be run to shutdown a remote computer (network access) is purely coincidental and is not how its being currently executed. I asked if anyone had an extracted copy from either the hotfix or SP2 that matches the attributes of the one that supposed to address the problem. Why my SP3 version didnt work still escapes me. Maybe the SP3 update install hit a bump there. Since Im already on SP3 the MS Extractor refused to install it but WinZip didnt care so I extracted it that way.

It appeared to finally work with HotFix'es SHUTDOWN.EXE, 19KB, CRDT=8/4/04, MDDT=4/13/08, even though it appeared to be the same as my original. To make doubly sure it didnt run a different copy, I specified the directory to run it from (e.g. "C:\WINDOWS\SYSTEM32\SHUTDOWN.EXE -S -F")

BTW, sorry you didnt get my joke Bob, and no, nothing was really directed at you or the other guy and any angst was clearly directed at Microsoft and their installation restrictions.

- Collapse -
I found this worked for me based on the above post
Sep 23, 2012 3:41AM PDT
Edward ODaniel had most of it right for my case of the dreaded 0x80070005 access error but I found my modification worked for me:
Windows XP forum: SHUTDOWN.EXE Task Schedule Error: Access is Denied
Click Start, Run and type Gpedit.msc to bring up the Group Policy editor.
In the Local Computer Policy list, expand Computer Configuration, Windows Settings, Security Settings, Local Policies,
Security Options,
then select "Accounts: Limit local account use of blank passwords to console logon only"
Select "Disable" and Apply.
This will now allow you program access when you add any new programs in scheduled tasks.

Here is my disclaimer; Although this worked for me on my 2, non pass-worded, XP pro computers I am not responsible for its effectiveness or security on anyone else's systems. The setting appeared to me to be innocuous to disable for my use. BUT I think I solved it!
- Collapse -
Maybe An Answer
Dec 8, 2010 11:01PM PST

I had this problem. Try changing the Users Account Type to Limited then back to Administrator. It worked for me.