[VLC Media Player 7.8.8 (x86 X64) Final Portable
Abdul Soumphonphakdy
Legal Report Trademark Abuse
VideoLAN, VLC, VLC media player and x264 are trademarks internationally registered by the VideoLAN non-profit organization.
VideoLAN software is licensed under various open-source licenses: use and distribution are defined by each software license.
My goal is to enable the use of 64-bit version of Windows Media Player (WMP) by default. Apparently, this process involves more than just changing the shortcuts in desktop, start menu and taskbar to reference mplayer2.exe in Programs Files directory, the location of 64-bit WMP, and not Program Files (x86), location of 32-bit WMP. I am comfortable with editing the registry and backup regularly. Windows 10 x64 Education v20H2.
(1) What do the keys do?
(2) Do the paths need to be changed from Program Files (x86) to Program Files?
(3) Do the keys that show up in the WOW6432Node in particular need the paths changed from Program Files (x86) to Program Files?
I am very sure these two keys need to be changed. I believe these keys involve launching WMP from the Run box using an alias (i.e., mplayer2), right?
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\mplayer2.exe
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\App Paths\mplayer2.exe
I am fairly sure these keys need to be modified as well since they are file type/web protocol associations, right?
HKEY_CLASSES_ROOT\DLNA-PLAYSINGLE\shell\open\command
HKEY_CLASSES_ROOT\MMS\shell\open\command
HKEY_CLASSES_ROOT\WMP11.AssocProtocol.DLNA-PLAYSINGLE\shell\open\command
HKEY_CLASSES_ROOT\WMP11.AssocProtocol.MMS\shell\open\command
Hi,
Per my search, there isn't exact resolution provided by Microsoft when switching WMP 64-bit as default but the experiences shared by users. Please allow me to share some of my findings related to your questions that might not be the exact answers.
(1) What do the keys do?
Most COM classes are registered with the operating system and are identified by a GUID that represents the Class Identifier (CLSID) within the registry (usually under HKLM\Software\Classes\CLSID or HKCU\Software\Classes\CLSID).The LocalServer32 key represents a path to an executable (exe) implementation.
I updated my VLC plugin to 2.1.3, the most up-to-date version of both the plugin and the software. Yet, Firefox says it's "vulnerable" for absolutely no reason. I also shut down and restarted firefox after the update, and it didn't make a whiff of difference.
Also, Adobe Reader 9.5.5 is the most up to date version of Reader 9, and is perfectly fine according to my add-on manager, but yet that's also "vulnerable" according to the plugin update checkfor absolutely NO reason. When I upgraded to Adobe Reader X a long time ago it didn't work at all with firefox as the plugin had severe issues and wasn't user friendly even outside of firefox. I therefore reinstalled 9 and never went back.
Lastly, if I go into the add-on manager and click on the "update now" link in that page it only brings me to the worthless page telling me the plugin was blocked, not about where to go to update it. This is a really irritating problem as you go to try to update it and you're not going to a website that will allow you to do it, it just brings you to a page that says absolutely NOTHING of value.
Here's even more information - for whatever reason VLC doesn't want to update the X86 version of the plugin, but updated the X64 version. Yet, if I try waterfox, the 64 bit version of firefox, the plugin used is still the X86 and outdated version.
The properties alone is the X64 version of the plugin file, then there's the mozilla add-on manager, and the third is the X86 version of the plugin. Can I just delete the latter (X86 version) and copy the X64 version into the X86 file?
If you want to keep the 64-bit VLC Media Player version for a 64-bit Waterfox browser, that's fine ... according to /questions/968058 you can have both installed ..... but you still need to install the 32-bit version of VLC Media Player to work with Firefox 24 on Windows.
I downloaded and installed both. First it was the X86 version of VLC player, which seemed to not be able to install numerous files, then I did the X64 version without issue. Then I tried to install just the plugin for X86 and had the same file issues. Waterfox should use the X64 plugin, not the X86 plugin, but yet, it still shows the VLC plugin version 2.0.0.
when you install VLC (32-bits), select Custom Install (I don't remember if the options come by default or not) and make sure the "Web browser plugins" options are selected and that your browsers are not open during installation.
I selected custom whenever I install anything to make sure what I need is in there. For every single installation of VLC, the browser plugin was included. You would need to uncheck the browser plugin in order for it not to install.
When you tell me I can use the X64 plugin for Waterfox, that allows me to say that BOTH browsers are using the wrong plugin. I am not going to post over there also when in reality the issue is that the browsers both have the same issue: They're both using the wrong plugin.
I downloaded and installed both. First it was the X86 version of VLC player, which seemed to not be able to install numerous files then I did the X64 version without issue. Then I tried to install just the plugin for X86 and had the same file issues.
You should ask about this over at the VLC Windows Troubleshooting forum and include this screenshot showing that the installed file version of C:\Program Files (x86)\VideoLAN\VLC\ npvlc.dll is still at 2.0.0 even though you installed the latest version.
It is possible that VLC hasn't updated their internal version number in the VLC plugin for Firefox. This has happened before and if you have installed the latest VLC version then you can ignore this warning message on the plugin check page.
However, the fact that VLC doesn't want to update the X86 file is an issue. I looked in the VLC postings and nothing was there about it not installing the plugin properly. I could use the copy into browser folder for waterfox, but not firefox because the X86 file still says version 2.0.0. Is there any difference between the X86 and X64 files? Do you know whether I could copy the X64 into the X86 file and have it work? Thanks.
That finally worked. I had to take the npvlc.dll file from the VLC X86 folder and move it to the desktop, rename it. Then I extracted the updated version of the file onto my desktop from the zip file to get the file extracted (it wouldn't extract to the program folder). Then I moved the extracted one from my desktop to the appropriate VLC folder. Lastly, I shut down and restarted firefox. When I restarted it, I looked at the add-on manager, and it finally recognized it as updated.
Unreal Media Server
Current version is 15.0
Download x86 Edition: UMediaServer (7.4 MB).
Download x64 Edition: UMediaServer (x64) (8.7 MB).
The Media Server supports majority of industry standard streaming protocols, codecs and formats to stream to variety of player applications on any device. Windows 2016 and 2019 Server are most appropriate platforms for Unreal Media Server.
Free version limitations: 5 live broadcasts can be configured, 10 concurrent player connections can be served.
Purchase an unlimited version.
Unreal Archival Server
Current version is 2.0
Download: Unreal Archival Server (706 KB).
The Archival Server provides centralized recording of live streams on the media server side. It serves as DVR subsystem for Unreal Media Server. The recording can be controlled based on schedule, manual command or programmatic call.
Streaming Media Player
Current version is 7.1
Download: Streaming Media Player (610 KB).
This is our native player to play streams sent by Unreal Media Server via UMS protocol.
The player can be embedded into web page as a cross-browser plugin.
A few days ago my antivirus blocked a malicious website coming from a file on the Windows media player folder, the name of the file for reference is wmpnetwk.exe. Today not a few minutes ago my antivirus blocked yet another malicious website coming from a file on System32 called wininit.exe.
The good news is that malicious website protection blocked them. There might be "less than good" news though. The first IP listed is one that is being reported a lot lately and there is the possibility that you might have some malware on your computer. Please follow the instructions in this link.
A malware removal expert will then be able to evaluate the results and tell you what needs to be done next. There may or may not be malware present, but its best to know for sure, and do what is needed to keep your computer safe.
Thank you Borislav for your reply and i apologize for my delay, the scan took almost 4 hours to be done. I have done what you asked and the files you required are attached to this reply. I standby for further instructions.
I do not have the option to configure sharing on the options menu in the library tab, only configurations and updates on information that are missing on files. I might be interpreting this wrong but I do not have any other computers in the household, so i should not be part of any network. I might be wrong.
No, since the Eset scan i had one notification a few moments after the scan was done but after that just silence, the normal time where the notifications should have started to pop up after midnight, was silent. So no everything has been quiet.
This is VLC media player 3.0.20 on Fedora 39. It used to work before the upgrade and the file can be played on another Fedora system which is still running F38, both have VLC installed from RPM Fusion.
Try installing ffmpeg and/or libavcodec-freeworld from rpmfusion while using dnf. The command would be something like sudo dnf install ffmpeg libavcodec-freeworld --allowerasing as long as you have the rpmfusion-free repo enabled.
795a8134c1