We are updating VLC for EXE x86, EXE x64. and MSI x64. I am seeing that this new release 3.0.21 does not seem to have a version for MSI x64. Is that per the developer or something we need make plans for? We have 1275 on EXE x64 but we also have 972 on MSI x64, so we will need to work through migrating them all to EXE x64 if this new version will not be updated any longer. Please let us know.
We are monitoring their site for a new MSI:
https://get.videolan.org/vlc/3.0.21/win64/
Here is a thread on the vendor forum about it that is now locked:
https://forum.videolan.org/viewtopic.php?t=164735
Their MSI was problematic due to being compiled on Linux rather than Windows, so they may have run into some build issues:
https://code.videolan.org/videolan/vlc/-/issues/18985
If we decide to pull this from our catalog, we can add a pre-script to the EXE release to remove the MSI version.
Quote from: Dan Gough on June 17, 2024, 07:58:38 AMWe are monitoring their site for a new MSI:
https://get.videolan.org/vlc/3.0.21/win64/
Here is a thread on the vendor forum about it that is now locked:
https://forum.videolan.org/viewtopic.php?t=164735
Their MSI was problematic due to being compiled on Linux rather than Windows, so they may have run into some build issues:
https://code.videolan.org/videolan/vlc/-/issues/18985
If we decide to pull this from our catalog, we can add a pre-script to the EXE release to remove the MSI version.
Is there any update about this?
I concur in asking for an update. I agree that this should generally on the software vendor, but if you offered to script the removal of the MSI version, that would work around this vendor's lack of action.
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
To be frank, that post dates from 2 months ago.
I would rather remove the MSI version at this point and just use the exe version
Hi Dan, we'd appreciate an option to rollover our clients from MSI to EXE for VLC since it might be a while before this is resolved, can we have a seperate SKU for VLC just for this purpose?
I will discuss this internally - but normally we only configure updates to be able to detect and migrate from a different package type (e.g. EXE->MSI or x86->x64) when the vendor just offers a single installer type and they changed it.
There are a few options at your disposal to migrate users over - for example you can create a pre-script that will allow the EXE variant to uninstall the MSI (this script (https://github.com/PatchMyPCTeam/Community-Scripts/tree/main/Uninstall/Pre-Uninstall/Uninstall-Software) can help), then push this out to a collection of all devices that have the MSI variant installed.
I've looped into this situation via some rather loud CVE's on our Defender dashboard.
Though I am wondering if perhaps we are over thinking the problem?
Could we not just set the Exe version of VLC to supersede (With uninstall) the MSI version? Then target the exe to the same endpoints as the MSI?
I understand that PMPC doesn't have these options and would need to be done directly in Intune/SCCM.
Yes that would also work, with a few caveats:
- With ConfigMgr, the latest Application would resolve as being installed even if it was installed manually outside of ConfigMgr. Using supersedence here would work, and the option should be selected to uninstall the superseded product. You should also be able to set the EXE deployment settings to automatically upgrade any superseded products.
- Intune will not automatically evaluate the detection script of every available app to determine if it's installed, unless installation has been attempted at least once. Therefore you should supersede both the Application and Update - and if somebody installed it manually themselves, the published apps won't be recognised as installed, and so the supersedence rule may not apply.
Well, the heck with it.
We wrote a script, and removed the MSI on 2,500 devices, killed the package in SCCM, and using PatchMyPC, built the package as an .exe and deployed it as Install/Required.
It stinks, but we needed to clear the vulnerability in our endpoint tools, so...
6 of one, half dozen of the other, but Patch My PC will take care of the updates going forward, so... easiest way to get it done I guess.
We 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?
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
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.
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.
I thought as much, just wanted to clarify.
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.
Quote from: iamr00t on November 15, 2024, 10:42:35 AMI 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.
Quote from: Dan Gough (Patch My PC) on September 06, 2024, 01:45:50 AMThere 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 :( .
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....
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.
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!
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.
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!
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)
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
Thanks. So I can put that in a batch file and add as a pre req on the .exe package?
Quote from: Dan Gough (Patch My PC) on February 05, 2025, 10:59:07 AMWe do have a script available that will uninstall the VLC MSI if you are trying to deploy the EXE to override it:
We are currently rolling out the exe installer with your script.
What we noticed is that in the "Add/Remove programs" panel in windows, we see that both versions are installed.
Could you clarify how future updates will handle this situation??
Well then it seems that the script has failed or not been run correctly - only the EXE variant should remain in add/remove programs. Please could you submit a support case if you'd like this reviewed further?
@Dan Gough (Patch My PC) Trying to use this script and I get this-
*** Starting Detection script for VLC Media Player* with version 3.0.21
Detection script version 3.5
Ignoring the product VLC media player because the key name [{9675011C-2395-4AD7-B1CC-92910F991F58}] does not meet the installer type condition [Installer Type: Exe]
Found VLC media player version 3.0.21 installed on
Result of script for checking Detection: Installed
*** Ending Detection script for VLC Media Player* with version 3.0.21
3.0.20.0 is installed on the machine.
Are you trying to attach this script to the EXE application (not the update)?
Yes, attaching to the exe.
To the EXE application, rather than the update? The update will not automatically apply because the requirements script will not pick up the existing install to patch. But if you attach the script to the base install app, you can push that out as a required install to devices running the VLC MSI.
Understood. That's exactly what I'm doing. adding it to the exe application. it's not working for me.
I will take a look again.