@Vertaa Which version of the script did you try? Did you run the scripts in sequence? Like 1 first 2 second waves last? mpas-fe are the definitions for windows defender, nothing related to windows update (which is dead for Vista since last April, hence the legacy update server address is added). The filelist.txt are the links of the updates which then is being parsed by the 2-Download-Extract script and then installed by the waves script. @dudeluv MSE is beyond the scope of this script which is offline (as in not connected to the internet) installation of updates. This is a tool that helps you download all the updates for archiving so that you have a backup if M$ decides to pull the plug on hosting the updates as well help you install them in an automated manner.
I thought he wanted to use MSE, I use it and update it every time I use Vista.You have to do it manually but is fine with me
I cannot upload the updated files because 1.37mb file is to large compressed and its for x86 and x64.
v1.01.0090-20250114 and 1c-Populate-Full.bat. Yes I would like to use MSE though the update button doesn't work. Guess I'll have to learn how to get manually definitions updates.
Installed and working, thanks for this. However, before I did this, I used Legacy Update to get the system fully up to date with all of Vista's updates. In doing so, I've got MSE v4.9.218.0 installed with its EOL message and can't update the definitions. How do I remove this MSE? Unsure of which update it was that did this, no option to uninstall from the "Uninstall a program" in Control Panel either. Edit: On second thoughts, I'm not sure it is working? It grabbed updates for Windows Server '08 from 2020, but says it can't find anymore? I ran the latest script and all the updates from the script seemed to install without error.
This script has nothing to do with MSE. You might get more help if you create a topic related to MSE.
I have a problem, the latest updates are not updated, error 8007F0C6 pops up. Has anyone encountered this?
The only reason is that it will show up for installation in windows update because of metadata missing (I assume), although it is superseded. If you install kb4575904 then it won't show up but then you will need to run the WU_DataStore_Fix by Aboddi. I found it easier to just install both of them. Also note that I haven't updated this section for ages so where I say 2023-12 SMQR read the latest one available. Edit: The script updated with the updates for April.
Hello! This is not a bug related to the script as far as I understand. Definitely not related to Abbodi's script. I think it was a somewhat recent update that is causing this (it showed up few months ago I think) which makes it most likely that it is the cumulative update. I have the same problem on my en-US VM so it is not a matter of language. Definitely worth identifying which update it is causing this in case that it is not the cumulative. I started a new VM and updating it from scratch. I will report back. Regarding splitting the script it is not really practical but the good part is that you can remove any folder/updates that you don't want and the script will just skip them. For example the folders named as bulk can be just removed in my opinion. Nothing important there. They are named also after the description so the easiest thing is to delete any update is named just as "update" versus "security update". Edit: Completing the 3rd stage of the updates (cumulative updates mostly) without touching the 4th stage introduces the bug. Removing the latest cumulative update (kb5055609) restores the normal function of account management. So it is definitely M$ who f...ed it. The question now is going to be which is the latest cumulative update which doesn't introduce this bug. My guess is going to be a year old update. I will come back. Edit2: The latest cumulative update that doesn't break the account management is kb5014010 from 2022-05. So you will have to stay on this one if you plan on adding user accounts via the gui. It might be still possible to manage the user accounts via the command line but I haven't checked. Maybe @abbodi1406 knows more about this.
These scripts work on updating an ISO? I want to try it out on Audit mode and capture a install.wim for an updated Windows Vista x64 ISO.
I have never tried on audit mode. I will be interested to know your results. Directly on iso definitely no.