XP trouble

aeromed202

aeromed202

SOH-CM-2014
I have been told by MS that my .Net Framework is corrupted so I cannot install any more MS updates. Cleaning and re-installs have not worked and they can only recommend a re-formatting. Now this is what I am thinking, if I could get a second hard drive is it possible to move progams over then tell the OS that that is the new C drive? I could then fix up the old one without having to start from scratch. Even if I got a new hard drive and couldn't move programs over I could at least install them over time while doing normal things off the old one right? Is this possible?
 
Rather than just attempting to reinstall the .NET packages, have you tried removing them first via the Control Panel, Add/Remove Programs?

Also, which version of .NET are you installing? I had some issues, but reinstalling the latest version (4.0 iirc) seemed to fix things.
 
No, you cannot simply copy your stuff to a new drive and tell windows to looks elsewhere. It was possible on win98 and earlier but XP maintains critical running info in the registry that will be lost when you reinstall windows (ain't microsoft grand). Alot of times the un-installer will crash if the apps files are missing or corrupt but it's worth the effort to try it first. You also may get lucky if you have a backup of the registry done before .NET got corrupted. Take a look, and try restoring it if you have one.

In extreme last resort situations (this doesn't work everytime as windows XP and later appends data to certain system DLL's stuff from newer update packages, and that stuff can't be removed unless you overwrite the DLL with an earlier version)- I use the 'crowbar' method of update removal: Boot into safe mode, take your packages source CAB file and unzip it (winzip) to a temporary directory, do a search on your harddrive for every file unzipped to the temp folder, and delete them (don't delete the files in the temp directory), then reboot into normal mode.

Ya may end up with some funky settings when you're done but you can normally fix them in control panel. NOW try reinstalling the item.

I've only had to do 1 reinstall of windows in my life (because MS tech support had gotten my OS so messed up I had no other choice) and know a few tricks MS never thought of to keep the OS running. Good luck to you.
 
I have fs on a separate hd inside the box. the os is on c:, and it got corrupted and .net was one of the issues.

I was able to do a "maintenance reinstall" I think it is called, of the xp os without wiping the c: drive, and so far things have worked well. It also allowed me to update everything, service packs, .net frame, etc.

if you have your xp disc, it's worth looking into.
 
First I didn't know there was a .NetV4 so I installed that and used REVO to get rid of all scraps of other .Net versions. Hope that was good to do. So I am now waiting for a new update to come along and see what happens. There are 3 outstanding ones, two that deal with .Net versions older than V4 so I guess I don't care and one that is for something like Word 2003 which I also guess I don't care much about. I checked them to not keep trying to install for now just so I don't have to see that red shield anymore. The test will be when the next updates arrive. If they behave then I will consider myself lucky.

I am still inclined to add another HD if only because in the long run I need the space and I can maybe fudge around a full reformat. As far as backup registries I suppose I must have them somewhere. Where would I look though? Also aren't there programs that auto backup registries when you use them? I also never thought to try System Restore.
 
A couple of notes:
1) various programs use different versions of .net without overlapping so if you are using things like BGLXML you may end up having to reinstall net V2.0 or some other variant. There's a thread recently on here discussing the subject.

There are programs like Acronis True Image that will allow you to 'clone' your drive and computer settings ( including the registry) and then copy it all or partly back to a new drive with a high percentage of reliability (since it saves the registry bits too). That module is intended for cases where you have to replace any, but primarily the OS drive.

True Image has lots of other modules like a backup utility, re-partitioning on a live drive on-the-fly, etc. It's my preference and a few others here will agree.

http://www.acronis.com/homecomputing/products/trueimage/

Rob
 
Have mutiple installs

I'am a bit confused on this issue.I checked in control panel and have net.1.1,net.2.sp2.net.3.sp2,and finalliy net 3.5sp1 all installed with no problems running FS9.
Should I have uninstalled all but the latest net 3.5 sp1?I hate to mess with something that if it ain't broke don't fix it kind of thing.Thanks ,sorry if I'am misunderstanding this thread.
 
hurricane3 said:
I'am a bit confused on this issue.I checked in control panel and have net.1.1,net.2.sp2.net.3.sp2,and finalliy net 3.5sp1 all installed with no problems running FS9.
Should I have uninstalled all but the latest net 3.5 sp1?I hate to mess with something that if it ain't broke don't fix it kind of thing.Thanks ,sorry if I'am misunderstanding this thread.
Click to expand...

They can cohabitate quite nicely and, for some users, are needed for other programs to work. New versions do not necessarily (often don't) update earlier versions, they just contain additional code for diff. purposes.

The problem here may be that the one MS uses for the "Updates" function got FUBARed and as aeromed and I've found they can be a pain to get fixed. Fortunately, in my case, I was in the process of changing OS drives at the time so it got cured that way (with a re-install and update) but I had to go back and find the earlier .net bits myself.
 
ok that clears things up(mostly)

Thanks for the reply ,that clears things up ,except does that mean if you have a corrupt update you have to uninstall and reinstall the earlier updates? You'd have to start with the first one cause you wouldn't know what needs what. Also what about a new install,wouldn't it install the latest update,how would you know if you need older updates?
 
hurricane3 said:
Thanks for the reply ,that clears things up ,except does that mean if you have a corrupt update you have to uninstall and reinstall the earlier updates? You'd have to start with the first one cause you wouldn't know what needs what. Also what about a new install,wouldn't it install the latest update,how would you know if you need older updates?
Click to expand...

The subject is the .Net Framework, not Windows in general. One of the functions of .net is the handling of the Windows Updates and checking what is required for your system (stuff that is pushed out to systems across the internet like the Tuesday patches). As long as you can get the Windows updates, don't worry about it. If another program gives you an error referring to a .net version then you may have to do some digging and work.

If it's not broke...

The discussion here is that his .net framework (files) has been corrupted somehow (ask someone with higher powers than me for the "how and why") and it's inhibiting his ability to get new Windows updates or install them.

Aeromed,
have you tried PMing txnetcop and asking Ted if he can give you some advice? he's one of the most knowledgeable ones around here.
 
From my experience and MS's literature, MS.NET V2 family had issues and the service packs were NOT all inclusive, so they REQUIRE all updates be installed in order starting with the version 2 basic .NET package, and ending with .NET 3.5.

This is what I've installed on my 3 gaming rigs and never updated beyond 3.5, but XP sp3 and later may require later versions of the .NET package. I tend to agree with SrG, 'if it aint broke, dont mess with it'.
 
For clarity, let me reiterate what Rob said - .NET Framework versions prior to v4 are totally independent of each other. If a program was written to work with a particular version, then that program will work on your computer if and only if you have installed that version of the Framework, regardless of whether any other versions are installed. Version 3.5 of the Framework is NOT an update of version 2 in the way that most other software gets updated with new features and fixes.

Now, with .NET Framework v4, Micro$oft have had a change of policy and capability. Version 4 is supposed to be capable of running any programs created to work with previous versions of the Framework. At the same time, their announcement included a strongly worded caveat that this backward compatibility can be broken. As a .NET developer, my interpretation is that I will continue to develop my current programs under v3.5 and publish them as such. Only then will I consider installing v4 and checking whether the programs continue to work correctly.

There is also NO relationship between the .NET Framework version and the o/s under which it's running. That is, an o/s like WinXP SP3 does not need a particular version of the Framework - it's the programs you're running under WinXP SP3 that dictate which versions of the Framework you need to have installed. Obviously, running a particular version of the Framework demands a certain set of o/s features to work, so that, for example, you cannot run version 3.5 on any version of Windows prior to XP,
hope that helps,
Ro
 
Several more replies since I last checked, thanks for the advice. The MS person I was working with said each .Net version is independent of the priors. I pointed out that some of the failing updates were for older versions and do those matter if I am trying to re-install a later one, 3.5. I took what she said as good enough evidence to delete all versions and remnants then installed version 4, which was more than 3.5 managed to do. It errored repeatedly during installation attempts. She never mentioned version 4. I'm still in the pattern waiting for an update to see what happens.
 
aeromed, if MS is still working with you on the problem, stick with them until they surrender or fix it. While you are waiting, here's some reading...

this is intended for reference and not necessarily a cure:
*******************************************************

Article ID: 306160 - Last Review: July 2, 2010 - Revision: 7.0
How to repair an existing installation of the.NET Framework

You may need to repair your installation of the .NET Framework if you upgrade your operating system or if the current installation of the .NET Framework becomes corrupted. This article describes how to do so.
http://support.microsoft.com/kb/306160

APPLIES TO


  • Microsoft .NET Framework 2.0
  • Microsoft .NET Framework 1.1
  • Microsoft .NET Framework 1.0
*************************************************************
Here's another article that may lead to another route/solution. Remember, I'm not posting these as potential cures but as areas of study/search.
***********************************************
http://support.microsoft.com/kb/951950
The hotfix registration or the update registration is corrupted

After a hotfix or an update is installed on a Windows Installer-based product, the hotfix registration or the update registration may become corrupted. This problem can occur because of third-party registry cleaner utilities that remove certain registry keys. These keys include the keys that are meant for internal use by Windows Installer. In this case...
***********************************************
There is a huge library of support articles and forum posts but sometimes a bit of searching can dig up the right stuff. Start at the above article and then look around. This is not an uncommon issue so it has been addressed.

Also, as with any other system/subsystem repair, work slowly and methodically and read carefully.

Just as a note for those wondering about all the .net versions, problems have been noted when upgrading to W7 as there seems to be an issue with .net 2.0 so you can see this sort of problem can rear it's ugly head at any time with any system. Once more, as long as all bits are working, leave well enough alone. If you get a problem, use a scalpel, not a sledgehammer.

Just be aware too that this is getting pretty esoteric and may well get the thread moved to a different forum as it's not really a FS2004 issue.

If you have not, or are not interested in tinkering with the sensitive inner workings of Windows, flush all of this from your memory. It will cause headaches, paranoia, tremors and endless frustration.:isadizzy:
 
aeromed202,
I've not previously responded to your predicament because I was not aware that the M$ update process depended on the .NET Framework. Until now, I was willing to take their representative's word (as reported by you), but further thought has raised some doubt.

Last year, I bought two new netbooks which came with WinXP Home pre-installed. In both cases, there were NO versions of the Framework included as part of the build - I downloaded both v2.0 and v3.5 through the Windows Update process (I haven't needed either v1.1 or v4 yet). This makes me wonder how my update process functioned if it was indeed dependent on the Framework.

Which update process do you use (Windows or Microsoft) ? AFAIK, they both depend on an Active-X control, though each uses a different control. I've used both, and unfortunately I have no idea which control is needed for either. There are ways of switching between the two, and, while it may not work, it's possible that making the switch (either way) could just correct the problem.

Alternatively, if your problem gives an error code, then this page may help -
http://support.microsoft.com/ph/6527

Of course, you may have tried the above or found that reference, in which case, I'm sorry I have no other ideas at this time,
Ro
 
for a new install

So say if I buy a new computer and reinstall FS9 and if I have a big enough HD, FSX and other flight sims,how do I know which versions of NET to install?Or will the sims tell me that they need such and such version of Net? I know these may seem like dumb questions,but when my current computer dies,It's ten years old and runs fine(knock on wood) I want to be ready,if I decide to even stay with flight simming.
 
I don't believe that any of the M$ flight sims need any of the .NET Framework versions. If they do, it will be listed in the requirements on the box containing the CDs / DVDs. Similarly, any other program which requires one of the .NET Framework versions should say so on the packaging or in the documentation. AFAIK, at the moment, the only FS add-ons that do need .NET Framework are the Orbx FTX products - there may of course be others which I neither know nor use,
Ro
 
Thanks for the reply

Thanks for the reply,that finally clears things up in my tiny brain.Since I have no Orbix products no worries,I hope.
 
You must log in or register to reply here.
Back
Top