Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Removal of VCM causes dead device listed in conferencing software #37287

Open
S-p-Ace opened this issue Feb 4, 2025 · 2 comments
Open

Removal of VCM causes dead device listed in conferencing software #37287

S-p-Ace opened this issue Feb 4, 2025 · 2 comments
Labels
Area-Setup/Install Refers to installation mechanism Issue-Bug Something isn't working Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams Product-Video Conference Mute Refers to the Video Conference muting tool

Comments

@S-p-Ace
Copy link

S-p-Ace commented Feb 4, 2025 •
edited
Loading

Microsoft PowerToys version

0.88.0

Installation method

WinGet

Running as admin

None

Area(s) with issue?

Installer

Steps to reproduce

  • install PT < v0.88.0
  • activate and use PowerToys VideConference Mute camera in a program
  • update PT to v0.88.0

✔️ Expected Behavior

The installer should abort with an error stating that the VCM camera could not be removed

❌ Actual Behavior

The installer completes without error and any conferencing software or other programs that use webcams will still list the VCM camera

Other Software

No response

Workaround

Manually remove the registry keys for the PowerToys VideoConference Mute camera

paste into Registry Preview and click Write to Registry 
Windows Registry Editor Version 5.00

[-HKEY_CLASSES_ROOT\CLSID\{31AD75E9-8C3A-49C8-B9ED-5880D6B4A764}]

[-HKEY_CLASSES_ROOT\CLSID\{31AD75E9-8C3A-49C8-B9ED-5880D6B4A764}\InprocServer32]

[-HKEY_CLASSES_ROOT\CLSID\{860BB310-5D01-11d0-BD3B-00A0C911CE86}\Instance\{31AD75E9-8C3A-49C8-B9ED-5880D6B4A764}]

[-HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{31AD75E9-8C3A-49C8-B9ED-5880D6B4A732}]

[-HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{31AD75E9-8C3A-49C8-B9ED-5880D6B4A732}\InprocServer32]

[-HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{860BB310-5D01-11d0-BD3B-00A0C911CE86}\Instance\{31AD75E9-8C3A-49C8-B9ED-5880D6B4A732}]

[-HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{31AD75E9-8C3A-49C8-B9ED-5880D6B4A764}]

[-HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{31AD75E9-8C3A-49C8-B9ED-5880D6B4A764}\InprocServer32]

[-HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{860BB310-5D01-11d0-BD3B-00A0C911CE86}\Instance\{31AD75E9-8C3A-49C8-B9ED-5880D6B4A764}]

[-HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{31AD75E9-8C3A-49C8-B9ED-5880D6B4A732}]

[-HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{31AD75E9-8C3A-49C8-B9ED-5880D6B4A732}\InprocServer32]

[-HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{860BB310-5D01-11d0-BD3B-00A0C911CE86}\Instance\{31AD75E9-8C3A-49C8-B9ED-5880D6B4A732}]

[-HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Classes\CLSID\{31AD75E9-8C3A-49C8-B9ED-5880D6B4A732}]

[-HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Classes\CLSID\{31AD75E9-8C3A-49C8-B9ED-5880D6B4A732}\InprocServer32]

[-HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Classes\CLSID\{860BB310-5D01-11d0-BD3B-00A0C911CE86}\Instance\{31AD75E9-8C3A-49C8-B9ED-5880D6B4A732}]

[-HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\DeviceClasses\{40568484-56a9-4865-b6cc-7a39f7d02837}\##?#SWD#VCAMDEVAPI#710D1C65B18094BE0C2AC715D84034E34765317FD75269DAB710E149D9A7F592#{40568484-56a9-4865-b6cc-7a39f7d02837}]

[-HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\DeviceClasses\{40568484-56a9-4865-b6cc-7a39f7d02837}\##?#SWD#VCAMDEVAPI#710D1C65B18094BE0C2AC715D84034E34765317FD75269DAB710E149D9A7F592#{40568484-56a9-4865-b6cc-7a39f7d02837}\#{FCEBBA03-9D13-4C13-9940-CC84FCD132D1}]

[-HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\DeviceClasses\{40568484-56a9-4865-b6cc-7a39f7d02837}\##?#SWD#VCAMDEVAPI#710D1C65B18094BE0C2AC715D84034E34765317FD75269DAB710E149D9A7F592#{40568484-56a9-4865-b6cc-7a39f7d02837}\#{FCEBBA03-9D13-4C13-9940-CC84FCD132D1}\Device Parameters]

[-HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\DeviceClasses\{588c8d20-c0e3-4fd3-b511-8f2f692156f8}\##?#SWD#VCAMDEVAPI#710D1C65B18094BE0C2AC715D84034E34765317FD75269DAB710E149D9A7F592#{588c8d20-c0e3-4fd3-b511-8f2f692156f8}]

[-HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\DeviceClasses\{588c8d20-c0e3-4fd3-b511-8f2f692156f8}\##?#SWD#VCAMDEVAPI#710D1C65B18094BE0C2AC715D84034E34765317FD75269DAB710E149D9A7F592#{588c8d20-c0e3-4fd3-b511-8f2f692156f8}\#{FCEBBA03-9D13-4C13-9940-CC84FCD132D1}]

[-HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\DeviceClasses\{588c8d20-c0e3-4fd3-b511-8f2f692156f8}\##?#SWD#VCAMDEVAPI#710D1C65B18094BE0C2AC715D84034E34765317FD75269DAB710E149D9A7F592#{588c8d20-c0e3-4fd3-b511-8f2f692156f8}\#{FCEBBA03-9D13-4C13-9940-CC84FCD132D1}\Device Parameters]

[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{40568484-56a9-4865-b6cc-7a39f7d02837}\##?#SWD#VCAMDEVAPI#710D1C65B18094BE0C2AC715D84034E34765317FD75269DAB710E149D9A7F592#{40568484-56a9-4865-b6cc-7a39f7d02837}]

[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{40568484-56a9-4865-b6cc-7a39f7d02837}\##?#SWD#VCAMDEVAPI#710D1C65B18094BE0C2AC715D84034E34765317FD75269DAB710E149D9A7F592#{40568484-56a9-4865-b6cc-7a39f7d02837}\#{FCEBBA03-9D13-4C13-9940-CC84FCD132D1}]

[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{40568484-56a9-4865-b6cc-7a39f7d02837}\##?#SWD#VCAMDEVAPI#710D1C65B18094BE0C2AC715D84034E34765317FD75269DAB710E149D9A7F592#{40568484-56a9-4865-b6cc-7a39f7d02837}\#{FCEBBA03-9D13-4C13-9940-CC84FCD132D1}\Device Parameters]

[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{588c8d20-c0e3-4fd3-b511-8f2f692156f8}\##?#SWD#VCAMDEVAPI#710D1C65B18094BE0C2AC715D84034E34765317FD75269DAB710E149D9A7F592#{588c8d20-c0e3-4fd3-b511-8f2f692156f8}]

[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{588c8d20-c0e3-4fd3-b511-8f2f692156f8}\##?#SWD#VCAMDEVAPI#710D1C65B18094BE0C2AC715D84034E34765317FD75269DAB710E149D9A7F592#{588c8d20-c0e3-4fd3-b511-8f2f692156f8}\#{FCEBBA03-9D13-4C13-9940-CC84FCD132D1}]

[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{588c8d20-c0e3-4fd3-b511-8f2f692156f8}\##?#SWD#VCAMDEVAPI#710D1C65B18094BE0C2AC715D84034E34765317FD75269DAB710E149D9A7F592#{588c8d20-c0e3-4fd3-b511-8f2f692156f8}\#{FCEBBA03-9D13-4C13-9940-CC84FCD132D1}\Device Parameters]
@S-p-Ace S-p-Ace added Issue-Bug Something isn't working Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Feb 4, 2025
@S-p-Ace S-p-Ace changed the title Removal of VCM causes dead device listed in conferencing software Removal of VCM causes dead device listed in conferencing software (currently editing due to accidental ^enter) Feb 4, 2025
@S-p-Ace S-p-Ace changed the title Removal of VCM causes dead device listed in conferencing software (currently editing due to accidental ^enter) Removal of VCM causes dead device listed in conferencing software Feb 4, 2025
@Jay-o-Way
Copy link
Collaborator

Jay-o-Way commented Feb 5, 2025 •
edited
Loading

Manually remove the registry keys for the PowerToys VideoConference Mute camera

@jaimecbernardo is this something that's overlooked in #36772?

PowerToys/installer/PowerToysSetupCustomActions/CustomAction.cpp

Line 332 in b6bba9c

// We've deprecated Video Conference Mute. This Custom Action cleans up any stray registry entry for the driver dll.

PowerToys/src/common/utils/clean_video_conference.h

Line 4 in ab7394f

void clean_video_conference()

@Jay-o-Way Jay-o-Way added Area-Setup/Install Refers to installation mechanism Product-Video Conference Mute Refers to the Video Conference muting tool labels Feb 5, 2025
@S-p-Ace
Copy link
Author

S-p-Ace commented Feb 5, 2025

Hm, doesn't seem like an oversight in the clean up logic per se. Though apparently searching through the registry manually revealed a couple more keys for me than listed in clean_video_conference()
I'm not familiar enough with the registry to say.

The issue is probably that the installer was run in user scope and thus couldn't remove the keys anyway.
It's debatable if it would be better to let the installer fail in that case or continue without error and just log a warning to the console. Usually I upgrade my programs in bulk with winget and any additional log messages are easily missed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Setup/Install Refers to installation mechanism Issue-Bug Something isn't working Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams Product-Video Conference Mute Refers to the Video Conference muting tool
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@S-p-Ace @Jay-o-Way