On-PremisesCloud

 

How to deploy VLC Media Player patches using upload option?

Description

In certain cases, the VLC Media Player patches download fails due to the download URL being redirected to different mirror sites. In such cases, you can follow the methods listed below to resolve the issue.

Resolution

Method 1:

Add the domains listed in VideoLAN to the proxy server's exception list based on your requirement to function without any errors. Ensure that the proxy settings that have been configured has the permission to download files from the respective domains.

Method 2:

Follow the steps given below to manually download the patch and upload it to the patch store directly from console using upload patches option:

Download the updates of VLC Media Player manually.

  1. If you're using PMP Build Version 10.0.282 and above
    • Click on Upload near the Download failed error message. Using the Upload option you can install this patch.
    • Otherwise, navigate to Patches -> Downloaded Patches -> Upload Patches -> Search for the Bulletin ID TU-021 of VLC Media Player and click on Upload under Action.
    • Then select Install Patches to deploy.
  2. If you're using PMP Build Version below 10.0.282

    Note: To find the Patch Name, navigate to Patches -> Downloaded Patches -> Search for the Bulletin ID TU-021 of VLC Media Player and click on the Patch ID. There'll be a pop-up in which you'll find the Patch Name listed.

    • Rename the downloaded file in the below format:<PatchID>-<PatchName>
    • For example: 327878-vlc-3.0.18-win32.exe.

    • Navigate to the PatchManagerPlus_Server\webapps\DesktopCentral\store and place the renamed files.
    • Then go to Missing Patches -> Search for the Bulletin ID which has the same Patch Name and click on Install Patch.

If the patch is successfully downloaded automatically from the vendor, there is no need for manually uploading the patches. However, in instances where automatic download fails, you can proceed to manually upload the patches by following the above mentioned methods.

If the issue persists even after following the above-mentioned resolutions, please feel free to contact support.