On 03/02/2023 04:15, gfretwell@aol.com wrote:
> I remember installing XP long after support had expired and it still
> took all the updates overnight.
> Does 7 do that now?
> If not, can you go get them?
> I have 4 new to me W/7 machines with fresh software loads but I think
> at SP1.
>

How to: Get Windows 7 Updates working after a fresh install
-
https://community.spiceworks.com/how_to/132158-get-windows-7-updates-working-after-a-fresh-install

Update Windows 7 All at Once with Microsoft’s Convenience Rollup
-
https://www.howtogeek.com/255435/how-to-update-windows-7-all-at-once-with-microsofts-convenience-rollup/

Windows 7 x64 Updates (2011-2019) ISO
- https://archive.org/details/7upd-64-1

--
Regards
wasbit

In message <u8of1d$3k44k$1@dont-email.me> at Thu, 13 Jul 2023 10:10:04,
wasbit <wasbit@nowhere.invalid> writes
[]
>Windows 7 x64 Updates (2011-2019) ISO
> - https://archive.org/details/7upd-64-1
>
Do you have a similar link for the x86 version? (I tried "7upd-32-1" and
just "7upd", and "7upd-32", but none worked.)
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Parkinson: "What caused your conversion to women - was it the love of a good
one?" George Melly: "No the love of several bad ones" (Lizbuff in UMRA
'01-4-25)

On Thu, 13 Jul 2023 15:05:33 +0100, "J. P. Gilliver"
<G6JPG@255soft.uk> wrote:

>In message <u8of1d$3k44k$1@dont-email.me> at Thu, 13 Jul 2023 10:10:04,
>wasbit <wasbit@nowhere.invalid> writes
>[]
>>Windows 7 x64 Updates (2011-2019) ISO
>> - https://archive.org/details/7upd-64-1
>>
>Do you have a similar link for the x86 version? (I tried "7upd-32-1" and
>just "7upd", and "7upd-32", but none worked.)

I downloaded that package Paul talked about a few days ago but I
haven't had time to try it. I want to image my disk first in case
things go sideways. Life keeps getting in the way.

In message <2fl0bi5pbnr0h8je79tidaift80416r9fo@4ax.com> at Thu, 13 Jul
2023 15:53:33, gfretwell@aol.com writes
>On Thu, 13 Jul 2023 15:05:33 +0100, "J. P. Gilliver"
><G6JPG@255soft.uk> wrote:
>
>>In message <u8of1d$3k44k$1@dont-email.me> at Thu, 13 Jul 2023 10:10:04,
>>wasbit <wasbit@nowhere.invalid> writes
>>[]
>>>Windows 7 x64 Updates (2011-2019) ISO
>>> - https://archive.org/details/7upd-64-1
>>>
>>Do you have a similar link for the x86 version? (I tried "7upd-32-1" and
>>just "7upd", and "7upd-32", but none worked.)
>
>I downloaded that package Paul talked about a few days ago but I
>haven't had time to try it. I want to image my disk first in case
>things go sideways. Life keeps getting in the way.

Ah, would that be
"windows6.1-kb3125574-v4-x86_ba1ff5537312561795cc04db0b02fbb0a74b2cbd
[Windows 7 SP1 Convenience Rollup (32-bit)].msu"? (Bit in [] added by
me.) 331,377,414 bytes. I just wondered if the thing wasbit mentioned
was something different. (Apart from being 64-bit, obviously.)

Just out of curiosity, I tried the normal Windows Update on this machine
(which I bought, second-hand but I suspect with a new version of 7SP1-32
on it, earlier this year); I'm perfectly happy with it as it is, I just
set it to "tell me if any are available" after we'd been having this
discussion. It said - fairly quickly, about two or three seconds of
"Checking for updates" - "Windows could not search for new updates
An error occurred while checking for |
new updates for your computer. | Try again

Error(s) found:

Code 80072EFE Windows Update encountered an unknown error.
Get help with this error"

(which I didn't click on. [Clicking Try again repeated the process.])

So I'll leave well alone (-:

(I image C: from time to time anyway - backing up D: by copying,
somewhat more often - so I should be OK anyway, failing hardware
failure. I was just [mildly] curious.)
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

You need 10 wise men to get back a rock thrown in a lake by an idiot
- Romanian proverb (tweeted by Ovidiu S @plount_os 2023-2-6)

On 7/13/2023 5:49 PM, J. P. Gilliver wrote:
> In message <2fl0bi5pbnr0h8je79tidaift80416r9fo@4ax.com> at Thu, 13 Jul
> 2023 15:53:33, gfretwell@aol.com writes
>> On Thu, 13 Jul 2023 15:05:33 +0100, "J. P. Gilliver"
>> <G6JPG@255soft.uk> wrote:
>>
>>> In message <u8of1d$3k44k$1@dont-email.me> at Thu, 13 Jul 2023 10:10:04,
>>> wasbit <wasbit@nowhere.invalid> writes
>>> []
>>>> Windows 7 x64 Updates (2011-2019) ISO
>>>> - https://archive.org/details/7upd-64-1
>>>>
>>> Do you have a similar link for the x86 version? (I tried "7upd-32-1" and
>>> just "7upd", and "7upd-32", but none worked.)
>>
>> I downloaded that package Paul talked about a few days ago but I
>> haven't had time to try it. I want to image my disk first in case
>> things go sideways. Life keeps getting in the way.
>
> Ah, would that be
> "windows6.1-kb3125574-v4-x86_ba1ff5537312561795cc04db0b02fbb0a74b2cbd
> [Windows 7 SP1 Convenience Rollup (32-bit)].msu"? (Bit in [] added by
> me.) 331,377,414 bytes. I just wondered if the thing wasbit mentioned
> was something different. (Apart from being 64-bit, obviously.)
>
> Just out of curiosity, I tried the normal Windows Update on this machine
> (which I bought, second-hand but I suspect with a new version of 7SP1-32
> on it, earlier this year); I'm perfectly happy with it as it is, I just
> set it to "tell me if any are available" after we'd been having this
> discussion. It said - fairly quickly, about two or three seconds of
> "Checking for updates" - "Windows could not search for new updates
> An error occurred while checking for |
> new updates for your computer. | Try again
>
> Error(s) found:
>
> Code 80072EFE Windows Update encountered an unknown error.
> Get help with this error"
>
> (which I didn't click on. [Clicking Try again repeated the process.])
>
> So I'll leave well alone (-:
>
> (I image C: from time to time anyway - backing up D: by copying,
> somewhat more often - so I should be OK anyway, failing hardware
> failure. I was just [mildly] curious.)
>
Historically, Window Update does not have a good record, when it
comes to patching from unpatched state, upwards.

For example, one OS used a web-based approach, then made it
so an unpatched OS could not communicate with the server.

WSUSOffline knows about this, and it can have a folder with
the five "early patches" needed to up-lift a scruffy OS. It
also does stuff, like feed in up-to-date certificates, so that
there is a better chance of the comms working.

I have tested these, more than once, in a VM.

You may have to use your WSUSOffline media folder, around
five times, with a reboot after each one. The early cycles,
don't do too much, except to prepare the OS for the actual
patching cycle.

The Win7 one has at least 150 patches, and Windows Update
leaks memory a bit. The OS will slow down, before all 150 are
done in one of those patching cycles. You can <ctrl-C> the
script window and kill it, synchronizing your key press to
catch it between patches as best you can. Reboot the system,
run the media again, it will pick right up where it left off.
On a 64-bit OS, if the VM has maybe 5GB of memory assigned
to it, that may provide sufficient memory leak space, for
all 150 patches to be installed in one 40 minute session.
Obviously, 32-bit OSes won't fare as well.

There may be better ways to manage the media, than my description
in the previous paragraph. I was able to get through the whole
mess (even without adding RAM), using just the ctrl-C key combo
for control.

But even if you only ran the first few stages of WSUSOffline,
that's a big bonus for a OS with a completely-broken Updater.

Testing in a VM, and honing your craft, is a cheaper way to do it,
than making an unending stream of backups and restores on the live system.

Paul

In message <u8q235$3pdj2$1@dont-email.me> at Thu, 13 Jul 2023 19:41:23,
Paul <nospam@needed.invalid> writes
>On 7/13/2023 5:49 PM, J. P. Gilliver wrote:
[]
>> So I'll leave well alone (-:
>> (I image C: from time to time anyway - backing up D: by copying,
>> somewhat more often - so I should be OK anyway, failing hardware
>> failure. I was just [mildly] curious.)
[]
>Testing in a VM, and honing your craft, is a cheaper way to do it,
>than making an unending stream of backups and restores on the live system.
>
> Paul
>
>
By "stream of backups", I presume you mean incremental ones. I only do
full images. (I'm not even sure Macrium Free can _do_ incremental ones.)
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

"You play the market?" "No, the ukelele. And I sing too"
- Tony Curtis/Marilyn Monroe in SLIH

On Thu, 13 Jul 2023 22:49:51 +0100, "J. P. Gilliver"
<G6JPG@255soft.uk> wrote:

>In message <2fl0bi5pbnr0h8je79tidaift80416r9fo@4ax.com> at Thu, 13 Jul
>2023 15:53:33, gfretwell@aol.com writes
>>On Thu, 13 Jul 2023 15:05:33 +0100, "J. P. Gilliver"
>><G6JPG@255soft.uk> wrote:
>>
>>>In message <u8of1d$3k44k$1@dont-email.me> at Thu, 13 Jul 2023 10:10:04,
>>>wasbit <wasbit@nowhere.invalid> writes
>>>[]
>>>>Windows 7 x64 Updates (2011-2019) ISO
>>>> - https://archive.org/details/7upd-64-1
>>>>
>>>Do you have a similar link for the x86 version? (I tried "7upd-32-1" and
>>>just "7upd", and "7upd-32", but none worked.)
>>
>>I downloaded that package Paul talked about a few days ago but I
>>haven't had time to try it. I want to image my disk first in case
>>things go sideways. Life keeps getting in the way.
>
>Ah, would that be
>"windows6.1-kb3125574-v4-x86_ba1ff5537312561795cc04db0b02fbb0a74b2cbd
>[Windows 7 SP1 Convenience Rollup (32-bit)].msu"? (Bit in [] added by
>me.) 331,377,414 bytes. I just wondered if the thing wasbit mentioned
>was something different. (Apart from being 64-bit, obviously.)
>
>Just out of curiosity, I tried the normal Windows Update on this machine
>(which I bought, second-hand but I suspect with a new version of 7SP1-32
>on it, earlier this year); I'm perfectly happy with it as it is, I just
>set it to "tell me if any are available" after we'd been having this
>discussion. It said - fairly quickly, about two or three seconds of
>"Checking for updates" - "Windows could not search for new updates
>An error occurred while checking for |
>new updates for your computer. | Try again
>
>Error(s) found:
>
>Code 80072EFE Windows Update encountered an unknown error.
> Get help with this error"
>
>(which I didn't click on. [Clicking Try again repeated the process.])
>
>So I'll leave well alone (-:
>
>(I image C: from time to time anyway - backing up D: by copying,
>somewhat more often - so I should be OK anyway, failing hardware
>failure. I was just [mildly] curious.)

It was the WSUSOFFLINE deal. That is a utility that goes to microsoft
and gets the updates, then installs them. I still haven't installed
them but I have a bunch of updates. I just haven't had time to screw
with it. These are machines made from scratch. This one got the
updates from the original package years ago.