S
sheppardwk
I just recently purchased a Dimension 8400 with Windows XP
Service Pack 2. McAfee Security Center was previously
installed. While looking through the Windows Directory
(sorted by date), I noticed a file named SchedLgU (text
file). It contains the following: "McAfee.com Update
Check (user currently logged on) .job" (mcupdate.exex)
ERROR. The attempt to retrieve account information for
the specified task failed; therefore, the task did not
run. Either an error occurred, or no account information
existed for the task. The specific error is 0x8004130f:
No account information could be found in the Task
Scheduler security database for the task indicated.
I then went to Control Panel, Performance and clicke on
Scheduled Tasks. I found McAfee update.com entries for
all four (4) of the users of this computer. Each task was
scheduled for EVERY 5 minutes for 24 hours a day. A
little excessive? I then deleted all scheduled tasks and
went to the McAfee Security Center - Updates - and checked
Disable Security Updates. However, whenever a family
member logs onto the computer, a new McAfee update.com
scheduled task occurs with the above configuration of 5
minutes for a 24-hour period. If I change it to reflect a
Weekly update, when you log back on, it creates yet
another with the default of 5 minutes/24 hours. I will
manually update McAfee, I don't need to be reminded by a
program.
I have unsuccessfully attempted to communicate with
McAfee's Live Technician, who seems to follow a "script"
and obviously not reading what information I provide.
They have recommended uninstalling all of McAfee - seems
as though that is their "default" solution for everything -
http://tools.mcafeehelp.com/doc.php?
siteid=1&docid=71541 They also suggested
contacting Microsoft for a hotfix:
http://tools.mcafeehelp.com/doc.php?
siteid=1&docid=70557&support=ts Microsoft repsonded that
there is no such hotfix.
Any thoughts by anyone? I have thought about using
MSCONFIG, and unchecking the Mcupdate.exe under the
Startup list to see if that might help. However, I
thought I would see if anyone else may have experienced
this occurrence prior to doing that.
Thanks.
Service Pack 2. McAfee Security Center was previously
installed. While looking through the Windows Directory
(sorted by date), I noticed a file named SchedLgU (text
file). It contains the following: "McAfee.com Update
Check (user currently logged on) .job" (mcupdate.exex)
ERROR. The attempt to retrieve account information for
the specified task failed; therefore, the task did not
run. Either an error occurred, or no account information
existed for the task. The specific error is 0x8004130f:
No account information could be found in the Task
Scheduler security database for the task indicated.
I then went to Control Panel, Performance and clicke on
Scheduled Tasks. I found McAfee update.com entries for
all four (4) of the users of this computer. Each task was
scheduled for EVERY 5 minutes for 24 hours a day. A
little excessive? I then deleted all scheduled tasks and
went to the McAfee Security Center - Updates - and checked
Disable Security Updates. However, whenever a family
member logs onto the computer, a new McAfee update.com
scheduled task occurs with the above configuration of 5
minutes for a 24-hour period. If I change it to reflect a
Weekly update, when you log back on, it creates yet
another with the default of 5 minutes/24 hours. I will
manually update McAfee, I don't need to be reminded by a
program.
I have unsuccessfully attempted to communicate with
McAfee's Live Technician, who seems to follow a "script"
and obviously not reading what information I provide.
They have recommended uninstalling all of McAfee - seems
as though that is their "default" solution for everything -
http://tools.mcafeehelp.com/doc.php?
siteid=1&docid=71541 They also suggested
contacting Microsoft for a hotfix:
http://tools.mcafeehelp.com/doc.php?
siteid=1&docid=70557&support=ts Microsoft repsonded that
there is no such hotfix.
Any thoughts by anyone? I have thought about using
MSCONFIG, and unchecking the Mcupdate.exe under the
Startup list to see if that might help. However, I
thought I would see if anyone else may have experienced
this occurrence prior to doing that.
Thanks.