{"id":41700,"date":"2023-02-09T14:12:12","date_gmt":"2023-02-09T14:12:12","guid":{"rendered":"https:\/\/www.n-able.com\/?p=41700"},"modified":"2023-03-02T15:11:23","modified_gmt":"2023-03-02T15:11:23","slug":"big-changes-to-windows-feature-updates","status":"publish","type":"post","link":"https:\/\/www.n-able.com\/pt-br\/blog\/big-changes-to-windows-feature-updates","title":{"rendered":"BIG Changes to Windows Feature Updates"},"content":{"rendered":"

It is safe to say that anyone responsible for patch management will have had their fair share of issues with Windows Feature Updates over the years. These updates have amounted to new operating systems versions being released up to twice a year, and needless to say, could be huge in size\u2014ranging anywhere from 3GB to 6GB. This resulted in not only long download times, but also lengthy install times\u2014anywhere from one to two hours\u2014that required multiple reboots to complete. <\/span><\/p>\n

As a result of the size and complexity of these updates, IT administrators responsible for patch management, would often be forced to run them outside of normal scheduled maintenance windows. While this would minimize the disruption to the end-user, it would also increasing their own workload.<\/span><\/p>\n

Feature Enablement Packages<\/span><\/h2>\n

However Microsoft has been working to reduce the size and impact of these updates. Now, as you are installing your normal monthly updates, Microsoft is adding features along the way within dormant files that will later be activated by a Feature Enablement Package. When you choose to install the Feature Enablement Package it works as a master switch that activates these dormant features. The difference in this new approach can be quite stunning. The Feature Enablement Package itself can be below 1MB, which means download times will be slashed from many minutes to mere seconds, install times can drop from hours to less than a minute, and the need for multiple reboots will be reduced to just one.<\/span><\/p>\n

As you read this blog you may be sitting there and thinking, \u201cWell that\u2019s sorted then, it\u2019s Feature Enablement Packages for me from now on.\u201d However, in the words of the great American Football coach and broadcaster Lee Corso, \u201cNot So Fast, My Friend.\u201d Many of those responsible for managing patches\u2014be it in an in-house IT Department or working for an MSP\u2014use patch management applications<\/span><\/a> that as yet have no way to install these Feature Enablement Packages, with some vendors only supporting it via a script.\u00a0 <\/span><\/p>\n

Deploying Feature Enablement Package with N‑central and N‑sight<\/span><\/h2>\n

The good news though for those of you who use N‑able N‑central<\/span><\/a> or N‑sight RMM<\/span><\/a> is that with the recent release of Patch Management Engine 2.8<\/span><\/a>, this streamlined approach to installing feature updates is fully supported. It\u2019s also important to note that since not all feature updates are released using the Feature Enablement Package (Windows 11 being the most recent example), you can still use N‑central or N‑sight RMM to deploy feature updates using the original method.<\/span><\/p>\n

If you already use N‑central or N‑sight RMM for patch management<\/a><\/span>, then there are a few things to note:<\/span><\/p>\n