I notice that for weeks now at the end of the computer use and the Shut-off,
it always has 1 Update. I have gone to the update history and it always for
weeks the same (successful) update
"Security Update for Microsoft XML Core Services 4.0 Service Pack 2
(KB936181)
A security issue has been identified in Microsoft XML Core Services (MSXML)
that could allow an attacker to compromise your Windows-based system and
gain control over it. You can help protect your computer by installing this
update from Microsoft. After you install this item, you may have to restart
your computer. Once you have installed this item, it cannot be removed. "
I must have 40 or 50 downloads of this same service pack.
What gives? How can I stop that?
Step 1: Download Microsoft Windows Installer CleanUp utility
=============================================
1. Visit the following link to download the utility:
http://download.microsoft.com/download/E/9/D/E9D80355-7AB4-45B8-80E8-983A48D5E1BD/msicuu2.exe
2. Save the file to the computer.
3. Install this tool on the computer.
Step 2: Remove MSXML software
=========================
1. Click Start -> (All) Programs -> Windows Installer Clean Up.
2. See if you can find MSXML software. If so, remove them.
3. Restart the computer.
After that, please try to reinstall MSXML 4.0 Service Pack 2 and MSXML 4.0
SP2 Security Update KB925672 and KB927978.
Step 3: Reinstall MSXML 4.0 Service Pack 2
================================
1. Please download MSXML 4.0 Service Pack 2 and the related updates from the
following links and save them to the Desktop.
MSXML 4.0 Service Pack 2
http://download.microsoft.com/download/9/6/5/9657c01e-107f-409c-baac-7d249561629c/msxml.msi
MSXML 4.0 SP2 Security Update (KB936181)
2. When the File Download window appears, please click the Save button, and
follow the directions to save them to the Desktop.
3. After downloading the MSXML 4.0 Service Pack 2 setup file and its updates
on to the Desktop, please double-click the files to manually install them one
by one.
--
====================================
TaurArian [MVP] 2005-2008 - Australia
====================================
How to ask a question: http://support.microsoft.com/kb/555375
http://taurarian.mvps.org/index.htm
Emails will not be acknowledged - please post to the newsgroup so all may benefit.
Computer Maintenance: Acronis / Diskeeper / Paragon
"Ritter 197" <Ritt...@comcast.net> wrote in message
news:elrGQ%23oaI...@TK2MSFTNGP06.phx.gbl...
I will print out what you said and try it.
Do you have an idea WHY it downloaded again and again the same updates,
always successfully?
"TaurArian" <taurarian...@gmail.com> wrote in message
news:#jxJ0kpa...@TK2MSFTNGP04.phx.gbl...
--
====================================
TaurArian [MVP] 2005-2008 - Australia
====================================
How to ask a question: http://support.microsoft.com/kb/555375
http://taurarian.mvps.org/index.htm
Emails will not be acknowledged - please post to the newsgroup so all may benefit.
Computer Maintenance: Acronis / Diskeeper / Paragon / Raxco
"Ritter 197" <Ritt...@comcast.net> wrote in message
news:ea%23kurpa...@TK2MSFTNGP05.phx.gbl...
What you should consider then is what is happening during the boot.
E.g. probably there are modules which need to be renamed or copied then.
So then if you have something which is interfering (e.g. preventing
or later undoing) that step you would have the case that the update was
successfully installed but the next time that AU checks it would find that
module needed to be updated; hence your loop.
Good luck
Robert Aldwinckle
---
"Robert Aldwinckle" <rob...@techemail.com> wrote in message
news:ugv4ZTra...@TK2MSFTNGP02.phx.gbl...
That's the point. A critical part of the update is supposed to occur then.
If it isn't or if it is being reversed that would explain your symptom.
Before booting you can check why the boot is occurring,
e.g. either using information in the install log, or using the Event Viewer
or using RegEdit to see if there are any values in PendingFileRenameOperations
However you do it you could have a list of modules and versions which
are what you have before the update and what version they should be
if the update completes. If the modules do not have the version that
they should be after the boot then you would know the cause of your
symptom.
For an extreme diagnostic you could run ProcMon with its Boot Logging
option. However, I suggest first finding out what you would expect it to
show you by doing the above simpler analysis. E.g. if you looked at
the PendingFileRenameOperations and checked the specified modules
before the boot and discovered after the boot that they hadn't changed
as expected, why would that be? ProcMon's Boot Logging might be
the only way to find out exactly how it happened if not why.
Otherwise you have to guess at a cause, remove that possible cause and retest.
Good luck
Robert
---