[The fastest windows 10 on earth]

6 hours ago, crashnburn4u said:

Thanks. Wondering if you're still keeping this up to date? 

For the most part, these telemetry updates have all been included in the newest Monthly Rollup, so if you want to avoid it you should use @abbodi1406's script hosted on Askwoody: https://www.askwoody.com/forums/topic/2000012-neutralize-telemetry-sustain-win-7-8-1-monthly-rollup-model/

[Windows Vista Update Repository (until April 2017+)]

11 hours ago, Vista'erest said:

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!!

InstallUpdatesh.Vbs_.vbs 3.23 kB · 0 downloads

You can use the /l flag to create a log. It would go something like this:

start /w pkgmgr /ip /m:C:\Update\update.cab /s:C:\Sandbox /l:C:\log.txt

 

[Windows Vista Update Repository (until April 2017+)]

15 hours ago, Vista'erest said:

but I was wondering if there was any way of creating a cmd prompt or text file to see the installs in real time?

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.

I guess you could just install the Windows 7 AIK and adapt the script to use Dism, as it will act as a wrapper for pkgmgr, but I'm not sure it displays any more information.

[Installing Vista From Scratch]

On 8/24/2020 at 12:51 PM, XPHomeSP3 said:

I guess what I should have asked was whether the Server 2008 updates that can be applied to Vista suffer from telemetry being baked in to their Security Monthly Quality Rollups like Windows 7 and 8.1 do.

It does not. MS never bothered to port DiagTrack to NT 6.0.

[Server 2008 updates on a Vista machine not fully updated till Apr. 2017?]

50 minutes ago, asdf2345 said:

Wouldn't it be easier to install the updates needed for SHA-2, then update Vista?

SHA2 updates disable Windows Update, since they bump the build number to 6003

4 hours ago, TECHGEEK said:

Do you install the pre-EOL updates through pkgmgr in CMD? I am asking this as my knowledge of this is almost nil.

Yes, you open command prompt with admin rights, then run the commands. I recommend you put the updates in a path with no spaces, like "C:\Updates", just so it's easier to run the commands.

[Server 2008 updates on a Vista machine not fully updated till Apr. 2017?]

6 hours ago, TECHGEEK said:

1. Is there any method to install .cab updates from @greenhillmaniac's pre-EOL update repository other than slipstreaming?

Yes, I mention it in the thread.

6 hours ago, TECHGEEK said:

2. Is it pointless to install Server 2008 updates from @greenhillmaniac's other repository without installing pre-EOL updates?

Not entirely, but it is recommended that you install previous updates first. Some of the newer ones might not install without pre-requisites.

[How would I exactly install AMD Radeon 15.6 drivers onto Vista x64?]

Yeah, I posted it in a thread somewhere and it got lost to time (I can't find it either!). I still have those drivers archived: https://mega.nz/file/wgxAFCzJ#N8_D1L59p8isZ2Gz4nmgBPxkdXlFqS52uxbctbvumDQ

They're AMD Embedded drivers based on an early 15.100 branch, still compatible with Vista. To use your R9 300 GPU (or any other, since it has few cards listed) with them you need to edit the INF and add your HWID (I think I added my GPU's HWID in that archive, the R9 380, so you could use that as the baseline for changes specific to your card).

[Updates for Windows 2000, XP and Vista no longer available via WU]

I have a pertinent question... Why create a thread, when this topic is already being discussed:

• https://msfn.org/board/topic/181739-windows-update-error-code-80072efd/
• https://msfn.org/board/topic/178377-on-decommissioning-of-update-servers-for-2000-xp-and-vista-as-of-july-2019/

Furthermore, you're linking to the Server 2008 update repository that I created without any kind of credit.
Honestly, this thread seems pointless...

[Windows Vista Update Repository (until April 2017+)]

15 minutes ago, xpclient said:

Great so I got all English files installed now. With this batch file, I installed all the cab ones without making any mess of tons of files in the folder where the cabs themselves are located:

md %tmp%\Updates
cmd /c for %%U in (*.cab) DO pkgmgr /ip /m:"%%U" /s:"%tmp%\Updates" /quiet /norestart
rd %tmp%\Updates /q /s

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.

[Windows Vista Update Repository (until April 2017+)]

17 hours ago, xpclient said:

@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.

On 8/8/2020 at 11:26 PM, docR said:

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.

On 8/8/2020 at 8:23 PM, IntMD said:

By the way, have you crosschecked with what daniel_k's got to see if there are update urls that you didn't get but he did? Just to make sure we get this s*** complete.

I did go multiple times through this list at the time I compiled it, but I'll try to see what daniel_k has.

[How to install IE11 on Windows 8.0]

Big thanks to @daniel_k for discovering this method.

Tools you'll need:

• A copy of Windows 8 Embedded Standard (MS is gracious enough to provide us with a download link: https://www.microsoft.com/en-us/download/details.aspx?id=37019)
• 7-Zip to make it easier to copy files from inside the install.wim

This tutorial applies to both AMD64 and X86.

1. Download all 3 parts of Standard_8_64Bit_Bootable_IBW if using 64 bit, or all 2 parts if using 32 bits, and open part 1 to extract the ISO. After this you should have Standard_8_64Bit_Bootable_IBW.iso or Standard_8_32Bit_Bootable_IBW.iso
2. Open the ISO with 7-Zip and navigate to "sources/install.wim". Right click on the install.wim and select "Open inside".
3. Inside the install.wim, go to "Windows/servicing/Packages"
   Here's where it differs for both architectures.
   For 64 bit copy the following files into a folder in your computer:

   Quote

    

   
   Microsoft-Windows-Embedded-SKU-Foundation-Package-admin~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-admin~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-base~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-base~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-com~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-com~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-drivers~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-drivers~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-ds~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-ds~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-enduser~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-enduser~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-inetcore~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-inetcore~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-mergedcomponents~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-mergedcomponents~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-mincore~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-mincore~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-minio~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-minio~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-minkernel~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-minkernel~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-net~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-net~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-printscan~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-printscan~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-sdktools~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-sdktools~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-shell~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-shell~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-termsrv~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-termsrv~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-windows~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-windows~31bf3856ad364e35~amd64~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package~31bf3856ad364e35~amd64~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package~31bf3856ad364e35~amd64~~6.2.9200.16384.mum

    

   For 32 bit copy the following files:

   Quote

    

   
   Microsoft-Windows-Embedded-SKU-Foundation-Package-admin~31bf3856ad364e35~x86~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-admin~31bf3856ad364e35~x86~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-base~31bf3856ad364e35~x86~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-base~31bf3856ad364e35~x86~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-com~31bf3856ad364e35~x86~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-com~31bf3856ad364e35~x86~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-drivers~31bf3856ad364e35~x86~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-drivers~31bf3856ad364e35~x86~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-ds~31bf3856ad364e35~x86~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-ds~31bf3856ad364e35~x86~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-enduser~31bf3856ad364e35~x86~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-enduser~31bf3856ad364e35~x86~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-inetcore~31bf3856ad364e35~x86~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-inetcore~31bf3856ad364e35~x86~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-mergedcomponents~31bf3856ad364e35~x86~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-mergedcomponents~31bf3856ad364e35~x86~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-mincore~31bf3856ad364e35~x86~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-mincore~31bf3856ad364e35~x86~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-minio~31bf3856ad364e35~x86~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-minio~31bf3856ad364e35~x86~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-minkernel~31bf3856ad364e35~x86~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-minkernel~31bf3856ad364e35~x86~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-net~31bf3856ad364e35~x86~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-net~31bf3856ad364e35~x86~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-printscan~31bf3856ad364e35~x86~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-printscan~31bf3856ad364e35~x86~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-sdktools~31bf3856ad364e35~x86~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-sdktools~31bf3856ad364e35~x86~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-shell~31bf3856ad364e35~x86~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-shell~31bf3856ad364e35~x86~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-termsrv~31bf3856ad364e35~x86~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-termsrv~31bf3856ad364e35~x86~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package-windows~31bf3856ad364e35~x86~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package-windows~31bf3856ad364e35~x86~~6.2.9200.16384.mum
   Microsoft-Windows-Embedded-SKU-Foundation-Package~31bf3856ad364e35~x86~~6.2.9200.16384.cat
   Microsoft-Windows-Embedded-SKU-Foundation-Package~31bf3856ad364e35~x86~~6.2.9200.16384.mum

    

    

4. Next go to "Windows/winsxs/Manifests" and...
   For 64 bit copy these files into the same folder you extracted the previous ones:

   Quote

    

   
   amd64_microsoft-windows-e..-drivers-deployment_31bf3856ad364e35_6.2.9200.16384_none_4444b38b4ac9d2cc.manifest
   amd64_microsoft-windows-e..-enduser-deployment_31bf3856ad364e35_6.2.9200.16384_none_4e0ff941ac83cf57.manifest
   amd64_microsoft-windows-e..-mincore-deployment_31bf3856ad364e35_6.2.9200.16384_none_b1615a47d2a0b72a.manifest
   amd64_microsoft-windows-e..-termsrv-deployment_31bf3856ad364e35_6.2.9200.16384_none_131cc4307865811c.manifest
   amd64_microsoft-windows-e..-windows-deployment_31bf3856ad364e35_6.2.9200.16384_none_be960147c47f915c.manifest
   amd64_microsoft-windows-e..age-base-deployment_31bf3856ad364e35_6.2.9200.16384_none_8784fd06875ea0f8.manifest
   amd64_microsoft-windows-e..ckage-ds-deployment_31bf3856ad364e35_6.2.9200.16384_none_c995e55f1dc9533e.manifest
   amd64_microsoft-windows-e..ge-admin-deployment_31bf3856ad364e35_6.2.9200.16384_none_93f5fafac0c8e9d2.manifest
   amd64_microsoft-windows-e..ge-minio-deployment_31bf3856ad364e35_6.2.9200.16384_none_e0bddbe35cd9a2e9.manifest
   amd64_microsoft-windows-e..ge-shell-deployment_31bf3856ad364e35_6.2.9200.16384_none_4138dcc43b8b0da7.manifest
   amd64_microsoft-windows-e..inetcore-deployment_31bf3856ad364e35_6.2.9200.16384_none_25eb92fb03493a30.manifest
   amd64_microsoft-windows-e..inkernel-deployment_31bf3856ad364e35_6.2.9200.16384_none_b333814628fd821a.manifest
   amd64_microsoft-windows-e..kage-com-deployment_31bf3856ad364e35_6.2.9200.16384_none_774cef83dac211a4.manifest
   amd64_microsoft-windows-e..kage-net-deployment_31bf3856ad364e35_6.2.9200.16384_none_96316194079798a2.manifest
   amd64_microsoft-windows-e..mponents-deployment_31bf3856ad364e35_6.2.9200.16384_none_51d8b393b2f07e97.manifest
   amd64_microsoft-windows-e..rintscan-deployment_31bf3856ad364e35_6.2.9200.16384_none_1b35530e67f98a3d.manifest
   amd64_microsoft-windows-e..sdktools-deployment_31bf3856ad364e35_6.2.9200.16384_none_6f9fd3dc23f6d73a.manifest

    

   For 32 bit copy these files:

   Quote

    

   
   x86_microsoft-windows-e..-drivers-deployment_31bf3856ad364e35_6.2.9200.16384_none_e8261807926c6196.manifest
   x86_microsoft-windows-e..-enduser-deployment_31bf3856ad364e35_6.2.9200.16384_none_f1f15dbdf4265e21.manifest
   x86_microsoft-windows-e..-mincore-deployment_31bf3856ad364e35_6.2.9200.16384_none_5542bec41a4345f4.manifest
   x86_microsoft-windows-e..-termsrv-deployment_31bf3856ad364e35_6.2.9200.16384_none_b6fe28acc0080fe6.manifest
   x86_microsoft-windows-e..-windows-deployment_31bf3856ad364e35_6.2.9200.16384_none_627765c40c222026.manifest
   x86_microsoft-windows-e..age-base-deployment_31bf3856ad364e35_6.2.9200.16384_none_2b666182cf012fc2.manifest
   x86_microsoft-windows-e..ckage-ds-deployment_31bf3856ad364e35_6.2.9200.16384_none_6d7749db656be208.manifest
   x86_microsoft-windows-e..ge-admin-deployment_31bf3856ad364e35_6.2.9200.16384_none_37d75f77086b789c.manifest
   x86_microsoft-windows-e..ge-minio-deployment_31bf3856ad364e35_6.2.9200.16384_none_849f405fa47c31b3.manifest
   x86_microsoft-windows-e..ge-shell-deployment_31bf3856ad364e35_6.2.9200.16384_none_e51a4140832d9c71.manifest
   x86_microsoft-windows-e..inetcore-deployment_31bf3856ad364e35_6.2.9200.16384_none_c9ccf7774aebc8fa.manifest
   x86_microsoft-windows-e..inkernel-deployment_31bf3856ad364e35_6.2.9200.16384_none_5714e5c270a010e4.manifest
   x86_microsoft-windows-e..kage-com-deployment_31bf3856ad364e35_6.2.9200.16384_none_1b2e54002264a06e.manifest
   x86_microsoft-windows-e..kage-net-deployment_31bf3856ad364e35_6.2.9200.16384_none_3a12c6104f3a276c.manifest
   x86_microsoft-windows-e..mponents-deployment_31bf3856ad364e35_6.2.9200.16384_none_f5ba180ffa930d61.manifest
   x86_microsoft-windows-e..rintscan-deployment_31bf3856ad364e35_6.2.9200.16384_none_bf16b78aaf9c1907.manifest
   x86_microsoft-windows-e..sdktools-deployment_31bf3856ad364e35_6.2.9200.16384_none_138138586b996604.manifest

    

    

5. Now here's the interesting part. Open command prompt with Admin privileges and run:
   If using 64 bit:

   dism /online /add-package /packagepath:<path to folder>\Microsoft-Windows-Embedded-SKU-Foundation-Package~31bf3856ad364e35~amd64~~6.2.9200.16384.mum

   If using 32 bit:

   dism /online /add-package /packagepath:<path to folder>\Microsoft-Windows-Embedded-SKU-Foundation-Package~31bf3856ad364e35~x86~~6.2.9200.16384.mum

6. Reboot and install IE11 like you normally would. This time it will finish the installation and prompt you to reboot. After that, IE11 will be fully operational on your machine!

Here's some pics of the results:

Quote

 

[Windows Vista Update Repository (until April 2017+)]

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.

It has roughly the same format as my post-EOL repositories, with x86 and amd64 versions. A few highlight points:

• Most updates come in ".cab" format, because at the time it was easier to manage bulk installations in this format (I was trying to update offline images)
• Includes hotfixes not distributed through Windows Update. These were collected through a mix of the now defunct MS Hotfix service and the website "hotfixshare". There's some interesting fixes in there.
• While most of the updates are language agnostic, some are specific to the language I use, Portuguese of Portugal (like the IE9 installer). If you'd like to provide a version for your language, please contact me.

To install a ".cab" format update, just run the following command:

start /w pkgmgr /ip /m:<path to updates> /s:<temp path for extraction> /l:<path for log files> /norestart

To bulk install updates, I usually run the following set of commands:

forfiles /p <path to update folder> /m *.cab /c "cmd /c mkdir @fname"
forfiles /p <path to update folder> /m *.cab /c "cmd /c pkgmgr /ip /m:@file /s:@fname /norestart"

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:

forfiles /p "C:\Users\greenhillmaniac\Downloads\General" /m *.cab /c "cmd /c mkdir @fname"
forfiles /p "C:\Users\greenhillmaniac\Downloads\General" /m *.cab /c "cmd /c pkgmgr /ip /m:@file /s:@fname /norestart"

I'd recommend you install no more than 200 updates at a time. This can also be used to create an updated Vista ISO for later use (tutorial coming soon™)

Anyway, here's the link for the repository

Quote

https://mega.nz/folder/MgBRSKKK#rDcZY60CQ7uWMRUcagT4EQ

 

[Would an amd ryzen 7 1800x work on Windows Vista?]

44 minutes ago, asdf2345 said:

Do you still have the ISO? My attempt at making one failed

It's in Portuguese

On the weekend I'll post a tutorial on how to create an up to date image.

[Would an amd ryzen 7 1800x work on Windows Vista?]

1 hour ago, asdf2345 said:

What ISO are you using?

At the time I was using an updated ISO I built.

[[WIP] Windows Vista Extended Kernel]

5 hours ago, win32 said:

Yes, Widevine is also unable to find the MF files and Firefox 68/78 asks me to download the Media Feature Pack for N/KN versions of Windows. The mf.dll/mfplat.dll files are indeed less advanced than in 7 and above so perhaps I'll prioritize extending those files.

Windows 7 did get the update that ported a bunch of stuff from Windows 8, including DirectWrite and I think Media Foundation (though not sure on that last one).

[Certifacte Trust Provider error installing updates]

3 hours ago, lmacri said:

I decided to add a footnote to my instructions in the MS Answers thread Updates not working, it has been searching for updates for hours (where I post as user Great White North) in April 2020 and alert users to your solution since this problem installing KB4014984 has become so common.

I've also used that post for my own Vista installs! Thanks.

[Certifacte Trust Provider error installing updates]

19 hours ago, lmacri said:

Hi greenhillmaniac:

If the user saves the MicrosoftRootCertificateAuthority2011.cer certificate file in the root directory of C:\ (i.e., C:\MicrosoftRootCertificateAuthority2011.cer) is the correct syntax of the command certutil -addstore "Root" "C:\MicrosoftRootCertificateAuthority2011.cer" ?

Yes, it should work.

[[WIP] Windows Vista Extended Kernel]

21 hours ago, win32 said:

Though, while I'm at it, here are the missing functions in ntoskrnl required for Skylake graphics:

Is it possible that GPU drivers have a hard coded OS check at the sys level? I say this, because AMD drivers on Windows 8.0 completely BSOD, while they work just fine on Windows 7 (maybe there could be a similarity to Intel's Vista approach)

[[WIP] Windows Vista Extended Kernel]

11 hours ago, win32 said:

adding UWP support to Vista/7.

How would you go about in implementing this in a conceptual view? UWP seems so linked to the way Windows 10 handles all of its subsystems, it seems like an impossible task.

[[WIP] Windows Vista Extended Kernel]

On 6/21/2020 at 3:41 AM, win32 said:

And getting WDDM 1.1+ drivers on Vista is going to be one difficult undertaking, but probably easier than porting WDDM 1.0 drivers to XDDM (Windows 2000 Display Driver Model).

With that it would be possible to use newer AMD and nVidia GPUs, which would be a dream come true

Do keep on posting updates, this is an extremely interesting project.

[Certifacte Trust Provider error installing updates]

On 6/20/2020 at 4:29 PM, erpdude8 said:

this MS Certificate Authority 2011 certificate is still available for download from MS support article 3149737

That's actually where I got it originally! When I made the post I forgot about its origin. Thanks.

[NTOSKRNL Emu_Extender for Windows XP/2003]

12 hours ago, genieautravail said:

Nice, but do you have download links for already compiled drivers ? 

As you can guess, there could be some legal trouble in sharing modified MS driver files, so having instructions on how to do it is the best way.

12 hours ago, genieautravail said:

I understand the purpose of the NVME or USB 3.0 drivers but what is the purpose of the WDF and storport.sys drivers ?

WDF = Windows Driver Foundation has functions that allow newer drivers to work properly. WDF 1.11 was released with Windows 8.0 and as an update for Vista and 7. storport is a storage related driver that allows the generic AHCI drivers and NVMe to work.

[[WIP] Windows Vista Extended Kernel]

Don't programs load DLLs that are available on the same path as the executable first? Would it be possible to put the modified kernel32 in the program folder so it could use the extra functions it needed?

EDIT: Found this interesting article: https://docs.microsoft.com/en-us/windows/win32/dlls/dynamic-link-library-search-order

[[WIP] Windows Vista Extended Kernel]

9 minutes ago, win32 said:

So here is the first part of the Windows Vista x86 kernel extension tutorial. More functions are to come.

Since the code will be much longer than before, we will use HxD along with CFF Explorer and ExportTableTester to speed up the process.

Take the kernel32.dll from your X:\Windows\System32 folder (on x86 systems) or X:\Windows\SysWOW64 (on x64 systems) and copy it somewhere else. Open that copy of kernel32.dll in CFF Explorer and click "Section Headers [x]" on the left sidebar. Right-click on the table of sections and click the option to "Add Section (Empty Space)". Set the size to 0000B100, then name the new section .xdata. Set the characteristics to 60000020. Close CFF Explorer and open the file in HxD.

While in HxD, copy the code below into your file by right-clicking at the beginning of your new section (which will correspond to 000D2600 or slightly below; the "Raw Address" of .xdata as given in CFF) and then clicking the "Paste write option".

8B FF 55 8B EC 83 EC 30 56 8B 75 0C 85 F6 75 19 68 0D 00 00 C0 FF 15 68 05 D7 7D 50 FF 15 AC 0D D7 7D 33 C0 E9 8F 00 00 00 83 7D 10 28 73 04 6A 7A EB E9 83 7D 10 2C 57 6A 00 6A 30 8D 45 D0 50 6A 03 FF 75 08 1B FF 47 FF 15 20 05 D7 7D 85 C0 7D 12 50 FF 15 68 05 D7 7D 50 FF 15 AC 0D D7 7D 33 C0 EB 53 33 C0 85 FF 0F 95 C0 8D 04 85 28 00 00 00 89 06 8B 45 D8 89 46 04 8B 45 DC 89 46 08 8B 45 E0 89 46 0C 8B 45 E4 89 46 10 8B 45 E8 89 46 14 8B 45 EC 89 46 18 8B 45 F0 89 46 1C 8B 45 F4 89 46 20 8B 45 F8 89 46 24 85 FF 74 06 8B 45 FC 89 46 28 33 C0 40 5F 5E C9 C2 0C 00

This code represents K32GetProcessMemoryInfo, taken from Windows 7 instead of Server 2019.

Open ExportTableTester and drag-and-drop the file into its window. Click "Edit Exports" at the bottom of the window.

Enter the offset corresponding to the "Virtual Address" value for .xdata in CFF Explorer, and then the function name K32GetProcessMemoryInfo below.

Reopen the file in CFF Explorer, click "Rebuilder" on the left sidebar, select the checkboxes for "Rebuild PE Header" and "Update Checksum" then click "Rebuild" before saving.

Shut down Vista and boot into another OS on your PC (or a Linux Live CD/USB if you don't multiboot). Go to your X:\Windows\System32 and rename your present kernel32.dll to kernel32.old (if you're doing it from another Windows, you will probably have to take ownership of the file and adjust the permissions accordingly). Then paste in your edited kernel32.dll before booting into Vista.

Just a thought. Is it possible to fool programs to look for the modified kernel32 instead of actually modifying the system file? For example, renaming the updated file to kernel33 and changing some attributes in the executable to look for that file?

[Certifacte Trust Provider error installing updates]

9 hours ago, mikey8811 said:

Which of the updates from your repository should I install just to be as safe as possible given the outdated system?

The minimum required should be the Servicing Stack update and the Monthly Rollup. Don't forget about the SHA-2 update to install updates newer than September 2019 (though it renders WU useless, since it bumps the build number to 6003).

I actually need to update the repository with January's MR (you can just get it from here for now).