[Feature Request]: Handling winget upgrade reboots aka exit code 3010

[RNalivaika]

The request

Some software installs and upgrades (for example "Microsoft.VCRedist.2015+.x86") exit with code 3010. That means reboot required to complete installation.
I would like some options in handling that. For example, define x number of days before reboot is forced, pop up to inform the user about pending reboot and give opportunity to reboot now or snooze for x number of minutes.

Is your feature request related to a problem?

Some software installs and upgrades (for example "Microsoft.VCRedist.2015+.x86") exit with code 3010. That means reboot required to complete installation.
I would like some options in handling that. For example, define x number of days before reboot is forced, pop up to inform the user about pending reboot and give opportunity to reboot now or snooze for x number of minutes.

Additional information

No response

[AndrewDemski-ad-gmail-com]

Hey,

Ideas:
Toast Notification about 3010 - could be done
triggering actual reboot from within WAU - definitely not

IMHO this would be going too far.
Keep in mind that WAU is used in SOHO and enterprise scenarios.
It is up to the user (or administrator) to decide when such action should occur (preferably within a maintenance window if such a thing is defined).

BR
AD