Install Out of Band Patch KB5001567 before installing Update KB5000802

Ltd Data 21 Reputation points
2021-03-29T10:27:17.543+00:00

Servus Community,

btw: I hope I reach the right users here, unfortunately I have not found any categories where I could have placed the topic more purposefully.

We are affected by the printer issue triggered by update KB5000802. We have a 100% failure rate in an evaluation group in WSUS. The patch KB5001567 then fixed that issue.

My question now is whether I can install the KB5001567 patch before installing the KB5000802 update. It would be madness and completely crazy to release an update when I already know it will cause a serios problem.

The alternative would be not to release the update KB5000802 at all and wait for the April update. So what options do I have without waiting for the phone to ring non-stop after installing this update?

Finaly please note that your editor is broken.

Thx & Bye Tom

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
8,223 questions
No comments
{count} votes

Accepted answer
  1. Dave Patrick 330.5K Reputation points Microsoft MVP
    2021-03-30T14:09:21.227+00:00

    Referring to the patch KB5001567 or KB5001649, they are not a replacement for update KB5000802

    yes, they do in fact replace KB5000802

    82834-image.png

    --please don't forget to Accept as answer if the reply is helpful--

    No comments

6 additional answers

Sort by: Most helpful
  1. Dave Patrick 330.5K Reputation points Microsoft MVP
    2021-03-29T12:51:28.353+00:00

    You'll just need the SSU prior to installing KB5001567
    https://support.microsoft.com/en-us/topic/servicing-stack-update-for-windows-10-version-2004-and-20h2-january-12-2021-c8a86bf7-6d49-b7fe-4369-44b1429b33cf

    Also note the KB5001567 has been replaced by another OOB March 18, 2021—KB5001649 (OS Builds 19041.870 and 19042.870

    --please don't forget to Accept as answer if the reply is helpful--

    No comments

  2. AllenLiu-MSFT 22,396 Reputation points Microsoft Employee
    2021-03-30T07:26:18.993+00:00

    Hi, @Ltd Data
    Thank you for posting in Microsoft Q&A forum.
    We can install the KB5001567 patch before installing the KB5000802 update.
    With the Windows Update experience, servicing stack updates and cumulative updates are deployed together to the device. The update stack automatically orchestrates the installation, so both are applied correctly. Starting in February 2021, the cumulative update will include the latest servicing stack updates, to provide a single cumulative update payload to both Windows Server Update Services (WSUS) and Microsoft Catalog.

    And like DSPatrick said, KB5001567 has been replaced by KB5001649.


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    No comments

  3. Ltd Data 21 Reputation points
    2021-03-30T13:54:58.063+00:00

    @AllenLiu-MSFT

    Referring to the patch KB5001567 or KB5001649, they are not a replacement for update KB5000802, I definitely still need KB5000802 in any way? The CSV list of files of both patches is almost the same like KB5000802 and also the file size of both patches seems to me extraordinarily large for a simple bug fix.

    Since we are already close to the April update anyway, I could also wait for the April update and would there be all the necessary updates already included? These updates are cumulative as far as I know or will KB5001649 not be included since it is a bug fix which is not needed globaly?

    Thx & Bye Tom

    No comments

  4. Ltd Data 21 Reputation points
    2021-03-30T15:06:48.077+00:00

    @Dave Patrick

    Thanks a lot. Now every question is answered in detail. I integrate the update KB5001649 into our WSUS and deny the update KB5000802, which would probably happen automatically anyway.

    Thx & Bye Tom

    No comments