HAY GUYS

Excrono · Local time: Dec 10, 2007, 10:55 PM

I'm pretty sure it won't help, but you could try trusting one of the .NET assemblies (executables) and see if the problem is persistent. This can be done via the Microsoft .NET Framework x.x Wizards in Administrative Tools (on 2k/XP). Simply double click on "Trust and Assembly" and go through the wizard. When prompted for a file path, enter the full path to the program executable, then set the security level for the app to low. Aside from that, I would completely uninstall all version of .NET Framework, then go through and remove/rename all .NET folders and registry entries. At that point, a re-install of the latest version should take care of it.

Jam it back in, in the dark.

Excrono · Local time: Dec 11, 2007, 06:36 PM

Originally Posted by Zergrinch

I believe he tried to uninstall and reinstall, to no avail. Short of a reformat, I'm not quite sure how to advice RYU. I'm pretty sure that option is too drastic, and there's a less pain-in-the-ass fix

I understand that, however I also recommended he go through afterward and clear out any remaining .NET program directories and registry entries. Often times, the MSI package will leave a set of files (usually to preserve existing settings in the event of a re-install.) When you start uninstalling/re-installing newer versions problems can arise. Removing all traces of .NET framework will ensure (hopefully) that he is starting from a clean slate when he tries installing the latest version again.

There's nowhere I can't reach.

Excrono · Local time: Dec 11, 2007, 10:47 PM

That sounds like something a WMI repository rebuild could fix. This is easily accomplished by stopping the Windows Management Instrumentation service, and then renaming the following folder: C:\WINDOWS\system32\wbem\Repository to C:\WINDOWS\system32\wbem\Repository.old. After you do that, restart the WMI service and then reboot your system. It will be automatically rebuilt at this point, and you should be able to connect to WMI. Also check the application and system logs afterward for any errors pertaining to applications being unable to reload their counters into WMI and repair them if necessary. If you cannot rename the above folder due to it being in use even after stopping the service, boot into safe mode and rename the folder.

This thing is sticky, and I don't like it. I don't appreciate it.