greenhillmaniac

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/

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

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.

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

SHA2 updates disable Windows Update, since they bump the build number to 6003 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.

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

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

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

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.

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. 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. I did go multiple times through this list at the time I compiled it, but I'll try to see what daniel_k has.

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. 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 Open the ISO with 7-Zip and navigate to "sources/install.wim". Right click on the install.wim and select "Open inside". 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: For 32 bit copy the following files: Next go to "Windows/winsxs/Manifests" and... For 64 bit copy these files into the same folder you extracted the previous ones: For 32 bit copy these files: 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 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:

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

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

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

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

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

Yes, it should work.

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)

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.

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.

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

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

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

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?

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