|
Post by silverlining on Nov 12, 2008 14:53:49 GMT
I think I've mentioned this before but I've been having some problems installing some programs because the Microsoft .NET Framework 2.0 on my computer doesn't work properly. The programs that require it either crash while installing or on startup. If I try to reinstall/repair/uninstall the .NET Framework it crashes as well. I've tried to download the .NET Framework 2.0 from Microsoft's site to reinstall it, but that installation crashes also. I've been ignoring this for a while but as I've been itching to install the Wardrobe Wrangler lately it's started to bug me. Does anyone know what I can do to fix this or what might be causing it? Would I be able to use the programs that require the .NET 2.0 if I installed later versions like the .NET Framework 3.5 or whatever the newest is called? Am a bit generally confused.
|
|
CharlieChomper
Long Term Member
Totally Technical Helper
Please call me CharlieChomper (or even CC or "the other CC" on this forum). Thanks!
Posts: 1,756
|
Post by CharlieChomper on Nov 13, 2008 21:31:35 GMT
With the way the .Net framework was designed and has carried on (and with its lead developer and designer having left for Google quite some time ago which brought on some major changes to the framework with each release--just as Microsoft has been making some of these changes to try and keep it proprietary), it's hard for me to really to say for certain that there is any "backwards compatibility" (which would allow it to work without issues involving applications that required past releases of it) with it even now.
Having said that, though, assuming you don't also any past versions of .Net installed as well (such as 1.0 or 1.1) and are not running Vista or XP Media edition or something newer than XP Home or Pro (as XP Media and Vista along with 2003 and the tablet form of XP all come with 2.0 preinstalled and integrated into them), there is a way of manually removing it off your system in hopes of trying to reinstall it again. I would, however, recommend doing a system restore before attempting it as more of a precaution (since .Net has a way of finding itself entrenched into things in ways it otherwise shouldn't).
From the sound of things, either your install of it somehow may have become corrupted or there could have been a failed install of it to begin with.
If there are any specific error messages you're getting however, it may also help in possibly resolving this as different messages and error codes hold different meanings.
|
|
|
Post by silverlining on Nov 13, 2008 21:38:41 GMT
I have regular Windows XP. If I recall correctly, it used to work cos I used to be able to run the Clean Installer and such. I don't have any earlier versions of .Net Framework. So installing the latest one won't help? Is there any way of fixing it in which I don't need to backup and reformat the whole computer? If that's the only way I guess it'll have to wait a few weeks cos I need time to sort out what to save when reformating and stuff.
|
|
CharlieChomper
Long Term Member
Totally Technical Helper
Please call me CharlieChomper (or even CC or "the other CC" on this forum). Thanks!
Posts: 1,756
|
Post by CharlieChomper on Nov 13, 2008 21:42:25 GMT
I can give you the directions on how to go about manually removing it off your system to try and be able to do a "clean" install of it.
The system restore, again, is more of a precaution as some of it does involve getting into the registry.
Edited to add: I forgot to mention that there is a tool out there that can verify the installation state of .Net on your system and whether it's "functional" or not. It was designed more with developers in mind, but it should be useful regardless.
Edit#2: There is also a tool out there that may help with removal of it. However, I admittedly have not tried using it, myself, so I don't know how well it works or what would actually be involved with it.
|
|
|
Post by silverlining on Nov 13, 2008 21:46:16 GMT
How risky is it to do the manual removal without backuping? I don't have an external harddrive atm...
Where would I find said log?
|
|
CharlieChomper
Long Term Member
Totally Technical Helper
Please call me CharlieChomper (or even CC or "the other CC" on this forum). Thanks!
Posts: 1,756
|
Post by CharlieChomper on Nov 13, 2008 22:00:09 GMT
I should probably have just posted that as new versus an edit. The log files will be in your temp directory and if there are problems, will appear as any of the following: dd_depcheck80.txt, dd_dotnetfx20install*.txt, dd_dotnetfx20error*.txt, dd_depcheck_netfx20*.txt. If you have the first service pack for .Net 2.0, it may also be any of these: dd_net_framework20*.txt or dd_NET_Framework*20*LP*.txt As to what's involved with the manual removal, it mainly involves going into the registry and doing a bit of editing of "keys"/entries and deleting of things. However, for that reason alone is why I would recommend a system restore--as I would anytime anything is done in the registry.
|
|
|
Post by silverlining on Nov 13, 2008 22:03:40 GMT
There are several files called something about net framework, but only one which has error in the title. It contains the following error message;
[02/07/08,22:37:21] Microsoft .NET Framework 2.0a: [2] Error: Installation failed for component Microsoft .NET Framework 2.0a. MSI returned error code 1603
several times over, as I've tried installing it loads of times.
|
|
CharlieChomper
Long Term Member
Totally Technical Helper
Please call me CharlieChomper (or even CC or "the other CC" on this forum). Thanks!
Posts: 1,756
|
Post by CharlieChomper on Nov 13, 2008 22:24:44 GMT
Interestingly enough, that specific error code seems to indicate that it was generated by Windows installer versus the .Net's setup tool.
Are you by any chance running "Ad watch" by Lavasoft or as part of Ad Aware?
|
|
CharlieChomper
Long Term Member
Totally Technical Helper
Please call me CharlieChomper (or even CC or "the other CC" on this forum). Thanks!
Posts: 1,756
|
Post by CharlieChomper on Nov 14, 2008 0:44:24 GMT
Sorry for the double post, but I just thought I'd let you know, and didn't want you to miss seeing this, that I have found a much easier method for you to remove the .Net 2.0 framework and to try and reinstall it afterwards and which shouldn't cause you any serious problems to Windows in the process.
|
|
|
Post by silverlining on Nov 14, 2008 7:21:28 GMT
Actually I am running AdAware. Or well, I was but at some point it stopped being able to download the new updates and became sorta useless. It's still installed though and insists on scanning files people send me on MSN even though it's been several months since it's list of viruses and things was updated. Why do you ask? Should I remove it? I'm not using it anyway.
|
|
CharlieChomper
Long Term Member
Totally Technical Helper
Please call me CharlieChomper (or even CC or "the other CC" on this forum). Thanks!
Posts: 1,756
|
Post by CharlieChomper on Nov 14, 2008 7:47:18 GMT
Adaware on its own isn't a problem. There is a specific feature of it (which a user would need to be enabled--by default, it's usually disabled in the free version) called "Ad Watch" which has been known to conflict at times with .Net's installer. However, if you're not using Ad Watch, I wouldn't worry about it and would leave Adaware alone (although, it's always a good idea to keep it updated and running --it's main function is to find and remove malware of the spyware variety as opposed to your anti-viral software (I've yet to really encounter any anti-viral/security software out there that actually does a good job in checking for and removing spyware--at least, none which didn't purchase an existing program to shore things up a bit) which was not designed with that purpose in mind (as there are actually different forms and categories out there of malware).). That said, if you're interested in the easier method of trying to remove the broken form of the .Net framework--so you can clear it off your system safely without having to reinstall--I may have to PM you about as I'm waiting to hear back from someone on this and it isn't something I can post publicly, unfortunately. Edited for clarity and mostly due to bad grammar. I really should know better than to type anything feeling like a half-way zombie.
|
|
|
Post by silverlining on Nov 14, 2008 17:30:14 GMT
No, adwatch is disabled. Also..I do know what the program does, and I also know that it's good to keep it updated. But like I said, mine doesn't work. It won't download new updates, so it's rather useless. I've only had free programs on my computer, and I've never had a problem with malware or viruses.
Anyways, thanks for trying. I'll just get the Clean Installer and all that after I reformat I suppose..
EDIT: Actually, never mind! I decided to try installing the latest .NET Framework anyway and now the programs all work! :D
|
|
CharlieChomper
Long Term Member
Totally Technical Helper
Please call me CharlieChomper (or even CC or "the other CC" on this forum). Thanks!
Posts: 1,756
|
Post by CharlieChomper on Nov 14, 2008 21:49:08 GMT
I ran into similar problems with Adaware 2007 periodically (I lost count of how many times I had to manually remove it as I otherwise couldn't just uninstall and reinstall it--however, that wasn't the programs fault so much as it was Microsoft's decision to update their installer and bad timing for me as to when it happened). However, the current version, 2008 appears to (so far) work better and handle updates better than 2007 did. Regardless, I'm very happy to hear everything was resolved.
|
|