This might help - it's an extract from the 'netfxl.log' file created by the
hotfix in %TEMP%. The error code 1603 pops up. It suggests that the
problem may reside with an ASP.NET file...?
[2005-04-19 00:07:42]
[2005-04-19 00:07:42] ShadowLaunch started
[2005-04-19 00:07:42] Extracting embedded exe to
C:\DOCUME~1\BRIAN~1.STE\LOCALS~1\Temp\SL13CF.tmp
[2005-04-19 00:07:42] C:\ is not running on FAT (NTFS).
[2005-04-19 00:07:42] User is NT admin; preparing to shadow launch the
process.
..
..
..
[2005-04-19 00:07:43]
[2005-04-19 00:07:43] Executing:
C:\DOCUME~1\BRIAN~1.STE\LOCALS~1\Temp\SL13CF.tmp
[2005-04-19 00:07:43]
[2005-04-19 00:07:46] Received signal from created process; continuing.
..
..
..
[2005-04-19 00:07:46] CompleteShadowLaunch:
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspne t_isapi.dll
[2005-04-19 00:07:46] move
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspne t_isapi.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\SHADO W5396\aspnet_isapi.dll
[2005-04-19 00:07:46] move
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\SHADO W5396\_aspnet_isapi.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspne t_isapi.dll
[2005-04-19 00:08:07]
[2005-04-19 00:08:07] Process returned: 1603
[2005-04-19 00:08:07]
..
..
..
Regards,
Brian
"Brian Steele" <> wrote in message news:...
> Hi Everyone:
>
> Like a few other people have reported here, my PC continuously downloads,
> and fails to install, hotfix KB886903. I've tried downloading and
> manually installing .NET Framework 1.1 using the command
>
> dotnetfx.exe /t:%temp% /c:"msiexec.exe /fvecms %temp%\netfx.msi"
>
> ...then manually installing KB886903, but the error still occurs.
>
> I've turned on logging, and the following is the error message that's
> reported:
>
> Info 9006: This patch cannot be installed because it
> requires Microsoft .NET Framework 1.1 Service Pack
> 1 (SP1). No Micrsooft .NET Framework 1.1 SP can be
> detected on this computer. Please see
> http://support.microsoft.com/?kbid-886903 for more
> details.
>
> Of course, 1.1 IS installed. And the given link does not provide any
> details on how to resolve this problem.
>
> Any ideas?
>
>
> Brian
>
>