Replies

@b: thank you & good to know for next time … I ended up using bold instead

Win7 - PRO & Ultimate, x64 & x86
Win8.1 - PRO, x64 & x86
Groups A, B & ABS

1 user thanked author for this post.

b

Susan …

Today I submitted a long post #2543915 in topic: “Standalone installer script for Windows 7 ESU, regardless the license” where I tried to underline a few paragraph headings.

The post went to moderation ?

Unfortunately, I later realized that I used the wrong BBcode “ul … /ul” instead of the correct code “u … /u” for underlining text.

Because it was sent to moderation, I simply can’t correct my error nor delete then re-submit the post.

When I realized my error, I also discovered I can’t contact a forum moderator via Private Message to correct my error because I am not a Plus Member.

I also tried to do a simple <u>underline text</u> test in the testing forum but it was also sent to moderation as I am now sure this one will as well.

Is it now the case that registered members are essentially no different than anonymous posters ?

If so, it seems to me like a lot more time will now be wasted in trying to correct simple errors and/or delete posts by registered members and/or moderators.

Sorry and with respect, I find it extremely unsatisfying in contributing to discussions not knowing if or when my contributions end up in a black hole as without Private Message I’ll never know it’s gone.

Sincerely …

Win7 - PRO & Ultimate, x64 & x86
Win8.1 - PRO, x64 & x86
Groups A, B & ABS

First and foremost, I too wish to offer a sincere “Thank You” to abbodi86, PKCano & all others assisting us Win7 (& now Win8.1) diehards in keeping our pre-Windows 10 systems updated.

That said, for anyone who might be interested, here’s the Win7 ESU install process/method I’ve used since the very start in Feb 2020 and I’ve never had any install issues except for 1 unexpected hiccup with dotNet updates described after step 13.

Win7 ESU process …

1) created a “-ESU” (no “” marks) folder on Drive C … note: used “-” in folder name so it would sort at top (or bottom) of C drive’s directory listing

2) created a “-DotNET” (no “” marks) folder in the “-ESU” folder

3) downloaded/extracted abbodi86’s “W7ESUi_0.1.zip” script file to the “-ESU” folder … note: replaced “W7ESUI” script with the latest version as it was updated (version “_0.3” up thru Jan 2023)

4) downloaded/extracted abbodi86’s “dotNetFx4_ESU_Installer.zip” to the “-DotNET” folder … note: again replaced “dotNetFx4” script with the latest version as it was updated (version “_r” up thru Jan 2023)

5) download all current month’s “desired & appropriate” MS ESU updates (Security Only, Roll-ups, dotNet, OoBs, Hotfixes, SSUs, etc) from MS Update Catalog to the “-ESU” folder

6) “move” any/all version “4.x.x” dotNet ESU updates (4.5.x, 4.6.x, 4.7.x, 4.8.x) from the “-ESU” folder to the “-DotNET” folder by dragging them to the “-DotNET” folder leaving the dotNet version “3.5.x” updates in the “-ESU” folder

7) run the “W7ESUI” script (latest version) in the “-ESU” folder … installs ALL ESU updates in the “-ESU” folder except the dotNet version “4.x.x” updates in the “-DotNET” folder

8) reboot system when script completes (successful in all my cases)

9) after reboot & 10-15 min wait, open the “-DotNET” folder & run the “dotNetFx4_ESU_Installer” script (latest version) … installs ALL ESU dotNet version “4.x.x” updates in the “-DotNET” folder

10) reboot system when script completes (successful in all my cases)

11) after reboot & 5-10 min wait, verify MS Windows & dotNet updates were successfully installed via: Control Panel | Programs and Features | View Installed Updates

12) move all downloaded current month’s MS ESU updates from the “-ESU” & “-DotNET” folders to offline storage archive (for future use on other systems)

13) perform normal Windows Update to pick up other MS Updates (Office, MSRT, etc) as desired/necessary

The 1 dotNet hiccup …

When MS stopped support for dotNet versions 4.5.2 thru 4.6.1 in Apr 2022, I updated dotNet 4.5.2 to 4.6.2 using the .NET Framework 4.6.2 offline installer. After reboot & 15 min wait, ran normal Windows Update to pick up early dotNet 4.6.2 updates up thru Jan 2020 … all completed successfully.

With all remaining dotNet 4.6.2 updates released after Jan 2020 in the “-DotNET” folder, running the “dotNetFx4_ESU_Installer_r” script resulted in MS Installer FAILED error code message on several updates released in mid/2020 so aborted the “dotNetFx4” script after the 4th MS Installer failure.

The MS Installer failure (don’t remember the exact error code) seemed to indicate that the dotNet “.exe” update packages originally downloaded from the MS Update Catalog shortly after their release date were no longer valid. Re-downloading new ones didn’t help. Further investigation revealed that the MS dotNet update package’s certificate expiration date had passed.

Solution …

Set system date back to Dec 2020 – install all 2020 released updates using “dotNetFx4” script, set system date back to Dec 2021 – install all 2021 released updates using “dotNetFx4” script, set system date to current 2022 date – install all remaining 2022 released updates using “dotNetFx4” script … all 4.6.2 dotNet updates released after Jan 2020 were installed successfully.

Win7 ESU Embedded process … (Feb 2023 successful)

Same as Win7 ESU except … Drive C folder is “-ESU EMB” & dotNet folder is “-DotNET EMB”. Scripts used are the current “W7ESUI_0.4” & “dotNetFx4_ESU_Installer_u” versions placed in their appropriate folders.

Win8.1 ESU Embedded process … (Feb 23 successful)

Win8.1 ESU Embedded is the same as Win7 ESU except … Drive C folder is “-ESU EMB” & script used is “W81ESUI_0.1”.

Since Win8.1 ESU Embedded dotNet update files (3.5.x & 4.x.x versions) are all “.msu” files (as are the Win8.1 ESU Embedded update files), they remain in the “-ESU EMB” folder as they all get installed using the same “W81ESUI_0.1” script. Therefore, no “-DotNET EMB” folder or “dotNetFx4” script is required to install Win8.1 ESU Embedded dotNet updates.

Hope this is helpful to those still having difficulty installing the current crop of Win7/Win8.1 ESU Embedded Updates.

edits: made 5 paragraph headings bold

Win7 - PRO & Ultimate, x64 & x86
Win8.1 - PRO, x64 & x86
Groups A, B & ABS

1 user thanked author for this post.

fl

Thanks @abbodi86 … good to here that nothing’s changed in the Aug-22 SSU update that might impair ESU processing with W7ESUI

Win7 - PRO & Ultimate, x64 & x86
Win8.1 - PRO, x64 & x86
Groups A, B & ABS

@Microfix … tried duplicating your experience with W7ESUI & KB5016676 (Aug-22 SQMR)

I used an old ThinkPad laptop running Win7 PRO SP1 x86 brought fully up-to-date thru Jul-22 except for the latest Jul-22 Servicing Stack Update (SSU) KB5016057 … the SSU currently installed is the previous Mar-22 SSU – KB5011649.

Though I’m absolutely sure my system parameters differ GREATLY from yours … KB5016676 installed successfully without errors and without any deviation from previous W7ESUI installs.

Maybe MS “salted” the latest Servicing Stack Update (SSU) KB5016057 breaking @abbodi86’s W7ESUI script ??? … I’ll find out soon enough once MS DEFCON is lifted to 4 as all my other Win7 systems (both x86 & x64) have the latest Jul-22 SSU already installed.

My Win7 PRO SP1 x86 test system depictions are below along with KB5016676 successful installation and the SFC Scannow results (post Aug-22 SQMR installation) …

p.s.
I know … it’s a really old & practically useless laptop in this day & age but it’s been my Win7 Pro SP1 x86 “W7ESUI Test System” and for this task it’s performed exceptionally well … and I’m also using it right now for this reply …

Win7 - PRO & Ultimate, x64 & x86
Win8.1 - PRO, x64 & x86
Groups A, B & ABS

4 users thanked author for this post.

jburk07, rick41, abbodi86, Microfix

I believe the FireFox HTTP/3 bug in version 96.0 was just fixed in the latest version 96.0.1 released on 1/15/22 as reported by Martin Brinkmann on ghacks.net

Win7 - PRO & Ultimate, x64 & x86
Win8.1 - PRO, x64 & x86
Groups A, B & ABS

1 user thanked author for this post.

lmacri

Good point but … I’m not at all suggesting disabling it … just saying Firefox’s current default setting (True) can be set back to the way it was (False) prior to Firefox version 92 for those who might want (or need) to … like maybe temporarily when using current versions of Firefox to download dozens of files from Microsoft’s “mixed content” Microsoft Update Catalog website …

Win7 - PRO & Ultimate, x64 & x86
Win8.1 - PRO, x64 & x86
Groups A, B & ABS

This recent security feature “default” in newer versions of Firefox can be disabled as described by Martin Brinkmann here …

1. Load about:config in the Firefox address bar.
2. Confirm that you accept the risk.
3. Search for dom.block_download_insecure.
4. Use the toggle icon to set the value to
1. TRUE: to keep the security feature enabled.
2. FALSE: to disable the security feature.

Win7 - PRO & Ultimate, x64 & x86
Win8.1 - PRO, x64 & x86
Groups A, B & ABS

1 user thanked author for this post.

glnz

FYI … ghacks.net provides instructions to disable the Firefox background auto-update function on Windows …

On Windows, updates are now handled automatically in the background using a background agent. Mozilla mentioned the feature in the Firefox 90 release notes, and it is unclear why it is mentioned again in the Firefox 94 release notes.

The agent runs through a task in the Windows Task Scheduler, called Firefox Background Update. You may delete or disable the task, but it may be better to disable the option in the Firefox preferences.

Load about:preferences in the Firefox address bar.
Scroll down to “Allow Firefox to” on the page.
Uncheck “Use a background service to install updates”

Also an interesting discussion concerning which method to use in ghacks comments section …

Win7 - PRO & Ultimate, x64 & x86
Win8.1 - PRO, x64 & x86
Groups A, B & ABS

2 users thanked author for this post.

Lars220, Charlie

Though not as simple to use as an “online scanner”, the free & open source NMAP tool is a very robust network security scanner for both TCP & UDP and much more.

This link describes the command used to scan all 65535 ports.

It can be installed/used on most operating systems including Windows, Linux, FreeBSD, OpenBSD, Solaris, IRIX, Mac OS X, HP-UX, NetBSD, Sun OS, Amiga, and more.

Win7 - PRO & Ultimate, x64 & x86
Win8.1 - PRO, x64 & x86
Groups A, B & ABS

I believe this link will take you directly to GRC’s ShieldsUp!

Win7 - PRO & Ultimate, x64 & x86
Win8.1 - PRO, x64 & x86
Groups A, B & ABS

I suspect you meant to say … “KB5004378” not … “KB5004673” {this doesn’t exist}

Win7 - PRO & Ultimate, x64 & x86
Win8.1 - PRO, x64 & x86
Groups A, B & ABS

I like it … & now I don’t have to roll my own to keep in my tool box

Win7 - PRO & Ultimate, x64 & x86
Win8.1 - PRO, x64 & x86
Groups A, B & ABS

Sorry but, NO … it doesn’t

But this calculator at this website does it up to year 2100

And … the calculator at this website allows you to set the length of the desired search year period for your query.

Example: to find all years with June 12th occurring on Saturday between 1800 thru 2800 …

1) set: “Date to find day of week for:” to Jun 12 1800
2) set: “Optional number of years: #” to 1000
3) click: “Find Day of the Week”

Scroll all the way down near the bottom of the page and you’ll find 140 years listed between 1800 and 2800 with June 12th occurring on Saturday.

Enjoy

Win7 - PRO & Ultimate, x64 & x86
Win8.1 - PRO, x64 & x86
Groups A, B & ABS

1 user thanked author for this post.

wavy

It’s KB4592510

Win7 - PRO & Ultimate, x64 & x86
Win8.1 - PRO, x64 & x86
Groups A, B & ABS