It’s a pain to have to update your security software. People will delay or reject critical patches, leaving their systems vulnerable to exploitable bugs, Microsoft knows from experience. As a result, Windows 10 is proactive in applying necessary updates and rebooting to ensure active use. This is helpful for patch adoption, but it’s problematic if you’re in the middle of a presentation, an online game, or anything else you don’t want to be interrupted.

Microsoft hopes to alleviate some of this agony with the Windows 10 Creators Update. When an update is downloaded, an alert will appear with three options: install and reboot right away, set a time to install it (within the next three days) or snooze the warning to postpone the decision. This won’t allow you to defer an update indefinitely, but it should provide a decent balance between the requirement to update systems and the inconvenience of interruptions.

Large Windows updates (such as the Anniversary Update from last year and the upcoming Creators Update) cause more than automatic rebooting. Their deployment is very cautious, with Microsoft releasing the software first to known working configurations (such as computers that OEMs or Insiders have extensively vetted) before making it available to the general public. Similarly, computers with known incompatibilities will be held back from receiving the update. This condition causes significant dismay and annoyance, particularly among enthusiasts: one PC may receive an update instantaneously. At the same time, another takes much longer, with no apparent rhyme or reason for the difference.

In response to this dissatisfaction, Microsoft has promised to improve the Creators Update. First and foremost, the organization hopes to experience fewer blocking incompatibilities in the first place. Last year’s Anniversary Update, for example, had a major difficulty with the way it handled many popular webcams due to a big change in how Windows took such gear. While a few people were aware of the issue during the Insider phase, there was minimal concentrated testing of the new code because Microsoft did not make such significant changes public.

Microsoft is using Quests through the Feedback Hub for the Creators Update to expand coverage of regions that have seen this kind of under-the-hood improvement. Insiders are encouraged to perform specialized testing of certain operating system sections as part of Quests, which should help the business detect flaws much sooner.

Even with this improved testing, the possibility of delaying the Creators Update for some users due to a compatibility issue cannot be ruled out. Microsoft promises to be more transparent on this front, offering more details on what blocking issues have been discovered and the status of the rollout in general. This should make the upgrade much more predictable, and it should be much clearer why a certain system isn’t getting it.