• Welcome to Support Forum: Get Support for Patch My PC Products and Services.
 

Recent posts

#31
Unfortunately, it won't matter which version you deploy. It seems like the version on the machine auto-updates to the latest broken version before our version even has a chance to attempt to install, so the installation will return a failure at the moment. It seems Microsoft is aware of the issue, and I am hoping they pull that update soon.
#32
FYI, it looks like ours is failing with version 130.0.2849.80. The github post references version 131.0.2903.48.
#33
We had Edge Webview2 in our esp and autopilot is failing. We should deploy the old version instead until this is hopefully resolved in the next release?
#34
This is actually a bug with the latest WebView2, you haven't done anything wrong here. The latest version of WebView2 is not putting down the DisplayName in the ARP registry key, which is causing our Detection Script not to detect. There's a bug reported here: https://github.com/MicrosoftEdge/WebView2Feedback/issues/4931 We didn't update WebView2 yesterday due to this issue. We'll have to wait for Microsoft to resolve.
#35
I ran into a self-created snafu with Microsoft WebView2 today where installs of the product were failing in our task sequence. We were using the Patch My PC packaged deployment to ensure that WebView2 was the most current version and found today that it WebView2 was updating on its own before reaching the Install Application step where we had it. Since we happen to be in the limbo period where the latest published version of WebView2 is less than the most current version available from Microsoft, the install was throwing a -2147219187 (GOOPDATEINSTALL_E_INSTALLER_HIGHER_VERSION_EXISTS). After examining the detection script, it doesn't look like it's doing a greater than or equal to operation on the version being installed. Is this something that could be modified for future versions of WebView2?
#36
I have added the pre-script and deployed it to a system with the MSI install of VLC 3.0.20.0 and the app deployment is showing 3.0.21 as installed, but the installed version is still the MSI version 3.0.20.0. Should it not see the 3.0.20, uninstall MSI, and install EXE, because it's not.
#37
I thought as much, just wanted to clarify.
#38
Yes that's right - sorry about the confusion, we'll get that corrected.

It does state:

"The script is intended to be used a pre-script for the latest EXE variant of VLC Media Player. It will silently uninstall the MSI variant of VLC Media Player."

But then confuses matters by talking about applying it to the MSI.
#39
Thanks Dan, the script looks great. We'll be testing it shortly.

Can I confirm that needs to be run as a pre-script for the exe installer? The readme/documentation on the github page says it should be done with msi, which I expect is an error.

I'll report back how we go with it.
#40
Quote from: Donatello76 on November 15, 2024, 06:55:22 AMWe also need to get VLC updated to satisfy our security audits.

Is there a reason why setting the MSI installer to uninstall for all devices, and then setting the exe to install for all devices wouldn't work?

It would be better to use supersedence or an uninstallation pre-script here, in case the EXE installs first, then the MSI gets removed after, as that could result in a broken installation.

Also, we have now added a script to our GitHub to remove the MSI version. This can be added as a pre-install script to the Patch My PC package for the EXE variant:

https://github.com/PatchMyPCTeam/Community-Scripts/tree/main/Uninstall/Pre-Uninstall/Uninstall%20VLC%20Media%20Player%20MSI