Problems with software update services

I cannot update "Microsoft.net Framework 1.1 service Pack 1"
The reason Error Code 66A

listar wrote:

> I cannot update "Microsoft.net Framework 1.1 service Pack 1"
> The reason Error Code 66A
Hi

See if the tip from Eric57 works for you:

From: Eric57 <>
Subject: One Solution to .NET Framework Service Pack Install Errors
Date: Fri, 17 Sep 2004 22:49:02 -0700
Message-ID: <09C57381-9528-4BA9-8D71->
Newsgroups: microsoft.public.windowsupdate


<quote>
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:

\<windows dir>\Microsoft.NET\Framework\v1.0.3705\repair.htm <--1.0
\<windows dir>\Microsoft.NET\Framework\v1.1.4322\1033\repair Redist.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

</quote>


If the above doesn't work, and it is the .NET Framework v1.1 you
have trouble with, you could try this one:

How to troubleshoot Microsoft .NET Framework 1.1 installation issues
http://support.microsoft.com/?id=824643

Note this one from the URL above:

<quote>
4. Zap Windows Installer information from the registry by using the
Msizap.exe utility. The Msizap.exe utility is included with Microsoft
Windows Installer Software Development Kit (SDK). To download Windows
Installer SDK, visit the following Microsoft Web site:

http://www.microsoft.com/msdownload/...sdk/sdkupdate/
</quote>

A bit overkill to download and install WI SDK to obtain Msizap.exe ;-)

MSIZAP.EXE is included as a utility in the support tools installation
package on the WinXP CD.

Install "Support Tools" by starting suptools.msi from
<cd-drive>\Support\Tools\

Also note that there is updated versions of Support Tools available:

Windows XP Service Pack 2 Support Tools
http://www.microsoft.com/downloads/d...1-ba8011fabf38

If you don't have a WinXP CD, it should be ok to install and use the
downloadable SP2 version of Support Tools on a WinXP SP1 computer.


--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

As a professional developer myself, i hate to say that the Update-service
through I-Explorer is starting to fall over.
Microsoft is clearly out of control with this update-service.
For instance, if we look at the mess around SP2 for Windows XP. It's B.I.G.,
it fails to install way too often, and users are presented with a host of
different errors.
You might want to look at the troubles with .NET, which is clearly not fully
available, but presented as necessary.

If these updates were essential, you might expect a solid distribution in
place. Any system-responsable jock to make a descision on using SP2 and
..NET-material should think twice and has to come up with rock-solid arguments
why as to update, or get fired!

Hours and days are spoiled on non-issues. Come on, MS, we depend on you to
do better....

"Torgeir Bakken (MVP)" wrote:

> listar wrote:
>
> > I cannot update "Microsoft.net Framework 1.1 service Pack 1"
> > The reason Error Code 66A
> Hi
>
> See if the tip from Eric57 works for you:
>
> From: Eric57 <>
> Subject: One Solution to .NET Framework Service Pack Install Errors
> Date: Fri, 17 Sep 2004 22:49:02 -0700
> Message-ID: <09C57381-9528-4BA9-8D71->
> Newsgroups: microsoft.public.windowsupdate
>
>
> <quote>
> 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:
>
> \<windows dir>\Microsoft.NET\Framework\v1.0.3705\repair.htm <--1.0
> \<windows dir>\Microsoft.NET\Framework\v1.1.4322\1033\repair Redist.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
>
> </quote>
>
>
> If the above doesn't work, and it is the .NET Framework v1.1 you
> have trouble with, you could try this one:
>
> How to troubleshoot Microsoft .NET Framework 1.1 installation issues
> http://support.microsoft.com/?id=824643
>
> Note this one from the URL above:
>
> <quote>
> 4. Zap Windows Installer information from the registry by using the
> Msizap.exe utility. The Msizap.exe utility is included with Microsoft
> Windows Installer Software Development Kit (SDK). To download Windows
> Installer SDK, visit the following Microsoft Web site:
>
> http://www.microsoft.com/msdownload/...sdk/sdkupdate/
> </quote>
>
> A bit overkill to download and install WI SDK to obtain Msizap.exe ;-)
>
> MSIZAP.EXE is included as a utility in the support tools installation
> package on the WinXP CD.
>
> Install "Support Tools" by starting suptools.msi from
> <cd-drive>\Support\Tools\
>
> Also note that there is updated versions of Support Tools available:
>
> Windows XP Service Pack 2 Support Tools
> http://www.microsoft.com/downloads/d...1-ba8011fabf38
>
> If you don't have a WinXP CD, it should be ok to install and use the
> downloadable SP2 version of Support Tools on a WinXP SP1 computer.
>
>
> --
> torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
> Administration scripting examples and an ONLINE version of
> the 1328 page Scripting Guide:
> http://www.microsoft.com/technet/scr...r/default.mspx
> hello....the link provided is for 2.0 ......not 1.1 ?????