Recommended Posts

I use it all the time. I'm well aware that computers can be shut down by simply pressing the power button on your case but it's usually quicker to simply use the mouse (most of the time I'm already holding the mouse anyway) - not only that but my computer is under my desk and I don't particularly like having to lean down to press it when a simply mouse gesture will suffice. And I guarantee I'm far from the only person that shuts down their computer in that way - in fact I wouldn't be surprised if a majority currently shut down their computer from the start menu.

So this is a desktop. Just curious, why do you shut it down at all?

On a budget, power bills can get pretty tight. I save an average of 20 bucks a month keeping mine off when not using it.

Versus just letting it go to sleep? That seems unlikely. But if you're really concerned, you can set it to hibernate instead (which uses no power at all).

On a budget, power bills can get pretty tight. I save an average of 20 bucks a month keeping mine off when not using it.

I rent an appt, and I let my machines sleep. The only time they goes off is when there's a storm. My bills are no higher than they would be without my computers here.

My room mate, OTOH, still uses a circa 2001 desktop (w/ CRT) that does more damage to the bills, than any of my systems combined while in sleep mode.

This is so true, the way Win32 is now they'd be hard pressed to make any drastic changes. People want legacy dropped from Windows, they've said this often, and now with WinRT and Metro that's more or less happening. Yet at the same time we now have another group that doesn't want this to happen or just doesn't like it for xyz reasons. In the end Win32 will be replaced, not next year, not in 5 years but it will happen once the new WinRT APIs/Framework gets more mature. Also as it gets more mature we'll see less and less of these "rules" and "limitations" that we see now in Windows 8, which is basically version 1.0 for WinRT.

It's why I referred to Windows 8 (non-RT) as a user-version of a hedge-bet.

I knew right off that WinRT is not even *close* to being fully-matured as an API (it's decidedly the case compared to either Android or iOS).

It's also why I complained that judging Windows 8 on the basis of the sparse populace of WinRT apps would have been as silly as judging the nascent Windows 95 by the lack of Win32 applications.

I would think that users that cannot see the colors can enable them via accessability settings or a quick menu... imagine if windows shipped with high contrast by default it would turn most people away from using it. windows has always used a neutral palette so as to not make people's eyes hurt when looking at the UI. Metro goes against that and the colors might be too bright or vibrant to make them have migraines.

People are going to have migraines because they are going to look at the start screen all day?

Simple. Microsoft can't get anybody to use their Phone or Tablet software on their own merits so they're exploiting their existing desktop monopoly to do it. Microsoft's hoping by forcing everyone to use the same Metro/Tiles/Start Screen interface, they can create a demand and expand the same monopoly to mobile devices.

Will it work? Who knows. It's possible I suppose. But if you compare Windows Mobile to the desktop, it had a lot of similarities, yet it couldn't dominate the market like the desktop version does. This leads me to believe this time around won't be any different.

You're right sir!

Until the tiles start filling in with your data then you understand it's nothing like that silly AOL image with it's static images. It seems people just don't want to admit the fact that the live tiles are more than just icons. It seems like doing so would kill their argument about how silly the start screen is and so on.

I CAN'T wait to install Windows 8 to have live tiles telling me who who posted on Facebook or how hot it is outside!It will CHANGE our lives for the best! So many USEFUL informations! :) ...

So this is a desktop. Just curious, why do you shut it down at all?

The same reason most people shut down their computers - a) when required to do so after installing new drivers, b) when required to do so after installing new Windows updates, c) when required to do so after installing new software, and d) when leaving the house for long periods of time. I've found sleep and hibernate to be more trouble than they're worth. But that's irrelevant - it's simply more awkward and obscure than it was before.

Why are you people talking about the power options yet again? Seriously, it's one extra, insignificant step.

Because Microsoft has taken an action that was previously quick to access and easy to find and have hidden it behind the charms bar. The reality is that on the desktop there is simply no reason to use the charms bar at all, apart from to shut down your computer. It's a pointless and unnecessary change. Microsoft could have simply added shut-down options to the user tile on the Start Screen or the quick-access menu on the desktop. And it's not just that it's one extra step - it requires considerably more movement of the mouse and is considerably more fiddly, especially on multi-monitor setups. It's a bad implementation not at all suited to desktop use.

The same reason most people shut down their computers - a) when required to do so after installing new drivers, b) when required to do so after installing new Windows updates, c) when required to do so after installing new software, and d) when leaving the house for long periods of time. I've found sleep and hibernate to be more trouble than they're worth. But that's irrelevant - it's simply more awkward and obscure than it was before.

Because Microsoft has taken an action that was previously quick to access and easy to find and have hidden it behind the charms bar. The reality is that on the desktop there is simply no reason to use the charms bar at all, apart from to shut down your computer. It's a pointless and unnecessary change. Microsoft could have simply added shut-down options to the user tile on the Start Screen or the quick-access menu on the desktop. And it's not just that it's one extra step - it requires considerably more movement of the mouse and is considerably more fiddly, especially on multi-monitor setups. It's a bad implementation not at all suited to desktop use.

So basically they do it a few times a month, and most of those times they don't need to use the shutdown function since the updates/installer will do it automatically for them.

leaving only the leavign for extended periods... So why, again, should the shutdown button be using prime real estate at the front of your start menu/screen ? when it is, or should be in modern computing one of the least used buttons(or even fucntions) of fucntions you actually use on your machine...

The same reason most people shut down their computers - a) when required to do so after installing new drivers, b) when required to do so after installing new Windows updates, c) when required to do so after installing new software, and d) when leaving the house for long periods of time. I've found sleep and hibernate to be more trouble than they're worth. But that's irrelevant - it's simply more awkward and obscure than it was before.

I honestly can't remember the last time I had to reboot because of installing drivers, updates prompt me to restart, I can't remember I had to reboot either for new software, and when leaving, my machine goes to sleep. If I leave for an extended period of time, I do power down, but an extra click doesn't bother me at all.

Windows 8 is great as it is right now and at first time i used w8 i was like, what the... is this going to be the next major windows release?

But, using w8 every day i notice that i do my regular task faster like: start up is way faster, i open app from metro start screen and it's like i open them from ipad (smooth and fast), my applications are loading faster

like photoshop, games etc. i like how the weather app works and how the live tile works too, knowing what weather will be without opening the app is really great, copy paste is faster too.

Anyway i describe how i fee about w8 and i want it to stay as it is without combining it with the regular desktop or adding useless info, news and other bload. Also i'm waiting to see how the white non aero theme will

work cause i think that too much white will tire our eyes and that's not so good. One thing i really like from the leaked screenshots i saw is the transparent statusbar without blur!

I honestly can't remember the last time I had to reboot because of installing drivers, updates prompt me to restart, I can't remember I had to reboot either for new software, and when leaving, my machine goes to sleep. If I leave for an extended period of time, I do power down, but an extra click doesn't bother me at all.

just wondering Dot Matrix, but why do you need to argue so fervently in every windows 8 topic , we get it, you like it... do you work for Microsoft of somethin? In any case you must have made your point about a million times by now. and if Windows 8 is so great then why do you feel the need to argue, surely people will figure it out for themselves if they like it.

leaving only the leavign for extended periods... So why, again, should the shutdown button be using prime real estate at the front of your start menu/screen ? when it is, or should be in modern computing one of the least used buttons(or even fucntions) of fucntions you actually use on your machine...

You're missing the point, which is that a core system function is hidden unnecessarily when previous versions of Windows exposed it. At the end of the day the restarting your computer isn't a "Setting" and shouldn't be hidden in the charms bar, which serves no other purpose on the desktop.

I honestly can't remember the last time I had to reboot because of installing drivers, updates prompt me to restart, I can't remember I had to reboot either for new software, and when leaving, my machine goes to sleep. If I leave for an extended period of time, I do power down, but an extra click doesn't bother me at all.

Well clearly you don't have a dual-GPU setup, as driver installs disable the second GPU until a restart. You're coming up with excuses rather than addressing the core issue, which is that the shut down options shouldn't be hidden in an obscure menu when they were previously exposed and easy to find.

Can't believe how many people on a TECH site are so **** at using an OS. Whining about a startbutton (that you shouldnt even be using in vista or windows 7 anyways) and talking about how MS is stupid for doing metro. Metro is here to stay either deal with it or use Win7 or install linux and join the other 200 people saying its the year of linux every year.

Well clearly you don't have a dual-GPU setup, as driver installs disable the second GPU until a restart. You're coming up with excuses rather than addressing the core issue, which is that the shut down options shouldn't be hidden in an obscure menu when they were previously exposed and easy to find.

I'm not making excuses. Personally, I think they're right where they should be. They're no more hidden away then they were in 95-7, or any other options in Windows 8. I used to have the same opinion as you, but as I have used the OS more and more, it's just become second nature to me. Could they have their own Charm? Sure, but at the same time, I think the power options are right where they rightfully belong finally.

If you really feel adventurous, though, there are ways to place shut down and restart icons right on the Start Screen or Desktop.

Can't believe how many people on a TECH site are so **** at using an OS. Whining about a startbutton (that you shouldnt even be using in vista or windows 7 anyways) and talking about how MS is stupid for doing metro. Metro is here to stay either deal with it or use Win7 or install linux and join the other 200 people saying its the year of linux every year.

There is nothing wrong with voicing problems with Metro. Telling people to shut up because they don't sing the praises of Metro doesn't work either. Metro in my opinion is but a clear example of how MS has little clue about the consumer market, especially in maturing what W7 could have been, and kept maturing Aero. Metro has little use for complicated apps, especially ones such as image editing/creation software, browsers, office suites, etc/ -> its design principles are poor at best, its inefficient and going the opposite what GUI refinement has been about in the last decade. I personally feel sorry for MS and Metro, once people get over the FAD hype that is Metro, they'll be trying to figure out wth MS has been doing all this time since W7. Other than the shallow back end improvements, W8 certainly won't justify the wait or price.

Another Win or Fail Metro Integration, this time with Neowin News?

rU39p.jpg

Seeing this mockup, I'm not so sure Metro should be on the desktop. If Metro apps are single task, consumption apps like most tablet apps (even Netflix) that generally require all your focus, why should it? If creation apps (Office, Photoshop, InDesign, AutoCad) app that are multiwindow/multitasking go metro, then that would be problematic.

I think people will get used to the Start page and eventually forget it is less efficient that 7, and if you use a lot of Metro apps of the type currently available, you're probably not going to mind the full screeness.

There is nothing wrong with voicing problems with Metro. Telling people to shut up because they don't sing the praises of Metro doesn't work either. Metro in my opinion is but a clear example of how MS has little clue about the consumer market, especially in maturing what W7 could have been, and kept maturing Aero. Metro has little use for complicated apps, especially ones such as image editing/creation software, browsers, office suites, etc/ -> its design principles are poor at best, its inefficient and going the opposite what GUI refinement has been about in the last decade. I personally feel sorry for MS and Metro, once people get over the FAD hype that is Metro, they'll be trying to figure out wth MS has been doing all this time since W7. Other than the shallow back end improvements, W8 certainly won't justify the wait or price.

Mostly agree but can't agree with 8 having "shallow back end improvements." On the desktop, for sure, Metro is problematic on the front end. On the desktop. But for 8 and Server 2012 I think you should wait and take a closer look before you dismiss the actuall OS.

I've joined the party late, please excuse the format!..

So, I'm one of those weird guys that actually like Windows 8. I love Metro, how fast it is, the new functionality...

Nobody actually likes Metro.. :)

But, using w8 every day i notice that i do my regular task faster [..]

When was the last time you've installed Windows 7 on a formatted drive - it's blazing fast, for the things that you have mentioned (measured in mere seconds & less).

(that you shouldnt even be using in vista or windows 7 anyways)

Bottom left-click - start menu, bottom right - show desktop; it's how Microsoft made it and what we're used to. Simple, if you think about it.

If creation apps (Office, Photoshop, InDesign, AutoCad) app that are multiwindow/multitasking go metro, then that would be problematic.

Just have it auto-hidden and raised with a shortcut; Or activated as a Metro-app, etc. Real basic stuff.

There is nothing wrong with voicing problems with Metro.

Tnx. :D

You're missing the point, which is that a core system function is hidden unnecessarily when previous versions of Windows exposed it. At the end of the day the restarting your computer isn't a "Setting" and shouldn't be hidden in the charms bar, which serves no other purpose on the desktop.

so, just because a function that doesnt need to be featured prominently anymore, and in many ways shouldn't, used to be, it should always be? fail logic, that's how you don't progress.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • On what though? Not Ray Tracing.
    • Agreed, but now my muscle memory immediately creates a layer for each text portion, so editing is made a little easier.
    • Happy for him, it is one of the first apps I install on a new Windows machine, been using it for years!
    • I still don't think it's as simple as that. Should Amazon drop "Cloud" from their product/service branding? That's a platform too?
    • Microsoft explains why PowerToys 0.100.0 is faster and slimmer, there are new features too by Sayan Sen Microsoft has released PowerToys version 0.100.0 today, bringing a sizeable collection of upgrades across the utility suite. While the release contains fixes and improvements for multiple modules, the biggest highlights revolve around performance, reduced package size, Command Palette enhancements, a redesigned Shortcut Guide experience, and further refinements to the recently introduced Power Display utility. For anyone not familiar or who does not read Neowin regularly, Microsoft PowerToys is a free, open-source set of utilities for Windows 10 and 11 that are designed to help with customization that can also in turn boost your productivity. It offers tools such as FancyZones for window layouts, PowerToys Run for quick app launching, Color Picker, PowerRename, and more. The app is primarily meant for power users on Windows, and hence the name. One of the most notable changes in PowerToys 0.100.0 is its migration to .NET 10. Besides modernizing the codebase, the move greatly reduces the application's overall footprint and also claims to improve startup times and general responsiveness. For users who keep PowerToys running continuously in the background, this could mean a smoother experience and lower resource usage over time. It is no fluke for sure as is evident from the download size. While the previous release 0.99.1 was 376MB, the latest release is substantially smaller at just 272MB. That's a 28% drop. Microsoft is also continuing its development of Command Palette as the launcher receives another round of upgrades including a new utility called Extension Gallery. As the name suggests, it lets users browse through and also install various extensions without leaving the Command Palette. It is available within the Command Palette settings. Speaking of new utilities, a newly revamped Shortcut Guide experience has been added. It basically displays available Windows key shortcuts on demand and has been redesigned to make discovering and learning keyboard shortcuts easier. Given that Shortcut Guide was one of the earlier PowerToys features in its open-source era, the refresh brings it more in line with the modern design language Microsoft has been introducing throughout the project. Power Display, the monitor-management utility introduced recently, also receives meaningful improvements. The tool allows users to control supported monitor settings such as brightness, contrast, volume, and color profiles directly from the system tray without reaching for physical monitor buttons. Several existing modules have received smaller but useful improvements as well. Microsoft has continued refining FancyZones, File Locksmith, Advanced Paste, Image Resizer, Mouse utilities, and other components. As usual, the release includes a long list of bug fixes aimed at improving stability, reducing crashes, and addressing user-reported issues across the suite. The full changelog is given below: Advanced Paste Fixed Advanced Paste clipboard-to-JSON conversion so clipboard read failures return an empty result instead of surfacing an exception in #48124 Command Palette Extension Gallery & Extensions Added the Command Palette Extension Gallery so users can discover, browse, install, update, and uninstall community extensions from within Command Palette, with cached gallery data, extension details/screenshots, and WinGet status/progress integration Added Command Palette parameter pages so extensions can prompt for lightweight command inputs directly in the search experience, including sample pages and SDK support for parameter runs Updated Command Palette bookmarks to collect placeholder values as inline parameters, so bookmarked commands can be filled in directly instead of opening a separate placeholders page Improved Command Palette Extension Gallery link handling so only HTTP/HTTPS homepage, author, install, and metadata links are shown or opened from the gallery UI Fixed Command Palette Extension Gallery UI bindings so WinGet operation indicators continue to update correctly without build warnings Fixed an AOT-only Command Palette Extension Gallery crash when opening an extension page with screenshots Updated the Command Palette extension template to use the 0.11 SDK package Improved Command Palette accessibility so Narrator announces checkbox labels on the Installed Apps page in Extensions settings in Dock Added Command Palette Dock support for customizing dock bands separately per monitor, allowing multi-monitor setups to keep independent dock layouts Added Command Palette Dock edit mode support for dragging dock bands between monitors, so pinned commands can move across per-monitor dock layouts Added Command Palette Dock drag-and-drop bookmarking for files and URLs, immediately creating and pinning bookmarks, improving pinned folder bookmarks so they open the Command Palette browse experience Fixed Command Palette dock context menu commands so Page commands and confirmation dialogs open the palette at the dock item when invoked from a dock item menu Fixed Command Palette Dock band tooltips so they refresh when the item title or subtitle changes Fixed Command Palette dock startup animations so items pinned to the End section animate consistently with Start and Center items Fixed Command Palette dock subtitle visibility in compact mode so subtitles refresh correctly after async updates Fixed Command Palette hotkey navigation when the palette is showing a transient dock page Fixed a Command Palette dock window border that occasionally remained visible after disconnect/reconnect, by ensuring the owner HWND is set before frame removal Improved the Command Palette Pin to Dock dialog by reordering controls so they appear above the preview, making the dialog easier to scan Performance Monitor Added a Battery widget to Command Palette Performance Monitor that shows live charge percentage, charging/AC status, and estimated time remaining, updating the dock-band battery icon to reflect current charge level and charging state in Added Command Palette Performance Monitor dock bands for individual metrics like CPU, memory, network, GPU, and battery when available Fixed Command Palette Performance Monitor's CPU dock reading to use a 0–100% system CPU counter, preventing boosted CPUs from showing values above 100% Improved Command Palette Performance Monitor network widgets by giving Send and Receive distinct up/down arrow icons and simplifying their labels Reordered Command Palette Performance Monitor network dock bands to match Task Manager's send/receive order Fixed a Command Palette Performance Monitor crash when a GPU index falls outside the available range Fixed a Command Palette Performance Monitor settings file path collision that could cause widget settings to overwrite one another Calculator Added rand() and randi() to the Command Palette Calculator and improved error messages by distinguishing invalid expressions, NaN, and out-of-range results Fixed Command Palette Calculator parsing for multi-argument functions in cultures where comma is both thousands separator and argument separator, so expressions like max(1,2) and grouped numbers are handled correctly Fixed the Command Palette and Run Calculator 'log' and 'ln' functions when whitespace separates the function name from its argument, so 'log (n)' computes log base 10 and 'ln (n)' no longer errors out Reliability & UX Added a pinned commands section to the Command Palette Home page with context-menu actions for reordering pinned commands Updated Command Palette Shell provider to behave more like Windows Run, improving command execution and suggestions for network paths, NTFS paths, and other edge-case paths Improved Command Palette Window Walker by showing a loading state while open windows are queried during search Improved Command Palette list items by limiting visible tag pills to three and showing a +N overflow badge, preventing tags from crowding out titles Added a Command Palette All Apps setting to hide app description subtitles in search results for a cleaner list view Fixed Command Palette back navigation so the bottom command bar refreshes immediately when returning with Esc or Backspace Fixed Command Palette Extensions settings text so single command and fallback command counts use singular wording Improved Command Palette extension logging by routing extension messages to info, warning, or error logs according to their reported severity Updated Command Palette versioning to 0.11 Added stable Command Palette automation IDs so UI testing tools can reliably target controls and generated list items across sessions Fixed Command Palette Dock positioning when opening palette items from secondary displays, so the palette appears on the correct monitor Updated developer documentation with steps for debugging Command Palette directly through its Visual Studio solution filter Added Command Palette Remote Desktop support for connecting to arbitrary hostnames typed into the list page, in addition to discovered connections Improved Command Palette result scoring by synchronising fallback title and subtitle formatting so similar items rank consistently Added a Command Palette "Show details" / "Hide details" toggle (with an icon) to the context menu, replacing the previous separate entries FancyZones Added translator-comment guidance to the FancyZones Editor strings 'Space around zones' and 'Highlight distance' so localizers translate them as margin/padding and adjacent-zone detection distance, fixing misleading Japanese renderings File Explorer Fixed a Markdown preview crash on UTF-8 files (notably CJK content) that exceeded WebView2's NavigateToString byte limit by switching the size check to count UTF-8 bytes and falling back to the temp-file rendering path when the threshold is exceeded File Locksmith Fixed File Locksmith handling of Unicode file paths when passing paths between normal and elevated runs, preventing certain non-ASCII paths from being corrupted Grab And Move Fixed the LNK2038 C++/WinRT version mismatch breaking GrabAndMove on CI by adding the Microsoft.Windows.CppWinRT NuGet to GrabAndMove.vcxproj so it uses the repo-pinned CppWinRT instead of whatever the Windows SDK ships Removed the "NEW" tag from the Grab And Move entry in Settings now that the module has shipped through a full release Image Resizer Added live settings reload to Image Resizer so external changes to settings.json take effect immediately without relaunching the flow Improved Image Resizer accessibility so Narrator announces the Resize button by name and the window title now reads 'Image Resizer' instead of the generic 'WinUI Desktop' Keyboard Manager Enabled the redesigned Keyboard Manager editor by default, so new installations open the WinUI 3 editor without changing settings Mouse Without Borders Added Mouse Without Borders Refresh Connections to Quick Access and the Settings Dashboard so users can reconnect devices faster Refactored Mouse Without Borders logging cleanup with no intended user-facing behavior change Peek Added a 'Show file preview tooltip' toggle to Peek's Behavior settings so users can disable the on-hover metadata tooltip (filename, type, date modified, size), and fixed the binding so toggling off no longer leaves an empty popup attached PowerDisplay Improved Power Display by automatically disabling the feature after a detected DDC/CI capability crash and showing a Settings warning before users re-enable it Fixed Power Display flyout keyboard handling so pressing Escape closes the window Improved Power Display monitor detection by rescanning displays when the screen wakes and temporarily locking controls until the refresh completes Updated PowerToys documentation to include telemetry events for Grab And Move and Power Display Updated Power Display localization comments so the product name remains untranslated in UI strings, including the system tray tooltip Improved Power Display monitor discovery by distinguishing internal panels from external monitors before applying brightness controls, reducing unnecessary DDC/CI probing on built-in displays Fixed Power Display upgrades so existing per-monitor preferences are carried forward from older monitor IDs to the current stable IDs Added a Power Display Max compatibility mode setting that can find monitors skipped by standard DDC discovery, with an immediate rescan and warning in Settings when enabled Improved Power Display brightness, contrast, and volume sliders by committing changes after a short debounce and allowing mouse-wheel adjustments Fixed Power Display brightness, contrast, and volume controls on monitors whose native DDC/CI ranges are not 0-100 by scaling slider percentages correctly Added a Power Display Settings confirmation prompt before enabling the module and improved monitor diagnostics for troubleshooting Fixed Power Display per-monitor settings so toggles persist across restarts, monitor reordering, and transient discovery failures Added a built-in Power Display monitor blacklist so known problematic displays are skipped during DDC/CI discovery and reported in logs instead of being probed Fixed a Power Display false-positive crash detection when the host process exits cooperatively, so the safety lockout no longer triggers on clean shutdowns Removed the "NEW" tag from the Power Display entry in Settings now that the module has shipped through a full release Reworked the Power Display warning dialog with clearer messaging, distinct warning kinds, and a dedicated dialog view-model so users get more actionable guidance after a DDC/CI issue PowerToys Run Improved PowerToys Run Calculator to return a friendly error for expressions whose result is a complex number (e.g. sqrt(-1)) instead of throwing during decimal conversion Documented the third-party PowerToys Run plugin Community.PowerToys.Run.Plugin.DiskAnalyzer for scanning folders/drives to find the largest files and folders Quick Accent Updated Quick Accent’s popup UI to standard PowerToys styling while keeping the accent selector experience unchanged Improved Quick Accent language selection consistency by sharing the same language list between the accent popup and Settings UI Added Greek Polytonic as a Quick Accent language, making polytonic Greek characters available from matching letter keys and Settings in Fixed Quick Accent popup sizing, positioning, and selection glitches on high-DPI or multi-monitor setups, and improved Shift-key detection for navigation Settings Added Image Resizer size preset validation so empty or whitespace names are ignored, keeping presets named and easier to understand Fixed the Settings UI resource list by removing a duplicate Quick Accent Greek Polytonic language entry, allowing Settings builds to complete cleanly Improved Settings UI with refreshed PowerToys imagery, constrained OOBE/SCOOBE layouts, and cleaner General settings controls and icons Fixed the Settings “No shortcuts to show” empty-state message so it displays with a single period Updated Grab And Move settings localization guidance so the Korean translation for “Activation modifier key” uses the feature activation meaning instead of product activation wording Fixed the Quick Access flyout shortcut editor so clicking Reset no longer crashes PowerToys Settings and leaves the shortcut empty cleanly Fixed PowerToys auto-update so it now actually relaunches after install with a 'successfully updated' toast, backs up all JSON configs before updating with restore on detected corruption, and defaults AutoDownloadUpdates to true for fresh installs Renamed the OOBE overview "Learn" link label to "Documentation" so the call-to-action is clearer to first-time users Shortcut Guide Fixed Shortcut Guide key visuals to show readable key names instead of raw numeric key codes, while preserving arrow key glyph behavior Improved Shortcut Guide V2 reliability and accuracy by showing the configured shortcut, including additional PowerToys module shortcuts, matching app manifests correctly, and exiting cleanly from Esc or the close button in Added Shortcut Guide V2, a redesigned shortcut reference with built-in manifests for Windows, PowerToys, and common apps, plus taskbar/context-aware navigation and updated Settings, OOBE, docs, and installer support Renamed the Settings UI module label from "Shortcut Guide V2" to "Shortcut Guide" now that V2 is the only shipping version Fixed a Shortcut Guide V2 crash that occurred when the per-app Manifests directory was missing or unreadable, by treating the directory as empty in that case Reworded the Shortcut Guide module and OOBE descriptions so they better explain what V2 does and how to invoke it Workspaces Reworked the Workspaces editor with WPF Fluent theming (dropping ControlzEx and ModernWpf), refined fonts, spacing, and Mica background, and moved action buttons to the top with full-width scrolling ZoomIt Removed a stale Microsoft.Windows.ImplementationLibrary NuGet import from ZoomItBreak.vcxproj that was unused but broke the official build after the .NET 10 upgrade bumped the sibling project's WIL version Added webcam capture overlay and multi-clip append-with-transitions support to the ZoomIt recording/trim editor, exposed the new options in the ZoomIt Settings page, and fixed microphone/webcam selection-dialog bugs along the way Fixed ZoomIt's record-hotkey registration so when Alt is the only modifier the window-record hotkey (base XOR Alt) is no longer registered as a modifier-less key that had been hijacking every bare keypress Exposed ZoomIt's 16:9 aspect-ratio toggle for the screen-region recording hotkey (default Ctrl+Shift+5) in the PowerToys Settings UI Development Build / dependency improvements: Updated PowerToys build and developer tooling to .NET 10, with Visual Studio 2026 now required for building from source Fixed Shortcut Guide v2 release signing by adding the YamlDotNet dependency to the signed binaries list Updated shared PowerToys .NET runtime and library packages from 10.0.7 to 10.0.8 for the latest servicing fixes Improved PowerToys build tooling so build scripts discover Visual Studio 2026 Insiders/Preview installations with C++ tools and skip unusable installs Updated PowerToys WinUI platform dependencies, including Windows App SDK 2.0.1 and WebView2, for apps and the Command Palette extension template Updated shared PowerToys .NET runtime and library packages from 10.0.6 to 10.0.7 for the latest servicing fixes Fixed Quick Accent release signing by adding PowerAccent.Common.dll to the signed binaries list Fixed Advanced Paste release signing by adding the Google Gemini-related dependency DLLs to the signed binaries list Updated Advanced Paste AI dependencies, including Semantic Kernel and provider connectors, to newer package versions CI & automation: Added a Telemetry PR Check workflow that detects telemetry event changes in pull requests and posts contributor guidance Updated GitHub issue triage automation by renaming the area-labeling workflow and removing the legacy product auto-label workflow Added GitHub issue triage automation that applies Product/Area labels to new or reopened issues and supports manual backfill Fixed GitHub issue auto-labeling by correcting Product label names so the workflow applies existing repository labels Added a GitHub Action and tester for issue triage that applies Product labels from issue template areas, with AI fallback and manual modes Fixed GitHub issue auto-labeling so the workflow can authenticate with GitHub Models and apply area labels again Updated spell-check CI expectations by removing obsolete tokens, reducing noisy advisory comments on pull requests Updated CI to skip automatic builds for draft pull requests until they are ready for review Fixed the README roadmap reference for v0.100 so it renders as a clickable milestone link Updated README download guidance to point users to release assets and changes the release notes link to the releases page Updated the GitHub issue tracker duplicate-resolution reply to more clearly point users to the original tracking issue To download the new release, head over to PowerToys official GitHub repo here.
  • Recent Achievements

    • One Year In
      Primer1st earned a badge
      One Year In
    • Experienced
      JayZJay went up a rank
      Experienced
    • Reacting Well
      Sir_Timbit earned a badge
      Reacting Well
    • Week One Done
      rubentuben8 earned a badge
      Week One Done
    • Week One Done
      ARaclen earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      512
    2. 2
      PsYcHoKiLLa
      229
    3. 3
      Edouard
      136
    4. 4
      ATLien_0
      87
    5. 5
      Steven P.
      80
  • Tell a friend

    Love Neowin? Tell a friend!