Re: Unable to install .NET 1.1 via Windows Update and Redistributables



See http://support.microsoft.com/kb/923100 (ignore the title)
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/

sensei wrote:
I return with new information:

I've downloaded the .NET 1.1 and .NET 3.0 setup files from
(C|Net)Download.com and those files also experienced much the same problems
-- although the .NET 3.0 actually had a valid certificate. After doing a
bytewise-comparison between the two files, I noticed that only ONE single
byte was different, but that was enough to throw off the certification.

As fascinating as this all is, it brings me to the bleak realization that
there probably isn't anything that corrupt about the .NET files sitting on
Microsoft's servers because the behaviour is the same for both copies of the
file.

"sensei" wrote:

I've installed Windows XP Pro on many systems, but this is the first time
I've encountered this problem.

I just can't seem to get the following software installed via Microsoft
Update without an error code of: 0x80246002

.NET 1.1
.NET 3.0

I'm starting with a fresh install of Windows XP Pro on a brand new
quad-core workstation.

I installed software in the following order:

Windows XP SP1 (from original installation CD)
SP2 (redistributable executable from microsoft)
Microsoft Update (and every critical and major update successfully
installed)

I was, however, able to install .NET 1.0 from the XP CD-Rom, and .NET 2.0
worked from a redistributable file. Nothing unusual happened during the
installation of those two programs, but I cannot apply service packs to
them without the same 0x80246002 error.

Finally, one more conundrum:

I've noticed that the .NET 1.1 redistributable does not have a proper
certificate -- Windows claims that it comes from an "Unknown Publisher",
and when I run it anyways, it dies when extracting InstMsiW.exe with the
error:

"Extracting file failed. It is most likely caused by low memory (low disk
space for swapping file) or corrupted Cabinet file."

This can't be the case, since this is a brand new computer with over 700GB
of free space and 2 GB of ram, with nothing running in the background. I've
attempted redownloading the same file several times, but I'm led to believe
that maybe the file on Microsoft's website is corrupted because the file
does not change in any way with each successive download, even after
clearing my cache.

I'm dying to get this new workstation started. Your help is greatly
appreciated.

.



Relevant Pages

  • Re: Unable to install .NET 1.1 via Windows Update and Redistributa
    ... sensei wrote: ... me to suspect it, but I used Microsoft's RAM testing application, and I ... there probably isn't anything that corrupt about the .NET files sitting ... Windows XP SP1 (from original installation CD) ...
    (microsoft.public.windowsupdate)
  • Re: GOD
    ... I'm not a Microsoft basher by any means. ... Framework you now have installed. ... Then your problem with the repeating installation (or other possible ... And if it IS corrupt, shouldn't a well-written update try to fix ...
    (microsoft.public.windowsupdate)
  • Re: GOD
    ... I'm not a Microsoft basher by any means. ... Framework you now have installed. ... Then your problem with the repeating installation (or other possible ... And if it IS corrupt, shouldn't a well-written update try to fix ...
    (microsoft.public.windowsupdate)
  • RE: Unable to install .NET 1.1 via Windows Update and Redistributables
    ... there probably isn't anything that corrupt about the .NET files sitting on ... I just can't seem to get the following software installed via Microsoft ... Windows XP SP1 (from original installation CD) ... of free space and 2 GB of ram, with nothing running in the background. ...
    (microsoft.public.windowsupdate)
  • Re: SBS 2003, lost companyweb
    ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... The original Windows SBS installation was preinstalled by an OEM. ... Important You must change this registry entry on all domain controllers. ...
    (microsoft.public.windows.server.sbs)

Loading