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.

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

[VCM]Deprecate the Video Conference Mute utility #36772

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

jaimecbernardo
Copy link
Collaborator

Summary of the Pull Request

Removes the Video Conference Mute Utility
Removes the Webcam Report Tool from the helper tools, which was used to gather information about webcams.

Adds logic to remove stray registry entries from previous versions of PowerToys, so that VCM gets unlisted. This is done both in the installer and when running PowerToys as administrator (User-scope installers are unable to run the code to remove these registry entries.

PR Checklist

Detailed Description of the Pull Request / Additional comments

For the clean up of previous registry values cleanup code, these are the relevant commits in the PR:
6b51209
7763763

Validation Steps Performed

Built a 0.87.10 installer and tested many upgrade scenarios:
1 - Install 0.87.1, enable VCM, uninstall 0.87.1 and then install 0.87.10 machine-scope installer. Verify that the VCM camera is no longer an option on Teams. (Need to restart Teams for that).
2 - Install 0.87.1 machine-scope, enable VCM, and then upgrade to 0.87.10 through the machine-scope installer. Verify that the VCM camera is no longer an option on Teams. (Need to restart Teams for that).
3 - Install 0.87.1 user-scope, enable VCM, and then upgrade to 0.87.10 through the user-scope installer. Verify that VCM camera is still there. Restart PowerToys as administrator. Verify that the VCM camera is no longer an option on Teams. (Need to restart Teams for that).

Copy link
Collaborator

@stefansjfw stefansjfw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

some minor comments, but overall looks good.

displayName: Sign x86 DirectShow VCM
signingIdentity: ${{ parameters.signingIdentity }}
inputs:
FolderPath: 'x86/$(BuildConfiguration)' # Video conf uses x86 and x64.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's one more comment # Video conf uses x86 and x64. in this file, I guess just remove it so we don't have a reference to removed stuff.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, that comment is weird... thanks for noticing.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need revision update here?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indeed. Just pushed.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

revision update?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indeed. Just pushed. Thank you for the review!

Copy link
Member

@DHowett DHowett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I cannot unilaterally "approve" removing VCM, but I have reviewed the changes to the build pipeline and the installer and they look good.

Copy link
Collaborator

@htcfreek htcfreek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jaimecbernardo, @cinnamon-msft, @DHowett
Don't remove the policy from ADMX. Doing this is a don't.

Reason: The registry value is stil added to the policy file and you can't remove it anymore because of the missing template definition.

Solution: Update supported on value and add "(Depreciated)" to the policy name. (Maybe moving it into a "depreciate policies" folder like done for Google Chrome.)

@htcfreek htcfreek added the Status-Blocked We can't make progress due to a dependency or issue label Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status-Blocked We can't make progress due to a dependency or issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants