-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Notebooks
- Notebook Video, Display and Touch
- Incorrect recognition of webcam on Firefox

Create an account on the HP Community to personalize your profile and ask a question
04-22-2020 12:14 PM
The webcam is properly installed. In the Device Manager Properties on the Controller there is "CyberLink WebCam Virtual Driver 6.0" with updated and good working drivers. But there is also in "HP TrueVision HD" Image Capture Devices, with updated and functional drivers.
When I launch the "YouCam6" app from the Desktop, the window showing the video in real time appears regularly, and in the Settings function the only webcam set is "HP TrueVision HD". Everything works fine.
The problem is when using the web browser. I use Firefox 75.
When I type url: https://it.webcamtests.com, or when I use Gmeet or something else, the default webcam that is used by the browser is "Cyberlink Webcam Splitter 6.0" and the video image is the "YouCam6" logo always fixed. That is, the webcam does not function as a webcam, but as a still image app.
After reloading the page, then with the website program https://it.webcamtests.com, the choice between two solutions of the app is presented on the "Allow" of the browser: videoinput # 1 and videoinput # 2.
Choosing videoinput # 1 displays the word "Cyberlink Webcam Splitter 6.0" on "Allow", and the webcam does not work, while if you choose videoinput # 2, then the choice appears on "Allow": "HP TrueVision HD" and after "Allow" the webcam then works regularly well.
When I use Gmeet the problem is that the default webcam is CyberLink Webcam, and the video on Gmeet doesn't work. Then I have to choose "Settings on Gmeet", where I can choose between CyberLink and HP TrueVision HD, and if I choose HP TrueVision HD then the video starts regularly and well.
The problem I present therefore is: how to start directly the "HP TueVision HD" webcam in the browser by default only, and disable CyberLink, which does not work on the browser?
I tried to search the Windows registry among the various entries, but I did not find the key or string to disable.
And around the web searching and browsing I have not found any mention of this specific topic.
Thanks to those who will find a valid solution.
User with 40 years of experience on PC.
Solved! Go to Solution.
Accepted Solutions
04-28-2020 10:30 PM
Waiting for an answer from this forum, which has not arrived yet, I tried to solve the problem myself, and I started to work on finding the solution.
I was able to verify that in choosing the two cameras, the browser, through the url:
https://it.webcamtests.com, identified two types of webcam:
the number one "CyberLink Webcam Splitter 6.0", for the webcam in the sense " hardware ", and
the number two "HP TrueVision HD", for the webcam in the" USB drive "sense.
I armed myself with patience and searched for the term "CyberLink Webcam Splitter 6.0" using the "Find" functions of Regedit.exe (which is in the Windows folder), searching for keys, values and strings.
After a while, various results came out, involving 6 keys and total subkeys.I found that some (three of them) were linked to the following hexadecimal string:
{65E8773D-8F56-11D0-A3B9-00A0C9223196}, while three others were on the string
{6994AD05-XXXX-XXXX-XXXX-XXXXXXXXXXXX}, where for the letter X there were numbers and hexadecimal characters.
All distributed among three main subkeys, namely CurrentControSet, ControlSet001 and ControlSet002.
In particular:
[HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ DeviceClasses \ {65E8773D-8F56-11D0-A3B9-00A0C9223196},
[HKEY_LOCAL_MACHINE \ SYSTEM \ ControlSet001 \ Control \ DeviceClasses \ {65E8773D-8F56-11D0-A3B9-00A0C9223196} and
[HKEY_LOCAL_MACHINE \ SYSTEM \ ControlSet002 \ Control \ DeviceClasses \ {65E8773D-8F56-11D0-A3B9-00A0C9223196}.
At this point, how to find the right key or the right ones that appeared in the browser indications, since they all contained in the same way "CyberLink Webcam Splitter 6.0"?
However, I noticed that in fact there were only two subkeys, because they repeated in identical pairs on CurrentControSet, ControlSet001 and ControlSet002, for reasons that should be evident to the experts.
There was nothing left then to choose which of the two subkeys contained the instructions that pointed to the wording "CyberLink Webcam Splitter 6.0" which appeared in the choice of webcams in the browser:
{65E8773D-8F56-11D0-A3B9-00A0C9223196} or
{6994AD05-XXXX-XXXX-XXXX-XXXXXXXXXXXX}.
So I chose to work on CurrentControSet, and here I changed the name "CyberLink Webcam Splitter 6.0" to "CyberLink Webcam Splitter 6.0.1" on the first hexadecimal string and to "CyberLink Webcam Splitter 6.0.2" on the second.
Clearly after the change also on ControlSet001 and ControlSet002 these values have changed as well as on CurrentControlSet, automatically, as those who are expert in the Windows Registry should know.
So I started the browser and I tested the webcam online, connecting https://it.webcamtests.com, discovering that instead of appearing as the first webcam "CyberLink Webcam Splitter 6.0", now "CyberLink Webcam Splitter 6.0.1" appeared, while the second webcam was always “HP TrueVision HD”.
At this point it was clear what the key and subkeys concerned were.
I went back to the registry, I put the word "CyberLink Webcam Splitter 6.0.2" back in place, returning it to its original value "CyberLink Webcam Splitter 6.0".
Then I reset the writing "CyberLink Webcam Splitter 6.0.1" to the correct value, returning it to the initial value "CyberLink Webcam Splitter 6.0", and made a complete copy of the subkey that I would have eliminated, so as to reactivate it in case of subsequent problems.
Finally I deleted the key and the subkeys that previously contained the wording "CyberLink Webcam Splitter 6.0.1".
Clearly the same thing also happened in ControlSet001 and ControlSet002, but automatically.
Redone the test with the browser, at this point the wording "CyberLink YouCam Splitter 6.0" was gone and the only webcam that could be used was "HP TrueVision HD".
Not happy, I tested the webcam on other computer software, to verify that it worked regularly to see images and to record videos, then I restarted the Notebook and then I connected to Gmeet for the final check.
The Google program worked regularly and the only webcam that was immediately recognized and used via the browser, already for the initial consent, was only one, “HP TrueVision HD”.
Permanently fixed the problem of the blocked CyberLink. I think anyone who has a CyberLink with this problem, either on Google Chrome or Firefox, should try this solution.I indicate here the complete key that I deleted:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{65E8773D-8F56-11D0-A3B9-00A0C9223196}\##?#ROOT#MEDIA#0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}]
"DeviceInstance"="Root\\MEDIA\\0000"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{65E8773D-8F56-11D0-A3B9-00A0C9223196}\##?#ROOT#MEDIA#0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\#GLOBAL]
"SymbolicLink"="\\\\?\\Root#MEDIA#0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\\GLOBAL"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{65E8773D-8F56-11D0-A3B9-00A0C9223196}\##?#ROOT#MEDIA#0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\#GLOBAL\Device Parameters]
"CLSID"="{17CCA71B-ECD7-11D0-B908-00A0C9223196}"
"FriendlyName"="CyberLink Webcam Splitter 6.0"
"CorrespondedYouCamVersion"="6"
"FilterData"=hex:02,00,00,00,00,00,20,00,01,00,00,00,00,00,00,00,30,70,69,33,\
08,00,00,00,01,00,00,00,12,00,00,00,01,00,00,00,50,01,00,00,30,74,79,33,00,\
00,00,00,60,01,00,00,70,01,00,00,31,74,79,33,00,00,00,00,60,01,00,00,70,01,\
00,00,32,74,79,33,00,00,00,00,60,01,00,00,70,01,00,00,33,74,79,33,00,00,00,\
00,60,01,00,00,70,01,00,00,34,74,79,33,00,00,00,00,60,01,00,00,70,01,00,00,\
35,74,79,33,00,00,00,00,60,01,00,00,70,01,00,00,36,74,79,33,00,00,00,00,60,\
01,00,00,70,01,00,00,37,74,79,33,00,00,00,00,60,01,00,00,70,01,00,00,38,74,\
79,33,00,00,00,00,60,01,00,00,70,01,00,00,39,74,79,33,00,00,00,00,60,01,00,\
00,80,01,00,00,3a,74,79,33,00,00,00,00,60,01,00,00,80,01,00,00,3b,74,79,33,\
00,00,00,00,60,01,00,00,80,01,00,00,3c,74,79,33,00,00,00,00,60,01,00,00,80,\
01,00,00,3d,74,79,33,00,00,00,00,60,01,00,00,80,01,00,00,3e,74,79,33,00,00,\
00,00,60,01,00,00,80,01,00,00,3f,74,79,33,00,00,00,00,60,01,00,00,80,01,00,\
00,40,74,79,33,00,00,00,00,60,01,00,00,80,01,00,00,41,74,79,33,00,00,00,00,\
60,01,00,00,80,01,00,00,90,01,00,00,00,00,00,00,81,42,6c,fb,53,03,d1,11,90,\
5f,00,00,c0,cc,16,ba,76,69,64,73,00,00,10,00,80,00,00,aa,00,38,9b,71,59,55,\
59,32,00,00,10,00,80,00,00,aa,00,38,9b,71,7d,eb,36,e4,4f,52,ce,11,9f,53,00,\
20,af,0b,a7,70,20,b3,47,47,ce,62,cf,11,a5,d6,28,db,04,c1,00,00,00,00,00,00,\
00,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{65E8773D-8F56-11D0-A3B9-00A0C9223196}\##?#ROOT#MEDIA#0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\#GLOBAL\Control]
"Linked"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{65E8773D-8F56-11D0-A3B9-00A0C9223196}\##?#ROOT#MEDIA#0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\Control]
"ReferenceCount"=dword:00000001
I remind everyone that these operations must be carried out exclusively by an expert.
Contact some friend or competent technician. I am sure that among the "20 friends" that each of us has, there is certainly one who "can do it".
In addition to making a copy of the key to be deleted, it would be even better if you made a complete backup of the C: system partition, before each manipulation, if you want to have the "absolute" certainty that in case of trouble, you can return exactly to the starting point without any damage.
I use both Aomei Backupper, for whole disks, and Ghost64 for partitions, even on disks configured in GPT.
I like Ghost64 because it works on disk or Live usb pen on boot, and because it is very fast and it does not have to "freeze", that is "unmount" the partition before backing up.
Obviously, the copy of the disk or partition must be made on an external drive of the Notebook, such as USB external disk, or other, and that the backup copy made must always be checked before tampering with the operating system or the registry files.
I always "work" like this, in fact, sometimes I also make two separate backup copies.
Finally, it is clear that everyone must take responsibility for any manipulation that derives from the use of the material I wrote here, as it is never certain that a proposed procedure is infallible and that it is free of collateral damage.
So, be careful!
04-28-2020 10:30 PM
Waiting for an answer from this forum, which has not arrived yet, I tried to solve the problem myself, and I started to work on finding the solution.
I was able to verify that in choosing the two cameras, the browser, through the url:
https://it.webcamtests.com, identified two types of webcam:
the number one "CyberLink Webcam Splitter 6.0", for the webcam in the sense " hardware ", and
the number two "HP TrueVision HD", for the webcam in the" USB drive "sense.
I armed myself with patience and searched for the term "CyberLink Webcam Splitter 6.0" using the "Find" functions of Regedit.exe (which is in the Windows folder), searching for keys, values and strings.
After a while, various results came out, involving 6 keys and total subkeys.I found that some (three of them) were linked to the following hexadecimal string:
{65E8773D-8F56-11D0-A3B9-00A0C9223196}, while three others were on the string
{6994AD05-XXXX-XXXX-XXXX-XXXXXXXXXXXX}, where for the letter X there were numbers and hexadecimal characters.
All distributed among three main subkeys, namely CurrentControSet, ControlSet001 and ControlSet002.
In particular:
[HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ DeviceClasses \ {65E8773D-8F56-11D0-A3B9-00A0C9223196},
[HKEY_LOCAL_MACHINE \ SYSTEM \ ControlSet001 \ Control \ DeviceClasses \ {65E8773D-8F56-11D0-A3B9-00A0C9223196} and
[HKEY_LOCAL_MACHINE \ SYSTEM \ ControlSet002 \ Control \ DeviceClasses \ {65E8773D-8F56-11D0-A3B9-00A0C9223196}.
At this point, how to find the right key or the right ones that appeared in the browser indications, since they all contained in the same way "CyberLink Webcam Splitter 6.0"?
However, I noticed that in fact there were only two subkeys, because they repeated in identical pairs on CurrentControSet, ControlSet001 and ControlSet002, for reasons that should be evident to the experts.
There was nothing left then to choose which of the two subkeys contained the instructions that pointed to the wording "CyberLink Webcam Splitter 6.0" which appeared in the choice of webcams in the browser:
{65E8773D-8F56-11D0-A3B9-00A0C9223196} or
{6994AD05-XXXX-XXXX-XXXX-XXXXXXXXXXXX}.
So I chose to work on CurrentControSet, and here I changed the name "CyberLink Webcam Splitter 6.0" to "CyberLink Webcam Splitter 6.0.1" on the first hexadecimal string and to "CyberLink Webcam Splitter 6.0.2" on the second.
Clearly after the change also on ControlSet001 and ControlSet002 these values have changed as well as on CurrentControlSet, automatically, as those who are expert in the Windows Registry should know.
So I started the browser and I tested the webcam online, connecting https://it.webcamtests.com, discovering that instead of appearing as the first webcam "CyberLink Webcam Splitter 6.0", now "CyberLink Webcam Splitter 6.0.1" appeared, while the second webcam was always “HP TrueVision HD”.
At this point it was clear what the key and subkeys concerned were.
I went back to the registry, I put the word "CyberLink Webcam Splitter 6.0.2" back in place, returning it to its original value "CyberLink Webcam Splitter 6.0".
Then I reset the writing "CyberLink Webcam Splitter 6.0.1" to the correct value, returning it to the initial value "CyberLink Webcam Splitter 6.0", and made a complete copy of the subkey that I would have eliminated, so as to reactivate it in case of subsequent problems.
Finally I deleted the key and the subkeys that previously contained the wording "CyberLink Webcam Splitter 6.0.1".
Clearly the same thing also happened in ControlSet001 and ControlSet002, but automatically.
Redone the test with the browser, at this point the wording "CyberLink YouCam Splitter 6.0" was gone and the only webcam that could be used was "HP TrueVision HD".
Not happy, I tested the webcam on other computer software, to verify that it worked regularly to see images and to record videos, then I restarted the Notebook and then I connected to Gmeet for the final check.
The Google program worked regularly and the only webcam that was immediately recognized and used via the browser, already for the initial consent, was only one, “HP TrueVision HD”.
Permanently fixed the problem of the blocked CyberLink. I think anyone who has a CyberLink with this problem, either on Google Chrome or Firefox, should try this solution.I indicate here the complete key that I deleted:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{65E8773D-8F56-11D0-A3B9-00A0C9223196}\##?#ROOT#MEDIA#0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}]
"DeviceInstance"="Root\\MEDIA\\0000"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{65E8773D-8F56-11D0-A3B9-00A0C9223196}\##?#ROOT#MEDIA#0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\#GLOBAL]
"SymbolicLink"="\\\\?\\Root#MEDIA#0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\\GLOBAL"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{65E8773D-8F56-11D0-A3B9-00A0C9223196}\##?#ROOT#MEDIA#0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\#GLOBAL\Device Parameters]
"CLSID"="{17CCA71B-ECD7-11D0-B908-00A0C9223196}"
"FriendlyName"="CyberLink Webcam Splitter 6.0"
"CorrespondedYouCamVersion"="6"
"FilterData"=hex:02,00,00,00,00,00,20,00,01,00,00,00,00,00,00,00,30,70,69,33,\
08,00,00,00,01,00,00,00,12,00,00,00,01,00,00,00,50,01,00,00,30,74,79,33,00,\
00,00,00,60,01,00,00,70,01,00,00,31,74,79,33,00,00,00,00,60,01,00,00,70,01,\
00,00,32,74,79,33,00,00,00,00,60,01,00,00,70,01,00,00,33,74,79,33,00,00,00,\
00,60,01,00,00,70,01,00,00,34,74,79,33,00,00,00,00,60,01,00,00,70,01,00,00,\
35,74,79,33,00,00,00,00,60,01,00,00,70,01,00,00,36,74,79,33,00,00,00,00,60,\
01,00,00,70,01,00,00,37,74,79,33,00,00,00,00,60,01,00,00,70,01,00,00,38,74,\
79,33,00,00,00,00,60,01,00,00,70,01,00,00,39,74,79,33,00,00,00,00,60,01,00,\
00,80,01,00,00,3a,74,79,33,00,00,00,00,60,01,00,00,80,01,00,00,3b,74,79,33,\
00,00,00,00,60,01,00,00,80,01,00,00,3c,74,79,33,00,00,00,00,60,01,00,00,80,\
01,00,00,3d,74,79,33,00,00,00,00,60,01,00,00,80,01,00,00,3e,74,79,33,00,00,\
00,00,60,01,00,00,80,01,00,00,3f,74,79,33,00,00,00,00,60,01,00,00,80,01,00,\
00,40,74,79,33,00,00,00,00,60,01,00,00,80,01,00,00,41,74,79,33,00,00,00,00,\
60,01,00,00,80,01,00,00,90,01,00,00,00,00,00,00,81,42,6c,fb,53,03,d1,11,90,\
5f,00,00,c0,cc,16,ba,76,69,64,73,00,00,10,00,80,00,00,aa,00,38,9b,71,59,55,\
59,32,00,00,10,00,80,00,00,aa,00,38,9b,71,7d,eb,36,e4,4f,52,ce,11,9f,53,00,\
20,af,0b,a7,70,20,b3,47,47,ce,62,cf,11,a5,d6,28,db,04,c1,00,00,00,00,00,00,\
00,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{65E8773D-8F56-11D0-A3B9-00A0C9223196}\##?#ROOT#MEDIA#0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\#GLOBAL\Control]
"Linked"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{65E8773D-8F56-11D0-A3B9-00A0C9223196}\##?#ROOT#MEDIA#0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\Control]
"ReferenceCount"=dword:00000001
I remind everyone that these operations must be carried out exclusively by an expert.
Contact some friend or competent technician. I am sure that among the "20 friends" that each of us has, there is certainly one who "can do it".
In addition to making a copy of the key to be deleted, it would be even better if you made a complete backup of the C: system partition, before each manipulation, if you want to have the "absolute" certainty that in case of trouble, you can return exactly to the starting point without any damage.
I use both Aomei Backupper, for whole disks, and Ghost64 for partitions, even on disks configured in GPT.
I like Ghost64 because it works on disk or Live usb pen on boot, and because it is very fast and it does not have to "freeze", that is "unmount" the partition before backing up.
Obviously, the copy of the disk or partition must be made on an external drive of the Notebook, such as USB external disk, or other, and that the backup copy made must always be checked before tampering with the operating system or the registry files.
I always "work" like this, in fact, sometimes I also make two separate backup copies.
Finally, it is clear that everyone must take responsibility for any manipulation that derives from the use of the material I wrote here, as it is never certain that a proposed procedure is infallible and that it is free of collateral damage.
So, be careful!