Home News Microsoft released PowerToys 0.61.0 update: Improve Always on Top, FancyZones, etc.

Microsoft released PowerToys 0.61.0 update: Improve Always on Top, FancyZones, etc.

0

Microsoft has released the PowerToys 0.61.0 update today for all users. The project is still in public preview, but the latest version adds some significant changes and improvements. Microsoft says version 0.61 focuses on stability and improvements.

The following are the release highlights in PowerToys 0.61.0.

Operational quality improvements for Always on Top, FancyZones, and PowerToys Run.

The full changelog for version 0.61.0.

"General

● Upgraded Windows App SDK runtimes to 1.1.2.

● New Windows 11 right-click menu entries are now correctly added to the Windows 11 Dev channel internal release. (This is a patch for 0.60)

● Old right-click menu entries are displayed with the new Windows 11 right-click menu entries for compatibility with software that overrides Windows 11 context menu behavior. (This is a patch for 0.60)

● Integrated C# language versions across solutions. Thanks @davidegiacometti!

● Removed deprecated Segoe icon glyph code and replaced it with the correct code. Thanks to @niels9001 and @Jay-o-Way!

● Fixed an issue that caused random accent keys to be pressed on some keyboard layouts when certain modules were enabled.

Always at the top

● Fixed an issue with flickering borders when activated. Thanks @davidegiacometti!

● Fixed bug that caused Always on Top to activate and hang when exiting PowerToys. Thanks @davidegiacometti!

● Fixed a black edge appearing on rounded corners.

● Fixed a bug that caused 100% CPU consumption.

FancyZones

● Fixed bug that prevented layouts from being applied correctly when many monitors reported having the same serial number. (This is a patch for 0.60)

● Fixed a bug that prevented layouts from being applied correctly on some virtual monitor settings (this is a 0.60 patch)

● "Row" default layout is now applied to vertical monitors instead of "column" layout. Thanks @augustkarlstedt!

Image Resizer

● Screen reader now announces the size name instead of the class name.

File Browser Plugin

● Fixed an issue when creating thumbnails for SVG files created with Inkscape.

Keyboard Manager

● Adjusted wording on the editor when keys are isolated.

Mouse Utilities

● Fixed bug that caused the current "Find My Mouse" spotlight to hang when activated in the upper left corner of the screen. (This is a patch for 0.60)

PowerRename

● The PowerRename window will react to the current dpi when created.

PowerToys Run

● Fixed typo in WindowWalker plugin UI. Thanks @rohanrdy!

● Improved performance by saving search history files only on exit. Thanks @davidegiacometti!

● PowerToys Run no longer shows results for some plugins when querying gaps in global queries. Thanks @davidegiacometti!

● Added support for displaying localized names of certain win32 programs in program plugins. Thanks @htcfreek!

● Program plugins will now take into account settings changed directly in ProgramPluginSettings.json. Thanks @bezgumption!

Settings

● The PowerToys run settings page correctly grayed out the score adjustment settings when the plugin was not global. Thanks @jefflord!

● The PowerToys Run plugin score adjustment field only accepts numeric characters. Thanks @jefflord!

● If launched directly from its executable, it will not run, just like it did before the WinUI 3 upgrade.

● Fixed typo in the description of the PowerToys Run settings page. Thanks @eltociear!

Installer

● Removed invalid code to make MSIx installer.

Updated .NET dependencies to 6.0.7.

● If user manually removes it, no new PowerToys shortcuts are created on update."

PowerToys 0.61 comes with several known issues.

● After installing PowerToys, the new Windows 11 context menu entries for PowerRename and Image Resizer may not appear until the system is restarted.

● There are reports of users not being able to open the Settings window. This is due to incompatibility with certain applications (RTSS RivaTuner Statistics Server and MSI AfterBurner are known examples of this). If you are affected by this, please check the linked issue to verify if any of the provided solutions work for you.

Exit mobile version