Microsoft explains how Windows Server Hotpatching works

Click to enter: ChatGPT Tool Plug-in Navigation Microsoft describes its hot-patching efforts for Windows Updates to instantly apply updates to Windows systems and eliminate the need to reboot the system to install updates. A new blog post on the Microsoft Technology Community site announces the introduction of hot patch support in Azure Automange for Windows Server. Microsoft recently released Windows Server 2022. Hot patches offer several advantages over traditional methods of installing updates on Windows machines. In a blog post, Microsoft highlighted three core benefits: Fewer reboots, resulting in improved availability. Faster deployment because update packages are "smaller, faster to install, and patch orchestration is easier." Improved protection because security updates can be installed immediately instead of scheduling a reboot. According to Microsoft, hotfixes work by "establishing a baseline using the latest cumulative update from Windows Update." The company plans to regularly release hotfixes based on this baseline, and these updates will not require a reboot. The baseline is refreshed with new cumulative updates and then periodically. Hot patches can be released every Patch Tuesday (once a month) and new baselines can be released every three months. In the best case scenario, the server needs to be restarted four times per year when a new baseline is applied. Microsoft differentiates between planned and unplanned baselines Planned baselines are released periodically to move the system to a new baseline. Hot patches can then be installed between these planned baseline releases. If hotfixing does not work for a specific patch, an unplanned baseline will be required to patch the system. Microsoft specifically mentioned fixes for zero-day vulnerabilities. These unscheduled baseline releases do require a reboot and contain everything from the latest cumulative update. According to Microsoft, the update may be installed outside of the Hotpatch program, but it requires disabling and unregistering the hotpatch to return to Windows Server's default update behavior. You can re-register at any time. The remainder of the announcement provides implementation details for server administrators.

The above is the detailed content of Microsoft explains how Windows Server Hotpatching works. For more information, please follow other related articles on the PHP Chinese website!