Windows 7 -- Approach to System Performance


Recommended Posts

Business, Home, Home Ultimate, Server

That's all they need todo.

Business should be cut down, no sparkly effects, just raw performance and ease of use

Home should be basic, a few effects here and there but again performance focused for standard families.

Home ultimate should be the best looking version of them all, many effects, gaming performance mode, lots of extras

Server, standard server edition

(Y)

Good. Let's get rid of Basic. It's useless. Same for Vista Ultimate. I purchased it, and I don't know but it's no better than Home Premium.

Low end SKUs should definetely be canceled in certain markets or controlled carefully. Do you know how many small OEMs here put Vista Starter Editions in their cheap boxes to save a couple of bucks, where they would even probably run Home Premium? You should of see the faces of people when I told them it was an OS limitation after they asked me why they can't run more than 3 programs at the same time. Definetely not a good marketing image for Microsoft, is it?

It is impossible for Microsoft to have only one SKU of Windows. It would cost billions of dollars to give up even one of the existing SKUs. It's just not going to happen.

Apple has multiple OS editions at differnet price points too. You just don't notice because they bake it into the price of their hardware. Since their business operates in an entirely different way than Microsoft, you cannot compare the two.

Also, Apple is mainly interested in converting PC buyers into Mac buyers. Thus, success / growth for them means taking someone who would have bought a PC and getting them to buy a Mac. For Microsoft, everybody already buys PCs. Getting new people to buy PCs is very difficult since there are only so many people in the world (and only so many in a position to buy a computer).

So it's hard for Microsoft to grow by getting new users. So instead, Microsoft's best option for growth is to get existing users to pay more. That can mean buying more computers, buying new kinds of devices (like an Xbox, a Media Center, a Tablet, or a Windows Home Server). But it can also mean buying more expensive versions of Windows. In order to do that, those higher-priced editions need to offer compelling enough feature sets or other advantages that make them worth more money to a significant number of people.

Really, asking for one version of Windows is like asking Sony to stop making different PS3s with different hard drive sizes. Well yeah, if you only want the 40GB one then you don't care about the other options. But some people want the option to pay more for an 80GB or 120GB version. Just because you don't want to doesn't mean they shouldn't offer the option. Now, some of you will say that Microsoft should just sell Ultimate at the cheapest price. That's just like saying that Sony should get rid of the 40GB and 80GB PS3s and sell a 120GB model at the price of the 40GB. It won't happen because it's a losing proposition for them, and asking for it just makes you sound ridiculous.

Sounds fair in theory but the impact is really unpleasant options for the consumer. An OS should be a platform for building from. It would be far more consumer friendly for MS to make adding the different features of their OS versions by buying them afterwards. None of this "I want feature x but have os version x so I need to buy os version y and then either upgrade the OS or reinstall the OS".

All of the following could be purchaseable otions:

Domain support

Disk Encryption

Virtual PC host

Media Center

Tablet support

Dreamscene

Windows Games

Photo gallery

Movie maker

Businesses would not be loaded with unwanted options and consumers could easily add the business features they wanted and MS gets a new market to make money from. Everyone's a winner.

Maybe MS should have thought through the difficulties they were generating with the multiple sku's before they added so many.

Basic shouldn't exist, home premium and business are like xp home and pro, and ultimate just includes options from those 2 (like pro was the real deal). but yeah, scrap ultimate too. I would ship just a server and a client version

You are incorrect in your statement on Home Basic and Home Premium.

Home Basic is equal to XP Home.

Home Premium is equal to XP MCE

Business is equal to XP Pro

The only new SKU to Vista is Ultimate.

My suggestion to the whole Windows version debacle is for them to make 2 main versions, and then a server product:

1.) Windows Business - Contains everything except for Media Center, Games, Movie Maker, DVD Maker, and other multimedia packages. This is suitable for both home and business users, and is the less expensive version.

2.) Windows Complete - The complete version of Windows. This is for both home and business users.

3.) Windows Server - Server product.

And finally, they should lower the price. My "Windows Complete" suggestion should not sell for more than $200 for a full retail version.

I know Apple has it's Server product and Desktop product.

The Desktop product is just one version, there is no multiple SKU's in Retail.

Brandon. I hate to sound like a broken record. But Apple and Linux distributions do this. You buy one version. It's the complete version. You then choose what to not install in custom installation settings. Comparing Hardware to Software is not really comparing apples with apples.

No, they do NOT have one edition.

They have the Macbook and they have the Macbook Pro. Those are different price points. Different SKUs, if you will. One has more features and costs more than the other. It's the exact same thing. Why would Apple bother to have "Macbook with OS X Home Edition" and "Macbook Pro with OS X Business Edition" when they might as well just call them the Macbook and Macbook Pro?

If they sold their OS to OEMs, then it would be a fair comparison.

Linux obviously isn't a fair comparison, it's free. You can't have different price points if they're all free. Make no mistake, the whole point of different SKUs is different price points.

My suggestion to the whole Windows version debacle is for them to make 2 main versions, and then a server product:

1.) Windows Business - Contains everything except for Media Center, Games, Movie Maker, DVD Maker, and other multimedia packages. This is suitable for both home and business users, and is the less expensive version.

2.) Windows Complete - The complete version of Windows. This is for both home and business users.

3.) Windows Server - Server product.

And finally, they should lower the price. My "Windows Complete" suggestion should not sell for more than $200 for a full retail version.

Vista Business costs more than Home Premium, Or i would have bought it. Never had a need for Media Center.

I have to agree with both approaches, Which is exactly what Steve is trying to say - There is no clear-cut solution. You have to compromise.

Personally, I'd love it if Microsoft put a "Custom Install" option, clearly noting that it is NOT supported. The people who would bother to use are most likely advanced users, Who wouldn't need Microsoft support either way.

Sounds fair in theory but the impact is really unpleasant options for the consumer. An OS should be a platform for building from. It would be far more consumer friendly for MS to make adding the different features of their OS versions by buying them afterwards. None of this "I want feature x but have os version x so I need to buy os version y and then either upgrade the OS or reinstall the OS".

All of the following could be purchaseable otions:

Domain support

Disk Encryption

Virtual PC host

Media Center

Tablet support

Dreamscene

Windows Games

Photo gallery

Movie maker

Businesses would not be loaded with unwanted options and consumers could easily add the business features they wanted and MS gets a new market to make money from. Everyone's a winner.

Maybe MS should have thought through the difficulties they were generating with the multiple sku's before they added so many.

That's more or less how it works today, right? Yeah there's no a la carte option, but you can buy Home Basic and then use the Windows Anytime Upgrade feature to turn it into Business or Home Premium if you want those features.

The only major difference between Home Basic and Home Premium is Media Center support. Other than that it's all little things like Flip3D and such).

Brandon, may I make a quickie request, you can ignore it....but...

FOR THE LOVE OF ALL THAT IS HOLY AND RIGHT IN THE WORLD! lol..

Anyways, how about UI unification, for instance, in the classic non-glass areas of Vista, like in those apps that use XP style menus and such, it looks horrible, outstretched and out of place..

post-118616-1220048615_thumb.jpg

No, they do NOT have one edition.

They have the Macbook and they have the Macbook Pro. Those are different price points. Different SKUs, if you will. One has more features and costs more than the other. It's the exact same thing. Why would Apple bother to have "Macbook with OS X Home Edition" and "Macbook Pro with OS X Business Edition" when they might as well just call them the Macbook and Macbook Pro?

If they sold their OS to OEMs, then it would be a fair comparison.

Linux obviously isn't a fair comparison, it's free. You can't have different price points if they're all free. Make no mistake, the whole point of different SKUs is different price points.

That's a silly comparison, because they sell 10.5 as a single product as well and not just bundled with the hardware. Apple did sell hardware before they released 10.5 and consumers are welcome to upgrade if they want--everybody will pay a flat price for a single version that has all the features.

A Macbook Pro does not have more software features than a Macbook. Neither does a Mac Pro. Nor an iMac. The difference in prices are merely between the hardware--not software.

Brandon, may I make a quickie request, you can ignore it....but...

FOR THE LOVE OF ALL THAT IS HOLY AND RIGHT IN THE WORLD! lol..

Anyways, how about UI unification, for instance, in the classic non-glass areas of Vista, like in those apps that use XP style menus and such, it looks horrible, outstretched and out of place..

http://www.aerotaskforce.com/

That's a silly comparison, because they sell 10.5 as a single product as well and not just bundled with the hardware. Apple did sell hardware before they released 10.5 and consumers are welcome to upgrade if they want--everybody will pay a flat price for a single version that has all the features.

A Macbook Pro does not have more software features than a Macbook. Neither does a Mac Pro. Nor an iMac. The difference in prices are merely between the hardware--not software.

Thanks @ giga. (Y)

Perhaps Brandon needs to go to a Mac store and see for himself.

Microsoft has got to realize that whatever their (flawed, IMO) justifications, most customers don't want to choose from the number of Windows versions that are currently available. IMO For Home customers their should be - Windows Home and for Enthusiasts - Windows Premium. Get rid of Ultimate, that was a scam.

Then for Business have a Windows Business and Windows Server. That's it! That has got to be easier for everyone.

what would be a good solution is make 3 versions. a business version that has stuff a business needs and a business can purchase a few extras if needed and a home version for home users that has all a home user needs and have 1 that has the best of both worlds but the 3rd one could have backwards compatability at least partialy removed and cost slighty more than the home version but less than the business version but if you needed backwards compatability turned on fully ypu could have an option to do that.

The reason Windows hasn't grasped on to this subject can be found in linux. Linux has the repos to install WHAT a user wants through..well YAST since I like Opensuse. it doesn't shove all that crap down our throats at install.

this is my thought on windows 7

win7wi5.jpg

Microsoft has got to realize that whatever their (flawed, IMO) justifications

But the thing is that these things have to be REALLY well justified. If you have some profound analysis that countered the SKU design plans and led to some particular revelation - get a job in this space. Given all the available data out there, the Vista plan was designed. And any Windows 7 design would have to account for all the relevant factors as well, with the benefit of hindsight upon the Vista plan. Any plans have to be analyzed and approved given all available data. If somebody decides to just ignore important feedback without great justification, they're probably not going to succeed or keep their job.

I think the consistent point you raise is that the Vista SKU story could be cleaned up. I don't believe the Windows 7 SKU story if any is public at this time, and the article in question certainly doesn't key off of that. Assume that the right people here are not idiots, understand your criticism, and more importantly understand that any SKU variation comes at a non-trivial cost to the company.

Taken at least the last two points for granted (haters can assume the MS world is made up of monkeys on keyboards if they need to) combined with the fact that a new robust componentization system was first generally introduced in Vista, I would assume that Windows 7 would probably build off of that. Catering to the vLite "My Personal Win SKU" crowd requires significant cost (testing 10,000 variations well, oddly enough, takes around 10,000 tests). The "There Should Only Be 'N' SKUs" crowd should avoid a street rumble with the vLite crowd and realize that there has to be some pretty profound justification for any given SKU. If you personally don't feel that there should be 'N' SKUs, you should realize that that's your personal opinion without all the facts on hand. I can probably hook you up with the right people if you're really interested in a job in SKU design. If we're just armchair quarterbacking here, that's cool, but it's strange in a Windows 7 thread given that I'm not aware that the Windows 7 SKU plan is being publicly discussed at this point. :)

All these opinions prooffered so far are valuable and all are concerns or considerations that the right people are aware of. <3

@ zachdms. Do you work for Microsoft? (zachd_at_online.microsoft.com) ?

I understand what your saying zachdms, you say that it costs to change SKU's (perhaps costs a lot).

So why did Microsoft change the sensible Windows XP SKU's to the schizophrenic confused mess that is Vista SKU'?

There must have been reason, perhaps it was made by the marketing team? Either way. It's No. 1 Confusion Central.

I don't hate Microsoft or Vista. I like Vista, now, that it's had it's SP1, drivers are solid and compatibility has been improved.

Microsoft however should take a good look at itself. Windows is becoming an unwieldy behemoth.

Componization needs to be accelerated.

Setup needs to be granular for those who want the option and performance needs to take priority.

Multithreading / SMP need to take priority at Kernel level and Application level. By the time Windows 7 ships computers are

likely to ship standard with a Quad Core CPU and 4 to 8GB RAM.

Also, I don't accept the argument 'too many SKU's too much testing'. Apple can do it. Yeah? So can Microsoft.

If you're offering me a job at Microsoft. Seriously. Let's talk. I can talk the talk and walk the walk.

Edited by splicer707
Also, I don't accept the argument 'too many SKU's too much testing'. Apple can do it. Yeah? So can Microsoft.

You mean too much customizing. Well, Apple doesn't have to release quite as many patches as MS does.

And REALLY is it too hard to figure out what Vista version you want?

Am I using it mostly at home? Home Premium

Am I using it mostly at work? Business

Am I a home-business? Ultimate

Made the wrong choice? Windows Anytime Upgrade

This is perhaps the OEM's fault, Microsoft's fault, and the user's. For a long time, the pre-installed Windows has usually been the 'right' one for the user. Now it's occasionally the wrong one because the OEM shoves Vista Basic on it. I

Simple. 2 versions.

1) Professional

2) Home

XP had it right as far as i am concerned. No confusion. If you are a professional or business buy Professional. If you are a home user, buy Home. Done and dusted.

Microsoft should NOT be complicating this part. Its essential for them to nail it on the head. I think XP nailed it. No confusion.

That's a silly comparison, because they sell 10.5 as a single product as well and not just bundled with the hardware. Apple did sell hardware before they released 10.5 and consumers are welcome to upgrade if they want--everybody will pay a flat price for a single version that has all the features.

It's not silly. As I said, the only people who can buy the boxed version of 10.5 are people who already gave Apple a huge amount of money for at least one machine. For Apple, upgrade purchases are just gravy. Their business model doesn't involve selling those boxed software products, the revenue from it is tiny in comparison to their hardware sales.

A Macbook Pro does not have more software features than a Macbook. Neither does a Mac Pro. Nor an iMac. The difference in prices are merely between the hardware--not software.

No, the difference covers the entire package. They don't sell laptops with Mac OS Home Edition and Mac OS Business Edition, they sell the Macbook Home Edition and the Macbook Business Edition. There is no point in having different software SKUs since they don't sell software. They can't get an OEM to pay more for Mac OS Business Edition since they are the only OEM.

Thanks @ giga. (Y)

Perhaps Brandon needs to go to a Mac store and see for himself.

Until about a week ago my laptop was a Macbook (and I still have it, though probably not for much longer). So no, I don't need to visit an Apple store to see anything.

Until about a week ago my laptop was a Macbook (and I still have it, though probably not for much longer). So no, I don't need to visit an Apple store to see anything.

If you're giving it away. I'll send you my postal address. ;)

It's not silly. As I said, the only people who can buy the boxed version of 10.5 are people who already gave Apple a huge amount of money for at least one machine. For Apple, upgrade purchases are just gravy. Their business model doesn't involve selling those boxed software products, the revenue from it is tiny in comparison to their hardware sales.

No, the difference covers the entire package. They don't sell laptops with Mac OS Home Edition and Mac OS Business Edition, they sell the Macbook Home Edition and the Macbook Business Edition. There is no point in having different software SKUs since they don't sell software. They can't get an OEM to pay more for Mac OS Business Edition since they are the only OEM.

There's bothing like a Macbook Home and Business edition, there's no difference software wise between the two and the both are perfectly well suited to work at home or in a business so I can't see how your analogy works with this.

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!