It is one of those things that don't get updates so it is enough to install it once. I also don't know how to effectively check if it is installed or not so that I don't try to install it every time. So it is short of there for manual installation if you prefer. I had completely forgotten about it. I will try to figure it out. Thank you for reminding me!
7zip is part of the script already. As goes for browsers I just install firefox esr 56 so that I can get winget. It has a permanent link from mozilla's repository. I might even remove that since I have wrote a small program in C that can handle the downloads and is only 60 kb. I just haven't tested it yet. Also distributing a binary is not ideal. Regarding WMF3.0 the installation is complex and involves patching the servicing stack, restart the computer, install WMF3.0 and then restore the servicing stack back to its original. I have tried in the past to automate it in one script and I haven't managed. Needless to say that even if I do manage at some point it would be an independent script where anyone trying it knows well what they are trying.
tell me why in the file c:\d\assemblies\vista\updateVista-v1.01.0094-20250408\302-CU\filelist.txt there are many links but in the end only 3 files are downloaded?
When a link starts with ';' character the link is ignored by the script when the time comes to determine what to download. The links remain just in case that anyone needs to troubleshot something, see the history or what ever. So as a general habit I just comment them out by adding ';' in front instead of deleting them. I still clean them once a while but I am not in any particular harry to remove old links. Code: for /f "eol=; tokens=1,2*" %%i in (filelist.txt) do ( .... )
Thanks for the answer. Can you also tell me what to change in the script if I want to use the Microsoft update catalog at the end instead of legacyupdate?
If you mean windows update, it doesn't function anymore on windows 6.0. Microsoft dropped support for cryptographic elements that vista / ws2008 suport on april 2024. This is the only reason why i use legacy update. If you want to give it a try anyway just remove / comment out the two registry commands near the end of the scrip. (Somewhere before the detect now command)
you are wrong. updates work. you just need to add the WSUS_Proxy_NT6 package from abbodi1406 to your script. Look, today I turned on the update center (it is not Legacy Update, it is configured for the standard Microsoft update catalog). And there was an update for May 2025 and it was successfully installed. The kernel version became 6.0.6003.23279
If I am wrong why WSUS_Proxy_NT6 has the word "proxy" in its name? Both legacy update and Abbodi's script are exactly that WSUS proxies. Those are needed because we cannot access windows update servers directly anymore. Incorporating a whole script into another script is a lot more work than changing the link from windows update to legacy update. I will have a look at it at some point when I have more time available. (Have a look at this comment) The script has been updated with the May Cumulative update (the out of band one). I was so confused yesterday when after finishing installing the update was still available. I didn't notice the different KB number naturally...
In regards to WSUS proxy: My script is a solution for those who want to backup all the updates (for when/if MS pulls them off) and install them in an offline manner. I don't care particularly much about windows update as an online service. In fact I don't think that you should be online at all with Vista any more. The fact that I even bothered with Legacy update is because of how easy it was to integrate it. WSUS is not as straight forward to integrate since it has requirements that are not met on a fresh installation like VC++ runtime. Regarding BypassESU: At some point I thought that could be useful to some people so I just included it in the tools for download. Other than that I don't use it in the script and the point of it became somewhat moot after Abbodi made the .net repacks which he updates monthly. As such I don't need to update it but rather remove it all together. Regarding the WinDef-Definitions-x64.url: I am not sure what lines you are referring to. Url files are just links and even if you manage to open them with a text editor they have exactly 5 lines of code in them. The only reason why I include it is that when you run it you get the download link for the latest definition updates for defender. Please understand that this whole script was made a few years back when I was learning batch script and has a lot of problems. If I would have to refactor it I would probably just remove half of the code so as long as it works without breaking anything I am happy with it and I would rather focus on other things. Currently I am learning GUI programming in C. If you have any knowledge on this I will happy to listen
ok) in the 3-Waves script, line 325 says echo Installing Windows Update Client, but apparently no installation is taking place. because when I turn on the Update Center, the first thing it offers is to download and install the Installing Windows Update Client. Isn't that what happens here? Or what's wrong with me? today I did a clean install of vista ultimate. executed your last script. only instead of 408-WU_DataStore_Fix, I used 407-BypassESU_LH_v8. and you know what - the update center is working and finds updates. at the same time, I did not use WSUS_Proxy_NT6 and did not even run it. As of today, my Vista kernel version is 6.0.6003.23317
First please edit your previous message instead of posting a new one when you are the last poster. It makes forums much less bloated and easier to navigate and read. In regards with Abbodi's script which you are referring to and is integrated in lines 310 - 559 of the 3-waves script (I could only wish that I had this kind of knowledge to write such an advance script, I have just adapted the paths a bit so that it can work with my script without intervention): It installs the windows update client v7.7 which is installable only on WS2008. So Abbodi has made a script which enables this update on normal Vista installations. The very thing that windows update is working for you proves that this installation was successful.. What is happening after (again as far as I understand it) is that windows update (now being enabled) checks for the newer windows update client for your edition of vista and installs it. This is a behavior that changed at some point 2-3 years ago btw. Before you would get stuck with the "ugly" looking wu client. Regarding 407-BypassESU_LH_v8: It doesn't exist in my script and I have never tried it out. I will probably at some point but as said the time is limited. Regarding 408-WU_Datastore_Fix: While it does exist in my script is commented out since forever. I realized early enough that it is not needed if you don't install kb4575904 and that was the end of it. It remains because the issue we had back then can reoccur at any given point of time. Those two script are doing completely different things btw. You saying "instead of 408-WU_DataStore_Fix, I used 407-BypassESU_LH_v8" makes no sense what so ever to me. I would suggest you to go in this subforum and read everything from start to finish. It will solve a lot of your questions. While doing so you will understand the reason for my first point above.
Did a few mergers. Should be less cluttered now. @xmr2 Please don't double-(or triple-, quadruple-)post. If no one posted after you, edit your posts instead. You can use the following code for inserting a dividing line. [HR][/HR]