Defragment as task, wake computer from sleep.
Posted by admin on Nov 12th, 2006
Having some trouble with my defragment task. I set up a scheduled task to wake the computer and run defragment. The computer at the appropriate time starts, but shuts off approximately 2 minutes later for a minute, then starts up again only to keep repeating this until I actually logon. I have the timer for the power profile under the main user to sleep after 2 hours, but this keeps happening. Sleep otherwise works properly. Does anyone know how to get this to run without this shutdown/startup happening?
Nov 14th, 2006 at 05:42 pm
Sounds like a question for the Task Scheduler team have you had this issue with any other tasks? Is defrag the only one you're trying to run from sleep? "Timdog"
Nov 18th, 2006 at 12:58 pm
On Mar 7, 6:10 pm, "Victoria House [MSFT]" wrote: I have this same issue. Any task I schedule with the "wake up the computer" option set (as well as "run whether user is logged on or not" and "run with highest privileges") will wake the PC and the task will start, but the system falls back to sleep again 60 seconds later, even as the task is still running (ignoring my preferences in this regard in my power profile, to not go back to sleep for an hour). I have had it fall asleep in the middle of a virus scan, imaging my C drive, defragging my C drive, etc. No matter what the task, it wakes up, starts running but falls asleep again in 60 seconds, I am involved in a running conversation with MS support on this (Case: SRX1030236402). I've made it past level 1, but still no progress. bc
Nov 21st, 2006 at 03:32 am
In a strange way I'm glad to see I'm not the only one having this problem. Does anyone know if the login screen for vista has it's own power profile? This might explain it because if I resume from sleep, but don't login, my computer will power down after a couple minutes. If there is, how do we change its settings?I hope someone will figure this out. This is currently the only task I run waking the computer from sleep. But I do have more I would like to start running.Thanks in advance,Timdog "bob.cronin@gmail.com" wrote:
Nov 23rd, 2006 at 04:23 pm
The .Default user is the user when there isn't one. This is NOT the same as Default user but <Dot>Default. You will find her settings here in the registry HKEY_USERS\.DEFAULT"Timdog"
Nov 24th, 2006 at 03:51 pm
you can check the EVENT logs under Task Scheduler to see what is running at that time.mikeyhsd@sport.rr.commikeyhsd@sport.rr.com "Timdog" In a strange way I'm glad to see I'm not the only one having this problem. Does anyone know if the login screen for vista has it's own power profile? This might explain it because if I resume from sleep, but don't login, my computer will power down after a couple minutes. If there is, how do we change its settings? I hope someone will figure this out. This is currently the only task I run waking the computer from sleep. But I do have more I would like to start running. Thanks in advance, Timdog "bob.cronin@gmail.com" wrote:
Nov 26th, 2006 at 12:24 pm
On Mar 8, 3:49 pm, Timdog wrote: Still no progress with MS support, but your idea about default user suggested it might be interesting to try exporting the PowerCfg section of the HKEY_CURRENT_USER\Control Panel registry tree, edit it to change the path to HKEY_USERS\.DEFAULT\Control Panel and then import it. I've done that now, and whereas HKEY_USERS\.DEFAULT did not formerly have a PowerCfg section in the Control Panel tree, now it does (and it is a duplicate of whats configured for my primary logon). It will be interesting to see if this had any effect tomorrow morning when my imaging task kicks off. bc
Nov 28th, 2006 at 10:14 pm
On Mar 20, 11:02 am, "bc" wrote: Ok, MS support tells me:I can understand the inconvenience that this issue causes. Actually, this issue can also be reproduced on test machines at our technical support site. Therefore, we can confirm that the issue is not system specific but is related to the programs and codes. I have immediately forwarded this issue to the relevant team for further investigation. Please be assured that our developers will look into this issue and find a permanent solution. Your patience and understanding on this is greatly appreciated.So there is some hope for a fix eventually. bc