| VLC plug in is NOT in Extensions. Nothing is in Extensions.
| VLC plug in is NOT in Plugins either.
| How do I get VLC plugin to install? As I said, I made sure this option
was checked when installing VLC
|
I don't use plugins, but I tested VLC and it worked
fine. It installed npvlc.dll and npvlc.dll.manifest to
C:\Program Files\VideoLAN\VLC. I then ran Filemon to
see what FF is doing. When FF loads it's looking in
various places for plugins. It seems the Mozilla people
have broken their system at least once, originally putting
plugins in a plugins folder that no longer exists. The
actual trigger to load the plugin was pluginreg.dat, in
the app data profile folder. That file should list info
about VLC. If it's not there perhaps you can copy it
from someone else. (But first check blocklist.dat,
explained below.)
I don't know what else might go wrong, but 2 ideas
to look into would be UAC file restriction problems or
32/64 issues. That is, you can't load a 32-bit DLL in
a 64-bit process. So if VLC is 32-bit then FF needs to
be 32-bit. (Does FF even have a 64-bit version? I
don't know.)
Another possibility is a file called blocklist.dat. I find
it in both the program folder and the app data profile
folder. Blocklist.dat seems to contain a record of what
versions of what things can be installed. A kind of
ninny-list of possible security concerns. Here's what
I see in my blocklist.dat:
<match name="filename" exp="npvlc\.dll" /> <versionRange minVersion="0"
maxVersion="2.0.5" severity="0" vulnerabilitystatus="1"></versionRange>
I happen to have VLC 2.0.5 because I had trouble
with jumpy video when I installed a later version.
Where did blockilist.dat get 2.0.5? I don't know.
Maybe there's a good reason for it. Maybe not. I'm
guessing it's probably an irrelevant entry that just
corresponds with the version of VLC current at the
time the FF installer was written. (Extensions have
a similar system. An XPI may refuse to install based on
the min/max FF version info embedded in the XPI, but
that info is not necessarily relevant.)
If you tried other things and find a similar npvlc
entry in your blocklist.dat then you might try either
installing VLC 2.0.5, or editing your blocklist.dat
files to prevent interference, then re-install VLC 2.2.2.