Leaderboard

General and specific solutions for problems regarding AU/WU/MU in Windows XP List of used abbreviations: AU = Automatic Updates AV = Antivirus IE = Internet Explorer KB = Knowledge Base MDL = My Digital Life Forums. Link: https://forums.mydigitallife.net/ MKB = Microsoft Knowledge Base MU = Microsoft Update OS = operating system OSs = operating systems WU = Windows Update WUMT = Windows Update MiniTool We all are well informed about restoring WU/MU in Windows XP. A lot of threads and solutions to get access to WU/MU website. But we are here in a Windows XP forum. Therefore, this thread is targeted on Windows XP only and is meant to collect and provide solutions for general or specific problems which can occur after or while restoring update functionality. The main WU/MU related thread, which is targeted on Windows 2000, Windows XP and Windows Vista, is totally bloated and completely out of control, many post are definitely off-topic. To find general or specific solutions, you have to be a Sherlock Holmes or you'll need a lot of time to read tons of posts with no or low quality of information. And a lot of solutions are simply missing. I am no longer interested in posting new solutions or self-created fixes which can never be found again in such threads. From now on, I rather try to avoid posting in threads where people are talking permanently off-topic. Therefore, I decided to create my own one. Anyway, this main thread can be found here: https://msfn.org/board/topic/178377-on-decommissioning-of-update-servers-for-2000-xp-and-vista-as-of-july-2019/ The second post of this thread contains a numbered list of general solutions for problems regarding AU/WU/MU and methods of restoring WU/MU functionality in Windows XP. After performing these general solutions and methods, users are able to exclude errors or misconfiguration relating to AU/WU/MU in their Windows XP system. It is senseless to solve a specific problem if there is a general one. If WU/MU can't be restored generally and a user thinks about a reinstallation, the general solutions listed in second post can be tried first. There are different solutions to do this restoring successfully. General solutions: Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1216506 The third post of this thread contains a numbered list of specific solutions for problems regarding AU/WU/MU in Windows XP. These specific solutions will be provided with a meaningful title and a link to the creator's post in this thread. Specific solutions: Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1216507 The ninth post of this thread contains a numbered list of additional resources which can be helpful or informative to find an efficient solution for a specific problem. I'll only add resources relating to the topic of this thread. Additional resources: Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1216513 More solutions or resources can be added by posting in commenting zone. The idea is one solution, one post. The same applies to additional resources. Today I start to post some general solutions and methods, a brand-new specific solution and an additional resource. If you want to post an AU/WU/MU related solution or an additional resource in this thread, you can use the commenting zone to do this. Please post it by choosing a meaningful headline in bold and font size 18 for better visibility! If it seems to be a real solution (it's not my job to test them all) or an interesting resource, I will list it in second, third or ninth post with a link to the member's original comment for better overview. Due to the modular character of this thread each posted solution or resource can be upvoted or liked separately with credits to their poster. Any discussions or questions about these solutions or resources are explicitly welcome. But one thing must be totally clear, everything should relate to this topic. That means please stay on-topic! If you enjoyed this thread or maybe you found it interesting and helpful, we would be pleased about any reaction by liking or upvoting and of course commenting. Kind regards, AstroSkipper

Hello to all readers of my thread! As I already mentioned in a previous post, my article "ProxHTTPSProxy and HTTPSProxy in Windows XP for future use" has been updated and enhanced by everything about my program packages in the last weeks. A lot has been rewritten due to the existence of the brand new TLS 1.3 proxies ProxyMII and ProxHTTPSProxy's PopMenu TLS 1.3 3V3. New sections about TLS protocols, cipher suites, and certificates have been added, too! Here is an up-to-date content overview of my article "ProxHTTPSProxy and HTTPSProxy in Windows XP for future use" in the first post of this thread. All orange sections have been revised, all blue sections have been added by me as brand new sections. From now on, all sections are numbered consecutively for a better structure of the article. 1. Introduction: 2. Purpose of ProxHTTPSProxy and HTTPSProxy: 3. Area of application: 4. The TLS protocols and their cipher suites 5. Certificates - CA and Root Certificates 5.1. The CA certficate of ProxHTTPSProxy 5.2. The Root Certificates of Windows XP 6. The TLS 1.2 proxies ProxHTTPSProxy and HTTPSProxy 6.1. Prerequisites: 6.1.1. Detailed information: 6.2. Installation: 6.3. Configuration: 6.3.1. Configuration of ProxHTTPSProxy: 6.3.2. Configuration of HTTPSProxy: 6.3.3. Configuration of these proxies to access the MU website successfully nowadays: 6.4. Usage: 6.4.1. Usage of ProxHTTPSProxy: 6.4.2. Usage of HTTPSProxy: 6.5. Maintenance of ProxHTTPSProxy and HTTPSProxy for future use: 7. The TLS 1.2 proxy ProxHTTPSProxy's PopMenu 3V1 7.1. Prerequisites: 7.2. Purpose and components of ProxHTTPSProxy's PopMenu 3V1: 7.3. Features of ProxHTTPSProxy's PopMenu 3V1: 7.4. Changelog of ProxHTTPSProxy's PopMenu 3V1: 7.5. Installation and configuration of ProxHTTPSProxy's PopMenu 3V1: 7.6. Tranferring all settings of an existing ProxHTTPSProxy's installation: 7.7. Usage of ProxHTTPSProxy's PopMenu 3V1: 8. The TLS 1.3 proxy ProxyMII 8.1. Prerequisites: 8.2. General information about ProxyMII 8.2. How to set up and use the TLS 1.3 proxy ProxyMII: 9. The TLS 1.3 proxy ProxHTTPSProxy's PopMenu TLS 1.3 9.1. Prerequisites: 9.2. General information about ProxHTTPSProxy's PopMenu TLS 1.3 9.3. ProxHTTPSProxy's PopMenu TLS 1.3 3V3 9.3.1. Features of ProxHTTPSProxy's PopMenu TLS 1.3 3V3: 9.3.2. Changelog of ProxHTTPSProxy's PopMenu TLS 1.3 3V3: 9.3.3. Installation and start of ProxHTTPSProxy's PopMenu TLS 1.3 3V3: 10. Versions: 10.1. Versions of the TLS 1.2 proxies ProxHTTPSProxy, HTTPSProxy, and ProxHTTPSProxy's PopMenu: 10.2. Versions of the TLS 1.3 proxies ProxyMII and ProxHTTPSProxy's PopMenu TLS 1.3: 11. Downloads: 11.1. Archived Downloads {obsolete}: 11.2. Latest Downloads: 11.2.1. Downloads related to the TLS 1.2 proxies: 11.2.1.1. Downloads related to ProxHTTPSProxy: 11.2.1.2. Downloads related to HTTPSProxy: 11.2.2. Downloads related to the TLS 1.3 proxies: 11.2.3. Downloads related to cacert.pem Certificate Update: 11.2.4. Downloads related to Root Certificate Updates: 12. Update notifications: 13. Conclusion: 14. Disclaimer: Have a lot of fun while reading! Greetings from Germany, AstroSkipper

Many thanks. I also managed to change small letter to Capital letter of the month October. I was curious if this was possible and how it was done, I hoped the edit would be fast and simple. But, it was not simple and it took long enough to change even 1 letter. So now, knowing how it's done, I would say you are right, the effort is not really worth it. But I am glad we tried it, thanks again.

After a long time I updated the translation to Portuguese Brazil 1046.dll

Bizzbob answered on page 25 July 31.

Solved the DEP problem simply ran sfc /scannow to remove extended kernel and then i reinstalled it. Thanks @Vistapocalypse!

Thanks for testing. Something on my set up, probably. I get this issue even with the latest one published yesterday. I will go back a couple of months and check, over the week. Cheers!

I found the file where the weekdays and months of different languages are contained. The German weekdays and months are located there, too. The file can be found in the folder windows\system32\ and is called locale.nls. Open this file with a Hex editor and search for the corresponding strings in your native language! PS: I was able to edit this file and change successfully the German month "Dezember" to "dezember", just for fun, of course. Frankly, I do not need to change anything with regards to this language file. Anyway, the hex editor I used was WinHex 20.3. You can find my recommendations of hex editors in this post: And now, a final tip! Backup the file locale.nls first and be careful when editing the strings! Do not change other signs, only the first ones of your months and weekdays otherwise you might destroy the file structure! Cheers, AstroSkipper

My Windows XP Professional SP3 is an original German version. I have never thought about in which files the weekdays and months are located. There was no need to do that in the past! When I'm back at my desktop computer, I'll see if I can find these files. But I can't promise anything. Presumably, it depends on the already existing version of Windows XP, too. There are multilanguage versions of Windows XP Professional. Or, the user has installed one or more language packs subsequently. BTW, you should also ask yourself whether all the effort is really worth it just because of the upper and lower case of a few strings. Greetings from Germany, AstroSkipper

Yes, I also think I need to modify my system language files in order to achieve that. (change first Month letter from small to Capital) In Regional and Language Options > Regional Options > Standards and formats the first 10 languages on my system for example, in 8 of them the Month starts with small letter, in 2 of them the Month starts with Capital letter, so it's different for all. Where are these system language files located? And is it possible to modify them?

As another person who just got force-fed 22H2, I second this motion - or actually, third. (It looks to me like they left room for the "Checkboxes" option, but forgot to check whether the user actually wants checkboxes.)

I run XP on all NINE of my computers/laptops. But I do not classify this as "retro-computing". Retro-computing is Commodore C64 or VIC-20, Apple IIe, Tandy 100, et cetera. Not XP. https://en.wikipedia.org/wiki/Retrocomputing

It is not a big deal, since with respect to WUv5 it only adds compatibility with Windows 2000 Service Pack 2. Also, the same story happens as the WUv3 inventory, only updates until October 2005 appear. I'll go the hard way, although its helps to remove the getmanifest.asp error, when checking for updates on the WUv4 Site, it gets stuck at 0% and doesn't throw the 500 error. Something that makes this difficult is that http requests do not appear in fiddler if they are executed in asp code. It must be that asp rejects proxies. It's the only way to get WUv4 to work on Windows 98/ME.