Error: 0x13EC Microsoft .NET Framework 3.0 Service Pack 1 (KB92930

I get this code when trying to install update for Microsoft .NET Framework
3.0 Service Pack 1 (KB929300)
It fails to install the update.

First, see http://support.microsoft.com/kb/923100 (ignore the title).

If no joy, see this recent post by my colleague MowGreen:
http://groups.google.com/group/micro...76de7769d04493

--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/

The Dane wrote:
> I get this code when trying to install update for Microsoft .NET Framework
> 3.0 Service Pack 1 (KB929300)
> It fails to install the update.

This issue can be caused by a damaged .NET Framework 2.0 installation. In
order to resolve the issue, we have to remove/reinstall previous versions of
..NET Framework. Based on its current status, I suggest trying the following
troubleshooting steps.

Step 1: Download Microsoft Windows Installer Cleanup Utility
=============================================
1. Please visit:
http://download.microsoft.com/downlo...BD/msicuu2.exe
2. Save the file on your Desktop
3. Double click the file msicuu2.exe on the Desktop to install this tool on
the computer.

Step 2: Remove the previous version of .NET Framework 2.0 if installed.
================================================== ===
1. Click Start -> (All) Programs->Windows Installer Clean Up.
2. Please locate and remove all .NET Framework products.

After removing .NET Framework components, let's reinstall .NET Framework 3.0
and its updates.

Step 3: Manually downloading and installing Microsoft .NET Framework 3.0
================================================== =====
1. Click the following link:

Microsoft .NET Framework 3.0
http://go.microsoft.com/fwlink/?LinkID=70848

2. When the file download window appears, please click "Save", and follow
the directions to save it on the Desktop. After downloading the Microsoft
..NET Framework 3.0 setup file on your Desktop, double-click to manually
install it.

3. After completing the above steps, please restart the computer and install
the updates for .NET Framework 3.0 from the following links:

Microsoft .NET Framework 3.0 Service Pack
http://download.microsoft.com/downlo...30SP1setup.exe

Update for .NET Framework 3.0: x86 (KB932471
http://www.download.windowsupdate.co...1a583dbb81.exe

Best Regards,

Calven

Hi, Calven,

I've been following your instructions in response to The Dane's original
question. All was proceeding well until I got to the installation of the
Microsoft .NET Framework 3.0 Service Pack 1. The installation fails, and I
get the error message, "[02/01/08,23:54:38] Microsoft .NET Framework 2.0SP1
x86: [2] Error code 1603 for this component means "Fatal error during
installation."
[02/01/08,23:54:39] Microsoft .NET Framework 2.0SP1 x86: [2] Setup Failed on
component Microsoft .NET Framework 2.0SP1 x86
[02/01/08,23:54:50] WapUI: [2] DepCheck indicates Microsoft .NET Framework
2.0SP1 x86 is not installed.

I had thought that the Microsoft .NET Framework 3.0 stood alone from
previous versions, but I get the sense that this error message means I need
to install version 2.0 as well. How is this going to work?

Thanks so much,
Missysmom


"Calven" wrote:

>
> This issue can be caused by a damaged .NET Framework 2.0 installation. In
> order to resolve the issue, we have to remove/reinstall previous versions of
> .NET Framework. Based on its current status, I suggest trying the following
> troubleshooting steps.
>
> Step 1: Download Microsoft Windows Installer Cleanup Utility
> =============================================
> 1. Please visit:
> http://download.microsoft.com/downlo...BD/msicuu2.exe
> 2. Save the file on your Desktop
> 3. Double click the file msicuu2.exe on the Desktop to install this tool on
> the computer.
>
> Step 2: Remove the previous version of .NET Framework 2.0 if installed.
> ================================================== ===
> 1. Click Start -> (All) Programs->Windows Installer Clean Up.
> 2. Please locate and remove all .NET Framework products.
>
> After removing .NET Framework components, let's reinstall .NET Framework 3.0
> and its updates.
>
> Step 3: Manually downloading and installing Microsoft .NET Framework 3.0
> ================================================== =====
> 1. Click the following link:
>
> Microsoft .NET Framework 3.0
> http://go.microsoft.com/fwlink/?LinkID=70848
>
> 2. When the file download window appears, please click "Save", and follow
> the directions to save it on the Desktop. After downloading the Microsoft
> .NET Framework 3.0 setup file on your Desktop, double-click to manually
> install it.
>
> 3. After completing the above steps, please restart the computer and install
> the updates for .NET Framework 3.0 from the following links:
>
> Microsoft .NET Framework 3.0 Service Pack 1
> http://download.microsoft.com/downlo...30SP1setup.exe
>
> Update for .NET Framework 3.0: x86 (KB932471)
> http://www.download.windowsupdate.co...1a583dbb81.exe
>
> Best Regards,
>
> Calven
>
>

The issue can occur if the damaged .NET Framework component has not been
removed properly. At this time, let’s use another tool to finish the removing
job in an easier way, the tool can find the related file and remove them
automatically.

Let us refer to following steps:

Remove .NET Framework using removal tool
================================
1. Please download the tool from the following link:

http://astebner.sts.winisp.net/Tools...eanup_tool.zip

2. Please save the zip file (dotnetfx_cleanup_tool.zip) from the above link
to the local Desktop and extract it.
3. Double click cleanup_tool.exe to run the tool.
4. Please follow the instructions given.
In the "Product to cleanup:" box, please select ".NET Framework - Both
versions".
5. Click "Cleanup Now" button.

After that, please perform the following suggestions to reinstall .NET
Framework 2.0 and its updates.

Reinstall .NET Framework Version 2.0 Redistributable Package and its updates
================================================== ========
Please download and install the following updates in order.

Microsoft .NET Framework Version 2.0 Redistributable Package (x86)
http://download.microsoft.com/downlo...a/dotnetfx.exe

Microsoft .NET Framework 2.0 Service Pack 1 (x86)
http://download.microsoft.com/downlo...x20SP1_x86.exe

Note: When the "File Download" window appears, please click "Save", and
follow the directions to save the file on the Desktop. After downloading all
the setup files, please double-click on each one to install them.

Manually downloading and installing Microsoft .NET Framework 3.0
================================================== =====
1. Click the following link:

Microsoft .NET Framework 3.0
http://go.microsoft.com/fwlink/?LinkID=70848

2. When the file download window appears, please click "Save", and follow
the directions to save it on the Desktop. After downloading the Microsoft
..NET Framework 3.0 setup file on your Desktop, double-click to manually
install it.

3. After completing the above steps, please restart the computer and install
the updates for .NET Framework 3.0 from the following links:

Microsoft .NET Framework 3.0 Service Pack 1
http://download.microsoft.com/downlo...30SP1setup.exe

Update for .NET Framework 3.0: x86 (KB932471)
http://www.download.windowsupdate.co...1a583dbb81.exe


Best Regards,

Calven

Me too.

"The Dane" wrote:

> I get this code when trying to install update for Microsoft .NET Framework
> 3.0 Service Pack 1 (KB929300)
> It fails to install the update.

I got this error code too but then when I tried to install the optional
update Language Pack for Microsoft .NET Framework 3.0:x86.
I've asked Microsoft what this error means but they didn't know. So I
tried to install it manually and then I got the notification that I've
got a newer version of the program on my PC, so the update didn't
install.
Until now I still don't know what 0x13EC means and why I get this update
offered by Windows Update.
--
Jan Kuipers




"crazy chic 001" wrote:

> Me too.
>
> "The Dane" wrote:
>
> > I get this code when trying to install update for Microsoft .NET Framework
> > 3.0 Service Pack 1 (KB929300)
> > It fails to install the update.

"Jan Kuipers" <> wrote in message news:...
>I got this error code too but then when I tried to install the optional
> update Language Pack for Microsoft .NET Framework 3.0:x86.
> I've asked Microsoft what this error means but they didn't know. So I
> tried to install it manually and then I got the notification that I've
> got a newer version of the program on my PC, so the update didn't
> install.

> Until now I still don't know what 0x13EC means and why I get this update
> offered by Windows Update.


http://forums.techarena.in/windows-update/726335.htm

(Live Search for
0x13EC 5100
)


So far it seems nobody who has reported this symptom has tried any diagnosis.


Hmm... but apparently the "heavier hammer" approach has been successful...


http://social.msdn.microsoft.com/for...-7f0124488373/

(same search)

<quote>
I had the same problem and installing 3.5 manually before the VS installed worked for me.
</quote>



Good luck

Robert Aldwinckle
---



> --
> Jan Kuipers
>
>
>
>
> "crazy chic 001" wrote:
>
>> Me too.
>>
>> "The Dane" wrote:
>>
>> > I get this code when trying to install update for Microsoft .NET Framework
>> > 3.0 Service Pack 1 (KB929300)
>> > It fails to install the update.
>

Hi Robert, the first link:
http://forums.techarena.in/windows-update/726335.htm I had already found
but there it's about the .Net Framework 3.0 itself and not about the
update Language Pack.
The second link:
http://social.msdn.microsoft.com/for...0-7f0124488373
doesn't work at the moment because of maintenance, so I look later.
But I still wonder why Microsoft doesn't know the error code. By the
way, in Software I find that I already have .Net Framework 3.0 Service
Pack 1 Language Pack - NLD and also version 3.5 with Dutch language
pack.
So I begin to think that I don't need that optional update for 3.0
because I have a newer version 3.0 SP1. This explains maybe why I get
that message that I've got a newer version of the program on my PC when
I try a manual installation. And it may be that Windows Update gives an
unnecessary update?!
--
Jan Kuipers




"Robert Aldwinckle" <> wrote in message
news:#FW$:

> "Jan Kuipers" <> wrote in message news:...
> >I got this error code too but then when I tried to install the optional
> > update Language Pack for Microsoft .NET Framework 3.0:x86.
> > I've asked Microsoft what this error means but they didn't know. So I
> > tried to install it manually and then I got the notification that I've
> > got a newer version of the program on my PC, so the update didn't
> > install.
>
> > Until now I still don't know what 0x13EC means and why I get this update
> > offered by Windows Update.
>
>
> http://forums.techarena.in/windows-update/726335.htm
>
> (Live Search for
> 0x13EC 5100
> )
>
>
> So far it seems nobody who has reported this symptom has tried any diagnosis.
>
>
> Hmm... but apparently the "heavier hammer" approach has been successful...
>
>
> http://social.msdn.microsoft.com/for...-7f0124488373/
>
> (same search)
>
> <quote>
> I had the same problem and installing 3.5 manually before the VS installed worked for me.
> </quote>
>
>
>
> Good luck
>
> Robert Aldwinckle
> ---
>
>
>
> > --
> > Jan Kuipers
> >
> >
> >
> >
> > "crazy chic 001" wrote:
> >
> >> Me too.
> >>
> >> "The Dane" wrote:
> >>
> >> > I get this code when trying to install update for Microsoft .NET Framework
> >> > 3.0 Service Pack 1 (KB929300)
> >> > It fails to install the update.
> >

"Jan Kuipers" <> wrote in message news:%...
> Hi Robert, the first link:
> http://forums.techarena.in/windows-update/726335.htm I had already found
> but there it's about the .Net Framework 3.0 itself and not about the
> update Language Pack.


Ok. I was just using it as an example. Essentially I'm suggesting
that you to search for both the hex and decimal values of that code
in *any* diagnostic file which the update creates or changes.



> The second link:
> http://social.msdn.microsoft.com/for...0-7f0124488373
> doesn't work at the moment because of maintenance, so I look later.


The main message from that example is that doing the relevant manual install
apparently worked for one user. That is a common observation for many
types of updates.

There are several reasons why it succeeds. If there is a permissions issue it may be
that the manual installer is more authorized than the Windows Update service.
If the auto update is packaged as an minimal patch that procedure may not work
as smoothly as a full downloaded update. Most significantly IMO its diagnostics
are usually clearer than they are when obscured by the Auto Update machinery.
And in that case too, the user becomes more aware that a problem installing a
manually downloaded patch is more associated with the product being updated
than the distribution software (such as Windows Update); so then they are more
likely to try finding others with more specific experience in other more relevant
newsgroups and forums.


> But I still wonder why Microsoft doesn't know the error code.


One of the links I found explicitly acknowledged that 5100 = Asia
That could be relevant but I suspect it could also be a red herring.
That's why I emphasized that *context* is more important than the
value of a return code.



> By the
> way, in Software I find that I already have .Net Framework 3.0 Service
> Pack 1 Language Pack - NLD and also version 3.5 with Dutch language
> pack.
> So I begin to think that I don't need that optional update for 3.0
> because I have a newer version 3.0 SP1. This explains maybe why I get
> that message that I've got a newer version of the program on my PC when
> I try a manual installation. And it may be that Windows Update gives an
> unnecessary update?!


Perhaps but I suspect what it really indicates is that one of the common modules
has been regressed, so AU is picking a security update which would repair that
damage. Is there a repair option for the thing that you have already installed?

Also, you might get some ideas by checking out Aaron Stebner's blog...

Hmm... you haven't disclosed your OS, have you? ; }
So, if you have Vista this may be of interest...

http://blogs.msdn.com/astebner/archi...ows-vista.aspx

(Search on that blog for
language pack
)

<quote>
One key difference to note is that if you try to run an MSI-based .NET Framework 3.0
language pack setup on Windows Vista, the return code is not artificially mapped to 0
to indicate success like it is in the .NET Framework 2.0 language packs. Instead it will
return code 5100, which according to this list that I previously published is a generic
setup block return code.
</quote>


HTH

Robert
---


> --
> Jan Kuipers
>
>
>
>
> "Robert Aldwinckle" <> wrote in message
> news:#FW$:
>
>> "Jan Kuipers" <> wrote in message news:...
>> >I got this error code too but then when I tried to install the optional
>> > update Language Pack for Microsoft .NET Framework 3.0:x86.
>> > I've asked Microsoft what this error means but they didn't know. So I
>> > tried to install it manually and then I got the notification that I've
>> > got a newer version of the program on my PC, so the update didn't
>> > install.
>>
>> > Until now I still don't know what 0x13EC means and why I get this update
>> > offered by Windows Update.
>>
>>
>> http://forums.techarena.in/windows-update/726335.htm
>>
>> (Live Search for
>> 0x13EC 5100
>> )
>>
>>
>> So far it seems nobody who has reported this symptom has tried any diagnosis.
>>
>>
>> Hmm... but apparently the "heavier hammer" approach has been successful...
>>
>>
>> http://social.msdn.microsoft.com/for...-7f0124488373/
>>
>> (same search)
>>
>> <quote>
>> I had the same problem and installing 3.5 manually before the VS installed worked for me.
>> </quote>
>>
>>
>>
>> Good luck
>>
>> Robert Aldwinckle
>> ---
>>
>>
>>
>> > --
>> > Jan Kuipers
>> >
>> >
>> >
>> >
>> > "crazy chic 001" wrote:
>> >
>> >> Me too.
>> >>
>> >> "The Dane" wrote:
>> >>
>> >> > I get this code when trying to install update for Microsoft .NET Framework
>> >> > 3.0 Service Pack 1 (KB929300)
>> >> > It fails to install the update.
>> >
>