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

[New Feature]: Add ability to display warning to user before upgrade #1786

Open
Masamune3210 opened this issue Dec 8, 2021 · 9 comments
Open
Labels
Area-Manifest This may require a change to the manifest Issue-Feature This is a feature request for the Windows Package Manager client.

Comments

@Masamune3210
Copy link

Description of the new feature/enhancement

While upgrading programs, all my explorer windows closed with no warning due to WinMerge closing it as part of its upgrade path. Would it be possible to add a warning to programs known to interfere with others as part of their upgrades or installs?

Proposed technical implementation details (optional)

Add a upgrade after user issues command to the tone of "This upgrade might close other programs as part of its upgrade, make sure you save your work first!" with a prompt Y/N before continuing and a flag to the upgrade command to ignore possible upgrade closures to disable the prompt for scripts and people who don't care

@denelon
Copy link
Contributor

denelon commented Dec 8, 2021

We've seen this with programs aborting Windows Terminal and added a key to the manifest schema. This sounds like a similar scenario, but might need to be handled a bit differently.

@denelon denelon transferred this issue from microsoft/winget-pkgs Dec 8, 2021
@ghost ghost added the Needs-Triage Issue need to be triaged label Dec 8, 2021
@denelon denelon added Area-Schema Issue-Feature This is a feature request for the Windows Package Manager client. and removed Needs-Triage Issue need to be triaged labels Dec 8, 2021
@sredna
Copy link
Contributor

sredna commented Dec 9, 2021

WinMerge closing it as part of its upgrade path

WinMerge uses Inno Setup which does support the Restart Manager. It would perhaps be nice if we could figure out if WinMerge is doing something special or if there is an issue with Inno.

@Masamune3210
Copy link
Author

All I know is it kills all open explorer windows on install upgrade or uninstall because it adds a properties sheet which requires explorer to be closed. haven't done much research been at work all day

@Masamune3210
Copy link
Author

Actually I think it adds a context menu entry rather than a properties sheet

@Masamune3210
Copy link
Author

I think it manually closes all open explorer windows as part of its install script, so there might not be much able to be done to mitigate it other than a warning

@sredna
Copy link
Contributor

sredna commented Dec 9, 2021

But does it have custom code to close Explorer or does it use Restart manager?

Manually closing Explorer is broken by design since other applications (anything with a open/save dialog) might also have the shell extension .DLL loaded.

Restart manager is supposed to fix this. You give it a list of files, it closes all apps using said files, you replace/update the files and finally you tell Restart manager to restart the apps. Explorer is somewhat special since it also owns the taskbar and that might be the same process as a File explorer window.

@Masamune3210
Copy link
Author

I'm not sure, this is all from observation, not taking a look at the scripts or anything. I don't know if it tries to kill all of explorer or not, as I run File Explorer as a separate process from the taskbar for stability reasons

@denelon
Copy link
Contributor

denelon commented Feb 1, 2022

What kind of name were you thinking for the manifest key?

"VolatileInstaller" as a boolean?

We could provide a message like:

"This installer is known to interfere with running applications"

I'm open to suggestions here.

@Trenly
Copy link
Contributor

Trenly commented Mar 6, 2024

The original PR for this has been closed, so this is not truly In-PR Issue related to a PR

@microsoft-github-policy-service microsoft-github-policy-service bot added Area-Manifest This may require a change to the manifest Issue-Feature This is a feature request for the Windows Package Manager client. and removed Area-Manifest This may require a change to the manifest In-PR Issue related to a PR Issue-Feature This is a feature request for the Windows Package Manager client. labels Mar 6, 2024
@denelon denelon removed this from the v.Next-Client milestone Nov 14, 2024
@ranm-msft ranm-msft assigned JohnMcPMS and unassigned ryfu-msft Dec 26, 2024
@JohnMcPMS JohnMcPMS removed their assignment Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Manifest This may require a change to the manifest Issue-Feature This is a feature request for the Windows Package Manager client.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants