Postby oblivioncth » 21 Oct 2019 22:05
Wow, talk about a facepalm. When I copied the name of the build I did so directly from the 7-zip I downloaded just to make sure it was "correct" and paid no attention to what it actually said. I believe what happened was that at the time of download I slipped slightly and accidentally clicked "last" which points to the 10-19 build of 4.0 instead of the 10-20 build of 3.09 since they are right next to each other and didn't notice since on the next page I was just focused on making sure I downloaded installer-less, non-debug version.
Any way, I tried again with both the 3.09 build from 10-20 and 10-21 (I tripled checked that they were the correct versions and still have the same error message
vlc-3.0.9-20191020-0511-win64.7z [SHA-512: 659d0782b9762a71c026b223b31143c9f1f6b65d56b8ba8a1a57281c5a27939c6f8ba08854473e2f626a6cfc737c263928ba9e87de4ba3c0a06dbb6a03a88b49]
vlc-3.0.9-20191021-0510-win64.7z [SHA-512: aa0148e8f324f1c3cb16a19983e58b0a2c8fa5baffa90e7ffbea94e9af68a987d5918964477506ca77d7eba392e37606143b48a9f018ef1a4fdab4ea22c60f43]
I do have the current release version of 3.09 installed just in case the new exe could for some reason try to read the registry/AppData and end up pulling a database or the like from that build instead (doubt it but I thought it was worth mentioning). I ran the Nightly from "C:\Program Files\VideoLAN\VLC Nightly 3.09" vs my standard install at "C:\Program Files\VideoLAN\VLC". I obviously made sure to try and open the file directly from within the nightly version of VLC and not just making use of the VLC file-type association.