Discussion:
Tip: Service Pack 1
(too old to reply)
T
2019-08-16 22:12:53 UTC
Permalink
Hi All,

Had a customer yesterday that needed Service Pack 1 (SP1)
installed manually. Looked all over M$'s web site and
found several. They ran and no service pack 1 afterwards.
I finally found the correct KB with the correct SP1 that
Windows Update recognizes.

Here are my notes:

-T

Windows 7: Manual installation of Service Pack 1:

There are a lot of hits on Windows 7 Service Pack One, including
on M$'s own web site, that are not actually the correct service pack
that is recognized by Windows Updates


The correct service pack is KB976932:

https://support.microsoft.com/en-us/help/15090/windows-7-install-service-pack-1-sp1

Tip: scroll down to
"Download and run the System Update Readiness Tool"

Windows 7 64-bit (x64)
http://go.microsoft.com/fwlink/?linkid=181491

Windows 7 32-bit (x86)
http://go.microsoft.com/fwlink/?linkid=181492
VanguardLH
2019-08-17 00:40:58 UTC
Permalink
Post by T
Had a customer yesterday that needed Service Pack 1 (SP1)
installed manually. Looked all over M$'s web site and
found several. They ran and no service pack 1 afterwards.
I finally found the correct KB with the correct SP1 that
Windows Update recognizes.
There are a lot of hits on Windows 7 Service Pack One, including
on M$'s own web site, that are not actually the correct service pack
that is recognized by Windows Updates
https://support.microsoft.com/en-us/help/15090/windows-7-install-service-pack-1-sp1
Tip: scroll down to
"Download and run the System Update Readiness Tool"
Windows 7 64-bit (x64)
http://go.microsoft.com/fwlink/?linkid=181491
Windows 7 32-bit (x86)
http://go.microsoft.com/fwlink/?linkid=181492
Seems to be easily discoverable by searching Microsoft's update catalog
site at:

https://www.catalog.update.microsoft.com/

I did a search on "windows 7 service pack 1" and the first entry was for
the KB article you mentioned. However, that was for x64. The x86
(32-bit) SP-1 wasn't listed, so I did an online search of:

https://www.google.com/search?q=windows+7+service+pack+1+x86

First hit was for:

https://support.microsoft.com/en-us/help/15090/windows-7-install-service-pack-1-sp1

and that had a link to:

https://www.microsoft.com/en-us/download/details.aspx?id=5842

After clicking on the Download button, the next page listed the .iso
file which doesn't indicate x86 or x64; however, because of its 1.9GB
size which is twice the size of the x64-only download, the ISO probably
contains SP-1 for both x86 and x64. I downloaded the ISO file and
looked inside. It has 3 SP-1 update files: x86, x64, and ia64.
T
2019-08-17 02:40:04 UTC
Permalink
Post by VanguardLH
Post by T
Had a customer yesterday that needed Service Pack 1 (SP1)
installed manually. Looked all over M$'s web site and
found several. They ran and no service pack 1 afterwards.
I finally found the correct KB with the correct SP1 that
Windows Update recognizes.
There are a lot of hits on Windows 7 Service Pack One, including
on M$'s own web site, that are not actually the correct service pack
that is recognized by Windows Updates
https://support.microsoft.com/en-us/help/15090/windows-7-install-service-pack-1-sp1
Tip: scroll down to
"Download and run the System Update Readiness Tool"
Windows 7 64-bit (x64)
http://go.microsoft.com/fwlink/?linkid=181491
Windows 7 32-bit (x86)
http://go.microsoft.com/fwlink/?linkid=181492
Seems to be easily discoverable by searching Microsoft's update catalog
https://www.catalog.update.microsoft.com/
I did a search on "windows 7 service pack 1" and the first entry was for
the KB article you mentioned. However, that was for x64. The x86
https://www.google.com/search?q=windows+7+service+pack+1+x86
https://support.microsoft.com/en-us/help/15090/windows-7-install-service-pack-1-sp1
https://www.microsoft.com/en-us/download/details.aspx?id=5842
After clicking on the Download button, the next page listed the .iso
file which doesn't indicate x86 or x64; however, because of its 1.9GB
size which is twice the size of the x64-only download, the ISO probably
contains SP-1 for both x86 and x64. I downloaded the ISO file and
looked inside. It has 3 SP-1 update files: x86, x64, and ia64.
The hit was better when I switch from Yahoo search to google
T
2019-08-17 03:55:48 UTC
Permalink
Post by VanguardLH
Post by T
Had a customer yesterday that needed Service Pack 1 (SP1)
installed manually. Looked all over M$'s web site and
found several. They ran and no service pack 1 afterwards.
I finally found the correct KB with the correct SP1 that
Windows Update recognizes.
There are a lot of hits on Windows 7 Service Pack One, including
on M$'s own web site, that are not actually the correct service pack
that is recognized by Windows Updates
https://support.microsoft.com/en-us/help/15090/windows-7-install-service-pack-1-sp1
Tip: scroll down to
"Download and run the System Update Readiness Tool"
Windows 7 64-bit (x64)
http://go.microsoft.com/fwlink/?linkid=181491
Windows 7 32-bit (x86)
http://go.microsoft.com/fwlink/?linkid=181492
Seems to be easily discoverable by searching Microsoft's update catalog
https://www.catalog.update.microsoft.com/
I did a search on "windows 7 service pack 1" and the first entry was for
the KB article you mentioned. However, that was for x64. The x86
https://www.google.com/search?q=windows+7+service+pack+1+x86
https://support.microsoft.com/en-us/help/15090/windows-7-install-service-pack-1-sp1
https://www.microsoft.com/en-us/download/details.aspx?id=5842
After clicking on the Download button, the next page listed the .iso
file which doesn't indicate x86 or x64; however, because of its 1.9GB
size which is twice the size of the x64-only download, the ISO probably
contains SP-1 for both x86 and x64. I downloaded the ISO file and
looked inside. It has 3 SP-1 update files: x86, x64, and ia64.
Oh you know another one of my problems was that had at first
read the failed SP1 KB from the M$ Update report. And when
I look up the KB, it said the same stuff you said above. And
they even installed, but no tomato.

I did have to go in and do a reset. I even had to use Linux
Live to get around some of the freakin' file locks.

And yahoo's search engine truly sucks.
Paul
2019-08-17 03:06:15 UTC
Permalink
Post by T
Hi All,
Had a customer yesterday that needed Service Pack 1 (SP1)
installed manually. Looked all over M$'s web site and
found several. They ran and no service pack 1 afterwards.
I finally found the correct KB with the correct SP1 that
Windows Update recognizes.
-T
There are a lot of hits on Windows 7 Service Pack One, including
on M$'s own web site, that are not actually the correct service pack
that is recognized by Windows Updates
https://support.microsoft.com/en-us/help/15090/windows-7-install-service-pack-1-sp1
Tip: scroll down to
"Download and run the System Update Readiness Tool"
Windows 7 64-bit (x64)
http://go.microsoft.com/fwlink/?linkid=181491
Windows 7 32-bit (x86)
http://go.microsoft.com/fwlink/?linkid=181492
You can use the WSUSoffline kit, to prepare a folder
full of updates, with an application inside to apply them.

It's scripting, and the files come off a Microsoft server
and not off the Wsusoffline site.

http://www.wsusoffline.net/

05.08.2019 Version 11.8 released [likely Win7+]

04.06.2019 Version 9.2.5 ESR [should be suitable for WinXP,
don't know if Vista is in there]

Vista is perilously close to unmaintainable, and is a
waste of brainpower for an IT guy to try to fix. It
took me three tries to get the install order right,
and tip the Windows Update engine upright long enough
to finish. Each session took me a couple of days, to
try to finish.

The Wsusoffline people, have determined what "prerequisite"
files must be installed first, to keep Windows Update
responsive. In some cases, that's about 5 of the 150 plus
updates, that must be installed first, because they
prune the supersedence tree nicely. Vista used to have
information like that available, but as soon as some
shitty little update comes out, it can "break Vista
all over again" and then Windows Update never comes
back with a list of updates.

As part of good practice, you should be running these
patching strategies at home in your spare time. I've done
a few of these, am not an expert, but can see the
advantage in the field of being able to say
"yes, I can fix that".

You don't need any fancy facilities for Wsusoffline.
You could collect the information on a hard drive folder,
copy it to a USB stick as required, and slip it into
your kit bag before you go. You don't have to follow
any of the cheesy suggestions to "burn a DVD" or something.
That's not necessary.

It'll probably be at least 2GB of downloads, or a bit more.

Wsusoffline won't likely use the Win7 SP1 rollup, and some
attention will have been paid to a "CEIP free" version.
But it's pretty hard to patch up to date and stay CEIP free.
Or avoid the library that assists in running Universal
Apps or something. There's a couple items "the kids don't like".

So what you want to do as a "Windows Expert" is try the
different patching methods, time them, and see which
ones are a big win. To time the automation, you can leave
a screen recorder running, so you can review the progress
later. I think Wsusoffline needs multiple reboots (thanks
to Microsoft), and unfortunately I don't think there is
a way around that part. It has to do with installing
an updated version of Windows Update, plus some other
unsavory stuff.

And with any luck, they will also avoid installing any
WGA packages. (Windows Genuine Advantage).

I patched up Windows 7, one patch at a time, reading
every patch description and rejecting patches with
suspicious descriptions. It took me *hours* and my neck
was sore from the stress later :-) You have to try that
once, as a benchmark. That would be "what a tinfoil hat
person must pay for good patching".

While there are currently "security only" patches, they
don't cancel their more bloated counterparts. So it's not
like such a strategy is particularly easy or safe.
(If one of the bloated packages installs because
you made a mistake, your effort is in vain.)

Wsusoffline doesn't have to be any faster. It avoids the
download step (because you download them in advance). If
there is a problem with wuauserv, Wsusoffline can stop dead
in its tracks. This is why, on occasion, you need to test it.
Just to make sure it's still workable. This is part of the
reason they need to test their prerequisites list, to
ensure the engine is ready to go for the rest of the updates.

Once Windows 7 is patched far enough, any of the Jumbo
patches should install with less fuss. A more likely case
though, is the one you ran into, which is essentially as
bad as a reinstall for all practical purposes.

If you tick the box, Wsusoffline will include x86 and x64 versions
of SP1 installer package. So you can have it include those,
just plug it in and walk away. Checking early on, that
the train hasn't left the tracks. Once the 150 start
bunging in, enough has happened by that point it should
be OK.

At the current time, Wsusoffline should be installing the
SHA2 signing patch, so that the signing will work. The
installer checks that the packages are valid, before installing
them.

Paul
T
2019-08-17 03:29:15 UTC
Permalink
You can use the WSUSoffline
I have used it. It is great stuff.

All I really need top do was get SP1 installed so I could
get Dot Net to install.
Paul
2019-08-18 21:56:00 UTC
Permalink
Post by T
Post by Paul
You can use the WSUSoffline
I have used it. It is great stuff.
All I really need top do was get SP1 installed so I could
get Dot Net to install.
I did some timings.

Wsusoffline (current version) 2 hours 30 minutes install time
Probably around 5 reboots (I lost count).

Native Windows Update It was set to beat Wsusoffline, but when it
throws errors, the extra time needed to hunt
down the error numbers, extends the time.
If you use the "Convenience Rollup", that can
cut down on the 150 individual updates needed.
It might have been a bit over 2 hours if it had
worked. Instead it took 2 hours 15 minutes.

There is a difference in quality of install as well. Wsusoffline
has a tick box for "use Security Only patches", which means
CEIP and the Universal App library might not be there.

Wsusoffline still leaves items in Windows Update, but the said
items are "functionally" duplicates of the Security Only ones.
I don't know how you're supposed to handle those, to maintain
the partitioning. (So someone on MDL would be "proud of you".)

Summary:

1) One hell of a long time to patch an OS.
Microsoft should not be proud of this.

2) Even after two and a half hours, your job
is not finished. You have all those "unlabeled"
Optional packages, like "adding the Pound symbol
to the Pago Pago version of Windows 7" or "Time zone
change for Puerto Rico". And you have to look up the KB,
to get the details. A customer who is paying you,
expects you to sort through that crap, and there can be
as many as 60 of those.

A person who maintains their own OS, could "hide"
those after reading them, as a management technique.
If you process them as they show up, you can distribute
the task over multiple sessions.

Paul
Ant
2019-08-19 01:42:41 UTC
Permalink
Paul <***@needed.invalid> wrote:
...
Post by Paul
Wsusoffline (current version) 2 hours 30 minutes install time
Probably around 5 reboots (I lost count).
Native Windows Update It was set to beat Wsusoffline, but when it
throws errors, the extra time needed to hunt
down the error numbers, extends the time.
If you use the "Convenience Rollup", that can
cut down on the 150 individual updates needed.
It might have been a bit over 2 hours if it had
worked. Instead it took 2 hours 15 minutes.
There is a difference in quality of install as well. Wsusoffline
has a tick box for "use Security Only patches", which means
CEIP and the Universal App library might not be there.
Wsusoffline still leaves items in Windows Update, but the said
items are "functionally" duplicates of the Security Only ones.
I don't know how you're supposed to handle those, to maintain
the partitioning. (So someone on MDL would be "proud of you".)
1) One hell of a long time to patch an OS.
Microsoft should not be proud of this.
2) Even after two and a half hours, your job
is not finished. You have all those "unlabeled"
Optional packages, like "adding the Pound symbol
to the Pago Pago version of Windows 7" or "Time zone
change for Puerto Rico". And you have to look up the KB,
to get the details. A customer who is paying you,
expects you to sort through that crap, and there can be
as many as 60 of those.
A person who maintains their own OS, could "hide"
those after reading them, as a management technique.
If you process them as they show up, you can distribute
the task over multiple sessions.
This is why we need service packs so we can slipstream into our own
Windows. Or better, give us updated W7 installer like their W10 that
includes all the updates.
--
Quote of the Week: "It is certain that there may be extraordinary mental
activity with an extremely small absolute mass of nervous matter: thus
the wonderfully diversified instincts, mental powers, and affections of
ants are notorious, yet their cerebral ganglia are not so large as the
quarter of a small pin's head. Under this point of view, the brain of an
ant is one of the most marvelous atoms of matter in the world, perhaps
more so than the brain of a man." --Charles Darwin (from The Origin of
Species, 1859)
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org /
/ /\ /\ \ http://antfarm.ma.cx. Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )
Paul
2019-08-19 03:53:58 UTC
Permalink
Post by Ant
This is why we need service packs so we can slipstream into our own
Windows. Or better, give us updated W7 installer like their W10 that
includes all the updates.
There *is* actually an updated W7 installer.

The people on MDL refer to it as the "Intern disc set",
because of some of the mistakes made. If all you need
is a "maximal efficiency disc to snow a customer machine",
it might even be a good choice. Just not the best
choice for your personal machine. It's not
a complete set either. Starter is missing, as is
Home Basic. Just Home Premium, Pro, Ultimate.
There is only one OS on those discs (not multi-SKU
like the release discs).

*******

I would sooner wait 2 hours 30 minutes for a quality
job on my personal machine, than just bodge in a bunch
of crap I haven't checked in 2 hours plus change.

I haven't had to reinstall my Win7 since I installed
it, and the idea of doing that isn't all that appearing.
My timings were done on test installs (not activated).
And just to see if there was a significant difference
in runtime. But the difference isn't big enough to
get excited about.

Paul

Mayayana
2019-08-17 12:56:47 UTC
Permalink
"T" <***@invalid.invalid> wrote
|
| Had a customer yesterday that needed Service Pack 1 (SP1)
| installed manually. Looked all over M$'s web site and
| found several. They ran and no service pack 1 afterwards.
| I finally found the correct KB with the correct SP1 that
| Windows Update recognizes.
|

You seem to do a lot of tech support. Why didn't you
already have the file? You should keep backups of all
such things. There's no telling when you might not be
able to get them.

I always look around until I find the actual direct download
link. There are usually tech support sites that post them.
Then I back up the file so I never have to do that again.
Microsoft go to great lengths to make it convoluted and
force you to enable script. I see no reason not to assume
that they're rummaging around on your system when you
get the download from their page. There's no other excuse for
requiring script, even in the download link itself.

I keep copies of SP1, the "SP2" rollup, the winhttp update
that enable TLS 1.1 and 1.2 in winhttp on Win7, the update
to enable reading HLP files, and a couple of security updates
for things like CPU vulnerabilities.

Examples: Here's the link for SP1 64. It seems to still be valid:

http://download.microsoft.com/download/0/A/F/0AFB5316-3062-494A-AB78-7FB0D4461357/windows6.1-KB976932-X64.exe

This is the link for the winhttp TLS update for Win7-64:

http://www.download.windowsupdate.com/c/msdownload/update/software/updt/2016/04/windows6.1-kb3140245-x64_5b067ffb69a94a6e5f9da89ce88c658e52a0dec0.msu

It still works. But at some point it might not. So you shouldn't
just share the page links. Share the file links and keep backed up
copies yourself.

Microsoft break their links more than any website I know. (Though
I haven't yet seen them break one of those ridiculously long
direct file download links.) They're notoriously
bad at designing and organizing their data store. That's probably
partly due to design-by-committee. It's probably also due partly
to their tendency to not know when to quit. They're addicted to
complexity. But I think it's also partly a design to keep control
over their customers and charge as much money as possible.

For instance, their MSDN docs. They should offer a download,
but they don't. It's expensive to get a subscription. It *is* all
online, but you could spend days going from one page to the next,
trying to get the info you need. One topic with a table of
contents will be broken into dozens or hundreds of pages.

They even lie. Older MSDN docs used to accurately say which
version of Windows was the first to support a particular function.
More recently they're apt to lie and say they only work in recent
or supported versions. For instance, GetUserName. My copy of
MSDN says it's supported in Win3.1NT and win95. The current online
docs say it requires Win2000 Pro. When they were first trying to
phase out XP many of their API pages said Vista was the oldest
supported OS version! They actually changed the docs to lie,
in order to make people think that XP was no longer a usable
system. But in terms of the base API, Win95 is still perfectly
up-to-date.

If Microsoft decide it's in their interest to stop offering downloads
for Win7 then they'll do exactly that. There may be no notice.
I don't think most things are available anymore for XP. (The TLS
update, for instance, was only available for XP kiosk.)

Win7 SP1 was released in 2010. That means you shouldn't have
needed to download it for the past *9* years. You should have
saved a copy in 2010. I actually put all that kind of thing on DVDs,
along with things like UBCD and other boot disks, which I keep
in a sort of briefcase, which I can take with me if I need to work
on someone's computer.
T
2019-08-18 23:16:08 UTC
Permalink
Post by Mayayana
You seem to do a lot of tech support. Why didn't you
already have the file
I do. I forgot my sinkin' briefcase !!!!!
Continue reading on narkive:
Loading...