Windows 10: In Windows 10 v1709 how do I get Task Scheduler Credentials to work?

In Windows 10 v 1709 Fall Creators Update, I am tracking down the cause of hibernate breaking randomly, waking-up my Dell computers. All Internet remedies have failed so far. Taking ownership of Reboot and adapting Permissions and even deleting Reboot in Update Orchestrator fails to prevent random wake-up. A basic PC box with just a power cable and monitor attached wakes. However, there is remaining, just one option: a check-box in Task Scheduler > Reboot, that is intended to wake the computer. I need to remove the tick in that box. I can't get past the Task Scheduler, credentials check for Username S-1-5-18 and password to do that.

I need an expert on this credentials problem. It may be that it just isn't possible to remove the tick that check box. Permissions and credentials foxes me a bit. I am not certain if I should use elevated command prompt or operate inside my Administrator Account (net use administrator /active:yes) I couldn't find a tutorial and I don't fully understand the Credentials Manager but I believe this is a fruitful area to investigate.



Thank you... from

:)

 

Windows 10 automatic upgrade via task sheduler

Thanks for replying!

Okey, if i can not use task scheduler to create the thing myself, then can i somehow replicate how the "get windows 10" does it? If it can add it to task scheduler as GWX with multiple tasks then can i do it aswell?

 

Windows Defender auto scan frequency

My task scheduler is corrupt or missing libraries. When I bring it up I get an overwhelming amount of errors just to find out it doesn't work. How do I fix the task scheduler?? Windows 10 professional

 

Try this to see if it helps:
No permission to disable a task in Task Scheduler - Windows 10 Forums

 

Thank you topgundcp, from

Just got in from a bike ride. I will have a go at your link tonight and will get back to you. I saw your link on TenForums the other day and I have just figured it out. I am also wondering if this access point is blocked by MS. Logically it would be sensible to do that because updates were user driven and voluntary from Hibernate (probably up to pre-1703) although Microsoft driven and mandatory from a Shutdown and Start-up; driving users into Shutdown would solve the immediate protection issues, with a minor inconvenience. I can run ExecIT on Windows 10 v1709 x64 and 32 bit.

Back in a while... it will be good to tease-put the origins of this hibernate waking-up annoyance.
Gratefully from .

 

Hi there topgundcp, (from ),

I've run ExecTI.....

Now in the following path, Reboot doesn't display (The folder UpdateOrchestrator appears empty), and Reboot has no file extension and it isn't visible to ExecTI possibly because it isn't an (.exe)...

Path: Local Disk > Windows > System32 > Tasks > Microsoft > Windows > UpdateOrchestrator (No Reboot listed so click Browse)...Use Notepad to show the contents

So - I have run ExecTI. I've copy-pasted the Notepad that opened. There is a Wake command. I just don't know how to proceed. I would guess there is a developer's modification for this command which removes the tick in the checkbox for: "Wake the computer to run this task".

I have a Restore Point set which covers the Local Machine hive and a System Image completed, so I am OK as far as the protection of my OS and Data is concerned; just that I am at my limit.

Any thoughts on it topgundcp ? I am comfortable with the work, although I am off my map edge... I would like to drill-down into the Reboot > Wake issue a bit more.

The Notepad script follows to conclude this Quick Reply .... with respect from:





END

 

Hi,
Not really sure why but here's my screen running with execti and it allows to modify this task. Boot is a schedule task not an executable. By any chance did you somehow delete this task ?

 

Hi there topgundcp (from ),

You have the same in Task Scheduler! I did delete the Reboot file. Initially I cautiously renamed it Reboot.bak and then I was woken up by the computer waking. So - I deleted it. I was woken up again. That was when I headed off to Task Scheduler and was stuck at the username and password request from the credentials manager. Thou' shalt not pass.

I've been searching up-and-down in the registry over several days and I just can't find Reboot. Searches with "Find" and manual searches in the explorer just doesn't locate it. Is it a decoy? Red Herring? A rose by any other name?

<WakeToRun>true<\WakeToRun>

What if...

<WakeToRun>false<\WakeToRun>

I did Basic and Algol60 at college in the 60s so I am flying blind.

It's a tease isn't it topgundcp...? From

 

Hi topgundcp (from ),

I'm about to do an overnight run of Reboot from Task Scheduler with ExecTI. The "Wake the computer to run this task" checkbox is unchecked and all looks OK to Go!

From where did you get the file name: mmc.exe /s taskschd.msc ?

I am looking forwards to a night's sleep. It may be the computer's insomnia will be cured; I bl***y well hope mine will be...

See you in the morning with the result.

 

Reboot parameters are not the same here: all of them are disabled. Does not wake-up.

Reboot is available in Ccleaner Pro: Tools/Startup/Scheduled Tasks/Advanced mode/Reboot/Access is denied

In 1709, it is not possible to disable it no more. If you copy the location, regedit returns no result. Seems to be hidden now.l

 

Hello MikeMecanic (From )

MikeMecanic...thank you so much...I guessed as much.

I left a post on Superuser asking if there were hidden files (not conventional Menu > View > Hidden) I mean like malware; files that were known about at Microsoft and are intended to break into a customer's computer. I couldn't locate a Reboot in regedit either.

Hello topgundcp (From )

The results of the over-night run: the Dell Optiplex 755 woke at random at 06:27 this morning (Snippet below to evidence - check box remained empty).




Below is the Event viewer log of the start-up:





topgundcp...I will have a look at that script and see if I can test false instead of true as a What If trial. Shot-in-the-dark.... At least Shutdown is available still; until someone breaks into Microsoft and then we are sunk.
A quick PS Edit to this post:

Under ExecTI: I've made some settings changes to Task Scheduler to see if it will reconfigure:
Set Reboot to Enable Ready
Change User to Administrators
Change to Run when user is logged on.
Configure to Windows 10
The check box for Wake the computer to run this task is unchecked.

Under ExecTI: In Local Disk > Windows > System32 > Tasks > Microsoft > Windows > Update Orchestrator > Reboot
Ensure that: <WakeToRun>true</WakeToRun is changed to: <WakeToRun>false</WakeToRun>

It is confirmed by a check and will be hibernated today. See what incubates over the 24 hours.

Any thoughts?

 

Hi MikeMecanic and topgundcp,

You may not be surprised by the outcome of last night's hibernation test. The computer (Dell Optiplex 755, running Windows 10 v 1709) woke randomly at 02:45 in the morning.

I will try a few more ideas out during the week. The problem must surely be in the OS and I can't explain it; there is one place I haven't looked: Task Scheduler > Windows Update > Scheduled Start has a WakeToRun command. I will change permissions to have a look. There may be hidden places and malware we don't know about still. A malware search was done with Avira, Malwarebytes, Windows Defender and AdwCleaner. Note: a totally Clean installation completed with Windows updates but without 3rd Party downloads had the problem.

Question: Is there anyone running Windows 10 v 1709 who has hibernate holding and not waking up? I've been told of an Acer Aspire XC-705 but it isn't verified.

 

Does powercfg not tell you the reason for waking?

You seem to have assumed it is this one task scheduler entry but I can't see why.

For me \Microsoft\Windows\UpdateOrchestrator\Reboot is a disabled task (which I can toggle on and off the wake computer box incidentally). It is triggered when I reboot to do whatever it does. That is it runs when I reboot - it doesn't trigger the reboot.

I don't see why you think it wakes the computer. Not saying it doesn't but I can't understand why you think it does.

Just for interest in case it is useful, S-1-5-18 is SECURITY_LOCAL_SYSTEM_RID (A special account used by the operating system) - see Well-known SIDs (Windows) It doesn't have a password.

The C:\Windows\System32\Tasks\Microsoft\Windows\UpdateOrchestrator\Reboot object (on my PC) is owned by Administrators group with LOCAL SERVICE and Administrators having Read/Execute authority and SYSTEM having full control. You should be able to (and I can) change it if you are part of the Administrators group. You don't need the built in Administrator.

What does powercfg /lastwake show anyway? Anything interesting?

 

Hi Ix07

Reboot:
Reply for "why you think it wakes the computer": I couldn't find anything else to check that I hadn't already checked. That is why I asked TenForums. I reasoned that Reboot was just a settings log (.txt) summary. I've been looking for check-boxes that have WakeToRun functionality such as mouse, keyboard and network adapter. Task Scheduler have a few.

One of my basic computer boxes with just a power cable and monitor attached will wake from hibernate randomly; I have three Dell computers doing it. I've placed two into Shutdown. I couldn't find a virus. The older Dell GX620 with a clean installation of Windows 10 v 1709 from Microsoft's web site completed with Windows Updates and no 3rd Party software wakes randomly. I am working on a Dell 755 which is newer.

powercfg /lastwake
Nothing indicated... I've done wake timers and wake-armed.

Shutdown
Performs perfectly.
Hibernate
Wakes sporadically.

Temporary conclusion: My computers are not compatible with Windows 10 V 1709.

Puzzled.
Edit Post script: I have a raw Windows 10 v 1709 without updates that I can run. My W10 v1709 with Updates wakes. I can see if it is an update. The Dell GX620 (Pentium 4) with most tasks disabled is blisteringly fast after the reduction (similar to the Dual Core) but wakes. I used Glary Utilities 5 to strip them out and also used the link below and did it manually:

See link:

Scheduled Tasks - Eliminating Most is a Good Thing - Windows 10 - MSFN
Scheduled Tasks - Eliminating Most is a Good Thing - Windows 10 - MSFN

It started with V1703..

 

From ... Work in progress:

I've been stripping-out registry items; you will have to adjust permissions but it is easy from the registry in comparison to Task Scheduler.:
LOCAL_MACHINE\SYSTEM\Control Set 001\Control\Ubpm

This is the location of CriticalTask_UsoReboot
It also locates other suspect items such as maintenance tasks. So far I've Deleted all the UpdateOrchestrator items and I am working through CriticalMaintenance items.

I do a Restart each sweep-out...

Outcome: The computer still wakes randomly. LOCAL_MACHINE is protected by Restore Points OK but take a System Image also if you care to participate in the trash-and-burn of Microsoft products.
Temporary end...