PowerToys no longer requires you to run it as an admin

Microsoft PowerToys logo
Microsoft PowerToys logo (Image credit: Microsoft)

What you need to know

  • An update is available for PowerToys on Windows 10.
  • The update resolves almost 100 issues.
  • The update also makes it so you don't have to always run it as an admin.

A new update for PowerToys for Windows 10 is avaialble through GitHub. The update resolves almost 100 issues and also makes it so you don't always have to run it as an admin. Microsoft's Brandon LeBlanc announced the update on Twitter.

Here are a few highlights from the release notes of PowerToys v0.15.0:

  • Make you aware there is a new version from within PowerToys
  • Removed requirement to always 'run as admin'
  • Added almost 300 unit tests to increase stability and prevent regressions.
  • Resolved almost 100 issues
  • Made .NET Framework parts of the source run faster with NGEN
  • Improved for how we store data locally
  • Increased FancyZones compatibility with applications
  • Created the v1.0 strategy, the launcher, the keyboard manager specs
  • Work on cleaning up our issue backlog and labels

PowerToys is a resurrection of an old utility from the Windows 95 days. The Windows 10 version initially shipped with just two tools, but its usefulness has increased over time. Late last year, PowerToys gained a tool to rename files in batches.

Since PowerToys is an open source project, you can read through extensive lists of changes and follow its development on its GitHub page.

Sean Endicott
News Writer and apps editor

Sean Endicott is a tech journalist at Windows Central, specializing in Windows, Microsoft software, AI, and PCs. He's covered major launches, from Windows 10 and 11 to the rise of AI tools like ChatGPT. Sean's journey began with the Lumia 740, leading to strong ties with app developers. Outside writing, he coaches American football, utilizing Microsoft services to manage his team. He studied broadcast journalism at Nottingham Trent University and is active on X @SeanEndicott_ and Threads @sean_endicott_.