In your 3-Waves.cmd script, you install dotNetFx35_x86_x64 and NDP462-x86-x64-ENU, but you don’t install DirectX_Redist_Repack_x86_x64, even though it’s included in the files. Why isn’t it being installed?
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...