LegacyUpdate
LegacyUpdate copied to clipboard
kirb
What's the best method to update WinXP ?
I first try checking the ''legacy update box'' only.
I still prefer to use the WUMT (stupid user from ru-board) to download my updates
I first download everything except NET 1.1 - NET 3.5 - NET 4.0 / IE 8.0 / Search 4.0 / MP 11.0 / Live Essentials / Security Essentials / AMD CPU driver (not sure why this driver shows up)
once done I start with the NET framework updates procedure and I have realized that it doesn't matter whether installing them all at the same time or one by one. (1.1 + updates + restart >>> 3.5 + updates + restart >>> 4.0 + updates) because the number of updates brought out is exactly the same.
as you know there are 3 official offline installers (NET 3.5 and NET 3.5 SP1 and NET 4.0) I wonder if it's worth using them instead ?
there are some AIO Visual C+ repacks out there but I have decided to use the one avalable in this github repo because it seems to be the most complete for WinXP and surprisingly it didn't brought any optional update up to WUMT https://github.com/abbodi1406/vcredist/releases/tag/v0.35.0
I didn't play around with Office 2003 and its updates yet
AOMEI backupper saves me a lof of time because I can reinstall XP countless times and allows me to reset my testing within a few minutes
second part, this time I check both boxes ''legacy update'' and ''embedded 2009''
the number of updates displayed on the upper column (Windows XP) doesn't match anymore to the first method above
I wonder if this is due to the fact that the lower column updates (XP embbeded) do replace some of other XP updates
Question: do you people install upper and lower updates at the same time or do you install everything from the upper column in first place and leave the embedded updates for last ?
given the last update for NET framework was released on February 2014 and the first embedded update was released on May 2014 I thought it was not a good idea to install everything at the same time and we should respect that order
I am unable to install this one KB2686509 that is listed on the first column along with the other XP udaptes
Question: what happens with Internet Explorer 7.0 ? why is it displayed when using an alternate WSUS update method ?
Question: is it mandatory to install Internet Explorer 8.0 ? I am fine with IE 6 because I like the classic layout and don't actually use this browser for anything
Question: what happens with Media Player 10 ? it's the one I most like but it's never displayed on either update methods I have used so far
Question: the other update method brings NET 4.0 KB982670 + KB982671 however Legacy update misses the second one 982671.... the other update method brings M$ Silverlight KB2977218 however it misses NET framework 1.1
this is just a little example I have spotted at first glance because it would be a headache to check and compare every update one by one
now I am getting really confused and wonder if someone selected these updates by hand or what the best possible update method is ...
the number of updates displayed on the upper column (Windows XP) doesn't match anymore to the first method above
I wonder if this is due to the fact that the lower column updates (XP embbeded) do replace some of other XP updates
Yes, probably, as I said here.
given the last update for NET framework was released on February 2014 and the first embedded update was released on May 2014 I thought it was not a good idea to install everything at the same time and we should respect that order
I agree; we should respect that order (but I'm not educated in computer engineering). Having installed .NET Framework 4, you can install .NET Framework 4.0.3 from here.
I am unable to install this one KB2686509 that is listed on the first column along with the other XP udaptes
Please see my answer here (you should first install the official Windows XP updates, then activate the "POSReady" option) or install it directly from here. Please note that the "normal" version of the update might not accept installing if "POSReady" is enabled. You may disable POSReady by denying "SYSTEM" reading access to the POSReady registry key using the built-in "regedit.exe". (Go to [HKEY_LOCAL_MACHINE\SYSTEM\WPA\PosReady], right-click on "Permission", click on "Advanced", select "SYSTEM", "Edit", and click the checkbox "Deny" for the option "Query Value". Lastly, click "OK" and "Yes".)
Question: what happens with Internet Explorer 7.0 ? why is it displayed when using an alternate WSUS update method ?
I don't know why, but here it is for others who may be searching for it. Since the download page is a new webpage that sometimes is not saved in the Wayback Machine, you probably have to look up the source of the first website (usually by pressing Ctrl+U or going to "Tools" and "Source") and find the URL containing "IE7-WindowsXP-x86-[part of language ID].exe". For other languages than English, you have to change "en-gb" in the URL, after having gone to the IE7 download website, to get it corresponding to your language. Here you have a list of language abbreviations to use in the URL (please note that most programs are not available in all of these languages).
Question: is it mandatory to install Internet Explorer 8.0 ? I am fine with IE 6 because I like the classic layout and don't actually use this browser for anything
Of course it's not mandatory, but there are newer features on a newer version of Internet Explorer. The last security update for Internet Explorer 6 (with "POSReady" activated) is from 12 January 2016, while the last one for IE8 is from 9 April 2019 (and the last one for IE7 is from 12 April 2016). The security updates take effect on the whole computer (more or less), even if you aren't using Internet Explorer, especially on older Windows versions such as Windows XP.
Question: what happens with Media Player 10 ? it's the one I most like but it's never displayed on either update methods I have used so far
This is because it has been replaced by Windows Media Player 11. But you can still get it from this archived Microsoft website: http://web.archive.org/web/20121025054607/http://www.microsoft.com/en-gb/download/details.aspx?id=20426. Since it requires validation before downloading, which is no longer possible, you have to look up the source of the website (usually by pressing Ctrl+U) and find the URL containing "MP10Setup.exe". Here it is if you are using the English version of Windows XP. For other languages, you have to change "en-gb" in the URL above to get it corresponding to your language.
now I am getting really confused and wonder if someone selected these updates by hand or what the best possible update method is ...
As far as I know, LegacyUpdate gets access to the original Microsoft update servers for your (Windows 2000/XP/Vista and some more) computer. Shortly, it "resets" the connection to the update service, meaning that Microsoft's update service/server is offering you the updates. This means that any "complaints" about what updates are being offered should be directed to Microsoft, but since all these Windows versions have reached end-of-support, Microsoft doesn't take notice on such complaints anymore. (There might also be something wrong with LegacyUpdate itself, but – as far as I know – this should not affect what updates Microsoft offers you unless the error doesn't affect the Microsoft server's ability to correctly detect your computer.)
I would say that the best possible update method is using the built-in feature "Automatic Updates" (nowadays after having installed LegacyUpdate). When there are no more updates, check the LegacyUpdate website, install those that are present in there, and repeat the search (and the installations) until there are no more updates. Afterwards, use the Internet Archive Wayback Machine to find programs that have been depublished from the original websites, or even from the Windows Update/Microsoft Update/LegacyUpdate website, such as Microsoft Silverlight, Adobe Flash Player (big download since it contains the program for all type of computers), standalone version of Flash Player, Adobe Shockwave Player, Adobe Reader (use the following address: ftp://ftp.adobe.com/pub/adobe/reader/win/11.x/11.0.00/), Mozilla Firefox, Windows Live Essentials (all versions and languages), and a lot of more, but I'm not going to fill this thread with links that don't belong to the subject. (Maybe a new post?)
Question: […] however it misses NET framework 1.1
Microsoft .NET Framework 1.1 is available on the LegacyUpdate website (preferably when you have searched for updates) and here. As stated above, you have to change "en-gb" in the URL to your language (if it's not English) and you may have to retrieve the URL for the installation file (dotnetfx.exe) by pressing Ctrl+U or similar.
This is because it has been replaced by Windows Media Player 11. But you can still get it from this archived Microsoft website: http://web.archive.org/web/20121025054607/http://www.microsoft.com/en-gb/download/details.aspx?id=20426. Since it requires validation before downloading, which is no longer possible, you have to look up the source of the website (usually by pressing Ctrl+U) and find the URL containing "MP10Setup.exe". Here it is if you are using the English version of Windows XP. For other languages, you have to change "en-gb" in the URL above to get it corresponding to your language.
https://www.catalog.update.microsoft.com/Search.aspx?q=Media%20player%2010
https://www.catalog.update.microsoft.com/Search.aspx?q=Media%20player%2010
Oh, does it still exist in the Microsoft Update Catalog? I didn't think of that possibility. Very well and easy!
I first download everything except NET 1.1 - NET 3.5 - NET 4.0 / IE 8.0 / Search 4.0 / MP 11.0 / Live Essentials / Security Essentials / AMD CPU driver (not sure why this driver shows up)
AMD gives windows xp amdppm.sys in 2008
I first download everything except NET 1.1 - NET 3.5 - NET 4.0 / IE 8.0 / Search 4.0 / MP 11.0 / Live Essentials / Security Essentials / AMD CPU driver (not sure why this driver shows up)
AMD gives windows xp amdppm.sys in 2008
which only had amdk6 amdk7 amdk8 driver before , otherwise it will use standard processor.sys
I don't know why, but here it is for others who may be searching for it.
thanks for taking your time to reply but I didn't ask you to search the links for me. I just wanted to know if there's more than one active SUS server or if these updates are manually selected by different persons and not actually recommended by M$ because different update methods bring different updates
this method doesn't seem to work right now and its developer said it's a temporary issue only
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate] "WUServer"="http://wsus.gimme.money:8530" "WUStatusServer"="http://wsus.gimme.money:8530"
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU] "UseWUServer"=dword:00000001
Of course it's not mandatory, The last security update for Internet Explorer 6 (with "POSReady" activated) is from 12 January 2016, while the last one for IE8 is from 9 April 2019 (and the last one for IE7 is from 12 April 2016). The security updates take effect on the whole computer
I had been told some years ago it's mandatory to install IE8 because it's more than just a web browser but let me take this with a grain of salt
just because the IE8 update is newer doesn't make it necessary for IE6 that update was released because you installed IE8 and created another ''hole'' that was not there before. the Million dollar question is: would this IE8 update patch anything despite IE8 not being installed ?
I would say that the best possible update method is using the built-in feature "Automatic Updates" (nowadays after having installed LegacyUpdate).
the end result is pretty much the same whether using WUMT or Legacy Update with IE6
this is what I ran across on either of them (Embedded 2009 patch still disabled)
Media Format 9 KB2803821 fails to install NET framework 3.0 KB928416 fails to install
right after a fresh XP install if one only installs security updates + critical updates and leave all other updates for the next round, this update KB971513 will disappear from the list for no apparent rewson
more, Legacy Update forces you to install this KB951847 or KB982670 update separately I found it was unnecessary when using WUMT I have already mentioned this on my first post
I don't know why, but here it is for others who may be searching for it.
thanks for taking your time to reply but I didn't ask you to search the links for me. [...]
Yes, I know, but I got a little excited. Furthermore, I said "for others who may be searching for it".
I had been told some years ago it's mandatory to install IE8 because it's more than just a web browser but let me take this with a grain of salt
Yes, it's more than a web browser since many other parts of the Windows XP system interact with it, for example the (file) Explorer, the Search companion or the Activation Wizard. There is a reason for IE8 being classified as an important update, but the (virtual) computer is still yours and you have the non-recommended ability to deny updates.
just because the IE8 update is newer doesn't make it necessary for IE6 that update was released because you installed IE8 and created another ''hole'' that was not there before. the Million dollar question is: would this IE8 update patch anything despite IE8 not being installed ?
I don't know the answer to the "million dollar question", but I do know that it's not possible to install an update for IE8 without having installed IE8. Furthermore, we see on this Microsoft webpage, not to mention the Microsoft Update Catalog, that the same update is being used across many Internet Explorer versions and many Windows versions. Of course, there have to be individual copies for each version, as we see in the update catalogue, but we do still see the same KB number of the update and the same article for all these IE and Windows versions, meaning it's the same update for all of them.
This means that, for example, the April 2019 update for Internet Explorer 8 (with "POSReady" activated) may contain security fixes that would have been included for IE7 or IE6 if IE7 and IE6 still got updates.
What I want to say with this is the following: the "another 'hole' that was not there before" might exist in IE6 and IE7 and IE8, but the security updates do only fix it in IE8 after January 2016 (for IE6) and April 2016 (for IE7).
I would say that the best possible update method is using the built-in feature "Automatic Updates" (nowadays after having installed LegacyUpdate).
the end result is pretty much the same whether using WUMT or Legacy Update with IE6
Good. That should be expected, I believe.
[…] NET framework 3.0 KB928416 fails to install
(Tagged for information: @kirb ) If you are using a non-English version of Windows XP, Legacy Update will offer you some language packs for Microsoft .NET Framework. The KB number of the language packs is the same as the KB number of the .NET Framework installation package, as seen in the update catalogue.
Regarding KB928416 as the language pack for .NET Framework 3.0, an installation error will occur if you try to follow the installation order given by Microsoft Update/Legacy Update and you, thereby, install KB951847 (more specific this version of KB951847), which contains .NET Framework 3.5 (with SP1) and some parts of .NET Framework 3.0 and 2.0 in the same update, and then install KB928416 which is not even shown unless you have installed KB951847.
Recently, I realized how to encounter the error code of the installation attempt of KB928416 in plain text (since I haven't found it on the internet): if you manually download the (by Legacy Update) offered language pack for .NET Framework 3.0 from Microsoft Update Catalog, and open the download link in your Windows XP browser, there will be a visible installation wizard telling you the error in plain text.
The error information will tell you that a higher version of .NET Framework (that is 3.5) has already been installed (by the combined installation package offered by Microsoft Update, nowadays Legacy Update, that is KB951847, which, as I said, contains .NET Framework 2.0, 3.0 and 3.5 in the same package).
The only solution, as far as I know, is to download and install Microsoft .NET Framework one version at a time, followed by each language pack, respectively, before installing a newer version of .NET Framework, and not using the combined update.
@AntonFromSweden what's up with this update ? why does it go away ? https://www.catalog.update.microsoft.com/Search.aspx?q=971513
it's listed under the ''optional software updates'' tab I start by downloading the high priority updates during the first round then restart the computer and focus on the next round which includes optional updates, 3rd round for NET framework's..etc I don't know why this update dissapears from the list after the first restart
@AntonFromSweden what's up with this update ? why does it go away ? https://www.catalog.update.microsoft.com/Search.aspx?q=971513
it's listed under the ''optional software updates'' tab I start by downloading the high priority updates during the first round then restart the computer and focus on the next round which includes optional updates, 3rd round for NET framework's..etc I don't know why this update dissapears from the list after the first restart
Neither do I know why it disappears, but I can confirm the behaviour when using Windows XP with Service Pack 3 built-in (as a virtual machine) and with Windows XP Mode with the "POSReady" trick enabled as well as not enabled. (But I haven't evaluated the behaviour using, or beginning with, Windows XP with a lower Service Pack or without Service Pack (RTM).)
I have to say that I wasn't even aware of this update until now (I didn't think about it any further after you asked about it for the first time, because I wasn't aware of an immediate answer, so I left it to other contributors), since I, usually, do always use the feature "Automatic updates" (including restart) before having a look at the update list on the Legacy Update website.
Usually when an update disappears, that happens because another update supersedes it (when this another update is being installed before the one that disappears). Source: the information about how to restore hidden updates on the FAQ page of the old Microsoft Update website which still works. But the update catalogue doesn't mention any updates that would supersede KB971513 on Windows XP, which makes it strange that KB971513 disappears!
I think this disappearing behaviour is some kind of bug in the Microsoft update service, since there are some more strange things. For example, when listening to Legacy Update or the automatic update feature, you are prompted to install both Internet Explorer 8 and the last security update for Internet Explorer 6 at the same time. Since the order, in which the updates are being installed when not deselecting any of them, appears to be randomly chosen, the installation process sometimes install IE8 before the update for IE6, causing the IE6 update to fail. Therefore, I do always, nowadays, deselect IE8 until I have installed the IE6 update (with or without the "POSReady" registry setting. Generally, I do also install IE7 and its corresponding updates before installing IE8). This kind of behaviour is seen even nowadays on Windows 10 computers which have not been updated for a while, when trying to update them. Imagine that you (still) have Windows 10, version 1809, for example. If you let the computer search for updates, it may begin with installing the feature update to Windows 10, version 22H2 and after that, during the same installation process, before restarting, it may try to install the latest (cumulative) update for version 1809. (I have seen it myself!)
A third example of Windows Update/Microsoft Update (nowadays Legacy Update) going wrong is of course the one I mentioned in my last comment, with the update service offering the language pack for .NET Framework 3.0 after having installed the three-in-one combined update which includes .NET Framework 2.0, 3.0 and 3.5 in the same update, causing the language pack installation to fail because of a higher version than 3.0 already being installed (by the update service itself!).
I have to mention a fourth example! If you have the real Windows Embedded POSReady 2009 and install Legacy Update on it, it will not offer you Microsoft Security Essentials, even when you block the POSReady registry key, which (I believe) should make the update service think that the POSReady version is a "normal" Windows XP. At least, this makes the "End of support notification" update (KB2934207) for "normal" Windows XP available in POSReady. (After having installed Microsoft Security Essentials on "normal" Windows XP, you can retrieve the download link from C:\WINDOWS\WindowsUpdate.log and use it in POSReady to download and install MSE on POSReady.)
Very interesting, anyway, about this KB971513! As you may have noticed, it can be installed manually from Microsoft Update Catalog despite it having disappeared from the update list in Legacy Update. Now I have put this update on my own list of programs and updates to install on Windows XP, so thank you for making me observing this update!
I do always, nowadays, deselect IE8 until I have installed the IE6 update
what IE6 update are you talking about ? do you install POSready updates before IE8 ?
I have no problems with IE8 whether installing it during the first round or keep it for later on
IE8 updates (POSready-less) KB2510531, KB2632503, KB2598845
I do always, nowadays, deselect IE8 until I have installed the IE6 update
what IE6 update are you talking about ?
I'm talking about KB2879017 (for IE6 on Windows XP) which is included in the first round of (security) updates, at least when using Windows XP with Service Pack 3 preinstalled.
do you install POSready updates before IE8 ?
Usually, yes, regarding the POSReady update for IE6. The other POSReady updates usually have to wait until I have installed IE7, the IE7 updates, and finally IE8 and its updates. After that, I install the remaining POSReady updates.
Please note what I have discovered, at least when installing in that order: somewhere during the update installation process, with POSReady activated, the MSI installer (C:\WINDOWS\system32\msiexec.exe, or maybe some of its support files (DLL files), which are used for each program whose installer is in .msi format and can be updated by installing KB942288) stops working, with KB942288 as well as without KB942288. One of the POSReady updates (KB4494528) is claimed to address some installation problems, which makes me installing this update last of all, but to me, the MSI installer still doesn't work. I have to follow some instructions found on answers.microsoft.com, according to which you have to write the following commands in the Command Prompt to get Windows Installer working again:
msiexec /unregister
msiexec /regserver
I have no problems with IE8 whether installing it during the first round or keep it for later on
IE8 remains working even if the said IE6 update (KB2879017) has been installed at the same time as IE8 was installed (as it has by Windows Update/Microsoft Update/Legacy Update if you didn't deselect IE8 during the first round), but if you or the feature "Automatic Updates" install/installs IE8 before KB2879017, the installation of KB2879017 will fail.
IE8 updates (POSready-less) KB2510531, KB2632503, KB2598845
When you look in the update history in Control Panel, where you have the list of the installed programs, you will see that there is also KB2909921, without you doing anything, which means that the IE8 installer silently installs it together with IE8 (at least I believe so, since the IE7 installer has the same behaviour).
Don't forget the updates that are released for "normal" Windows XP after the end of support (if you don't activate the POSReady trick):
KB2964358, released on 1 May 2014, for IE6, IE7 and IE8.
Thereto the other 10 updates for "normal" Windows XP, mentioned in this Microsoft article, among which there is an IE8 update, and KB4500331. The last one has to be installed manually regardless of the POSReady setting.
Finally, this link may be interesting. It makes it possible for Windows Vista or later to recognize Windows XP in the network map on Windows Vista or later, but I haven't tested it myself yet since I haven't found the .exe file in my language in the Wayback Machine.
Thereto the other 10 updates for "normal" Windows XP, mentioned in this Microsoft article, among which there is an IE8 update, and KB4500331. The last one has to be installed manually regardless of the POSReady setting.
why do you say 10 updates ? I can count up to 12 and the first one's link is broken (968644) in other words which ones are not included in the Posready package ?
Thereto the other 10 updates for "normal" Windows XP, mentioned in this Microsoft article, among which there is an IE8 update, and KB4500331. The last one has to be installed manually regardless of the POSReady setting.
why do you say 10 updates ? I can count up to 12 and the first one's link is broken (968644)
I'm sorry for not being clear enough. If you search for each KB number, present in the list in the Microsoft article, in the Microsoft update catalogue, you will se that the first one (KB958644) and the second one (KB2347290) were released in 2008 and 2010, respectively, therefore being already included in the "Automatic updates" feature and/or on the Legacy Update website (I believe).
Thus, the first two updates mentioned for Windows XP in the Microsoft post-EOL article do not seem to be post-EOL, and therefore I didn't count them when I mentioned the post-EOL updates.
in other words which ones are not included in the Posready package ?
As far as I know, KB4500331 is the only (security) update (released after 8 April 2014) that is not included in the POSReady package (since it was released after the end of support even for POSReady).
What about the following item, then, which does also have to be installed manually?
Well, I believe it's included in KB4018271 for IE8 (and in KB3124275 for IE6, KB3148198 for IE7 and KB4493435 for IE8) since the Internet Explorer updates are cumulative. If you don't activate the POSReady updates, KB2964358 will (as far as I know) be the last Internet Explorer update for IE6 and IE7 and KB4018271 will be the last one for IE8. Please note that maybe KB2964358 isn't cumulative, which means that you should install all the "normal" Windows XP updates before installing KB2964358. After that, you can install the POSReady updates. But, as I said, I think that KB2964358 is already included in the POSReady updates, meaning that you shouldn't need to install KB2964358 if you activate the POSReady trick.
What about the following item, then, which does also have to be installed manually?
I didn't know about this update, so it's not detected by Legacy Update ? do you install them all ? IE7 is only offered with the other WSUS alternative method but their SUS server doesn't work anymore. http://i430vx.net/files/wsusstuff/ I think I will stick to IE6 and will not install IE8 on my definitive backup
The only solution, as far as I know, is to download and install Microsoft .NET Framework one version at a time, followed by each language pack, respectively, before installing a newer version of .NET Framework, and not using the combined update.
this time I tried to install the standalone executable files from M$
NET 3.5 https://www.microsoft.com/en-us/download/details.aspx?id=25150 with Legacy Update I get 27 updates for NET 3.5 KB951847(69MB) with the M$ NET 3.5 package (231MB) I get 28 updates (same updates + 1) here is the additional update KB951847
NET 4.0 https://www.microsoft.com/en-us/download/details.aspx?id=17718 with Legacy Update I get 15 updates for NET 4.0 KB982670 (28MB) with the M$ NET 4.0 package (35MB x86 only) I get 17 updates (same updates + 2) here are the two additional updates KB2487367 - KB2736428
NET 1.1 (no english site ?) https://www.microsoft.com/fi-fi/download/details.aspx?id=26 with Legacy Update I get 2 updates for NET 1.1 no KB number (23MB) with the M$ NET 1.1 package (23MB) I get 3 updates (sames updates + 1) (KB2833941 fails to install this time, no sure why though) the additional update is a language pack with no KB number
1- as you can see, the KB951847 doesn't get installed along with the M$ NET 3.5 package unlike the KB982670 that doesn't show up anymore.
2- there's a huge difference between 69MB and 231MB, I have used ''universal extractor'' to take the file apart to see what other things are being installed.
3- do you think the two NET 4.0 additional updates are necessary at all or have they been superseded ?
4- I'm not sure if I should install the NET framework standalone installers rather than using Legacy Update....
What about the following item, then, which does also have to be installed manually?
I didn't know about this update, so it's not detected by Legacy Update ?
No, it's not detected by Legacy Update since Legacy Update does only follow the official Windows Update (or, rather, Microsoft Update) which does, apparently, only show the updates that were released within the official support peroid which ended on 8 April 2014. None of the "extra" updates for "normal" Windows XP, released after 8 April 2014, are shown in Legacy Update. They do all have to be installed manually if you don't activate the POSReady trick. If you do activate the POSReady trick, only KB4500331 has to be installed manually.
do you install them all ? [KB2964358 for each version of IE]
Yes, I do (nowadays, when I have been aware of this update).
IE7 is only offered with the other WSUS alternative method but their SUS server doesn't work anymore. http://i430vx.net/files/wsusstuff/ I think I will stick to IE6 and will not install IE8 on my definitive backup
On 3 November 2023, in this thread, I provided the official (but saved in the Wayback Machine) web link for being able to install IE7 in English and I did also tell you how to find IE7 in other languages.
Generally, Legacy Update doesn't offer an individual update (including IE7) if there is a newer update (or a newer version of IE) available. Therefore, IE7 isn't offered in Legacy Update. I don't know why it is (or was) offered by the WSUS server, but since WSUS is intended for companies which have to maintain control over a large group of computers with unique computer programs that need, for example, IE7 to work, this may be the reason for IE7 still being offered in WSUS.
If you do decide to stick to IE6, then you should install all the updates offered by "Automatic Updates" or Legacy Update, then install KB2964358 for IE6 (of course in the same language that your Windows XP version is using) and then, lastly (maybe) activate POSReady and install the updates that "Automatic Updates" or Legacy Update offers you in this case. (This time I didn't reckon with .NET Framework, Windows Live Essentials and so on.)
The only solution, as far as I know, is to download and install Microsoft .NET Framework one version at a time, followed by each language pack, respectively, before installing a newer version of .NET Framework, and not using the combined update.
Now I have tried this myself properly, and not only claimed it, and I have to say that this method really makes it possible to install the language pack for Microsoft .NET Framework 3.0, when it's offered by Legacy Update, after you have installed .NET Framework 3.0 manually. But the language pack for .NET Framework 3.0 does remain as an available update when you install newer versions manually (or by using Legacy Update). If you then try to install the language pack (again), it will fail since there is a newer version of .NET Framework already installed.
this time I tried to install the standalone executable files from M$
Okay, but now when I've tried this myself, I have to say that it's quite difficult to understand what to install and in what order to do it. At the same time, there may not be any need for this anymore because of the language pack installing error, mentioned above, still being there. Then the easiest way is to follow Legacy Update, but still install one version at a time (as far as possible). Please note that .NET Framework 4.0.3 has to be installed manually, either way.
I don't know why the updates differ when you have installed .NET Framework using Legacy Update or using the standalone package, but maybe the larger standalone installers are developer versions. Or maybe Legacy Update knows what parts are essential, while the standalone package contains ALL possible files. Another example of this is Adobe Flash Player, the last (?) version without the timebomb of 12 January 2021; that standalone installer package is about 388 MB in size, but the IE (ActiveX) installer, included in the package, does only have a size of, approximately, 20 MB and the standalone Flash Player window, also included, does only have a size of 14,7 MB.
And no, there should not (according to Microsoft) be any download links for .NET Framework 1.1 available anymore since 26 July 2021, but thanks to https://web.archive.org (or http://web.archive.org on older Windows versions), many websites and downloads are still available in some kind!
I have also noticed that there are some missing KB numbers, but I think that there is a KB number in the background. For example, when you search for "Microsoft .NET Framework 1.1 Service Pack 1" (which should be installed before KB2833941) in the Microsoft Update Catalog, and then click on "Download", the link that will show up contains a KB number, namely KB867460.
Now I will try to comment/answer your numbered comments/questions:
-
I don't know why it is like this.
-
Okay, let's see if you are able to detect "what other things are being installed". Maybe the larger one is a developer version with more tools.
-
If you search for the KB number in the Microsoft update catalogue, click on the appropriate update and then click "Package Details", you will find that there are no updates superseding KB2487367 and KB2736428, so yes, they should be necessary.
-
If you follow my installation order below and check what files are in C:\WINDOWS\Microsoft .NET\Framework between each step, you will find that there are quite remarkable changes, so maybe it doesn't matter at all what installation method to use; the newer versions will "take over" the older ones even if you are using the standalone installers for each version. Thereto, we have the language pack for .NET Framework 3.0 that remains available in Legacy Update after having installed it, which means that installing each version by its own standalone installers may be an unnecessary effort.
However, I've found that this seems to be an appropriate order of installation if you still want to use the standalone installers.
a) Microsoft .NET Framework 1.0 (optional since it's claimed to be included in .NET Framework 1.1, but it is necessary if you want to install the Windows XP Tablet PC exclusive components on "normal" Windows XP): http://web.archive.org/web/20200112023200/https://download.microsoft.com/download/e/b/2/eb247c2a-e6b3-4694-98a2-b27111d233dd/dotnetredist.exe (this download is in English, but there are some other languages available). Then search for and install updates until there are no more available.
b) Microsoft .NET Framework 1.1 from Legacy Update, followed by its appropriate updates.
c) .NET Framework 2.0: KB829019 to be found in the Microsoft Update Catalog. Be sure to choose the right one (x86, 22,4 MB).
d) Language pack for .NET Framework 2.0 (KB829019).
e) .NET Framework 3.0: http://web.archive.org/web/20110424022737/http://download.microsoft.com/download/3/F/0/3F0A922C-F239-4B9B-9CB0-DF53621C57D9/dotnetfx3.exe
f) Language pack for 3.0 from Legacy Update.
g) .NET Framework 3.5: http://web.archive.org/web/20181113085418/http://download.microsoft.com/download/6/0/f/60fc5854-3cb8-4892-b6db-bd4f42510f28/dotnetfx35.exe
h) Language pack for .NET Framework 3.5: for the moment, I have not found the download page, but I do have the Swedish URL for the installer, so I have found it earlier.
i) .NET Framework 3.5 SP1: http://web.archive.org/web/20180928200930/http://download.microsoft.com/download/2/0/e/20e90413-712f-438c-988e-fdaa79a8ac3d/dotnetfx35.exe
j) Language pack for .NET Framework 3.5 SP1 offered by Legacy Update.
k) .NET Framework 4: normal version for users: https://www.microsoft.com/en-gb/download/details.aspx?id=24872 .NET Framework 4 full version: https://www.microsoft.com/en-gb/download/details.aspx?id=17718
l) .NET Framework 4.0.3: http://web.archive.org/web/20170803205224/http://download.microsoft.com/download/3/3/9/3396A3CA-BFE8-4C9B-83D3-CADAE72C17BE/NDP40-KB2600211-x86.exe
My own additions to this thread:
Sadly, I have noticed that http://www.google.co.uk/homepage/search/sp-ie.html does not work anymore (on IE7 and newer, of course you have to change the URL to get the web page in your own language or country).
In addition to the overall experience, you can install some DirectX extra components for Windows XP here: http://web.archive.org/web/20180401172135/http://download.microsoft.com/download/8/4/A/84A35BF1-DAFE-4AE8-82AF-AD2AE20B6B14/directx_Jun2010_redist.exe. After having downloaded and extracted (when prompted), you have to manually navigate to the extraction path and double-click the installation file (the .exe file).
More suitable downloads, for the overall experience, are to be found here. Most of the downloads mentioned on this site (Microsoft Visual C++ Redistributables) are being installed automatically when you install a program that needs any of them, but when you use the downloads on this site, you will get the latest updates for each version, which may not be included in the installation of another program.
The last version of Microsoft Visual C++ Redistributable that works on Windows XP is "Microsoft Visual C++ 2019 Redistributable, version 14.27.29114", which can be downloaded here, but please note that most of the downloads in the list on this website are not cumulative, meaning that it's not enough to install this last version to get the full experience. To get the full experience, you have to install all versions (2005, 2008, 2010, 2012, 2013, 2015, 2017, and 2019), but the 2015 version, the 2017 version and the 2019 version are the same single item when you install the 2019 version since that one is cumulative.
As far as I know, KB4500331 is the only (security) update (released after 8 April 2014) that is not included in the POSReady package (since it was released after the end of support even for POSReady). They do all have to be installed manually if you don't activate the POSReady trick. If you do activate the POSReady trick, only KB4500331 has to be installed manually
I have created a libre office file with all available updates so I can carefully look up missing updates
6 out of 10 are not offered within the POSReady updates
KB4012598 - KB4018271 - KB4018466 - KB3197835 - KB4024402 - KB4019204
(the 4018271 is an exception because I didn't install IE8)
regarding the KB2964358 it's not even listed in the Windows catalog website
Now I have tried this myself properly, and not only claimed it, and I have to say that this method really makes it possible to install the language pack for Microsoft .NET Framework 3.0, when it's offered by Legacy Update, after you have installed .NET Framework 3.0 manually. But the language pack for .NET Framework 3.0 does remain as an available update when you install newer versions manually (or by using Legacy Update). If you then try to install the language pack (again), it will fail since there is a newer version of .NET Framework already installed.
I talked about this on the issue # 166. there are two links for the KB951847 but it's the same file size and they include the same installers even though the descritpion doesn't match
Microsoft .NET Framework 3.0: x86 (KB928416) Microsoft .NET Framework 2.0: x86 (KB829019) +++++++++++++++++++++++++++++++++++++++++++++++ Microsoft .NET Framework 2.0 Service Pack 1 (KB110806) (x86) Microsoft .NET Framework 3.0 Service Pack 1 (KB929300) (x86) Microsoft .NET Framework 3.5 Family Update (KB959209) x86 Microsoft .NET Framework 3.0: x86 (KB928416)
NET Framework 4.0.3 has to be installed manually, either way.
ok. I forgot about this one. if it doesn't add up any significant advantage I will just ignore it.
And no, there should not (according to Microsoft) be any download links for .NET Framework 1.1 available anymore since 26 July 2021, but thanks to https://web.archive.org (or http://web.archive.org on older Windows versions), many websites and downloads are still available in some kind!
the WinXP ISO contains a folder called DOTNETFX which refers to NET 1.1 package but I don't know why it's not installed throught XP setup
If you search for the KB number in the Microsoft update catalogue, click on the appropriate update and then click "Package Details", you will find that there are no updates superseding KB2487367 and KB2736428, so yes, they should be necessary.
I asked the question because these two updates are part of the NET 4.0 standalone package if Legacy Update doesn't bring them out to me throught the KB982670 update I won't install them unless you think they are necessary.
In addition to the overall experience, you can install some DirectX extra components for Windows XP here:
https://mcrip-systemfiles.en.lo4d.com/windows https://www.softpedia.com/get/System/System-Miscellaneous/McRip-SystemFiles.shtml
The last version of Microsoft Visual C++ Redistributable that works on Windows XP is "Microsoft Visual C++ 2019 Redistributable, version 14.27.29114", which can be downloaded here
https://github.com/abbodi1406/vcredist/issues/67#issue-1666335832
IE7 is only offered with the other updating alternative but their SUS server doesn't work anymore. http://i430vx.net/files/wsusstuff/
I don't know why it is (or was) offered by the WSUS server, but since WSUS is intended for companies which have to maintain control over a large group of computers with unique computer programs that need, for example, IE7 to work, this may be the reason for IE7 still being offered in WSUS.
well I have just checked out some old screencaps I took back in the day when the other SUS server was up and running. the KB982671 (XP entry removed ?) was offereded alongside the KB982670 and IE 7 KB940767
I found out other security udpates not being offered by Legacy Update KB2813347 - KB969084 - KB2264107 I didn't took it too seriously but there surely are much more missing updates :(
However, I've found that this seems to be an appropriate order of installation if you still want to use the standalone installers.
thanks for this extended explanation but Legacy Update already offers the same language packs for the standalone installers someone asked in portuguese a question regarding this language pack so it used to be a common issue https://answers.microsoft.com/en-us/windows/forum/all/microsoft-net-framework-30-x86-language-pack/16788989-1660-4d40-a295-1d89f63accee
6 out of 10 are not offered within the POSReady updates
KB4012598 - KB4018271 - KB4018466 - KB3197835 - KB4024402 - KB4019204
Well, now I have investigated this a bit. All of those mentioned updates are available in the Windows Embedded version of the support article and in the Microsoft Update Catalog.
Most of them are superseded by newer ones when you use "Automatic Updates" or Legacy Update! Therefore they aren't offered within the POSReady updates. But KB3197835 and KB4024402 don't seem to be superseded and should, therefore, be offered. I've checked my real Windows Embedded POSReady 2009 and they are not installed! Very strange! Maybe this is another example of the update service (originally Windows Update) not working perfect. However, I was able to install KB3197835 and KB4024402 manually on the real POSReady (virtual) machine.
Another possible reason for KB3197835 and KB4024402 not being offered may be this one: they may have been superseded by one or more updates that are not shown in the update catalogue since the catalogue does only show what updates have (not) superseded KB3197835 and KB4024402 for "normal" Windows XP and for Windows XP Embedded, not for Windows Embedded POSReady 2009 since the POSReady version – I believe – uses the "normal" version whose information is intended for the "normal" version (and the "normal" version doesn't have a superseding update!). The superseding updates for POSReady would then be available when you search for updates, and in the catalogue, but we don't know which they are since there is no cross-reference between the newer ones and the older ones since the information for the older ones isn't intended for POSReady.
This would explain why I didn't have to restart the Windows Embedded POSReady 2009 (virtual) machine when I had installed KB3197835 and KB4024402 – maybe the corrections (patches) of the updates have already been installed by another, superseding update!
regarding the KB2964358 it's not even listed in the Windows catalog website
Yes, I know. That's strange. But we have seen that it does exist on the official Microsoft Download Center website.
NET Framework 4.0.3 has to be installed manually, either way.
ok. I forgot about this one. if it doesn't add up any significant advantage I will just ignore it.
I haven't evaluated its benefits, but according to its support article, there are many benefits, of course.
the WinXP ISO contains a folder called DOTNETFX which refers to NET 1.1 package but I don't know why it's not installed throught XP setup
Yes, the English one and the Spanish one (and probably some more) do contain this folder, but the Swedish one and the Windows XP Mode do not.
Neither do I know why it's not installed. It might be classified as optional software which you can install later. Sometimes there is an alternative, during setup, which is named something like: "Copy all installation files from the installation disc to C:\WINDOWS". If you choose this alternative, maybe .NET Framework 1.1 will be installed. Perhaps the same is true for OEM software (custom programs or various add-ons that the computer manufacturer has put on the installation disc).
If you search for the KB number in the Microsoft update catalogue, click on the appropriate update and then click "Package Details", you will find that there are no updates superseding KB2487367 and KB2736428, so yes, they should be necessary.
I asked the question because these two updates are part of the NET 4.0 standalone package if Legacy Update doesn't bring them out to me throught the KB982670 update I won't install them unless you think they are necessary.
Well, there must be a reason for them being marked as "security updates", so they should be necessary. But maybe they are only necessary if you use the standalone installer of .NET Framework 4. Have you installed the full one or the lighter one (the standard version, the same version as Legacy Update offers you)? Furthermore, it seems like I don't have them installed on my Windows XP, either, and I have installed all available updates from Legacy Update and some more discussed in this thread, such as KB2964358.
So yes, maybe you could ignore them since they are not offered by Legacy Update. But, in general, I would always install security updates. However, nowadays I do only use Windows XP as virtual machines without visiting important websites, where you have to log on to the website, and so on, so to me it doesn't matter that much if I forget one update or another.
In addition to the overall experience, you can install some DirectX extra components for Windows XP here:
https://mcrip-systemfiles.en.lo4d.com/windows https://www.softpedia.com/get/System/System-Miscellaneous/McRip-SystemFiles.shtml
The last version of Microsoft Visual C++ Redistributable that works on Windows XP is "Microsoft Visual C++ 2019 Redistributable, version 14.27.29114", which can be downloaded here
Thank you, but I prefer using official software as far as possible, and according to this Microsoft article, this one, and the download centre for Visual C++, version 14.27.29114 is the last one for Windows XP.
I didn't took it too seriously but there surely are much more missing updates :(
This shows us what we already know: you should always set up your copies of Windows before they go out of support. Preferably you should start using a Windows version some months after it was released (or after the first Service Pack) and then search for and install updates for it continuously (at least once a week), until it's not possible to search for updates anymore, and keep a look, continuously, at Microsoft's websites for extra updates. This is the only way to really get all the updates and don't miss any of them. Of course another possibility is to wait for the last Service Pack (or equivalent) being built-in on a Windows computer bought in a shop (OEM) or on an ISO disk image and then do this update work.
[…] someone asked in portuguese a question regarding this language pack [for .NET Framework 3.0] so it used to be a common issue […]
Yes, this is what I've ascertained before in this thread! When you have installed KB951847, or .NET Framework 3.5, you will still be offered the language pack for .NET Framework 3.0 which can't be installed because of the higher version already being installed, but it can be installed if .NET Framework 3.0 is the highest version installed.