One Solution to .NET Framework Service Pack Install Errors

I had originally posted a solution for .NET Framework 1.0 643 errors, but the
same methodology will solve the problem for 1.1 errors. In addition, the
following steps may rectify other hex code errors. The problem is a corrupt
Framework library and the solution is to restore it to a previous working
state. The important thing is to use the correct .NET Framework
Redistributable library in the following steps.

MS is aware of the Framework corruption issues as documented in the
following two files:

\WINNT\Microsoft.NET\Framework\v1.0.3705\repair.ht m <--1.0
\WINNT\Microsoft.NET\Framework\v1.1.4322\1033\repa irRedist.htm <--1.1

They note: "You may need to repair your installation of the .NET Framework
after upgrading your operating system or if the system becomes corrupted".
Each then recommend using "dotnetfx.exe" to restore the .NET Framework to a
previous state.

To obtain the correct dotnefx, first download either the

".NET Framework 1.0 Redistributable"
or
".NET Framework 1.1 Redistributable"

from: http://msdn.microsoft.com/netframewo...s/default.aspx

This download is a self-extracting file named "dotnetredist.exe". Click on
it
to obtain the "dotnetfx.exe" file. Next, from a command line prompt, change
to the directory containing "dotnetfx.exe" and enter:

dotnetfx.exe /t:%temp% /c:"msiexec.exe /fvecms %temp%\netfx.msi"

Note that the quotes are required after the /c: switch. When the installer
is done, invoke Windows Update and select the failed Framework Service Pack
for reinstall. WU should now complete and mark the update as Installed.

Hope this helps,
Eric Webb
--
Remove NOSPAM for email replies

Is it normal for WinUP in XP SP1 to be offering both:
Microsoft .NET Framework 1.0 Service Pack 3, English Version
Microsoft .NET Framework 1.1 Service Pack 1
at the same time??

If both are normal then what you are saying is that I should just use your
suggested fix?

See my thread:".NET FM 1.0 SP3 WinUP Failure" please.

"Eric57" <> wrote in message
news:09C57381-9528-4BA9-8D71-...
> I had originally posted a solution for .NET Framework 1.0 643 errors, but
the
> same methodology will solve the problem for 1.1 errors. In addition, the
> following steps may rectify other hex code errors. The problem is a
corrupt
> Framework library and the solution is to restore it to a previous working
> state. The important thing is to use the correct .NET Framework
> Redistributable library in the following steps.
>
> MS is aware of the Framework corruption issues as documented in the
> following two files:
>
> \WINNT\Microsoft.NET\Framework\v1.0.3705\repair.ht m
<--1.0
> \WINNT\Microsoft.NET\Framework\v1.1.4322\1033\repa irRedist.htm <--1.1
>
> They note: "You may need to repair your installation of the .NET Framework
> after upgrading your operating system or if the system becomes corrupted".
> Each then recommend using "dotnetfx.exe" to restore the .NET Framework to
a
> previous state.
>
> To obtain the correct dotnefx, first download either the
>
> ".NET Framework 1.0 Redistributable"
> or
> ".NET Framework 1.1 Redistributable"
>
> from:
http://msdn.microsoft.com/netframewo...s/default.aspx
>
> This download is a self-extracting file named "dotnetredist.exe". Click
on
> it
> to obtain the "dotnetfx.exe" file. Next, from a command line prompt,
change
> to the directory containing "dotnetfx.exe" and enter:
>
> dotnetfx.exe /t:%temp% /c:"msiexec.exe /fvecms %temp%\netfx.msi"
>
> Note that the quotes are required after the /c: switch. When the
installer
> is done, invoke Windows Update and select the failed Framework Service
Pack
> for reinstall. WU should now complete and mark the update as Installed.
>
> Hope this helps,
> Eric Webb
> --
> Remove NOSPAM for email replies

Hi Root,

Yes, both 1.0 and 1.1 Frameworks can coexist. As is understand it, 1.1 is
not entirely backwards compatible with 1.0. So, MS wants to keep a side by
side architecture for awhile.

If your 1.0 SP3 is failing due to a corrupt 1.0 Framework, the fix for 1.0
very well might fix the failure. It doesn't take too long to try.

Please let me know if it works for you.

Regards,
Eric

"root" wrote:

> Is it normal for WinUP in XP SP1 to be offering both:
> Microsoft .NET Framework 1.0 Service Pack 3, English Version
> Microsoft .NET Framework 1.1 Service Pack 1
> at the same time??
>
> If both are normal then what you are saying is that I should just use your
> suggested fix?
>

Thanks for posting this, it totally worked.

"Eric57" wrote:

> Hi Root,
>
> Yes, both 1.0 and 1.1 Frameworks can coexist. As is understand it, 1.1 is
> not entirely backwards compatible with 1.0. So, MS wants to keep a side by
> side architecture for awhile.
>
> If your 1.0 SP3 is failing due to a corrupt 1.0 Framework, the fix for 1.0
> very well might fix the failure. It doesn't take too long to try.
>
> Please let me know if it works for you.
>
> Regards,
> Eric
>
> "root" wrote:
>
> > Is it normal for WinUP in XP SP1 to be offering both:
> > Microsoft .NET Framework 1.0 Service Pack 3, English Version
> > Microsoft .NET Framework 1.1 Service Pack 1
> > at the same time??
> >
> > If both are normal then what you are saying is that I should just use your
> > suggested fix?
> >
>

Thanks Eric, step by step solid fix thanks.

"Eric57" wrote:

> I had originally posted a solution for .NET Framework 1.0 643 errors, but the
> same methodology will solve the problem for 1.1 errors. In addition, the
> following steps may rectify other hex code errors. The problem is a corrupt
> Framework library and the solution is to restore it to a previous working
> state. The important thing is to use the correct .NET Framework
> Redistributable library in the following steps.
>
> MS is aware of the Framework corruption issues as documented in the
> following two files:
>
> \WINNT\Microsoft.NET\Framework\v1.0.3705\repair.ht m <--1.0
> \WINNT\Microsoft.NET\Framework\v1.1.4322\1033\repa irRedist.htm <--1.1
>
> They note: "You may need to repair your installation of the .NET Framework
> after upgrading your operating system or if the system becomes corrupted".
> Each then recommend using "dotnetfx.exe" to restore the .NET Framework to a
> previous state.
>
> To obtain the correct dotnefx, first download either the
>
> ".NET Framework 1.0 Redistributable"
> or
> ".NET Framework 1.1 Redistributable"
>
> from: http://msdn.microsoft.com/netframewo...s/default.aspx
>
> This download is a self-extracting file named "dotnetredist.exe". Click on
> it
> to obtain the "dotnetfx.exe" file. Next, from a command line prompt, change
> to the directory containing "dotnetfx.exe" and enter:
>
> dotnetfx.exe /t:%temp% /c:"msiexec.exe /fvecms %temp%\netfx.msi"
>
> Note that the quotes are required after the /c: switch. When the installer
> is done, invoke Windows Update and select the failed Framework Service Pack
> for reinstall. WU should now complete and mark the update as Installed.
>
> Hope this helps,
> Eric Webb
> --
> Remove NOSPAM for email replies

I tried this, and it worked OK for the v1.1 error (although the whole thing
ran automoatically once I chose to run the download, and I didn't get a
chance to go to a Command line).

For the v1.0 redistributable though, it appeared to be working then came up
with a dialog box that said "This patch package could not be opened. Verify
that the patch package exists and that you can access it, or contact the
application vendor to verify that this is a valid windows installer patch".
I'm not sure which of the files that extracted from the download is actually
the patch package, but there are five files in the directory in addition to
the initial dotnetfx.exe and the notnetredist.exe files, as follows:
install.exe; InstMsi.exe; InstMsiW.exe; netfx.msi; neftf1.cab. Any
suggestions?

"Eric57" wrote:

> I had originally posted a solution for .NET Framework 1.0 643 errors, but the
> same methodology will solve the problem for 1.1 errors. In addition, the
> following steps may rectify other hex code errors. The problem is a corrupt
> Framework library and the solution is to restore it to a previous working
> state. The important thing is to use the correct .NET Framework
> Redistributable library in the following steps.
>
> MS is aware of the Framework corruption issues as documented in the
> following two files:
>
> \WINNT\Microsoft.NET\Framework\v1.0.3705\repair.ht m <--1.0
> \WINNT\Microsoft.NET\Framework\v1.1.4322\1033\repa irRedist.htm <--1.1
>
> They note: "You may need to repair your installation of the .NET Framework
> after upgrading your operating system or if the system becomes corrupted".
> Each then recommend using "dotnetfx.exe" to restore the .NET Framework to a
> previous state.
>
> To obtain the correct dotnefx, first download either the
>
> ".NET Framework 1.0 Redistributable"
> or
> ".NET Framework 1.1 Redistributable"
>
> from: http://msdn.microsoft.com/netframewo...s/default.aspx
>
> This download is a self-extracting file named "dotnetredist.exe". Click on
> it
> to obtain the "dotnetfx.exe" file. Next, from a command line prompt, change
> to the directory containing "dotnetfx.exe" and enter:
>
> dotnetfx.exe /t:%temp% /c:"msiexec.exe /fvecms %temp%\netfx.msi"
>
> Note that the quotes are required after the /c: switch. When the installer
> is done, invoke Windows Update and select the failed Framework Service Pack
> for reinstall. WU should now complete and mark the update as Installed.
>
> Hope this helps,
> Eric Webb
> --
> Remove NOSPAM for email replies

"Balrog" wrote:

> I tried this, and it worked OK for the v1.1 error (although the whole thing
> ran automoatically once I chose to run the download, and I didn't get a
> chance to go to a Command line).

OK, you must have replied Run instead of Save during the download? Glad it
worked.

> For the v1.0 redistributable though, it appeared to be working then came up
> with a dialog box that said "This patch package could not be opened. Verify
> that the patch package exists and that you can access it, or contact the
> application vendor to verify that this is a valid windows installer patch".
> I'm not sure which of the files that extracted from the download is actually
> the patch package, but there are five files in the directory in addition to
> the initial dotnetfx.exe and the notnetredist.exe files, as follows:
> install.exe; InstMsi.exe; InstMsiW.exe; netfx.msi; neftf1.cab. Any
> suggestions?

I think there is some collateral debris here from 1.1 and/or an invalid path
issue. I would delete everything in the list and search your hard drive for
any other instances of dotnetfix and netfix. Then delete the redistributal
download.

Next, I would redownload the 1.0 redistributal, save it to disk and extract
it. There should be only one file--dotnetfx.exe.

Then do the command line stuff and see if things work.

Let us know...

Regards,
Eric

After biting the bullet and deciding to get ALL 'critical
updates' including sp2 (which I installed via a disk) I
spent over an hour downloading the .net framework update
(which as a 'advanced every day user - non techie) I
always thought was a developer tool, like vb, anyway,
obviously not!

I have spent the last four or five hours trying to find a
SOLUTION to this issue, which is almost as annoying as the
fact that there is no WARNING (at LEAST) on the windows
update site to NOT install this or something! Took over
an hour to download it, now four or five hours trying to
fix it, searching the MSDN newsgroups, finally coming
here, and then again hearing a DIFFERENT 'solution'
(download something ELSE, no. nononononono. I have
already got this useless update on my pc, another stack of
mb's GONE or useless, sp2 cost me 1.2gb, etc etc etc.

Ridiculous. Especially for 'home users' who are just
TRYING to do GOOD MAINTENANCE. AS TOUTED!

..

oh! and I WOULD have put a post on the MSDN newsgroup
which is really MORE relevant than this (as at least you
can be more confident those in the '.net
framework' 'section' might READ posts there, but I had to
sign IN with my passport just to post. No way. Come on.
Jeez. I really DO like microsoft but things are getting
MESSY!

..

a FINAL note, I downloaded the GDI (sp?) detection tool
too, THAT told me I needed to update 'one note'. As it
was preinstalled on my machine, I need the disk. An on it
goes, messy, messy, messy. Yes I DO have the 'fancy
sticker' to prove I 'own' it. I just don't have the
disk. So the sticker is a little useless isn't it!


..
..
..

>-----Original Message-----
>Is it normal for WinUP in XP SP1 to be offering both:
>Microsoft .NET Framework 1.0 Service Pack 3, English
Version
>Microsoft .NET Framework 1.1 Service Pack 1
>at the same time??
>
>If both are normal then what you are saying is that I
should just use your
>suggested fix?
>
>See my thread:".NET FM 1.0 SP3 WinUP Failure" please.
>
>"Eric57" <> wrote in message
>news:09C57381-9528-4BA9-8D71-...
>> I had originally posted a solution for .NET Framework
1.0 643 errors, but
>the
>> same methodology will solve the problem for 1.1
errors. In addition, the
>> following steps may rectify other hex code errors. The
problem is a
>corrupt
>> Framework library and the solution is to restore it to
a previous working
>> state. The important thing is to use the correct .NET
Framework
>> Redistributable library in the following steps.
>>
>> MS is aware of the Framework corruption issues as
documented in the
>> following two files:
>>
>> \WINNT\Microsoft.NET\Framework\v1.0.3705\repair.ht m
><--1.0
>> \WINNT\Microsoft.NET\Framework\v1.1.4322\1033
\repairRedist.htm <--1.1
>>
>> They note: "You may need to repair your installation of
the .NET Framework
>> after upgrading your operating system or if the system
becomes corrupted".
>> Each then recommend using "dotnetfx.exe" to restore
the .NET Framework to
>a
>> previous state.
>>
>> To obtain the correct dotnefx, first download either the
>>
>> ".NET Framework 1.0 Redistributable"
>> or
>> ".NET Framework 1.1 Redistributable"
>>
>> from:
>http://msdn.microsoft.com/netframewo...oads/updates/d
efault.aspx
>>
>> This download is a self-extracting file
named "dotnetredist.exe". Click
>on
>> it
>> to obtain the "dotnetfx.exe" file. Next, from a
command line prompt,
>change
>> to the directory containing "dotnetfx.exe" and enter:
>>
>> dotnetfx.exe /t:%temp% /c:"msiexec.exe /fvecms %temp%
\netfx.msi"
>>
>> Note that the quotes are required after the /c:
switch. When the
>installer
>> is done, invoke Windows Update and select the failed
Framework Service
>Pack
>> for reinstall. WU should now complete and mark the
update as Installed.
>>
>> Hope this helps,
>> Eric Webb
>> --
>> Remove NOSPAM for email replies
>
>
>.
>

Thanks for posting this. It worked after many times trying to figure out
what was the problem. I reinstalled .NET Redistributable 1.1 and then went
to Windows Update and it installed finally.

It's too bad this advice is not more easily accessable when you search in
Microsoft files.

Thank you Erick it worked just fine.

"Eric57" wrote:

> I had originally posted a solution for .NET Framework 1.0 643 errors, but the
> same methodology will solve the problem for 1.1 errors. In addition, the
> following steps may rectify other hex code errors. The problem is a corrupt
> Framework library and the solution is to restore it to a previous working
> state. The important thing is to use the correct .NET Framework
> Redistributable library in the following steps.
>
> MS is aware of the Framework corruption issues as documented in the
> following two files:
>
> \WINNT\Microsoft.NET\Framework\v1.0.3705\repair.ht m <--1.0
> \WINNT\Microsoft.NET\Framework\v1.1.4322\1033\repa irRedist.htm <--1.1
>
> They note: "You may need to repair your installation of the .NET Framework
> after upgrading your operating system or if the system becomes corrupted".
> Each then recommend using "dotnetfx.exe" to restore the .NET Framework to a
> previous state.
>
> To obtain the correct dotnefx, first download either the
>
> ".NET Framework 1.0 Redistributable"
> or
> ".NET Framework 1.1 Redistributable"
>
> from: http://msdn.microsoft.com/netframewo...s/default.aspx
>
> This download is a self-extracting file named "dotnetredist.exe". Click on
> it
> to obtain the "dotnetfx.exe" file. Next, from a command line prompt, change
> to the directory containing "dotnetfx.exe" and enter:
>
> dotnetfx.exe /t:%temp% /c:"msiexec.exe /fvecms %temp%\netfx.msi"
>
> Note that the quotes are required after the /c: switch. When the installer
> is done, invoke Windows Update and select the failed Framework Service Pack
> for reinstall. WU should now complete and mark the update as Installed.
>
> Hope this helps,
> Eric Webb
> --
> Remove NOSPAM for email replies