VLC Media Player 3.0.21 (MSI-x64)?

[Donatello76]

I thought as much, just wanted to clarify.

[iamr00t]

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.

[Dan Gough (Patch My PC)]

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.

Was the script added to the EXE variant and the application re-published? Also check the ScriptRunner log to verify that the script actually ran.

[GeoSimos]

There is another post here where the developers have stated they ran into issues but still intend to get an MSI working:

https://code.videolan.org/videolan/vlc/-/issues/28677

Dan, you had created a script to fix those issues but I don't know if they used it. BTW your website https://pagkageology.com is not working .

[GeoSimos]

Now, seriously, I don't understand this thing, they use Linux to build the MSI via WINE which is quite notorious for it's incompatibilities.....
I mean, they have such a large base of installations and for their own reasons, despise of setting up a proper build platform, that's at least bizarre....

[[email protected]]

I yanked the MSI Version off about 2500 devices and redeployed the .exe.
Pain in the @$$, but I was able to clear 2500 entries off my vulnerability report.

[Dan Gough (Patch My PC)]

Article relocated here:
https://dangough.github.io/packageology/msi/fixing-vlcs-msi-package/

But we have no indication what their issues are in getting an MSI together for 3.0.21 or if this would help. Plus the script would need to be run on a Windows box, which seemingly they don't have or they'd just run WiX on there to build it in the first place!

[steadybird]

I just published the EXE installer using PMPC and set it to supersede (replace/uninstall) the prior MSI version.
Annoying but rather painless once all was said and done.

[Dan Gough (Patch My PC)]

Supersedence with ConfigMgr kicks in if the superseded app is detected as installed. But with Intune, supersedence only kicks in if the specific superseded app was actually installed via Intune.

Deploying the app as required to devices running VLC, or even meddling with the requirement script of the EXE update, along with a pre-script to remove the MSI is the alternative.

But a recent comment from the devs suggests that we'll have an MSI with the next release, so we're not removing it from the catalog just yet!

[Michnixo]

I have been trying to resolve this all day. Tried several scripts to remove the old msi and install the latest exe but no luck. The new exe is fine but can't get rid of the old version

I use SCCM in a college to package/deploy software but don't use patch my PC. Will I have to uninstall manually or can I push an uninstall from SCCM for the old msi?

I was just tempted to keep the old version deployed until an msi is released again (if it is going to be)

[Dan Gough (Patch My PC)]

We do have a script available that will uninstall the VLC MSI if you are trying to deploy the EXE to override it:

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

[Michnixo]

Thanks. So I can put that in a batch file and add as a pre req on the .exe package?