.Net Framework KB patches: The solution!
Solved
black Winny
Posted messages
24
Status
Contributeur
-
louis65 -
louis65 -
Here is the solution to the current problem faced by a significant number of people regarding the crash during the update of .Net Framework by the patches KB886903 and KB887219 from the security bulletin MS05-004 dated February 8, 2005, loaded by Windows Update:
Like many others, I encountered this problem, and no one apparently had the answer (even Microsoft's website says nothing about it!) I struggled like everyone else trying to uninstall .Net Framework through the control panel in order to reinstall it.
The uninstallation of this "unmentionable thing" was not accepted by Windows.
So I tried another method, using Windows Install Cleanup (which is also very interesting) available at this address:
http://support.microsoft.com/kb/290301
Once this Windows Install Cleanup was installed, I, of course, launched it from the Windows Start menu. It apparently allowed me to delete .Net Framework. Great! But the smile quickly disappeared when I saw that it was just an appearance because when I tried to reinstall .Net Framework... it didn't work any better!
So the solution was to search in the registry for the "Classes Root" declaration of .Net Framework. I quickly found it, it is located at:
HKEY_CLASSES_ROOT\Installer\Products\DDE7F2BCF1D91C3409CFF425AE1E271A
I deleted it (don't worry, I knew what I was doing), which allowed me to properly reinstall my .Net Framework followed by the .Net Framework SP1, followed by the updates... including the one that wouldn't go through. And everything works perfectly again now.
As I don't like to keep things to myself, I've written a small procedure for you to follow in three steps:
1. Delete the installation key of .Net Framework in the Registry
For this, there are two options: either you know how to handle Regedit safely by experience (then do step 1.a below) or you don't really want to touch "this thing full of codes everywhere" (then do step 1.b).
1.a: Method using Regedit:
- Open Regedit
- Delete (without making a mistake) the key:
HKEY_CLASSES_ROOT\Installer\Products\DDE7F2BCF1D91C3409CFF425AE1E271A
1.b: Method without using Regedit:
- Open the usual Windows Start menu, then click on "Run"
- In the small window that opens, copy and paste this line completely (without missing a character from the initial R to the final f!):
Reg delete HKEY_CLASSES_ROOT\Installer\Products\DDE7F2BCF1D91C3409CFF425AE1E271A /f
This deletes the key that annoys everyone.
2. Reinstall .Net Framework 1.1
Again, there are two options. If you still have the program dotnetfx.exe somewhere on your machine that is precisely 23710 KB, then go directly to point 2.b below. If you don't have it somewhere on your machine, then do point 2.a first before doing point 2.b.
2.a: If you can't find the program dotnetfx.exe which is precisely 23710 Ko on your machine, you need to find it on a CD from a computer magazine or download it directly from Microsoft's site at this address:
http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842-8157-034d1e7cf3a3&DisplayLang=fr
(note: if you don't have a high-speed connection, go to sleep and come back tomorrow morning...!)
2.b: Now launch the program dotnetfx.exe which is precisely 23710 KB. It will properly reinstall .Net Framework 1.1
3. Reinstall the .Net Framework 1 Service Pack
Again, there are two options. If you still have the program NDP1.1sp1-KB867460-X86.exe somewhere on your machine that is precisely 10453 KB, then go directly to point 3.b below. If you don't have it somewhere on your machine, then do point 3.a first before doing point 3.b.
3.a: If you can't find the program NDP1.1sp1-KB867460-X86.exe which is precisely 10453 KB on your machine, you need to find it on a CD from a computer magazine or download it from Microsoft's site at this address:
http://www.microsoft.com/downloads/details.aspx?FamilyID=a8f5654f-088e-40b2-bbdb-a83353618b38&displaylang=fr
(note: if you don't have a high-speed connection, go relax, have a coffee or a linden tea, and come back in an hour...!)
3.b: Now launch the program NDP1.1sp1-KB867460-X86.exe which is precisely 10453 KB. It will properly reinstall the Service Pack 1 of .Net Framework 1.1. It is quite possible that it will tell you that the SP1 is already installed... Do not pay attention to the warning and reinstall it anyway! No but really!
There you go. Once all this is done, you can serve yourself a nice cocktail (with or without alcohol). The usual installation of your security updates with Windows Update goes smoothly again.
The addresses I provided above are for Windows XP (regardless of the version). If you have Windows Server 2003, you should have no trouble finding the addresses for the equivalent versions on Microsoft's site, knowing that the procedure to follow is exactly the same.
Sincerely
Jacques
(Black Winny)
Like many others, I encountered this problem, and no one apparently had the answer (even Microsoft's website says nothing about it!) I struggled like everyone else trying to uninstall .Net Framework through the control panel in order to reinstall it.
The uninstallation of this "unmentionable thing" was not accepted by Windows.
So I tried another method, using Windows Install Cleanup (which is also very interesting) available at this address:
http://support.microsoft.com/kb/290301
Once this Windows Install Cleanup was installed, I, of course, launched it from the Windows Start menu. It apparently allowed me to delete .Net Framework. Great! But the smile quickly disappeared when I saw that it was just an appearance because when I tried to reinstall .Net Framework... it didn't work any better!
So the solution was to search in the registry for the "Classes Root" declaration of .Net Framework. I quickly found it, it is located at:
HKEY_CLASSES_ROOT\Installer\Products\DDE7F2BCF1D91C3409CFF425AE1E271A
I deleted it (don't worry, I knew what I was doing), which allowed me to properly reinstall my .Net Framework followed by the .Net Framework SP1, followed by the updates... including the one that wouldn't go through. And everything works perfectly again now.
As I don't like to keep things to myself, I've written a small procedure for you to follow in three steps:
1. Delete the installation key of .Net Framework in the Registry
For this, there are two options: either you know how to handle Regedit safely by experience (then do step 1.a below) or you don't really want to touch "this thing full of codes everywhere" (then do step 1.b).
1.a: Method using Regedit:
- Open Regedit
- Delete (without making a mistake) the key:
HKEY_CLASSES_ROOT\Installer\Products\DDE7F2BCF1D91C3409CFF425AE1E271A
1.b: Method without using Regedit:
- Open the usual Windows Start menu, then click on "Run"
- In the small window that opens, copy and paste this line completely (without missing a character from the initial R to the final f!):
Reg delete HKEY_CLASSES_ROOT\Installer\Products\DDE7F2BCF1D91C3409CFF425AE1E271A /f
This deletes the key that annoys everyone.
2. Reinstall .Net Framework 1.1
Again, there are two options. If you still have the program dotnetfx.exe somewhere on your machine that is precisely 23710 KB, then go directly to point 2.b below. If you don't have it somewhere on your machine, then do point 2.a first before doing point 2.b.
2.a: If you can't find the program dotnetfx.exe which is precisely 23710 Ko on your machine, you need to find it on a CD from a computer magazine or download it directly from Microsoft's site at this address:
http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842-8157-034d1e7cf3a3&DisplayLang=fr
(note: if you don't have a high-speed connection, go to sleep and come back tomorrow morning...!)
2.b: Now launch the program dotnetfx.exe which is precisely 23710 KB. It will properly reinstall .Net Framework 1.1
3. Reinstall the .Net Framework 1 Service Pack
Again, there are two options. If you still have the program NDP1.1sp1-KB867460-X86.exe somewhere on your machine that is precisely 10453 KB, then go directly to point 3.b below. If you don't have it somewhere on your machine, then do point 3.a first before doing point 3.b.
3.a: If you can't find the program NDP1.1sp1-KB867460-X86.exe which is precisely 10453 KB on your machine, you need to find it on a CD from a computer magazine or download it from Microsoft's site at this address:
http://www.microsoft.com/downloads/details.aspx?FamilyID=a8f5654f-088e-40b2-bbdb-a83353618b38&displaylang=fr
(note: if you don't have a high-speed connection, go relax, have a coffee or a linden tea, and come back in an hour...!)
3.b: Now launch the program NDP1.1sp1-KB867460-X86.exe which is precisely 10453 KB. It will properly reinstall the Service Pack 1 of .Net Framework 1.1. It is quite possible that it will tell you that the SP1 is already installed... Do not pay attention to the warning and reinstall it anyway! No but really!
There you go. Once all this is done, you can serve yourself a nice cocktail (with or without alcohol). The usual installation of your security updates with Windows Update goes smoothly again.
The addresses I provided above are for Windows XP (regardless of the version). If you have Windows Server 2003, you should have no trouble finding the addresses for the equivalent versions on Microsoft's site, knowing that the procedure to follow is exactly the same.
Sincerely
Jacques
(Black Winny)
Configuration: XP SP2 - Firefox 1.0 - Thunderbird 1.0 - 2 machines sharing a Wifi Linksys Wag54G - All software in Open Source or Freeware (except XP, Namo Web Editor 6, and Securitoo, which were purchased).
48 réponses
- 1
- 2
- 3
Suivant
Hello Titia 1307 Normally it should work with Vista, go to this address, https://forums.commentcamarche.net/forum/affich-1315567-net-framework-les-patchs-kb-la-solution#newanswer
Problem installing update KB951847 Framework 3.5 [Resolved]
Best answer: I had the same problem. But I just had to manually install .NET framework 3.5 SP1 and then the update happened automatically through Windows Update. You can download .Net framework 3.5 SP1 here: http://www.microso
Forum
Problem installing update KB951847 Framework 3.5 [Resolved]
Best answer: I had the same problem. But I just had to manually install .NET framework 3.5 SP1 and then the update happened automatically through Windows Update. You can download .Net framework 3.5 SP1 here: http://www.microso
Forum
Thank you very much for the explanations.
I knew I had to remove the key, but I didn't know which one it was.
Additionally, I didn't know about the .NET Framework service pack.
Thank you again.
I knew I had to remove the key, but I didn't know which one it was.
Additionally, I didn't know about the .NET Framework service pack.
Thank you again.
We are in 2008, and here I am (once again) facing the same installation issue with .NET Framework 1.1 SP1 (Windows XP SP2).
For your information: I didn't want to do all those manipulations mentioned above because my workstation was quite sensitive for work.
I found a solution that resolves everything in two seconds: add the P:\
In a cmd: "subst p: d:\"
This creates a fake P:\ that points to my D:\ (real drive).
This resolves my problem because the XP system was still looking for the mapped P:\ that existed during previous installations.
WARNING: Do not just add P:\ (which is valid for us), but try to find if there wasn't another drive/map (letter) that existed during previous installs and no longer exists today.
Francky
For your information: I didn't want to do all those manipulations mentioned above because my workstation was quite sensitive for work.
I found a solution that resolves everything in two seconds: add the P:\
In a cmd: "subst p: d:\"
This creates a fake P:\ that points to my D:\ (real drive).
This resolves my problem because the XP system was still looking for the mapped P:\ that existed during previous installations.
WARNING: Do not just add P:\ (which is valid for us), but try to find if there wasn't another drive/map (letter) that existed during previous installs and no longer exists today.
Francky
I had similar problems when trying to install version 3.5 (It's now 2009...).
The proposed solution did not work sufficiently: unable to install the new version.
Until I "tipped": It's no longer enough to uninstall version 1.1. You also need to remove 2.0 and 3.0 before reinstalling everything...
So I searched for ".Net framework" in the HKEY_CLASSES_ROOT\installer\products hierarchy
and found the last 2 which I deleted.
And it works!!!
Anakin
The proposed solution did not work sufficiently: unable to install the new version.
Until I "tipped": It's no longer enough to uninstall version 1.1. You also need to remove 2.0 and 3.0 before reinstalling everything...
So I searched for ".Net framework" in the HKEY_CLASSES_ROOT\installer\products hierarchy
and found the last 2 which I deleted.
And it works!!!
Anakin
Here is what I had collected as information back in 2005, I believe. If you follow the procedure, everything should return to normal. Good luck, @+,
best regards
Windows Operating System Tips
[Windows Update] .Net Framework The KB Patches: The Solution!
Last updated on November 16, 2009, at 5:36 PM by marlalapocket
Published by black Winny
Here is the solution to the current problem encountered by a significant number of people regarding the crash when updating .Net Framework through the KB886903 and KB887219 patches of the MS05-004 security bulletin from February 8, 2005 loaded by Windows Update:
Since February 8, 2005, two of the updates carried out by Windows Update refuse to install on certain machines. These are the updates KB886903 and KB887219 which concern a security hole in .Net Framework and ASP.Net.
The reason for this inability to correctly install these updates is an alteration of the original .Net Framework installation package, an alteration that occurred during the daily operation of the machine.
It is therefore necessary to repair or reinstall .Net Framework. However, it is noted that any attempt ends in failure, including uninstallation through the Control Panel.
Here's how to remedy the problem:
* Uninstallation of .Net Framework proving impossible even through the Control Panel (Add/Remove Programs), another uninstallation method must be found that remains simple and accessible to everyone, even without knowledge of computer tools.
* Trying a second method using Windows Install Cleanup (a very interesting program by the way) available at this address does not yield better results. Once Windows Install Cleanup is installed, I of course launched it from the Windows Start menu. It apparently allowed me to remove .Net Framework. Great! But the smile quickly faded when I saw that it was only an appearance because when trying to reinstall .Net Framework afterward... it didn't work any better! The reinstallation still ended in failure. This is actually normal because it turns out that Windows Install Cleanup did not actually uninstall .Net Framework at all, which is still present in the Registry entries!
How to proceed?
Let's look in detail at the procedure to follow. The description that follows will be approachable to both a complete beginner and a professional.
The procedure below is carried out in three very easy steps:
* 1. Deletion of the .Net Framework installation key in the Registry
o 1.a: Method using Regedit
o 1.b: Method without using Regedit
* 2. Reinstallation of .Net Framework 1.1
o 2.a Download DotnetFX
o 2.b Run DotnetFX
* 3. Reinstallation of .Net Framework Service Pack 1
o 3.a Download NDP1.1sp1-KB867460-X86.exe
o 3.b Install NDP1.1sp1-KB867460-X86.exe
* Conclusion
1. Deletion of the .Net Framework installation key in the Registry
For this, there are two possibilities: either you know how to handle Regedit confidently from experience (then do step 1.a below) or you really don’t want to touch "that thing full of codes everywhere" (then do step 1.b).
1.a: Method using Regedit
* Open Regedit
* Delete (without making a mistake) the key:
HKEY_CLASSES_ROOT\Installer\Products\DDE7F2BCF1D91C3409CFF425AE1E271A
1.b: Method without using Regedit
* Open the usual Windows Start menu, then click on "Run"
* In the small window that opens, copy-paste the following line completely (making sure to include every character from the initial R to the final f!):
Reg delete HKEY_CLASSES_ROOT\Installer\Products\DDE7F2BCF1D91C3409CFF425AE1E271A /f
* This deletes the problematic key.
2. Reinstallation of .Net Framework 1.1
Again, there are two possibilities. If you still have the program dotnetfx.exe somewhere on your machine, which is precisely 23710 Ko in size, then go directly to point 2.b below. If you don’t have it somewhere on your machine, then first do point 2.a before proceeding to point 2.b.
2.a Download DotnetFX
If you can’t find the program dotnetfx.exe which is precisely 23710 Ko in size, you need to find it from a computer magazine CD or download it directly from the Microsoft site at this address:
www.microsoft.com
(note: if you don’t have a broadband connection, go to sleep and come back tomorrow morning...!)
2.b Run DotnetFX
Now launch the program dotnetfx.exe which is precisely 23710 Ko in size. It will properly reinstall .Net Framework 1.1
3. Reinstallation of .Net Framework Service Pack 1
Again, there are two possibilities. If you still have the program NDP1.1sp1-KB867460-X86.exe somewhere on your machine, which is precisely 10453 Ko in size, then go directly to point 3.b below. If you don’t have it somewhere on your machine, then first do point 3.a before proceeding to point 3.b.
3.a Download NDP1.1sp1-KB867460-X86.exe
If you can’t find the program NDP1.1sp1-KB867460-X86.exe which is precisely 10453 Ko in size, you need to find it from a computer magazine CD or download it from the Microsoft site at this address:
www.microsoft.com
(note: if you don’t have a broadband connection, go relax, take a coffee or a herbal tea, and come back in an hour...!)
3.b Install NDP1.1sp1-KB867460-X86.exe
Now launch the program NDP1.1sp1-KB867460-X86.exe which is precisely 10453 Ko in size. It will properly reinstall the .Net Framework 1.1 Service Pack 1. It is very likely that it will tell you that SP1 is already installed... Do not pay attention to the warning and reinstall it anyway!
Conclusion
There you go. Once all this is completed, you can help yourself to a nice cocktail (with or without alcohol). The usual installation of your security updates with Windows Update goes smoothly again.
The addresses given above are for Windows XP (regardless of the version). If you have Windows Server 2003, you won’t have any trouble finding the addresses of the equivalent versions on the Microsoft site, knowing that the procedure to follow is strictly the same.
Jacques
(Black Winny)
Best responses for ".Net Framework The KB patches: The solution!"
best regards
Windows Operating System Tips
[Windows Update] .Net Framework The KB Patches: The Solution!
Last updated on November 16, 2009, at 5:36 PM by marlalapocket
Published by black Winny
Here is the solution to the current problem encountered by a significant number of people regarding the crash when updating .Net Framework through the KB886903 and KB887219 patches of the MS05-004 security bulletin from February 8, 2005 loaded by Windows Update:
Since February 8, 2005, two of the updates carried out by Windows Update refuse to install on certain machines. These are the updates KB886903 and KB887219 which concern a security hole in .Net Framework and ASP.Net.
The reason for this inability to correctly install these updates is an alteration of the original .Net Framework installation package, an alteration that occurred during the daily operation of the machine.
It is therefore necessary to repair or reinstall .Net Framework. However, it is noted that any attempt ends in failure, including uninstallation through the Control Panel.
Here's how to remedy the problem:
* Uninstallation of .Net Framework proving impossible even through the Control Panel (Add/Remove Programs), another uninstallation method must be found that remains simple and accessible to everyone, even without knowledge of computer tools.
* Trying a second method using Windows Install Cleanup (a very interesting program by the way) available at this address does not yield better results. Once Windows Install Cleanup is installed, I of course launched it from the Windows Start menu. It apparently allowed me to remove .Net Framework. Great! But the smile quickly faded when I saw that it was only an appearance because when trying to reinstall .Net Framework afterward... it didn't work any better! The reinstallation still ended in failure. This is actually normal because it turns out that Windows Install Cleanup did not actually uninstall .Net Framework at all, which is still present in the Registry entries!
How to proceed?
Let's look in detail at the procedure to follow. The description that follows will be approachable to both a complete beginner and a professional.
The procedure below is carried out in three very easy steps:
* 1. Deletion of the .Net Framework installation key in the Registry
o 1.a: Method using Regedit
o 1.b: Method without using Regedit
* 2. Reinstallation of .Net Framework 1.1
o 2.a Download DotnetFX
o 2.b Run DotnetFX
* 3. Reinstallation of .Net Framework Service Pack 1
o 3.a Download NDP1.1sp1-KB867460-X86.exe
o 3.b Install NDP1.1sp1-KB867460-X86.exe
* Conclusion
1. Deletion of the .Net Framework installation key in the Registry
For this, there are two possibilities: either you know how to handle Regedit confidently from experience (then do step 1.a below) or you really don’t want to touch "that thing full of codes everywhere" (then do step 1.b).
1.a: Method using Regedit
* Open Regedit
* Delete (without making a mistake) the key:
HKEY_CLASSES_ROOT\Installer\Products\DDE7F2BCF1D91C3409CFF425AE1E271A
1.b: Method without using Regedit
* Open the usual Windows Start menu, then click on "Run"
* In the small window that opens, copy-paste the following line completely (making sure to include every character from the initial R to the final f!):
Reg delete HKEY_CLASSES_ROOT\Installer\Products\DDE7F2BCF1D91C3409CFF425AE1E271A /f
* This deletes the problematic key.
2. Reinstallation of .Net Framework 1.1
Again, there are two possibilities. If you still have the program dotnetfx.exe somewhere on your machine, which is precisely 23710 Ko in size, then go directly to point 2.b below. If you don’t have it somewhere on your machine, then first do point 2.a before proceeding to point 2.b.
2.a Download DotnetFX
If you can’t find the program dotnetfx.exe which is precisely 23710 Ko in size, you need to find it from a computer magazine CD or download it directly from the Microsoft site at this address:
www.microsoft.com
(note: if you don’t have a broadband connection, go to sleep and come back tomorrow morning...!)
2.b Run DotnetFX
Now launch the program dotnetfx.exe which is precisely 23710 Ko in size. It will properly reinstall .Net Framework 1.1
3. Reinstallation of .Net Framework Service Pack 1
Again, there are two possibilities. If you still have the program NDP1.1sp1-KB867460-X86.exe somewhere on your machine, which is precisely 10453 Ko in size, then go directly to point 3.b below. If you don’t have it somewhere on your machine, then first do point 3.a before proceeding to point 3.b.
3.a Download NDP1.1sp1-KB867460-X86.exe
If you can’t find the program NDP1.1sp1-KB867460-X86.exe which is precisely 10453 Ko in size, you need to find it from a computer magazine CD or download it from the Microsoft site at this address:
www.microsoft.com
(note: if you don’t have a broadband connection, go relax, take a coffee or a herbal tea, and come back in an hour...!)
3.b Install NDP1.1sp1-KB867460-X86.exe
Now launch the program NDP1.1sp1-KB867460-X86.exe which is precisely 10453 Ko in size. It will properly reinstall the .Net Framework 1.1 Service Pack 1. It is very likely that it will tell you that SP1 is already installed... Do not pay attention to the warning and reinstall it anyway!
Conclusion
There you go. Once all this is completed, you can help yourself to a nice cocktail (with or without alcohol). The usual installation of your security updates with Windows Update goes smoothly again.
The addresses given above are for Windows XP (regardless of the version). If you have Windows Server 2003, you won’t have any trouble finding the addresses of the equivalent versions on the Microsoft site, knowing that the procedure to follow is strictly the same.
Jacques
(Black Winny)
Best responses for ".Net Framework The KB patches: The solution!"
Hello Jacques,
We could give you contributor status, for you to add this notice yourself to the knowledge base.
I will keep you informed, or one of the moderators will.
Thank you.
----
Dark Ways
We could give you contributor status, for you to add this notice yourself to the knowledge base.
I will keep you informed, or one of the moderators will.
Thank you.
----
Dark Ways
Ok.
So if you can remove the references... feel free.
Because when I replied to your message, I thought it was going to the concierge service. I had misread... :-)
Kind regards
Jacques
So if you can remove the references... feel free.
Because when I replied to your message, I thought it was going to the concierge service. I had misread... :-)
Kind regards
Jacques
Just a question... are you sure that the registry key in question is always the same regardless of the machine????
--
.O
(_)__ I'm not a nutri!...
--
.O
(_)__ I'm not a nutri!...
Thank you Black Winny for your contribution! :)
I'm having a problem installing patch KB886903
It's getting a bit late now, but I'll try your tips tomorrow!
I'm having a problem installing patch KB886903
It's getting a bit late now, but I'll try your tips tomorrow!
Hello black Winny,
Just a few lines to let you know OOOHHH how much thanks to you,
It's not a thorn but a tree trunk that you removed from my foot!!
I wanted to test a software called "pestpatrol corporate v5" and this software seemed to work with
"MICROSOFT .NET FRAMEWORK 1.1"
However, I changed my mind in the meantime, and I thought I was going "CRAZY" because it was absolutely impossible for me to get rid of this "parasite"..
So I thank you infinitely...
I hug you, best regards.
Just a few lines to let you know OOOHHH how much thanks to you,
It's not a thorn but a tree trunk that you removed from my foot!!
I wanted to test a software called "pestpatrol corporate v5" and this software seemed to work with
"MICROSOFT .NET FRAMEWORK 1.1"
However, I changed my mind in the meantime, and I thought I was going "CRAZY" because it was absolutely impossible for me to get rid of this "parasite"..
So I thank you infinitely...
I hug you, best regards.
Wow!
I love it when I get kisses!
Especially coming from a princess...
If one day you have a thorn in your finger, Princess, and you fall asleep... don’t hesitate! Black Winny is here!
I kiss you (uh... cordially, of course) :-)
Jacques
I love it when I get kisses!
Especially coming from a princess...
If one day you have a thorn in your finger, Princess, and you fall asleep... don’t hesitate! Black Winny is here!
I kiss you (uh... cordially, of course) :-)
Jacques
Hello everyone, and especially to Black Winny,
Congratulations on the clarity of the procedure provided for resolving the .NET Framework update.
However, I was still unable to complete this update.
I did find the infamous registry key before uninstalling .NET Framework, but once it was uninstalled (via Control Panel, Add or Remove Programs), the registry key disappeared!
Therefore, it was impossible to delete it using Black Winny's procedure.
I didn't dare delete the key before uninstalling, fearing that the uninstallation would become impossible.
After reinstalling .NET Framework and the patch, the problem remains, meaning that the patch does not appear in the list of installed programs and Windows Update still requests its installation, which ends up failing again (error code 80200010).
What do you think, and what do you advise me to do?
Configuration: XP Pro SP1, Firefox (and of course IE for Windows Update), Panda Titanium2005.
Kind regards
Premare
Congratulations on the clarity of the procedure provided for resolving the .NET Framework update.
However, I was still unable to complete this update.
I did find the infamous registry key before uninstalling .NET Framework, but once it was uninstalled (via Control Panel, Add or Remove Programs), the registry key disappeared!
Therefore, it was impossible to delete it using Black Winny's procedure.
I didn't dare delete the key before uninstalling, fearing that the uninstallation would become impossible.
After reinstalling .NET Framework and the patch, the problem remains, meaning that the patch does not appear in the list of installed programs and Windows Update still requests its installation, which ends up failing again (error code 80200010).
What do you think, and what do you advise me to do?
Configuration: XP Pro SP1, Firefox (and of course IE for Windows Update), Panda Titanium2005.
Kind regards
Premare
Hello
Have you also tried this?
http://www.commentcamarche.net/forum/affich-1322627
Best regards
Black Winny
Have you also tried this?
http://www.commentcamarche.net/forum/affich-1322627
Best regards
Black Winny
Good evening,
After a few hours spent on maintenance (disk check and defragmentation), I installed Rollup 1, which indeed was not installed (my XP installation dates back to November 2004), and then I followed your procedure, still without success regarding the .Net Framework update. The Registry key is deleted upon uninstallation, which seems normal to me if it is complete!
In the end, I managed to find and download the missing security update indicated by WU for .Net Framework version 1.1 SP1 (KB 886903) and I installed it manually.
It is likely that this worked thanks to the prior installation of Rollup 1.
Now, Windows Update is satisfied and is no longer asking me for any updates.
I think I have resolved my issue. In fact, I will only truly know with the next WU updates!
Anyway, you made me think and search in every nook and cranny of Microsoft and forums. It's excellent
as training!
In fact, there are 2 updates for .Net Framework: KB 886903 and
867460. Perhaps this is the source of the problem?
Friendly regards
Premare
After a few hours spent on maintenance (disk check and defragmentation), I installed Rollup 1, which indeed was not installed (my XP installation dates back to November 2004), and then I followed your procedure, still without success regarding the .Net Framework update. The Registry key is deleted upon uninstallation, which seems normal to me if it is complete!
In the end, I managed to find and download the missing security update indicated by WU for .Net Framework version 1.1 SP1 (KB 886903) and I installed it manually.
It is likely that this worked thanks to the prior installation of Rollup 1.
Now, Windows Update is satisfied and is no longer asking me for any updates.
I think I have resolved my issue. In fact, I will only truly know with the next WU updates!
Anyway, you made me think and search in every nook and cranny of Microsoft and forums. It's excellent
as training!
In fact, there are 2 updates for .Net Framework: KB 886903 and
867460. Perhaps this is the source of the problem?
Friendly regards
Premare
Hello... I've been looking for a way to update the .net framework for a while now, so when I saw this solution, I thought it was cool... but problems never come alone for me:
When I get to this point in your explanation
"3.a: If you can't find the program NDP1.1sp1-KB867460-X86.exe on your machine, which is precisely 10453 Ko in size, then you need to find it on a computer magazine CD or download it from Microsoft's website at this address:
http://www.microsoft.com/downloads/details.aspx?FamilyID=a8f5654f-088e-40b2-bbdb-a83353618b38&displaylang=fr
(Note: If you don't have a high-speed connection, go relax, have a coffee or a lime blossom tea, and come back in an hour...!)
3.b: Now launch the program NDP1.1sp1-KB867460-X86.exe, which is precisely 10453 Ko in size. It will properly reinstall the Service Pack 1 of .Net Framework 1.1. It is very likely that it will tell you that SP1 is already installed... Do not pay attention to the warning and reinstall it anyway! No way!
"
At the time of installation, a box appears (Windows Installer)
kindly telling me
"The component you are trying to use is on a network resource that is unavailable. Click OK to retry or enter an alternate path below to a folder containing the installation package tmp13d.tmp"
The problem is that I don't know where this tmp13d.tmp is, it's not on my PC, and even using the source it proposes (C:\DOCUME~1\COMPAQ~1\LOCALS~1\Temp) doesn't work....
The bottom line is that I'm still at the same point, the update is still not happening, and I've been going around in circles for a few days now....
HELP ME.... PLEASE!!!!
When I get to this point in your explanation
"3.a: If you can't find the program NDP1.1sp1-KB867460-X86.exe on your machine, which is precisely 10453 Ko in size, then you need to find it on a computer magazine CD or download it from Microsoft's website at this address:
http://www.microsoft.com/downloads/details.aspx?FamilyID=a8f5654f-088e-40b2-bbdb-a83353618b38&displaylang=fr
(Note: If you don't have a high-speed connection, go relax, have a coffee or a lime blossom tea, and come back in an hour...!)
3.b: Now launch the program NDP1.1sp1-KB867460-X86.exe, which is precisely 10453 Ko in size. It will properly reinstall the Service Pack 1 of .Net Framework 1.1. It is very likely that it will tell you that SP1 is already installed... Do not pay attention to the warning and reinstall it anyway! No way!
"
At the time of installation, a box appears (Windows Installer)
kindly telling me
"The component you are trying to use is on a network resource that is unavailable. Click OK to retry or enter an alternate path below to a folder containing the installation package tmp13d.tmp"
The problem is that I don't know where this tmp13d.tmp is, it's not on my PC, and even using the source it proposes (C:\DOCUME~1\COMPAQ~1\LOCALS~1\Temp) doesn't work....
The bottom line is that I'm still at the same point, the update is still not happening, and I've been going around in circles for a few days now....
HELP ME.... PLEASE!!!!
Hi everyone!
Well, listen, I know this isn't of much help because we don't know the exact origin of the problem.
But software suggested on the MSDN blogs "saved my system"... Basically, the frameworks have ALWAYS been a problem for me. After downloading and running the tool developed by Aaron Stebner, I ended up with a CLEAN system on which I was indeed able to install the frameworks...
The tool is available here:
http://astebner.sts.winisp.net/Tools/dotnetfx_cleanup_tool.zip
The address of his blog (and the topic we're talking about):
http://blogs.msdn.com/astebner/archive/2005/04/08/406671.aspx?CommentPosted=true#commentmessage
This saved my life ;)
Well, listen, I know this isn't of much help because we don't know the exact origin of the problem.
But software suggested on the MSDN blogs "saved my system"... Basically, the frameworks have ALWAYS been a problem for me. After downloading and running the tool developed by Aaron Stebner, I ended up with a CLEAN system on which I was indeed able to install the frameworks...
The tool is available here:
http://astebner.sts.winisp.net/Tools/dotnetfx_cleanup_tool.zip
The address of his blog (and the topic we're talking about):
http://blogs.msdn.com/astebner/archive/2005/04/08/406671.aspx?CommentPosted=true#commentmessage
This saved my life ;)
Hello,
I read and successfully applied with great interest the method you outlined regarding the uninstallation and reinstallation of Framework 1.1.
So everything went very well for the first part, but the .Net Framework SP1 refuses to install (I do have it and I actually re-downloaded NDP1.1sp1-kb867460-X86.exe); the message I receive from Windows Installer is that the installation is impossible!
As a result, I have other updates from Windows Update that are offered to me and that I cannot install.
I would appreciate your kind assistance if you have any ideas on this issue.
Congratulations again on the clarity of your presentation.
Thank you in advance.
I read and successfully applied with great interest the method you outlined regarding the uninstallation and reinstallation of Framework 1.1.
So everything went very well for the first part, but the .Net Framework SP1 refuses to install (I do have it and I actually re-downloaded NDP1.1sp1-kb867460-X86.exe); the message I receive from Windows Installer is that the installation is impossible!
As a result, I have other updates from Windows Update that are offered to me and that I cannot install.
I would appreciate your kind assistance if you have any ideas on this issue.
Congratulations again on the clarity of your presentation.
Thank you in advance.
- 1
- 2
- 3
Suivant