Originally Posted by
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
>
Bookmarks