Messages

Hi Adam,

Appreciate the comment. This is totally on Microsoft, and their packaging technics, and the fact that I am sure the community has screamed at them for how they have done this, it comes down to how they view the process and customers.

I do not expect you guys to fix Microsoft's issues (although you guys are a group of very smart and talented people), it is just the way it is (for now).

I look forward to seeing how you guys implement something like that, as I would really love to have the System-Wide installer updated on a regular basis... the user based installs is a totally different beast, and we just need to find creative ways to implement these things.

I really think there should be some way to maybe add a prestart script in the PMPC deployment for Teams to remove and older version... or just remove the current version regardless.

The challenge with having an old version of the System-Wide Installer installed on a machine is any new user that logs in, will get that initial version, then when it launches, it will get an update (at some point).

Security scan software will pick up the System-Wide Installer that is out of date, and need to have it updated.

So if the PatchMyPC deployment of Teams did do a remove first then an install, that I think may solve the issue.

I also thought that the deployment would remove and install (not upgrade) the latest version, as we still have version 1.5 on our workstations, so a technician may log into a desktop for the first time, and it will install version 1.5, then they log out and never to log back into that machine, security scan software will detect this as out of date, and need it remediated, which means we have to rip it out of peoples profiles.

the PatchMyPC Teams installer would not solve that issue, but keeping the System-Wide Installer up to date may help a bit in those use case scenarios... the ones Microsoft doesn't bother thinking of or testing.

So I vote for PMPC to look into this as part of the Teams installer.

yeah that is what I have kinda figured is what happened.

On a machine that had the issue, I logged in with an admin account and when I went to uninstall it from Control Panel I get a message that an error occurred while trying to uninstall, it may have already been  uninstalled. Would you like to remove it... so I thought that was strange.. but speaks to what you are saying..

I think this issue bit our company and we are currently trying to figure out how big of an issue this is.
We use Citrix Workspace and PowerBI Desktop and users with those applications are getting errors because of WebView2.

Do we know if the issue with having it named .55 then redone with .52 caused any other issues?

In our company when an update is detected (in this case Sunday .55 was updated) then the following morning it is deployed to everyone.
Then on Monday night it was fixed, so on Tuesday morning that fix was deployed to our users, and that is when we started seeing the issue.
Some users that have Ciitrix Workspace 2205 installed are now constantly seeing an error pop up referencing WebView2, when they close it, after a few hours it pops back up, and does this constantly.
So not sure if the files themeselves were different, but it seems this boo boo has caused things to break for us.

Wondering is anyone else has seen this?