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 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).
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
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?
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.
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
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.
but apparently the "heavier hammer" approach has been successful...
http://social.msdn.microsoft.com/for...-7f0124488373/
(same search)
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?!
I've been reading a lot of articles
about the .NET Framework.
But there is still one question on my side: why does Windows Update
offer an optional update (a Language pack) for .NET Framework 3.0 while
I don't have version 3.0 on my PC but 3.0 Service Pack 1?
That doesn't make sense to me.
(Using XP Pro with SP3)
Typically you can't have a Service Pack for a product without first having
the product.
In any case I gave you a possible reason.
Just to be sure I've tried a manual installation again of the optional
update. And again I got the message that the update couldn't be
installed because I have a newer version of the program installed.
So I phoned to Microsoft and finally they said that I don't need the
update at all. Also they didn't know why this optional update was
offered.
I understood that the Dutch Microsoft has no influence at the updates
which are offered by the US Microsoft. (And I thought that the Dutch
Windows Update came out of the Netherlands but that's not the case?!)
So I leave it this way. But thanks anyway!
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 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.
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.
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...
I still suspect that that means that part of the update (e.g. a module) has been regressed.
The manual install may be simply testing the registry values which say whether a
superseding update has been applied without testing whether all of it is still in place.
AU would be testing not just registry values but module versions as well.
You were right Robert. There was something not installed correctly
regarding to the .NET Framework.
Finally I have uninstalled all the versions from .NET Framework. It took
8 hours to get it all fixed again so I'm glad it's ready. I noticed that
it is very important to reboot again every time after a change has been
made. http://support.microsoft.com/kb/923100/en-us was the article I
used.
And now Windows Update gives no error code anymore.
Thanks for your advice.
I want to say because Net Framework 2 is worng version = 2.0.5. I found
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727. Currect version is Net
framework 2 Build 50727
But i can not find old version of Net Framework for ATI Catalyst
Control Center 8.12 Version. Because CCC was failed by worng version:
2.0.30276 from Net Framework 2 ( old version ).
A new version was released from AMD / ATI that it happens about worng
version of Net Framework.
Have you version older than Net Framework 2.0.5 ?
I am using ATI Radeon HD 2600 XT on my computer.
But my games won't start because Ati ccc 8.12 need old version of Net
Framework.
Thanks for tool clean for Net Framework. Now my computer works real and
cool like new computer...
I got error code 0x13EC (5100) too when I tried to install "Microsoft .NET Framework 3.0: Language Pack for x86 (KB928416)". I tried uninstalling all versions of .NET framework and reinstalling. The "Language Pack" still failed with same error code...
After reinstalling everything but this "3.0 Language Pack", I tried manually uninstalling the "2.0 Language Pack". After that the "3.0 Language Pack" installed with no error. "3.0 Language Pack" actually installs "2.0 Language Pack" too, just as "Microsoft .NET Framework 3.0"-installer will install "Microsoft .NET Framework 2.0" if not already installed.
Hooplehead Alert.