Task image is corrupt or has been tampered with 0x80041321

Anonymous
2011-01-03T00:31:58+00:00

When I try to do a monthly back up it want do it. It gives me Task image is corrupt or has been tampered with 0x80041321. I checked for virures & they come back clean. Can some one please help me out?????????

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2011-10-20T05:14:45+00:00

hi,

i just thought that this solution given by mouneshwar on page 2 of this thread (about three entries down) was too broad based. especially the part where he suggests deleting all the subkeys.

i had a similar issue with my task sched/ corrupted tasks, and the steps you suggested wouldn't have re-created clean tasks to replace the corrupt ones.

BY FAR the most thorough way to solve the issue is using regedit for the tasks, as well as correcting the corrupted tasks in system32 file.

all the steps can be thoroughly described to get the correct solution in the following microsoft support article:

MS10-092, specifically this support page: http://support.microsoft.com/kb/2305420

although it deals with a problem in the task sched caused by a windows update, the actual problem is exactly the same, with the same corrupt task messages.

this is the correct way to solve the issue, it takes a few steps but it's not difficult. just follow it closely, and only fix the tasks which are an issue in your system.

this is the most thorough way to fix this issue.

Was this answer helpful?

0 comments No comments
Answer accepted by question author
Anonymous
2011-02-01T12:23:35+00:00

Hi espbrian,

I would suggest you to try the steps mentioned below.

Steps to re-create Task Scheduler

Registry Disclaimer: The steps mentioned below includes system registry modification. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

How to back up and restore the registry in Windows


a.    Click on Start; in the start search type regedit.exe and press Enter.

If you get a consent prompt, click on Yes.

b.    Browse through the following location.

HKLM\SOFTWARE\Microsoft\Windows NT\Current Version\Schedule key and then delete its subkeys.

c.    Save the changes and then exit out of the registry editor.

Now check if Task Scheduler works.

Hope this information is helpful and let me know if you need any further assistance.

Mouneshwar R – Microsoft Support


Visit our Microsoft Answers Feedback Forum and let us know what you think

Was this answer helpful?

0 comments No comments

154 additional answers

Sort by: Oldest
  1. Anonymous
    2011-06-24T16:17:08+00:00

    when i did this, it increased the # of error messages from two to 52..DONT UNINSTALL the update... now when i tried to download the update, windows can't find it or it isn't in the list of downloadable updates..

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2011-07-01T02:39:31+00:00

    After not being able to backup since 2009, and having had a long and fruitless experience with MS support back then, all it took was deleting the registry sub-keys. Backup is running as I write this.

    Thank you!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2011-07-31T12:09:21+00:00

    Hi,

    In order to fix this, you have to delete the actual task XML  file that contains the task settings, then rerun the Task Scheduler to confirm that the error is gone, then import a non-corrupted version of the task back into the Task Scheduler.

    Most of the work you have to do is to locate the task file in question.

    The task files are located in C:\Windows\System32\Tasks.

    If you try to open the task folder, you might get a UAC prompt asking you for permission to access the folder, this is OK, just click continue to access the folder.

    In my case, the corrupt task was "Microsoft-Windows-DiskDiagnosticDataCollector".

    This was a Microsoft task, therefore I had to go into the C:\Windows\System32\Tasks\Microsoft\Windows\DiskDiagnostic folder to locate the actual task xml file,

    which was named "Microsoft-Windows-DiskDiagnosticDataCollector".

    Once you have located the task file, close the task scheduler, back up the corrupted task file to any location of your choice, then delete it, then open the task scheduler to confirm that the error has gone.

    What you now need to do is to export the non-corrupted  task from another computer or virtual machine, and import it into the task scheduler.

    To export the task in question from another computer, follow these steps.

    1. Open the Task Scheduler, then drill down into the task in question, then right-click on the task and select "Export...".
    2. Save the exported XML file to a location of your choosing, then copy it over to the affected computer.
    3. Once you are back on the affected computer, make sure that the task scheduler is closed, then you need to run the task scheduler as an Administrator.
    4. To run the task scheduler as an Administrator, click Start>All Programs>Accessories>System Tools, then locate "Task Scheduler", right-click it and select "Run as Administrator".
    5. Once the task scheduler is open, drill down to the folder where the task is supposed to be located, right-click on a blank portion of the window, and select "Import Task...".
    6. Once you have imported the task, a "Create task" window will open as shown below, just click OK to it.
    7.  The task should then be successfully imported, you can then close the task scheduler, and the problem should be fully resolved.

    Was this answer helpful?

    0 comments No comments