[Neale D. Hind]

I needed to do an 'upgrade repair' to my 'Windows XP Home' yesterday. I
did so from my slipstream CD and all went well. After completion Windows
automatic updates downloaded more fixes.

All of these updates installed with the exception of KB893803v2 (Windows
Installer 3.1). I downloaded the redistributable version so I could run
a local install, but this failed in exactly the same way.

From web search, I am not alone with this problem. I've tried two
'popular' (in that I saw them recommended in more than place)
suggestions:

1) rename the catroot2 folder and reinstall the update.
2) temporarily empty the windows\installer folder and reinstall the
update.

Neither of these worked.

The kb893803v2 log below includes the following 'DoRegistryUpdates
failed' and looks to be the symptom of the problem

Any alternate suggestions as to how I can fix this to?

>82.968: DoInstallation: Installing assemblies with source root path:
>d:\ebead38143fcad3c7af49c68\
>82.984: Num Ticks for Copying files : 14781
>83.750: DoRegistryUpdates:UpdSpInstallFromInfSection Failed for
>MSI.Reg.Install: 0x5
>83.750: DoInstallation:DoRegistryUpdates failed
>83.890: Access is denied.
>87.890: Message displayed to the user: Access is denied.
>87.890: User Input: OK
>87.922: KB893803v2 installation did not complete.
>
>Select 'OK' to undo the changes that have been made.
>89.328: Message displayed to the user: KB893803v2 installation did not
>complete.
>
>Select 'OK' to undo the changes that have been made.
>89.328: User Input: OK
>89.453: Starting process:
>C:\WINDOWS\$MSI31Uninstall_KB893803v2$\spuninst\spuninst.exe /~ -u -z
>97.750: Software Update Rollback has completed with return code 0xbc2.
>This rollback requires a reboot.
>97.765: KB893803v2 installation did not complete.
>
>Windows Installer has been partially updated and may not work properly.
>100.140: Message displayed to the user: KB893803v2 installation did not
>complete.
>
>Windows Installer has been partially updated and may not work properly.
>100.140: User Input: OK

Incidentally the original April 2005 KB893093 had previously installed
properly through automatic updates.

Cheers,
--
Neale Hind
Insanity is hereditary, you get it from your children

[Neale D. Hind]

In message <aKLRtBB78ouCFwB0@easton.demon.co.uk>, Neale D. Hind
<nospam@127.0.0.1> writes
>I needed to do an 'upgrade repair' to my 'Windows XP Home' yesterday. I
>did so from my slipstream CD and all went well. After completion
>Windows automatic updates downloaded more fixes.
>
>All of these updates installed with the exception of KB893803v2
>(Windows Installer 3.1). I downloaded the redistributable version so I
>could run a local install, but this failed in exactly the same way.
>
>From web search, I am not alone with this problem. I've tried two
>'popular' (in that I saw them recommended in more than place)
>suggestions:
>
>1) rename the catroot2 folder and reinstall the update.
>2) temporarily empty the windows\installer folder and reinstall the
>update.
>
>Neither of these worked.
>
>The kb893803v2 log below includes the following 'DoRegistryUpdates
>failed' and looks to be the symptom of the problem


I finally solved my install problem and thought I'd share the knowledge.

1) I attained a partial solution by running the update and waiting
for the 'access denied' dialog. Instead of clicking 'OK' (which
reverses the failed installation) I rebooted the machine. This
left all the files in the right place and worked with MS Update
v6.

2) I wasn't entirely satisfied with the workaround because I was
always going to have a nagging doubt about its stability. For
example the failed install did not create a remove option in
Add/Remove Programs.

So I did some more web research and came across
<http://support.microsoft.com/default.aspx?scid=kb;en-us;836926>.
Method 3 in this solution pointed at registry key permissions -
consistent with the original registry key update failures.
Essentially I opened
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Wind
owsUpdate and set permissions for Full Access *AND* ensured that
the setting to allow all subkeys was also set.

Fortunately this worked (ta-ra).

Hoping others can benefit from my pain (I've probably put around 30
hours effort onto this problem).

<snip kb893803v2 log>

Cheers,
--
Neale Hind
Insanity is hereditary, you get it from your children

[cactusjack]

I had similar frustrations and tried a variety of fixes without success.
Manual install of Windows Installer Hotfix KB893803v2 dialogue box said I was
successful but
the system event viewer in my SP Pro SP2 showed installation failure:

"Windows Installer Hotfix KB893803v2 installation failed.
KB893803v2 installation did not complete."

I finally installed the MSI Installer v2 after using right click context
menu -
"run as" administrator (after starting Secondary Log On in services.)

Cactus Jack




"Neale D. Hind" wrote:

> In message <aKLRtBB78ouCFwB0@easton.demon.co.uk>, Neale D. Hind
> <nospam@127.0.0.1> writes
> >I needed to do an 'upgrade repair' to my 'Windows XP Home' yesterday. I
> >did so from my slipstream CD and all went well. After completion
> >Windows automatic updates downloaded more fixes.
> >
> >All of these updates installed with the exception of KB893803v2
> >(Windows Installer 3.1). I downloaded the redistributable version so I
> >could run a local install, but this failed in exactly the same way.
> >
> >From web search, I am not alone with this problem. I've tried two
> >'popular' (in that I saw them recommended in more than place)
> >suggestions:
> >
> >1) rename the catroot2 folder and reinstall the update.
> >2) temporarily empty the windows\installer folder and reinstall the
> >update.
> >
> >Neither of these worked.
> >
> >The kb893803v2 log below includes the following 'DoRegistryUpdates
> >failed' and looks to be the symptom of the problem
>
>
> I finally solved my install problem and thought I'd share the knowledge.
>
> 1) I attained a partial solution by running the update and waiting
> for the 'access denied' dialog. Instead of clicking 'OK' (which
> reverses the failed installation) I rebooted the machine. This
> left all the files in the right place and worked with MS Update
> v6.
>
> 2) I wasn't entirely satisfied with the workaround because I was
> always going to have a nagging doubt about its stability. For
> example the failed install did not create a remove option in
> Add/Remove Programs.
>
> So I did some more web research and came across
> <http://support.microsoft.com/default.aspx?scid=kb;en-us;836926>.
> Method 3 in this solution pointed at registry key permissions -
> consistent with the original registry key update failures.
> Essentially I opened
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Wind
> owsUpdate and set permissions for Full Access *AND* ensured that
> the setting to allow all subkeys was also set.
>
> Fortunately this worked (ta-ra).
>
> Hoping others can benefit from my pain (I've probably put around 30
> hours effort onto this problem).
>
> <snip kb893803v2 log>
>
> Cheers,
> --
> Neale Hind
> Insanity is hereditary, you get it from your children
>

[cactusjack]

Forgot to mention that the previous failed fixes were attempted under my
other admin account and would not work with "run as" unless I selected the
admin account that I used to originally install XP.

snip quotes


> > Neale Hind
> > Insanity is hereditary, you get it from your children
> >