Old tasks in Task Scheduler

When opening up Task Scheduler there are several tasks in the task scheduler
library that seem to be leftovers. For instance:

Name/Status/triggers/Next Run Time/Last Run time ....
{41BCA710-8211-4323-AC4E-614F807A7A1E} / Ready / When the task is created or
modified / -blank- / 4/3/2007 ....

Each of the tasks triggers C:\Windows\system32\pcalua.exe with different
parameters (eg. -a E:\install.exe -d E:\ )

First glance is that these are some type of attempt to invoke some type of
compatibility activity (pcalua is Program Compatibility assistant from MS).

Question of the moment is what are the consequences of removing these
entries (I have 8 of them) ?

Thanks,
Michael

Hi Michael,

I just noticed several of these today as well.

Havn't found an answer yet (havn't looked too deep), but for now I just set
mine to "Disabled" to see what happens. Mine point to pcalua.exe + a couple
different installers/uninstallers.

I'm thinking perhaps they are Vista compatability adjustments of some kind?

"Michael" wrote:

> When opening up Task Scheduler there are several tasks in the task scheduler
> library that seem to be leftovers. For instance:
>
> Name/Status/triggers/Next Run Time/Last Run time ....
> {41BCA710-8211-4323-AC4E-614F807A7A1E} / Ready / When the task is created or
> modified / -blank- / 4/3/2007 ....
>
> Each of the tasks triggers C:\Windows\system32\pcalua.exe with different
> parameters (eg. -a E:\install.exe -d E:\ )
>
> First glance is that these are some type of attempt to invoke some type of
> compatibility activity (pcalua is Program Compatibility assistant from MS).
>
> Question of the moment is what are the consequences of removing these
> entries (I have 8 of them) ?
>
> Thanks,
> Michael
>
>

I removed them,
No effects (adverse or otherwise) noted.

Michael

"techie007" <techie007@discussions.microsoft.com> wrote in message
news:F10FFAD0-EECD-4280-8C1C-F2CC69FB3AB5@microsoft.com...
> Hi Michael,
>
> I just noticed several of these today as well.
>
> Havn't found an answer yet (havn't looked too deep), but for now I just
> set
> mine to "Disabled" to see what happens. Mine point to pcalua.exe + a
> couple
> different installers/uninstallers.
>
> I'm thinking perhaps they are Vista compatability adjustments of some
> kind?
>
> "Michael" wrote:
>
>> When opening up Task Scheduler there are several tasks in the task
>> scheduler
>> library that seem to be leftovers. For instance:
>>
>> Name/Status/triggers/Next Run Time/Last Run time ....
>> {41BCA710-8211-4323-AC4E-614F807A7A1E} / Ready / When the task is created
>> or
>> modified / -blank- / 4/3/2007 ....
>>
>> Each of the tasks triggers C:\Windows\system32\pcalua.exe with different
>> parameters (eg. -a E:\install.exe -d E:\ )
>>
>> First glance is that these are some type of attempt to invoke some type
>> of
>> compatibility activity (pcalua is Program Compatibility assistant from
>> MS).
>>
>> Question of the moment is what are the consequences of removing these
>> entries (I have 8 of them) ?
>>
>> Thanks,
>> Michael
>>
>>

[jamgoffer]

Hi guys,

I got Vista Premium recently and I noticed the same as you. It seems to me though that at least one of those tasks should be left in place (at least for me, the one that launches pcalua.exe -a E:\Setup.exe -d E:\), I dug into this a little bit when I was installing Call of Duty, I believe it was this trigger that allowed Vista to prompt me asking if I wanted install the program in a way that would make the "XP" application compatible with Vista. Basically best I could determine after filitering through several forums online is that if Vista detects a program install that might not be compatable this Task gives you the option of installing it and running it using more of the XP core similar to how Win98 was still able to run a true 16-bit DOS core for some programs. Thought this might help.