Starting with October the monthly Quality Update contains the dormant H2 features. The H1 version being updated must have its October Quality Update installed (or any monthly Quality Update released after October since they are cumulative).It does not work for updating versions from different years (for example, 1909 to 2004). The enablement package only provides an update path from the H1 version to the H2 version of the same year (i.e.The following applies to the enablement package: The ZENworks Patch Management content feed contains the enablement package for both Windand Windows 10 20H2. The H2 features remain dormant until they are turned on by applying the enablement package. Microsoft published an article explaining the details and benefits of this method that I'll let you review rather than rehashing here.
The new features for the H2 version are delivered starting in the last H1 monthly Quality Update prior to the H2 release. Starting in 2019, Microsoft began ensuring that both versions (H1 and H2) released in the same year share a common core operating system with an identical set of system files. There are a couple of methods- enablement packages and custom patches-you can utilize depending on the currently installed Windows 10 version and the target update version. This is primarily due to the larger file size and installation mechanism for Feature Updates.Įven though the content feed does not include Feature Updates, you can still use ZENworks Patch Management to deploy Windows 10 Feature Updates. In a previous article I explained that the ZENworks Patch Management content feed includes Windows 10 Quality Updates (security and reliability patches) but not Windows 10 Feature Updates (version updates).
0 kommentar(er)
