Microsoft .NET Framework 3.0: x86 (KB928416)

[Caroline]

This update will not install. I get the error message: Error Code: 0x643. I
thought maybe I had to uninstall NET Framework 3.0, but it is not listed in
Add or Remove Programs. Any ideas as what to do next?
Thanks

[MotorHome429]

I am suffering the exact same problem.CAN ANYONE help. Microsoft are IGNORING my Questions.

[David Kretchmer]

I have an Identical problem. .NET Framework 3.0 bombs out with an
"Installation Failure - Error Code: 0x643. "

Infact I'm here looking for possible solutions! :)

I'm glad to see that this isn't unique to my PC... I do however need 3.0
Framework for work ... Hope someone can come up with a solution for this
problem.

[David Kretchmer]

I have an Identical problem. .NET Framework 3.0 bombs out with an
"Installation Failure - Error Code: 0x643. "

Infact I'm here looking for possible solutions! :)

I'm glad to see that this isn't unique to my PC... I do however need 3.0
Framework for work ... Hope someone can come up with a solution for this
problem.

[David Kretchmer]

I have an Identical problem. .NET Framework 3.0 bombs out with an
"Installation Failure - Error Code: 0x643. "

Infact I'm here looking for possible solutions! :)

I'm glad to see that this isn't unique to my PC... I do however need 3.0
Framework for work ... Hope someone can come up with a solution for this
problem.

I am recieving this same error message. Has a solution been found?

[SEABEE]

I was getting a similar error. When the initial 3.0 upgrade was released I
accessed it through Windows Update and it showed as being installed
correctly. When the patch came out it constantly failed when it tried to
update. Rather than uninstall the .NET Framework 3.0, I went to the
Microsoft Downloads page, downloaded the program, saved it to my desktop and
installed it from there without uninstalling the program. It can up with the
standard "Repair" or "Remove" option. I choose "Repair" and when it was done
I rebooted. I then went back to the Window Update and applied the patch. Go
figure. it worked flawlessly this time. The only thing I can figure is that
the initial software on the Windows update site is corrupt.

[Chubbs]

I figured out how to install it, go here
http://www.microsoft.com/downloads/d...displaylang=en
Then download, then install. If you get an error on the install (towards the
end is where I got mine) go to add/remove programs and repair it.
This worked for me and hopefully you.

[cedrick]

Add me to the list! I had successfully downloaded "Microsoft .NET Framework
2.0 Service Pack 1 (KB110806) (x86)" as a high priority update. Then
rebooted and tried ot download "Microsoft .NET Framework 3.0: x86 (KB928416)"
as an optional update. Error Code: 0x643, same as the others. Using XP
SP3.

[cedrick]

Can anyone explain why I am only now showing .net framework 2 sp1 and .net
framework 3.0 x86 in my update list? I see others were downloading this at
the beginning of the year! I regularly check for updates, and these 2 just
now appeared? I'm running XP SP3.

Aaron's blog is *the* source for all installation issues with .NET.
If it's not on the blog, use http://blogs.msdn.com/astebner/contact.aspx
to contact him.

For now, see: Updated: what to do if other .NET Framework setup
troubleshooting steps do not help
http://blogs.msdn.com/astebner/archi...7/8108332.aspx

[lfdal]

I've been trying to install new framework 3.x for the last month. My system is XP-Pro fully patched through SP3, quad core, 4 gbyte memory, lots of disk space.

I've also tried the instructions that said to uninstall all versions of .net and start over. Done that via the uninstaller download tool.

I've got v1, v1.1 v2.0 framework etc all installed and patched just fine. System is very stable.

I gave up with downloading via the update site and downloaded the v3 redistributable package.

Symptoms are **always** the same. Never change. I start the installer, it unpacks the files, enters setup and it looks to hang at about 30-40% through. Fatal system hang, to get back into XP I need to boot into safe mode and do a system restore. Every time. There don't appear to be any errors in the log files in my temp directorys.

However the last entry in one of the logs mentions that its messing with the fonts. After the crash and restore, just opening the font directory produces a fatal error, either via explorer or by the control panel.

I found that deleting the fonts that started with global* via a cmd prompt window cleared that problem.

I've been chasing blogs, tech notes, MSDN articles etc for the last month. I'm pretty much at my wits end.

Anyone out there have any advice, I'd sure appreciate it.

Thanks

Thanks for the response.

I loaded the last of the v2 sp 2 items and that went fine. Then I downloaded the entire v3.51 sp as per the website recommendations.

Same problem....

Here's an excerpt from the end of the file named "dd_NET_Framework30_Setup12CD"

The ServiceModelReg tool has completed successfully.
05/04/09 23:05:36 DDSet_Status: Process returned 0
05/04/09 23:05:36 DDSet_CARetVal: 0
MSI (s) (40:60) [23:05:36:328]: Executing op: ActionStart(Name=RegisterFonts,Description=Registering fonts,Template=Font: [1])
05/04/09 23:05:36 DDSet_Exit: RunProcess ended
MSI (s) (40:60) [23:05:36:328]: Executing op: ProgressTotal(Total=4,Type=1,ByteEquivalent=1800000)
MSI (s) (40:60) [23:05:36:328]: Executing op: SetTargetFolder(Folder=C:\WINDOWS\Fonts\)
MSI (s) (40:60) [23:05:36:328]: Executing op: FontRegister(Title=Global Monospace,File=GlobalMonospace.CompositeFont)

This is the normal failure point. I had to execute a system restore to get back to where I was prior to the v3.51 stuff, as usual.

I'm going to post this before I look in the font directory because I imagine as soon as I do the system will hang until I restart and delete Global series of fonts. Again.

Should I just reformat the drive and reinstall?

Thanks again for the response.

I did leave a message for Aaron and also had YiChun Chen get back to me.

I've since cleaned the temp directory, reran the install (still messed up in the same spot), and run the collect utility to capture the logs which I uploaded to skydrive.

I'm keeping my fingers crossed. I've been at this for so long my eyes are already crossed.

Finally threw in the towel and reformatted my C: partition and did a clean install.

Everything worked, 1st time.

Didn't have much loaded on there and probably should have doen it sooner, just frustrated me that my 5 year old system updated fine and my new (5 month old) system wouldn't.

Was going to work through a list of differences in the software to see what the most likely culprit might have been but I really doubt that will be fruitful, or time effective.

[MowGreen]

You're mowst welcome. I know a little about .NET and a lot less
concerning Fonts. Perhaps you should contact Aaron prior to wiping and
reinstalling to confirm your suspicions and save yourself some time ?

[MowGreen]

Sorry to hear that you had to resort to the most drastic of steps in
order to get this issue resolved.
..NET framework installation issues can be frustrating, as you've
witnessed. Not sure what occurred prior to this but strongly suggest one
be *extremely* cautious when running disk and registry 'clean up' tools
as they are known to cause .NET update and framework installation issues
that eventually lead to either the uninstallation of all installed .NET
runtimes, running the Windows Installer Cleanup tool or Aaron's tool,
and then reinstalling the uninstalled frameworks, or a
reformatting/reinstalling of the OS.
IOW, a registry tool should never be run unless one fully understands
what it's doing and can do what the tool does manually.
Disk cleanup tools should only be used when one can *easily* restore
it's backups and it's been configured to leave installation source files
alone.

And then there's 'security software' that is so effective in guarding
the OS that legitimate file operations are interfered with, required
registry info, and/or files are subsequently missing .

[Jac]

About the same with me. I regularly check for updates (XP Prof SP3).
A few months ago I had a lot of trouble installing the latest version of
..NET Framework. Chased all messages in this forum, and at wits end removed
alle .NET stuff, started all over, which took me about half a day to get as
far as version 3.5.
To my surprise MS Update comes up with a Language Pack for Framework 3.0,
and it does not install (error message ox13EC).
So I chased this forum once more, found the solution "Redistributable",
downloaded it and ran it. Installation stopped, saying, that I have a newer
version on my computer (apparently 3..5).
So, I wonder why MS Update comes up with an update for 3.0, when I have 3.5
on my computer.
Secondly (yes, I'm complaining), why makes Microsoft software that is
apparently so complicated, that they do not understand it themselves any more.