[prev in list] [next in list] [prev in thread] [next in thread] 

List:       patchmanagement
Subject:    RE: [patchmanagement] Server 2016 Update Error 0x800705b4
From:       Steve Yates <steve () teamITS ! com>
Date:       2018-05-30 18:27:36
Message-ID: e4264a6cda634e9c9f72bdc65aec33d0 () ITS-SERVER-1 ! its ! local
[Download RAW message or body]

	Somewhere around late last year I think, give or take, MS changed their scheme for \
Windows 10 updates so the Feature Update for build "n" will now always change to have \
the KB number of the last monthly update.  In other words the KB of the Feature \
Update will change at every CU release.

	That said, you posted the words "feature pack" so possibly it was mismarked on MS's \
end?

	Is https://support.microsoft.com/en-us/help/4103720 listed, which is the CU from May \
17?

--

Steve Yates
ITS, Inc.


From: Stanley, Jeremy B (HSS) [mailto:jeremy.stanley@alaska.gov] 
Sent: Wednesday, May 30, 2018 11:42 AM
To: Patch Management Mailing List \
                <mailto:patchmanagement@listserv.patchmanagement.org>
Subject: RE: [patchmanagement] Server 2016 Update Error 0x800705b4

Except look at the KB numbers next to the titles.
One KB has 3 different titles depending on how you installed it.
4103723 was the May cumulative update. All names have the same associated KB.
Yet the name provided in Update History varies based on which method was used.
1 name when installed via WSUS, 2018-05 Cumulative Update… This is the one that is \
failing. 1 name when installed via delta .MSU from the Update Catalog, Feature Pack.
1 name when installed via full .MSU from the Update Catalog, Security Update.

All 3 are the same exact KB.

---
PatchManagement.org is hosted by Shavlik

The content on the email list is intended for assisting administrators.  If you would \
like to use any of this content in a blog or media publication, please contact the \
owners of the list for approval.

To unsubscribe send a blank email to leave-patchmanagement@patchmanagement.org
If you are unable to unsubscribe via this email address, please email
owner-patchmanagement@patchmanagement.org


[prev in list] [next in list] [prev in thread] [next in thread]