task scheduler corruption

The only way I can close the application is to turn it off is via the task manager, if I click ok the same error continutes to pop up until I force the application to close using the task manager.

web_tracker--Perhaps of help
http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/disk-defragmenter-displays-disk-defragmenter-was/0e061b8f-2b66-e011-8dfc-68b599b31bf5

http://www.vistax64.com/vista-general/154369-task-scheduler-corrupt.html

one way is to go into the task scheduler (adminsitrative tools / task scheduler)
task scheduler library /microsoft /Defrag and delete it

you can add it back by.. going into defrag and making a new task or importing this file I provide ScheduledDefrag.xml

<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.3" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
  <RegistrationInfo>
    <Source>Microsoft Corporation</Source>
    <Author>Microsoft Corporation</Author>
    <Description>This task defragments the computers hard disk drives.</Description>
    <URI>Microsoft\Windows\Defrag\ScheduledDefrag</URI>
  </RegistrationInfo>
  <Triggers>
    <CalendarTrigger id="DefragWeeklyTrigger">
      <StartBoundary>2011-12-16T01:00:00</StartBoundary>
      <Enabled>true</Enabled>
      <ScheduleByWeek>
        <DaysOfWeek>
          <Wednesday />
        </DaysOfWeek>
        <WeeksInterval>1</WeeksInterval>
      </ScheduleByWeek>
    </CalendarTrigger>
  </Triggers>
  <Principals>
    <Principal id="LocalSystem">
      <UserId>S-1-5-18</UserId>
      <RunLevel>HighestAvailable</RunLevel>
    </Principal>
  </Principals>
  <Settings>
    <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
    <DisallowStartIfOnBatteries>true</DisallowStartIfOnBatteries>
    <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
    <AllowHardTerminate>true</AllowHardTerminate>
    <StartWhenAvailable>true</StartWhenAvailable>
    <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
    <IdleSettings>
      <Duration>PT3M</Duration>
      <WaitTimeout>P7D</WaitTimeout>
      <StopOnIdleEnd>true</StopOnIdleEnd>
      <RestartOnIdle>true</RestartOnIdle>
    </IdleSettings>
    <AllowStartOnDemand>true</AllowStartOnDemand>
    <Enabled>false</Enabled>
    <Hidden>false</Hidden>
    <RunOnlyIfIdle>true</RunOnlyIfIdle>
    <DisallowStartOnRemoteAppSession>false</DisallowStartOnRemoteAppSession>
    <UseUnifiedSchedulingEngine>true</UseUnifiedSchedulingEngine>
    <WakeToRun>false</WakeToRun>
    <ExecutionTimeLimit>PT72H</ExecutionTimeLimit>
    <Priority>7</Priority>
  </Settings>
  <Actions Context="LocalSystem">
    <Exec>
      <Command>%windir%\system32\defrag.exe</Command>
      <Arguments>-c</Arguments>
    </Exec>
  </Actions>
</Task>

Select allOpen in new window

Apparently I provided wrong information in regard to the error messages that pop up when trying to run the task scheduler. When I try to open the task scheduler the first error that pops up is the one I originally posted. When I click the okay button the next error box is not referring to the scheduledDefrag but Task Microsoft-Windows-DiskDiagnosticResolver, I click on Okay, then the next error pops up indicating another scheduled task is corrupt. There are a total of 59 error boxes that pop up after hitting to okay button then finally the Task scheduler is fine. I beleive the comment mentioned in microsoft article to solve this issue may do the trick by trying to clean up the corrupted task. But I would have to do that for all 59 errors, that would be cumbersome. Especially difficult to do as I would need to first write down each error for each of the corrupted tasks, then go into the registry and locate the task references for each of these corrupted tasks to clean them up. I was hoping that there would be an easier method to clean this up.

I have solved my own issue by doing the following
I  backing up all contents in C:\windows\system32\tasks by renaming the folder.
Then I recreated a new C:\windows\system32\tasks
I then installed the patch http://technet.microsoft.com/en-us/security/bulletin/MS10-092
Then rebooted the computer and opened up my scheduled tasks and it opens without any problems. I will now have to recreate tasks that I want to schedule to run

I've requested that this question be closed as follows:

Accepted answer: 0 points for web_tracker's comment http:/Q_27541647.html#37468951

for the following reason:

I was able to solve my own problem by researching this issue and experimenting on my own.

That should be "very first answer".

There is no place in that article that stated that tells me to  back up all contents in C:\windows\system32\tasks by renaming the folder. Then recreating a new folder called C:\windows\system32\tasks. Then installing the patch. I was unable to solve my problem using the steps listed in the link you provided. I am therefore at liberty to say that your soluntion did not solve my problem. You are just trying to get points that you do not deserve.

web_tracker--
"I was unable to solve my problem using the steps listed in the link you provided."  
If you had said that in the first place, I would not have objected.

I feel my comment assisted him to find the solution
since I suggested this very thing
My comment 19/01/12 04:10 PM, ID: 37459355
It sounds like there is a corrupted task schedual that may have to be removed<< thne explained how to do it
Regards Merete

sorry I just did not want to argue with the person, it is as you say a minor miscommunication error, all I am saying is that his post did not really help me solve my problem. I had to do a lot of digging online in order to find my solution. The steps I have taken to solve my issue were not found in his post. It is sometimes people are a bit too agressive when they are trying to get points.  People delete my comments as I should not have said what I did. You can delete this one as well, as I am only trying to respond to the moderator.

Merete--Good for you.  I agree!!

web_tracker--
In MS 10-092 It says
"Step 2: Create a temporary copy of the corrupted task file

 To do this, follow these steps: 1.Open the following folder in Windows Explorer:
 
%SYSTEMDRIVE%\Windows\System32\Tasks\<Corrupted_Task_Name>

 2. Locate and then copy the task file that corresponds to the corrupted task to a temporary location."
Locating to a temporary location disables the old task schedule.

Disabling is what you did by "back up all contents in C:\windows\system32\tasks by renaming the folder"

Would you like to change your assignment of a solution.?

web_tracker--As you can see by the time stamp our posts have crossed.  
It is not possible to say whether you learned what you did without reference to my or Merete's suggestions .  We did,however, tell what you say was what you did.
I am perfectly happy to not be awarded any points.  But I think you definitely should lose points from your account.  Perhaps give to Merete?

Thankyou jcimarron, I didnt see your comment,
points is not the issue for me really and your welcome to them, I do this for free and the love helping out.
However as EE is about exchanging information the only way members can look up solutions is via accepted/assisted answers.
If you posted that first then are entitled to the accepted.
If mine was not adding anything new then it remains,
as per EE Rules if I may bring one up
how to close a question,
Accept an Expert's comment as the solution If an Expert has given you the solution to your question, or has led you to the solution, select this option.
https://www.experts-exchange.com/help.jsp#hs=29&hi=407
cheers Merete

I mentioned in my post that there were over 59 corrupted tasks listed, so if I did as per instructions Open the folder: %SYSTEMDRIVE%\Windows\System32\Tasks\<Corrupted_Task_Name>
this would have only corrected one error message, ie ScheuleDefrag, I had 59 erors so felt this would be too combursome to go through each of the 59 corrupted tasks and copy and clean up each individual task. The MS instructions tell me after I copy the corrupted task to another folder, then delete the specific task, then make changes in the registry as the next step, then the instructions tell me to copy the task file from the temp folder to create the task. I did not do this deleted the whole tasks folder and created a new folder called Tasks, so everything that was present in the old Task folder was in fact deleted. I did not need to make changes in the registery the ms fix took care of that. There is nothing in the article that said to delete the whole task folder, it asked me to delete specific corrupted tasks in that folder, then to make registry changes. I am sorry the answer given was not what I followed. It may have parially lead me to delete the whole folder, but I can not award full points for something that I did not follow.

The mod can award points if he feels differently

sorry I just did not want to argue with the person, it is as you say a minor miscommunication error, all I am saying is that his post did not really help me solve my problem. I had to do a lot of digging online in order to find my solution. The steps I have taken to solve my issue were not found in his post. It is sometimes people are a bit too agressive when they are trying to get points.  People delete my comments as I should not have said what I did. You can delete this one as well, as I am only trying to respond to the moderator.


This is after admitting that you mistated what you wanted to fix
https://www.experts-exchange.com/questions/27541647/task-scheduler-corruption.html?cid=1572#37468342

in which I wasted my time in preparing my answer for you...

I have solved my own issue by doing the following
I  backing up all contents in C:\windows\system32\tasks by renaming the folder.
Then I recreated a new C:\windows\system32\tasks
I then installed the patch http://technet.microsoft.com/en-us/security/bulletin/MS10-092
as stated in https://www.experts-exchange.com/questions/27541647/task-scheduler-corruption.html?cid=1572#37459355

Then rebooted the computer and opened up my scheduled tasks and it opens without any problems. I will now have to recreate tasks that I want to schedule to run

In fact, the original answer #37459335  the first answer in the Microsoft answer refers to Ms10-92 which has the following
Step 2: Create a temporary copy of the corrupted task file
To do this, follow these steps:
    Open the following folder in Windows Explorer:
    %SYSTEMDRIVE%\Windows\System32\Tasks\<Corrupted_Task_Name>
    Locate and then copy the task file that corresponds to the corrupted task to a temporary location.

in which you state:

There were too many so I just renamed the folder and then created a new folder with the filename Tasks

This DOES the EXACT same thing

I am just closing the question, the answers provided partial solutions to my issue and I did things not really mentioned in the solutions provided that ultimately solved my problem.