Event details
How do the .NET CU's work with hotpatching. It is very frequent that these updates require reboots? Also there are some tools and features that require the latest CU for them to work properly. Does this mean we will be forced to defer these updates until the next baseline? Will this not cause more issues? Or will we receiving these updates anyways and be forced to reboot. This also applied to driver updates that uses are running on a monthly basis.
Microsoft.NET updates are not covered by hotpatching. If a .NET update requires a reboot, the system will need to restart just as it would outside of hotpatching. You won’t have to wait until the next baseline—you can still install the .Net update when needed. However, a reboot may be required to complete the installation.
However, if a standard Windows Update is required for a dependency, then yes, you may need to wait until the next baseline unless you choose to install the standard update manually (which would require a reboot).
Regarding driver updates, hotpatching does not change driver update behavior. Drivers will still follow their normal update cycle, and if a driver update requires a reboot, the system will prompt for it as usual.
We understand the need to balance security with feature updates and stability. If you have specific use cases where waiting for a baseline could cause issues, we’d love to hear more about them to help improve the experience!