Access to PowerToys thru PowerShell

[TimTheinAtTabs]

Description of the new feature / enhancement

The feature would allow users to control or change settings of PowerToys thru using cmdlets. Most basic feature would allow users to enable/disable a PowerToy.

Scenario when this would be used?

Windows Task Manager could be set up to change a PowerToy settings or enable/disable a PowerToy.

Supporting information

No response

[Aaron-Junker]

@TimTheinAtTabs For what scenarios would you usethis exactly?

/needinfo

[TimTheinAtTabs]

I have Task Scheduler execute a PowerShell script on local connection to my user session, and a different script on remote connection to my user session. When on local connection, I would like to disable Keyboard Manager because I have a full keyboard to use and no need for Keyboard Manager, but on remote connection, I would like to enable it because I'm using my laptop and it lacks a full size keyboard.

[kevindashton]

To add on to the request from another perspective: It would also be very nice to be able to simply enable / disable a given powertoy via CLI commands instead of having to open the settings GUI.

Since configuration was also mentioned here as well: pre/re-configuring a client workstation would be a scenario that would be a great capability add.

[jun488]

Another scenario:
To avoid any potential end-user issues and confusion, multiple workstations in office need to have PowerToys deployed with a single utility enabled - Paste As Plain Text.

[MarioRicalde]

I have a case where MouseWithoutBorders can cause the mouse loop when using certain remoting applications. Also another case where being able to change FancyZones via PowerShell could be of use.

[LucasVinicius314]

Another use case: for me, powertoys run sometimes errors out when enabled for some reason, and being able to turn it off and on again through a powershell script would be so much more convenient than having to do it through the ui

[serrat839]

Another use-case I just ran into: When mouse without borders is being used and left on the wrong screen, windows RDP's mouse and keyboard connections won't work. If you needed to quickly disable it, you could ssh into the computer's shell and then shut it off, do your work, and then re-enable it when you're done.