UpdateVista from SP2 to 2025-01 Script

The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
Press any key to open the download link for wget-x86.

This is the shortcut for wget. (Lines 39-43) if I read this correctly.
You never got the link opened in firefox right?
Download manually for now (link on line 19 -replace %bit% with 32). Place it in 000-wget\x86\
This should bypass the loop. I will investigate more later.
Thank you for your help!

The name must be wget.exe

 

Here is the problem. The folder is renamed to 000-wget. I changed it recently. It makes more sense to be in the first folder instead of somewhere between other stuff. How come and you had a 409 folder? I guess you had archived the updates and the folder structure? I reinstalled virtualbox 6.50 today and testing the 32bit as we speak. It run fine after reverting to the old architecture check and saving the file in 000-wget. I will have to rethink the messages on the terminal I guess so that they are more descriptive of what actually matters.

 

I had the 409-wget folder because it was the next available folder back then. Soon enough though it stop making any sense so I changed it to 000-wget since it is the first thing you need to download anyway.
As of the problems at hand I finally downgraded VirtualBox and I run both x86 and x64 scripts. I realized that I have a lot of bugs when it comes to the extras for ultimate which I have mostly fixed now. I didn't got your problems though. In my VMs the script just worked. Even with the new logic for determine architecture which I assumed initially that it was the problem. I turn to believe that the name of the executable and the path was the problem in your case. I will have to refine the messages for sure because they are at least part of the confusion.
Pay attention on the :WGET label (lines 21 to 69 in the current version 1.01.0086)
There are two checks there one on line 22 and one on line 58. In both cases the filename and path of wget needs to match the checks otherwise you will be in loop forever.

Code:

if not exist "%~dp0000-wget\%arch%\wget.exe" (

This code for you means 000-wget\x86\wget.exe
So wget must be placed there with the correct file path.

@dudeluv I just realized that the Error message were giving the previous folder which was 409. This is obviously not correct since all the check were for the folder 000-wget. It was forgotten from the previous version. Sorry about that!

Edit: I have uploaded v1.01.0087 now. This should work for you now. Sorry for the frustration that I have caused.

 

This is the SHA-2 support. You cannot find it for vista because it is a WS2008 update. If this update didn't install properly you are missing many more updates. Every update from 2019+ is sha2 signed.

Check if it is in the folder 101-Important.If the file it is there check if it installs or gives an error. If it installing fine delete all the wave*.txt files start over the script after a restart.

I just did a minimum updated on a fresh vm and everything went fine. Any chance that wget was interrupted while downloading?

 

The update for tinker is Aug2008_d3dx9_39_x86_Redist which is included in the directx repack. So I don't have it separately.

The KB3196718 is superseded by KB4014794 which is included in 101 important. In some cases windows update can give you a superseded update though. I am not sure why.

The MRT cannot be installed outside windows update as far as I know (@George King have you found a way for this one? -Thank you!)

KB946253 is "RC1-GDI-Black-Screen-External-Monitors-Docking-Laptops". This is a cab file that I have offline but I didn't have a link for, although now that I think about it I could search for the link in the windows log file. It is fairly irrelevant update though at any rate. I even use docking station on vista laptops and I never had the described problem so I assume it is related to some specific docking station.

Overall it looks good. I could install directx as part of the script but I am not sure if everyone needs it so for the time being the setup is downloaded only. I could add a relevant message though so that people know to install it manually if they want.

 

Thank you for your suggestions!
Regarding legacy update: Every time I tried it on a physical machine it worked. When I try it on VMs some times does sometimes doesn't not. Resetting the data store is a potential fix for the problem but I haven't test this enough.
Regarding WSUS Proxy: I have said before when some people asked me to add legacy update that this script is meant as an offline update pack (offline as in offline from internet not as in WIM integration). As such it doesn't really matter even if I had the time to play around (which I don't).
Regarding MSE: If you are so invested in security you shouldn't use Vista in first place. Especially if the link is changing daily it is impossible for me to maintain it. I do create a shortcut that downloads the latest defender databases though and anyone can click on it as often as one likes. The latest MRT tool though can be installed only via a working windows update one way or the other. (again don't go online with Vista unless you don't mind wiping the VM/restoring an earlier snapshot when you are done.

Next time I have the time to update the script though I will consider adding a shortcut for the MSE 4.4.304. (Not such plans for this month since the latest cumulative breaks browsers and who knows what else.

 

I have updated the links with the 2025-01 updates. I didn't had time to test it though. Legacy update gets a bit wonky when I try to update the VM. On physical computers should work fine though.

 

I am not doing anything related to mse in my script and I have never installed mse on vista in general so I don't know.