RE: One Solution to .NET Framework Service Pack Install Errors
- From: raquelha <raquelha@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 7 Dec 2008 12:00:01 -0800
Hi. I just wanted to put a quick note here that I actually LOVE using the
command prompt (DOS) but didn't know where that stupid dotnetfx.exe file was
& I was basically wasting time looking for it discovering other fun things to
do when an idea hit me......I decided to perform a search for the file!!! I
know, brilliant of me....the search found the file very fast so I immediately
went to the directory storing it, did exactly as posted- dotnetfx.exe
/t:%temp% /c:"msiexec.exe /fvecms %temp%\netfx.msi"
I again ran windows update which of course found only that one program to
update (because I've hidden the ones I do NOT want such as IE7...ugh...hate
it) the update also downloaded and installed BEAUTIFULLY as stated!!
Thank you very much......
If you don't know where the heck the dotnetfx.exe file is, just use search
from the start menu....amazing how it works sometimes.
Thanks again. Good Luck to others. And if you still can't get it to work, to
hell with it, install a later version! :)
--
blh
"Darkw0lf" wrote:
oops, accidently didn't type anything in the last one :oP.
1. Yes, i've had the same problem for as long as others in the post...
2. Yes, Eric57's solution worked for me, Yay!
anywho, i just wanted to clarify Eric's instructions for people like me who
didn't auto assume some basic stuff that help make the fix work :oP
When you download the redistributable (of whichever you pick), Run the
self-extracter, then choose Save, not Run, for the dotnetfx.exe file,
otherwise you can't pick out dotnetfx.exe from within to somewhere where you
can easily access it from the Command Prompt; I chose My Downloads right in
my c/: drive (heck, not like I put anything in there anyway...). If you
allow dotnetfx.exe to self-install, there will be no EXE to access with
Command Prompt; you must manually choose somewhere to save, and then, using
Eric57's command line, run the file yourself.
Hope I haven't been too confusing ;oP
"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.htm <--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/netframework/downloads/updates/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
- Prev by Date: Error Code 0x80092004
- Next by Date: Error #: 0x8DDD0018
- Previous by thread: Error Code 0x80092004
- Next by thread: Error #: 0x8DDD0018
- Index(es):
Relevant Pages
|
