Feature Update to Win 10 Version 20H2 x64 2020-10 via Enablement Package for Win 10, version 2004 missing from my ZPM

I don't seem to have this in my list of available patches?

Is there some trick to making this available?

Running ZENworks 2017.4.0 appliance

  • This should be there....

    Search for "KB4562830"

    However, make sure the Pre-Requisites have also been deployed....

    https://support.microsoft.com/en-us/topic/feature-update-through-windows-10-version-20h2-enablement-package-02d91e04-931e-f00d-090c-015467c49f6c

    Perhaps it is some issue where it is not downloading because it is not applicable to any devices.

  • Hi Craig,

    That KB is not there.

    Almost all of our workstations are at v1909 and many of them have been working from home for the past many months. Some come into the office once in a few weeks and are getting some patches via ZPM.

    About 30 have updated to v2004 on their own outside the office. About 12 of those have been in the office and have since upgraded to v20H2.

    The over 300 users still running v1909 have started receiving Windows prompts to upgrade. Those who answered Yes are now at v2004 and having all kinds of problems. Slowness and freezing of Citrix sessions are the main concerns. Some users can't login anymore. Some fail the update and roll back. Our Helpdesk is swamped with calls.

    The ones that come into the office, and are still capable of logging in, seem to be getting upgraded to v20H2 and have v20H2 patches available in ZPM. We are trying to determine if we can force the v2004 ones to upgrade to v20H2 via ZPM and hoping that might fix the problems that the users are experiencing.

    But the v20H2 Enablement Package is not there. Perhaps the workstations coming in are already past that point?

    Somebody has made a real mess to the patching and upgrading of their OS!

    Any suggestions, ideas or thoughts are welcome at this stage.

    Thanks,

    Chris

  • I believe you may be a little confused about that KB.  That KB will not install to any Windows 1909 PCs.  In fact, it will actually not change a single Binary File on your PC.  Enablement Packages simply "Unlock" changes included in the latest release.  So a Windows 20H1 (v2004) that is patched through April will be binary identical to a 20H2 PC patched through April with the Enablement Package.  The package just enables certain features to be turned on.

    To upgrade from 1909 to 20H2, you will need to actually deploy the 20H2 Upgrade.  This would actually be a media upgrade that you can deploy via a ZCM bundle.  There was a Cool Solution Article on how to create the bundle and convert it into a ZPM patch, but the second step is not really required and actually something I generally have folks skip.

    In short, it is simply putting the extracted ISO on a share and running setup.exe or delivering the extracted ISO from the content-repo.  If you have a single site, I recommend the share.  If you have multiple sites, you will want to use the content-repo, but will want to do a few tricks to ensure the content is delivered efficiently.  Very Large content-bundles tend to be slow w/o a little tweaking.  We can cover that if need be.

    Note:  The fact your PCs are primarily 1909, is why you do not see the enablement bundle.  ZCM only downloads patches into ZPM that your PCs need based upon DAU scans.  This patch is not applicable to 1909 PCs.

  • I'm probably not being clear in my explanation.

    The laptops in question are coming back into the office already upgraded from v1909 to v2004 via the Internet.

    They are connecting to ZENworks for the first time in weeks or months and are then upgrading to 20H2. I assume that ZPM is doing this?

    I've read the Cool Solutions article several times and that is a possibility. We have been trying to upgrade from v1909 to v2004 via WSUS with mixed results - it often fails and rolls back.

    With so many laptops out of the office for so long, and not getting regular updates, when staff do come into the office to see clients (sometimes only for an hour or two) we don't want to risk making their laptop unusable during a client session.

    We are a children's health care provider and are under lockdown here. Clients are only being seen in person when the need is required for their treatment. We are trying to find the least impactful way to resolve this situation.

    Since we have had some v2004 laptops connecting to ZENworks, I was wondering why the v20H2 enablement package was not being detected as being needed? 

  • Keep in mind that running Windows v2004 is not SUFFICIENT to meet the requirements for the Enablement Package.

    So it can be that....

    #1 - Your v2004 devices are not running the DAU scan to indicate they need it.

    #2 - Your v2004 devices may lack the other requirements for the Enablement KB and hence are not reporting they need it.  Those requirements are detailed in the MS link in an earlier comment.

  • Keep in mind that running Windows v2004 is not SUFFICIENT to meet the requirements for the Enablement Package.

    So it can be that....

    #1 - Your v2004 devices are not running the DAU scan to indicate they need it.

    #2 - Your v2004 devices may lack the other requirements for the Enablement KB and hence are not reporting they need it.  Those requirements are detailed in the MS link in an earlier comment.

  • Keep in mind that running Windows v2004 is not SUFFICIENT to meet the requirements for the Enablement Package.

    So it can be that....

    #1 - Your v2004 devices are not running the DAU scan to indicate they need it.

    #2 - Your v2004 devices may lack the other requirements for the Enablement KB and hence are not reporting they need it.  Those requirements are detailed in the MS link in an earlier comment.

  • Keep in mind that running Windows v2004 is not SUFFICIENT to meet the requirements for the Enablement Package.

    So it can be that....

    #1 - Your v2004 devices are not running the DAU scan to indicate they need it.

    #2 - Your v2004 devices may lack the other requirements for the Enablement KB and hence are not reporting they need it.  Those requirements are detailed in the MS link in an earlier comment.

  • Keep in mind that running Windows v2004 is not SUFFICIENT to meet the requirements for the Enablement Package.

    So it can be that....

    #1 - Your v2004 devices are not running the DAU scan to indicate they need it.

    #2 - Your v2004 devices may lack the other requirements for the Enablement KB and hence are not reporting they need it.  Those requirements are detailed in the MS link in an earlier comment.

  • Keep in mind that running Windows v2004 is not SUFFICIENT to meet the requirements for the Enablement Package.

    So it can be that....

    #1 - Your v2004 devices are not running the DAU scan to indicate they need it.

    #2 - Your v2004 devices may lack the other requirements for the Enablement KB and hence are not reporting they need it.  Those requirements are detailed in the MS link in an earlier comment.