I'm able to download and install the updates and they require a restart.
During restart, I see the "configuring updates" message prior to the logon
screen. Somewhere in this process all of the updates fail. Every update
(the June patches) has the same update error.
I tried reinstalling the updates but the same error occurs.
I'm running Windows Vista Ultimate.
1: Error code 80071A90
Cumulative Security Update for Outlook Express for Windows Vista for
x64-based Systems(KB929123 ).
from this link
http://www.microsoft.com/technet/security/bulletin/ms07-034.mspx I tried to
install it manually
it will not install, says something about not needed for my system.
2: Error code 800F0826
Security Update for Windows Vista for x64-based Systems (KB931213)
I get the configuring updates message on restart, and again when system
reboots. Then system reboots again.
No configuring updates message after the second reboot. After the system
comes up I get notified that there are
updates available. When I check to see what updates are available, I get the
same update pending.
Needless to say I have turned off Automatic update, as it keeps trying to
install the same fix over and over again.
Now, what makes it even stranger is that when I look at installed updates, I
see
Security Update for Windows (KB931213).. Why two fixes with the same KB
number.
"David" <Da...@discussions.microsoft.com> wrote in message
news:FBA4C5E3-FD7C-48CE...@microsoft.com...
For 32-bit systems, download and save to hard disk, and then install:
<http://download.windowsupdate.com/v7/windowsupdate/redist/standalone/WindowsUpdateAgent30-x86.exe>
If this produces an error message about "Update agent already
installed", then execute the installer again manually, with parameter
/wuforce as in (at a comand prompt window):
WindowsUpdateAgent30-x86.exe /wuforce
If unable to install, disable any anti-virus or anyi-spyware application
active, then try the installation again.
- Robin Walker {MVP}
--
Gistcheckin
<cmd_output OS="XPsp2">
E:\>set /a c = 0x1aa7
6823
E:\>net helpmsg %c%
The system cannot find message text for message number 0x1aa7 in the message file for NETMSG.
</cmd_output>
Try the same thing in Vista. Perhaps that code has a meaning in it?
Alternatively, since codes have very little meaning without their context
anyway, search any files that the install created for those codes,
both the hex value (without the 0x prefix) and the decimal equivalent.
Good luck
Robert Aldwinckle
---
> I successfully installed latest update agent but still cannot install:
> Cumulative Security Update for Internet Explorer 7 in Windows Vista
> (KB933566) Installation status: Failed
> Error details: Code 80071AA7
> Any suggestions are welcomed.
Have you disabled all anti-virus, anti-spyware, popup-blocker, download
accelerator, third-party firewall?
--
Robin Walker [MVP Networking]
rd...@cam.ac.uk
"Gistcheckin" <Gistc...@discussions.microsoft.com> wrote in message
news:E07FD558-967C-4099...@microsoft.com...
1. Installing each update one by one worked for all except "Cumulative
Security Update for Windows Mail for Windows Vista (KB929123)". For it, I
still get the same 80071AA7 error.
2. Reinstalling the Windows Update client did not make a difference.
3. I could not find any matches for the error code in any of the download
files and when running "net helpmsg", I get the following response:
"The file cannot be opened transactionally, because its identity depends on
the outcome of an unresolved transaction."
Which is not much help as it is apparently a low level system error
(http://msdn2.microsoft.com/en-us/library/ms681389.aspx). Thanks for the tip
on looking up the decimal error codes though.
4. I disabled anti-virus and anti-spyware, and it still didn't work.
Interestingly, when I first logon after restart, the Windows Update window
shows that all updates are applied. A little while later, I get an error
message in the system tray saying an update has failed, and then the Windows
Update window changes to reflect that. So something is happening in the last
installation steps of the update.
Regards,
David
Not the download files, the files that the update creates or modifies. ; )
E.g. search for all files which are changed on that day, then order them
by Date Modified. That in fact is a misnomer because it sorts by a full
timestamp, so then you can just scroll to the minute when the update
was active and find all files which it changed.
> and when running "net helpmsg", I get the following response:
>
> "The file cannot be opened transactionally, because its identity depends on
> the outcome of an unresolved transaction."
>
> Which is not much help as it is apparently a low level system error
> (http://msdn2.microsoft.com/en-us/library/ms681389.aspx). Thanks for the tip
> on looking up the decimal error codes though.
Oops. I should have thought of doing that web search. Thanks.
>
> 4. I disabled anti-virus and anti-spyware, and it still didn't work.
Some users have found that there is still interference caused by such products
even when they are "disabled", so that better results may occur if they
are actually uninstalled instead. In particular if the disablement only
lasts for the current session (e.g. it doesn't survive a reboot) that could
explain your symptom, since the last step of the update (renaming of
in-use modules) would have to be done during a reboot.
>
> Interestingly, when I first logon after restart, the Windows Update window
> shows that all updates are applied. A little while later, I get an error
> message in the system tray saying an update has failed, and then the Windows
> Update window changes to reflect that. So something is happening in the last
> installation steps of the update.
Typical of the interference caused by security products.
E.g. the update requires a reboot in order to rename system files
which can not be updated on a live system. If the security product
blocks the rename operation from occurring the update is incomplete
and AU would detect that fact and reschedule it (ad infinitum until the
blockage was removed.)
You could try using ProcMon on that phase of the update to try to see why
it wasn't happening. The newest version of it now has the Boot Logging
option which might be the only way you could know this. E.g. I don't think
that this phase is included in the update's install log, even if verbose logging
is requested. BTW does the security product have any kind of report
(perhaps only available with advanced options?) which would confirm
that it *is* doing such blocking?
Have you tried doing a safe mode boot instead of a regular boot
when the update requests it? I don't know for sure if that would
continue with the renaming (e.g. it might only be in the registry branch
of the regular boot) but it would (hopefully) make it less likely that your
security products could continue their interference with that step,
if it can be done then.
BTW all of these hypotheses should be easily testable.
E.g. the install log (at least with verbose logging enabled)
would show you which modules had to be renamed
and before allowing the reboot you could inspect the
registry to see if those renames were scheduled
(e.g. in PendingFileRenameOperations)
Good luck
Robert
---
"David" wrote:
Hello David,
I had the same problem, Vista Home Premium and updates repeatedly failing
with the code 0x80071AA7.
I happened to stumble upon a solution for this (at least in my case) from
this blog post [1]:
http://blog.runonfriday.com/2008/10/07/error-80071aa7-solved/
The post explains how the problem can be pinpointed to a specific file
holding back the update by examining the file windows\WindowsUpdate.log
In my case the files occonfig.dll and ocsetup.exe were causing the update to
fail. They also prevented me from installing service pack 2. Following the
instructions in the post did the following.
1) booted into recovery mode (press F8 to get the boot menu during system
startup) and then select the topmost entry
2) when available, chose to enter command prompt.
3) copied the contents from windows\system32 to a temporary directory
4) deleted the files in Windows\System32
5) copied the files back to System32 from the temporary directory
It all seems like black magic, but I assume that the process destroys file
links or file locks that should not be there that are holding back the
installation of the update. (Someone who knows better could explain further)
I did also the chkdsk part suggested on the blog, but in my case chkdsk did
not report any problems.
In any case, the trick worked and I finally could install the updates that
had already failed to install numerous times.
Otto
p.s. The original blog post uses a lot safer mechanism, where the original
file is simply renamed and copied. Using my method resolves all files, but is
a bit riskier.
[1] Windows update error 80071AA7 *solved*,
http://blog.runonfriday.com/2008/10/07/error-80071aa7-solved/,
RunOnFriday.com blog, 7.10.2008, Hudson Valley Computer Associates, Inc,