Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
RNalivaika opened this issue Nov 15, 2024 · 6 comments
Open
Labels
enhancement New feature or request stale

Comments

@RNalivaika
Copy link

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

@RNalivaika RNalivaika added the enhancement New feature or request label Nov 15, 2024
@AndrewDemski-ad-gmail-com
Copy link
Contributor

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

@FaserF
Copy link
Contributor

FaserF commented Nov 24, 2024

I do not think that this is possible, since we cannot fetch the Exit Code with Powershell. Winget only displays it as text with the information from above.
But I think Andrew is right. Using it in a company makes handling return codes "easy", in a private scenario I do not think we need such feature.

@AndrewDemski-ad-gmail-com
Copy link
Contributor

Well. You do not need to tap into exit code from a single upgrade action performed by winget during WAU cycle.
The machine will manifest its own 'RebootRequired' state nonetheless.
There are several places in which such info/flags must be checked:

@AndrewDemski-ad-gmail-com
Copy link
Contributor

OMG I completely forgot about that script.. shame on me..

Copy link
Contributor

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale
Projects
None yet
Development

No branches or pull requests

4 participants