All Windows Vista Updates

0 views

Skip to first unread message

Patrice Mieczkowski

unread,

Aug 3, 2024, 5:10:59 PM8/3/24

to eginrapte

Finally got the time to create the much requested Update Repository for Vista.
I've collected these updates a year ago, but only recently took the time to put them on my Mega account and organize them.

The first command creates a folder for each individual update and the second one installs each update and extracts onto each created folder.
Here's a practical example. Say, I have all of the updates from the repository located in my Downloads folder inside my user profile. In this case, I want to install every update in the "General" folder. I'd use the commands above like so:

I have an ISO with Server updates through January 2020 that a friend of mine created. It's Ultimate, but the Ultimate Extras aren't pre-installed. (i'll look into releasing the image later) Is there any way to package those into offline msu's too? Bit concerned about that since they could disappear from Microsoft servers without warning.

Must be some telepathy because I just TODAY installed Windows Vista with SP2 just for fun in VMware and found they broke Windows Update due to SHA-2. Offline updating is always better. Thank you! By the way, Windows Vista offline updating finishes must faster if you disconnect from the internet otherwise every update tried to check applicability online and gets super slow. I hope everyone knows this. This was fixed in later versions of Windows.

@greenhillmaniac, which updates exactly are language-specific? I noticed some Ultimate Extras folders were named in Portuguese. I did find the updates with pt-pt or ptg in their file names. Any others too? Are Ultimate Extras non-English?

The updates that say pt-pt or ptg are in Portuguese. All others are language neutral. In fact, the Ultimate Extras are language neutral (forgot to change the folder names). I'd estimate only an extremely small amount of them are specific to my language.

It's Ultimate, but the Ultimate Extras aren't pre-installed. (i'll look into releasing the image later) Is there any way to package those into offline msu's too? Bit concerned about that since they could disappear from Microsoft servers without warning.

Just install the "cab" files through pkgmgr. Works just like you installed them through Windows Update. If you give that Ultimate Extras folder to your friend, he should know how to integrate them into the ISO.

The main advantage of creating a folder for each update is that all the extracted files that pkgmgr extracts will be contained in them. It's easier to maintain and then delete. Plus, I had a few errors (not sure why) when trying to install without specifying a temporary directory, so I like to do it just in case.

HI GHM, I just wanted to thank you for providing all these update files from your MEGA account as it really covers all of the ground work us Vista users would have struggled to achieve. I have been using the batch file you have kindly provided as well, and for the most part, I think it has been working. Checking windows update history is one way to authenticate the installation of a particular update, but I was wondering if there was any way of creating a cmd prompt or text file to see the installs in real time? I've tried to combine some of yours (and others) existing code to do this myself but cant seem to get it to work. I would be nice to know which ones are successful in installation and which have failed. Many thanks for any info!!!

Unfortunately, as far as I know, pkgmgr does not show any visual progress on update installation, unlike its successor, Dism. When an update is not applicable or has been superseded, pkgmgr simply doesn't install it, so you shouldn't have to worry too much about that. As long as you install updates in the correct order (from oldest to newest, installing first the Platform Update alongside IE9), you should be gold.

Ooh ok thanks for that information about pkgmgr not being able to show any visual progress. But what about a log file? Could that be created as the updates are being installed then? I was messing around with a script I found awhile back that I posted in here that installed all the msu, exe, msp, and cab files. It also leaves a log that can be referenced readily at anytime during the Vista updates installation. BUT, I chose not to use it for these cab files because it makes a mess of the update folder where all the updates are. It scatters the .cat, manifest, mum files and x86 folders everywhere through the location folder, not to mention, that it swells the folders to triple the size. The way you created your cab install *.bat file was great and simple because it contains all the files for deletion later. I just thought if it could create a log too, it would be the icing on the cake. I'm not sure if logs can be created because I'm not a programmer and please excuse me for this request if it cant be done, because I have no idea. But many thanks again for what you have provided so far!!

Checking windows update history is one way to authenticate the installation of a particular update, but I was wondering if there was any way of creating a cmd prompt or text file to see the installs in real time?

I'm pretty sure that you cannot install updates that are in the .cab form. Those are meant for slipstreaming updates onto the install disk. Try getting the updates from the windows update catalog here.

I read through your posts and I can only find ones regarding using a .cab update to integrate the update and not to install it. Do you have a link to a specific post with how to install a .cab on an already running version of windows?

You didn't read carefully. It states "The Package Manager command-line options give the following for the /s switch which can be used online or offline (I'm assuming online means while you are using Vista and offline means a mounted image or while in XP).

In the post right after mine by prathapml, he states he installed hold 'em poker using cab file! That shows it can be done. The syntax in that post. You don't need any other reference, but you'll need package manager.

I want to run my microsoft updates from the command line and this looks like the solution. I am not sure what to do with these. do i need to make 2 batch files or just use the bottom one. I can access an elevated command line etc. also am i right that i copy all the updates in to one folder.

I am using Windows Vista Business. I installed the Microsoft "critical updates" via the Windows Update tool on September 14, 2010. After rebooting, the theme seems to have changed to the "Windows Classic" style, and all of the options I've looked at in Personalization and and Themes don't allow me to change it back. I've been using the Windows Vista "look" for more than 2 years, along with the Aero transparent window features, and now they're gone! The "Themes" menu doesn't even list any other themes besides Windows Classic.

I know about System Restore, and will probably try that if my back really gets up against the wall, but before I get to that point does anyone know of something I might try to get my regular Vista UI back that doesn't involve reversing the windows updates, reintalling windows, or buying Windows 7?

I've discovered that when I go to "Performance Options", and view the "Visual Effects" tab, and select the "Custom" radio, I am unable to check either the "Enable Desktop Composition" and "Use Visual Styles on Windows and Buttons" checkboxes. When I check them and then click "OK", then reopen "Performance Options", they are unchecked again.

I had this same problem. No need to uninstall any updates, you just need to reboot your computer again, a second time (after the automatic reboot following the Windows Update), and you get your usual theme back.

It worked right away without restarting your machine nor uninstalling updates... I went to the "control panel" then clicked on "system and maintenance" then clicked on "performance information and tools" and finally clicked on the left pane option "adjust visual effects".

This saved me the trouble of a system restore and was relatively fast and pain free. Not many posts on this yet but hopefully MS will recognize the issue an re-issue the update as I am sure the hole still exists