Hi,
I've recently upgraded my graphics card and soundcard and had cause to
repair win xp sp2 installation. Now when i visit the win update i get the
above error.

Are the two related?. win xp sp2 was previously activated successfully prior
to the installation of the two cards.

How do I go about fixing my problem?

Cheers in advance
Denis

"Euclid" wrote:

> Hi,
> I've recently upgraded my graphics card and soundcard and had cause to
> repair win xp sp2 installation. Now when i visit the win update i get the
> above error.
>
> Are the two related?. win xp sp2 was previously activated successfully prior
> to the installation of the two cards.
>
> How do I go about fixing my problem?
>
> Cheers in advance
> Denis

Try the following, IAW the Windows Update Troubleshooter
http://v4.windowsupdate.microsoft.co...ndows%20Update

----------------------------------
Problem Description:
On the web site you will see that updates have failed to install. If you
check the Windows Update.log file, you will see an error similar to this:

Error IUENGINE See iuhist.xml for details: Install finished (Error
0x80070005: Access is denied.)


Resolutions:
Suggestion 1:

This error can occur if you have mapped network drives configured and you
don't have the correct permissions to access them. Try disconnecting all
mapped network drives and then try accessing the Windows Update site and see
if the installs still fail.

Suggestion 2:

If you are using the NTFS file system on your hard drive(s) then try these
steps.

Check permissions on the C:\WUTemp folder (if you have more than one hard
drive, check this folder on each drive).

1. Open Windows Explorer.
2. Navigate to the C:\WUTemp folder.
3. Right-click on the folder name and select Properties from the popup menu.
4. Click on the Security tab.
5. Set Full Control access for the following accounts:

Users
Power Users
Administrators

6. Click Apply, then OK.
7. Now try accessing the Windows Update site.

Suggestion 3:

1. Click on Start, Run and type "REGEDIT" (w/o the quotes). The Registry
Editor will open.

*WARNING*

Using Registry Editor incorrectly can cause serious problems that may
require you to reinstall your operating system. Microsoft cannot guarantee
that problems
resulting from the incorrect use of Registry Editor can be solved. Use
Registry Editor at your own risk.

2. Navigate to the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\WindowsUpdate

3. On the upper menu, click on Edit, and select Permissions from the
drop-down list.
4. Give Administrator (And / Or System) Full Control and Read permissions
by checking the allow boxes. NOTE: In certain instances these boxes are
grayed out. Insure that all accounts have appropriate permissions.
5. Click Apply, then OK.
6. Close the Registry Editor.
7. If you had to make any changes, then try the Windows Update site and see
if the error persists.

----------------------------------------------------------
I hope this helps. Arionly

"arionly" <arionly@discussions.microsoft.com> wrote in message
news:17829B4F-1B37-4A11-BF13-54368276040C@microsoft.com...
> Try the following, IAW the Windows Update Troubleshooter
> http://v4.windowsupdate.microsoft.co...ndows%20Update


arionly,

Good idea to use a troubleshooter.
However, OP's OS version (XPsp2) implies that the connection will be
with WUv5 or WUv6 instead of WUv4. Therefore, it would have been
even better to have found the equivalent troubleshooter articles for those
connections.

Fortunately in this particular case the suggested resolutions may even
be applicable or at least benign.


Thanks for trying to help. <w>


Robert Aldwinckle
---

"Euclid" <Euclid@discussions.microsoft.com> wrote in message
news:A3233225-B684-448E-B691-4AF37E23237B@microsoft.com...
> Hi,
> I've recently upgraded my graphics card and soundcard and had cause to
> repair win xp sp2 installation. Now when i visit the win update i get the
> above error.
>
> Are the two related?. win xp sp2 was previously activated successfully prior
> to the installation of the two cards.
>
> How do I go about fixing my problem?


If Arionly's tip to try using the WU troubleshooter doesn't lead to
a resolution, try a search?

Since you are using the web interface to newsgroups you can do that
simply by pressing Alt-7 and entering the code in the search input box.

Hmm... that's a bit overwhelming, even using the filters. ;}


Instead try using Google Groups:

http://groups.google.com/group/micro...ead5ae515d0dce

(Google Groups search for
(0x80070005 OR 80070005) (MSFT OR MVP) group:microsoft.*.windowsupdate
- sorted by date to try to capture current thinking
)


The most useful thing you could do though, if just taking stabs at others'
reported resolutions doesn't help, is start diagnosing your symptom,
e.g. search for any files which were updated on that day which contain
instances of that 80070005 string. You could also search for the
decimal equivalent -2147024891 but usually when it appears the hex
is given too. I suggest that more general approach to finding logs, etc.
because sometimes the diagnostics filenames are obscure, especially
when an unusual install is being done.


HTH

Robert Aldwinckle
---

Robert,

I'd just like to say you're a STAR!!...

I followed your advice about trying to diagnose my symptom and decided to
plough through the WU log and came across the following..

2005-11-10 21:29:54 1644 7bc Agent WARNING: Failed to evaluate Installed
rule, updateId = {ED300F67-421C-4C08-B3BA-F35C55F3B427}.100, error =
0x80040154
2005-11-10 21:29:54 1644 7bc Agent WARNING: Failed to evaluate Installed
rule, updateId = {794F5418-EDF1-44D6-97F4-8D693BC4CD97}.17, error = 0x80040154
2005-11-10 21:29:54 1644 7bc EEHndlr FATAL: MSI DLL version is 3.0. Version
3.1 is required.
2005-11-10 21:29:54 1644 7bc Agent WARNING: Failed to evaluate Installed
rule, updateId = {6248B8B1-FFEB-DBD9-887A-2ACF53B09DFE}.102, error =
0x80241001
2005-11-10 21:29:54 1644 7bc EEHndlr FATAL: MSI DLL version is 3.0. Version
3.1 is required.

I did a search for msi.dll and replaced the offending file in
c:\windows\system32\ with version 3.1 also found on c drive. Rebooted and
updated windows no problem.

Once again thanks for your time and effort invested in my problem, that goes
for you arionly also.

I'm one happy bunny again,
Denis

"Robert Aldwinckle" wrote:

> "Euclid" <Euclid@discussions.microsoft.com> wrote in message
> news:A3233225-B684-448E-B691-4AF37E23237B@microsoft.com...
> > Hi,
> > I've recently upgraded my graphics card and soundcard and had cause to
> > repair win xp sp2 installation. Now when i visit the win update i get the
> > above error.
> >
> > Are the two related?. win xp sp2 was previously activated successfully prior
> > to the installation of the two cards.
> >
> > How do I go about fixing my problem?
>
>
> If Arionly's tip to try using the WU troubleshooter doesn't lead to
> a resolution, try a search?
>
> Since you are using the web interface to newsgroups you can do that
> simply by pressing Alt-7 and entering the code in the search input box.
>
> Hmm... that's a bit overwhelming, even using the filters. ;}
>
>
> Instead try using Google Groups:
>
> http://groups.google.com/group/micro...ead5ae515d0dce
>
> (Google Groups search for
> (0x80070005 OR 80070005) (MSFT OR MVP) group:microsoft.*.windowsupdate
> - sorted by date to try to capture current thinking
> )
>
>
> The most useful thing you could do though, if just taking stabs at others'
> reported resolutions doesn't help, is start diagnosing your symptom,
> e.g. search for any files which were updated on that day which contain
> instances of that 80070005 string. You could also search for the
> decimal equivalent -2147024891 but usually when it appears the hex
> is given too. I suggest that more general approach to finding logs, etc.
> because sometimes the diagnostics filenames are obscure, especially
> when an unusual install is being done.
>
>
> HTH
>
> Robert Aldwinckle
> ---
>
>
>

"Euclid" <Euclid@discussions.microsoft.com> wrote in message
news:5018C409-277D-464A-8A22-731F9560D12F@microsoft.com...
> Robert,
>
> I'd just like to say you're a STAR!!...
>
> I followed your advice about trying to diagnose my symptom and decided to
> plough through the WU log and came across the following..
>
> 2005-11-10 21:29:54 1644 7bc Agent WARNING: Failed to evaluate Installed
> rule, updateId = {ED300F67-421C-4C08-B3BA-F35C55F3B427}.100, error =
> 0x80040154
> 2005-11-10 21:29:54 1644 7bc Agent WARNING: Failed to evaluate Installed
> rule, updateId = {794F5418-EDF1-44D6-97F4-8D693BC4CD97}.17, error = 0x80040154
> 2005-11-10 21:29:54 1644 7bc EEHndlr FATAL: MSI DLL version is 3.0. Version
> 3.1 is required.
> 2005-11-10 21:29:54 1644 7bc Agent WARNING: Failed to evaluate Installed
> rule, updateId = {6248B8B1-FFEB-DBD9-887A-2ACF53B09DFE}.102, error =
> 0x80241001
> 2005-11-10 21:29:54 1644 7bc EEHndlr FATAL: MSI DLL version is 3.0. Version
> 3.1 is required.


That's a clear message for you. <w>

So, there was no 0x80070005 code after all?

FYI searching for just the 0x80241001 code finds this answer
from TaurArian [MVP] in August:

http://www.microsoft.com/communities...074&sloc=en-us


>
> I did a search for msi.dll and replaced the offending file in
> c:\windows\system32\ with version 3.1 also found on c drive. Rebooted and
> updated windows no problem.
>
> Once again thanks for your time and effort invested in my problem, that goes
> for you arionly also.


I only suggested you try a rational approach. You took it.
Well done!

Thanks for the feedback.


Robert
---


>
> I'm one happy bunny again,
> Denis
>
> "Robert Aldwinckle" wrote:
>
>> "Euclid" <Euclid@discussions.microsoft.com> wrote in message
>> news:A3233225-B684-448E-B691-4AF37E23237B@microsoft.com...
>> > Hi,
>> > I've recently upgraded my graphics card and soundcard and had cause to
>> > repair win xp sp2 installation. Now when i visit the win update i get the
>> > above error.
>> >
>> > Are the two related?. win xp sp2 was previously activated successfully prior
>> > to the installation of the two cards.
>> >
>> > How do I go about fixing my problem?
>>
>>
>> If Arionly's tip to try using the WU troubleshooter doesn't lead to
>> a resolution, try a search?
>>
>> Since you are using the web interface to newsgroups you can do that
>> simply by pressing Alt-7 and entering the code in the search input box.
>>
>> Hmm... that's a bit overwhelming, even using the filters. ;}
>>
>>
>> Instead try using Google Groups:
>>
>> http://groups.google.com/group/micro...ead5ae515d0dce
>>
>> (Google Groups search for
>> (0x80070005 OR 80070005) (MSFT OR MVP) group:microsoft.*.windowsupdate
>> - sorted by date to try to capture current thinking
>> )
>>
>>
>> The most useful thing you could do though, if just taking stabs at others'
>> reported resolutions doesn't help, is start diagnosing your symptom,
>> e.g. search for any files which were updated on that day which contain
>> instances of that 80070005 string. You could also search for the
>> decimal equivalent -2147024891 but usually when it appears the hex
>> is given too. I suggest that more general approach to finding logs, etc.
>> because sometimes the diagnostics filenames are obscure, especially
>> when an unusual install is being done.
>>
>>
>> HTH
>>
>> Robert Aldwinckle
>> ---
>>
>>
>>