O' Tellos, Heed My Call

[LeftEyeNine]

Hello fellows,

Since I got my 2x3 GB Triple DDR3 pack today, I had to move onto Windows 7 x64 today.

And, among my to-do list was installing .NET Framework 4 since some programs tend to look for it in order to run.

But towards the end of the installation, I got a sudden BSOD and had to restart.

When I logged back on, it was how I had predicted it to be: .NET Framework 4 installation is in somewhere like Purgatory, nor it is installed neither could be removed.

I got a dump of system files in my hands now that will bug me from time to time, I guess and I want a way out of this for I can not handle another OS refresh after my 3rd shot at it tonight.

Help please, thanks in advance.

[Whacker]

You probably need to do a burn-in. The past 2 systems I've built have all needed several days (no less than 3 IIRC) non-stop 24/7 of full ram burn-in using a bootable CD running Memtest+. Once the ram "acclimates" to your system and mobo, it should be smooth sailing and should stop giving errors. Also make sure that your RAM is being run at manufacturer specified speeds and settings in BIOS.

[LeftEyeNine]

I guess I misplaced myself about the situation.

I'll be running Memtest+ in half an hour or so as I go to bed. But I want to re-install .NET Framework 4, but it's not happening.

If it was some other regular program, deleting its folder and making a registry cleaning via TuneUp Utilities would do the trick but, you know, this (redist) is something more entangled with the OS itself.

[Tellos Athenaios]

Was it installed via Windows Update? Try reverting the update (there will be a link to a list of installed updates on the side of the Control Panel item on Windows Update)...
Do you have a restore point just before you attempted to install (you should have if this was installed through Windows Updates)? Try reverting to that restore point.
Does it show up in the Control Panel under the installed programs? If yes, try uninstalling it from there.
Do you still have old cruft in %TMP% or %TEMP% (case insensitive) ? Try deleting anything you can in those locations. (you can type that in Windows Explorer and it should navigate to the directories these system variables point to.)
Do you still have old cruft in C:\Temp or C:\Tmp (case insensitive) ? Try deleting anything you can in those locations as well.

By the way .NET libraries are located in C:\Windows\assembly on a Win 7 Professional 64bit installation. Don't ask me how I know that. :sweatdrop:

[LeftEyeNine]

By the way .NET libraries are located in C:\Windows\assembly on a Win 7 Professional 64bit installation. Don't ask me how I know that. :sweatdrop:

Blowing up whole content would... ?

(I tried to install it via its redist installer downloaded from Microsoft Download, not Windows Update. When I tried to remove the one with "Extend blabla" (?) next to it, it said it couldn't find the files to do it and offered a removal of the related entry. When I wanted to re-run the installer, it said "the framework itself or a higher version is already installed" and stalled)

[Tellos Athenaios]

Blowing up whole content would... ?

Remove a significant number of runtime libraries from your system, though the OS itself *should* continue to work fine. However the registry would be unaffected and other programs might no longer run.



(I tried to install it via its redist installer downloaded from Microsoft Download, not Windows Update. When I tried to remove the one with "Extend blabla" (?) next to it, it said it couldn't find the files to do it and offered a removal of the related entry. When I wanted to re-run the installer, it said "the framework itself or a higher version is already installed" and stalled)

If that is a MSI file (or you can open it with something like 7zip and extract the MSI file from it) then you can use the following from the commandline to repair the installation:


msiexec /f amus the_file.msi

See: http://msdn.microsoft.com/en-us/library/aa367988(VS.85).aspx

EDIT:
The code posted does the following:
Run the msi package installer included with Windows, and instruct it to:
(1) Re-install all files in the MSI package regardless of whether or not a file exists at the location it will be installed to
(2) Rewrite all machine specific registry settings for the MSI package
(3) Rewrite all user specific registry settngs for the MSI package
(4) Re-install any shortcuts for the MSI package if applicable.

[LeftEyeNine]

Well, I placed the file under C root and typed "msiexec /f amus c:\dotNetFx40_Full_setup.exe". It only came up with a window that describes a set of parameters available.

My DOS, hence commandline knowledge failing me ? ~:(

[LeftEyeNine]

The content of the .exe is a bunch of directories and files which are run by a setup.exe. :/

[LeftEyeNine]

Oh.

Who could guess a utility by the name dotnetfx cleanup tool could exist ? Not me, but hey, it works.

Thanks for the brainstorm. :bow: