Late to the game for standalone installer script

Topic

New Reply

I have an old Win7 32-bit VM that I would like to revive with post-EOL updates.  The installer script thread is very long and is oriented toward those following the topic for a long time and who are updating on a monthly basis.

 

Playing catch-up, how would one go about implementing post-EOL updates using the standalone script today?

Reply | Quote

Replies

Purchase 0patch Pro.  I never took the MS EOL updates.  I strictly used 0Patch Pro micro-updates. Never had a problem.

Reply | Quote

To use 0patch Pro, the computer must be up-to-date as of Jan 2020 Patch Tuesday.

1 user thanked author for this post.

Alex5723

Reply | Quote

The basic instructions are in the top post #2209020 in this Topic.
You need to be up to date with updates as of Jan 2020.These updates can be downloaded through Windows Update if you use the Rollups.

The updates requirements are included under “Limitations” in that post and in #2377425 (skip the requirements for the ESU licensing). The download links for the update scripts (OS and .NET) are included in #2209020.

You can choose to install the Rollups (cumulative, which contain the IE1 CUs, or use AKB2000003 to install the Security-only (NOT cumulative) Updates and the IE11 CUs.

Basically, you create a folder for the OS updates and W7ESUI and another folder for the dotNetFx4_ESU_Installer_r and the .Net updates, then execute the scripts as Administrator. Follow the directions from there.

You will need to download the updates from the MS Update Catalog.

1 user thanked author for this post.

abbodi86

Reply | Quote

I started to download the needed scripts and was stopped cold by a Firefox warning when I clicked on the link for the .Net related script.  As you can imagine, I did not proceed and would prefer to obtain the .Net related script from a different source.   Is that possible?  This is what Firefox displayed –

Reply | Quote

Standby. I will contact @abbodi86 and get back with you.
I get the same warning in FF90.

1 user thanked author for this post.

EricB

Reply | Quote

OK, try again.
New link should be OK.

Reply | Quote

Thanks, no issues with the new link.

Reply | Quote

My target Win7 Sp1 system is current through January 2020 and meets the SHA2 prerequisite requirements.  It does not have the August 2020 servicing stack installed.

My plan was to use the script to install the July 2021 servicing stack and the June 8, 2021 rollup at the same time and install the July 2021 rollup subject to the defcon level.

For the .Net Framework it seems I have various versions installed — 3.5 SP1, 4.62, 4.7, 4.71, 4.72 and 4.8.  So I downloaded the KB5003779 rollup but I am not sure if I should attempt to use the dotnet script to install all of the items.  Following are the rollup contents –

My understanding of the process is that I do not need to install :

msipatchregfix-x86_94a84b80b8b45a1ac53a0e5d085513da0f099655.exe

ndp45-kb4578955-v4-x86_0d56ddc9a776640fef3a89f287af62ca68370ed5.exe

windows6.1-kb4019990-x86_1365fb557d5e5917cbf59b507eac066ad89ea3f7.msu.  Already installed Windows Update.

Should I proceed as described?

Reply | Quote

You only need the ones with the KB numbers associated with the versions you have installed. Both the version and KB numbers are part of the file name. (example ndp48 is v4.8 and kb5003543) If you have been updating, you will not need the Oct issues for v3.5 and v4.5.2 – the KBs beginning with “4”. See links below.

Each month I publish the released updates for Win7 in https://www.askwoody.com/forums/topic/standalone-installer-script-for-windows-7-esu-regardless-the-license/
Example for July #2377425 and #2377439. If you need older information scroll up, and the same information is (usually) posted at the top of the main Patch Tuesday Blog Post each month when they are released. There is also a link to the older, Archived Standalone thread at the bottom of the top post on the current thread listed above.

Make two folders, one for the OS updates and one for the .NET updates, with the scripts for each included in the associated folder. .NET 3.5 updates need to go in the OS folder using W7ESUI. The .NET 4.x updates go in the .NET folder with dotNetFx4_ESU_Installer_r.

The Rollup is not a single file. In the Catalog, when you click to download the Rollup, you will see the individual version updates. You only need the ones for your version(s) – 47 and 48 since 3.5 is already installed.

Reply | Quote

Thanks for responding.  This would be my very first attempt to update Windows 7 post EOL in January 2020.  No updates have been installed since then.  So it seems to me that I should include the update for .Net Framework 3.5 since that framework version is installed.

I assume that my plan to install the July 2021 service stack update along with the June 2021 is adequate for Win7.

Since the Win7 rollup and the .Net Framework rollup are cumulative it seems to me that I only need to install the relevant June 2021 rollups to become current as of June and before the OK is given for July updates.

Reply | Quote

You should install the Aug 2020 servicing stack (see link 2377425 above) first as it is required. Then the current. SSUs don’t get uninstalled, so you need the required.
The Rollups are cumulative so you need the latest (June ?). I believe the .NET are cumulative also, so scroll up and get June’s.

Reply | Quote

Should the August 2020 SSU be installed separately or can it be combined with the June 2021 rollup?

I’m very confused now.  Before you responded above I ran a test and used the script to install the July 2021 SSU along with the June 2021 Win7 rollup and the .Net 3.5 rollup.  The script completed without error and update installation appeared to proceed normally when restarting the system.  These items appeared as installed updates –

So all appears ok regarding Win7.   Am I missing something here?

Reply | Quote

It has to be installed before the others will install. It is a prereq. Install it first, alone in the folder.
Then you can put the July SSU in with the June Rollup if you want to install it.

1 user thanked author for this post.

EricB

Reply | Quote

Thanks again.  I updated my prior post for a test that seemed to work but based on this response I’ll start over.

Also, during the test the script left a telemetry related .cmd file on the desktop.  Should this be installed on the running system? The readme file talks about this script in the context of offline-integration, not the running system.

Reply | Quote

I created a folder in which I put the .cmd and the associated updates. I leave the folder in place with the script included. Each month, I add the update downloads to the folder. After running, the script cleans up the extracted .cab files in the folder. After the reboot and install completes, I go back and delete the downloaded update files. The next month, the folder with the script contained is ready to go again without hassle.

1 user thanked author for this post.

EricB

Reply | Quote

Well, I used the scripts to bring Win7 and .Net Framework current through June 2021.  They worked flawlessly.

Interestingly, although the .Net Framework detection tool that I used (ASoft .NET Version Detector) indicated that framework versions 4.62, 4.7,  4.71, 4.72 and 4.8 were installed the dotnet script only installed the June 2021 update for the 4.8 framework.  This made sense to me because when I did my own version checking with regedit only the 4.8 version was reflected in the registry.

1 user thanked author for this post.

PKCano

Reply | Quote