TaskBackgroundConfigSurveyor:The task image is damaged

[julio99]

TaskBackgroundConfigSurveyor:The task is damaged or has been tampered with. That is the error I get when I open Task Scheduler. It just makes the error sound and it pops up I have no idea why and that is why I'm here. If it's a task I can't find it. About a week ago I did an Acronis Backup to a month earlier and the error was gone. A couple of days later and it's back. The path for this is System32/Tasks/Microsoft/Windows/PerfTrack/BackgroundConfigSurveyor. I was just about ready to delete the folder but I thought I better check wit you all first and see if I can get some help at getting this error fixed.
This error happens when I open the Task Scheduler. I'm running Windows 7 HP on an Acer laptop. 4GB RAM/32Bit

 

[zigzag3143]

TaskBackgroundConfigSurveyor:The task is damaged or has been tampered with. That is the error I get when I open Task Scheduler. It just makes the error sound and it pops up I have no idea why and that is why I'm here. If it's a task I can't find it. About a week ago I did an Acronis Backup to a month earlier and the error was gone. A couple of days later and it's back. The path for this is System32/Tasks/Microsoft/Windows/PerfTrack/BackgroundConfigSurveyor. I was just about ready to delete the folder but I thought I better check wit you all first and see if I can get some help at getting this error fixed.
This error happens when I open the Task Scheduler. I'm running Windows 7 HP on an Acer laptop. 4GB RAM/32Bit

You can of course keep restoing from the acronis backup but at some point if you want to repair it you are going to have to do a repair install at least.

Have y ou tried a system file check

(type cmd in search>right click and run as admin>sfc /scannow)

Let us know if you need help

Ken

 

[julio99]

I just did a chkdsk with computer tools and nothing there. I tried a repair install and it never goes through all the way. I follow all the instructions with the upgrade disk and it goes just about to the end and then just gives me back my old setup. Why won't that go through? You can't just delete that file ? It's that important. I'll try the sfc, but I'll bet that don't help. Let me know if you know anything else?

I did the sfc /scannow and it came up with solid integrity. I'm totally baffled