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
    2016-09-14T20:41:09+00:00

    This worked great for me.

    https://gallery.technet.microsoft.com/scriptcenter/Repair-CorruptedTampered-c8d2e975

    Repair "Corrupted/Tampered With" Scheduled Tasks.

    This script properly removes and re-adds scheduled tasks on a computer when those tasks are reported as "The task image is corrupt or has been tampered with". It does require a little bit of up front configuration by the administrator of that computer.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-04-05T19:52:29+00:00

    Thank you  Mouneshwar R google brought me to you and your slolution was very helpful.. Thank you once again

    Was this answer helpful?

    0 comments No comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more