-
Notifications
You must be signed in to change notification settings - Fork 850
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
[Bug]: Upgrading to 5.10.2 using EXE or in app check for update pops up a Windows installer help popup #3270
Comments
@gdelia-pm I'm unable to reproduce this. I do see a quick flashing window that might the same as the one you're seeing, but it is immediately dismissed for me. I'm also on Windows 11. Is this consistently reproducible for you, ie. are you able to reinstall v5.8 and try upgrading again, and see if it happens consistently? |
Yup it's happening consistently. Just tested on a test vm (newly deployed, pretty much nothing on it. If I push 5.8 to it and our config, then in app do the check for updates > Download updates > restart and update I see that window pop up and the install doesn't proceed until I close the window. |
I think i can see a potential cause for this. With procmon running I see an attempt to run msixec /x and it looks like the GUID is being found programmatically. My org has constrained language mode enforced for powershell and it looks like there's an a attempt to use objects that are blocked in constrained language mode to determine what guid to uninstall. Can you try to reproduce with constrained language mode enabled and as a non admin user?
|
Okay so I wasn't able to reproduce your exact issue, but I got something arguably worse. In my case the application kept saying that Mattermost was open and I had to close it to continue the update. Of course MM was closed, and the update failed. Seems as though the case for constrained language might be something we have to work around a bit. I'll make a ticket to try and look at this. However, given the environment you're in I'd recommended having your system administrator install Mattermost for you via the MSI and have them update for you as needed. |
Lol I'm the admin 🤣 It's fine we'll just stick on 5.8 until release 5.11 is ready. The reason we're using user based installs because when we tried to swap to a machine install with the msi and setting things via the GPO config we found that notifications required manual approval from each user which wasn't tenable. We've been told that would be fixed with the target feb release of 5.11, so we can just wait and test that out. |
Lol for sure, we should have that out for v5.11 so stay tuned. |
Checks before filing an issue
Mattermost Desktop Version
5.10.2
Operating System
Windows 11
Mattermost Server Version
No response
Steps to reproduce
I can also reproduce this on a fresh install using just the exe.
Expected behavior
The pic in step 4 shouldn't pop up at all and the update should happen at step 3 and step 4 would open mattermost directly
Observed behavior
What should be silent installs or upgrades fully handled by mattermost get interrupted and require intervention to continue.
Log Output
Additional Information
No response
The text was updated successfully, but these errors were encountered: