{"id":107827,"date":"2023-02-14T07:00:00","date_gmt":"2023-02-14T15:00:00","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/oldnewthing\/?p=107827"},"modified":"2023-02-13T17:39:10","modified_gmt":"2023-02-14T01:39:10","slug":"20230214-00","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/oldnewthing\/20230214-00\/?p=107827","title":{"rendered":"Why are the Windows chassis hardware button hotkeys so strange?"},"content":{"rendered":"

Someone asked the shell team, “Why did you pick Power<\/kbd>+VolumeDown<\/kbd> as the hotkey to take a screen shot? Why not something simpler?”<\/p>\n

Set the time machine to 2010. Windows 8’s tablet-focused user interface is being designed, along with tablet hardware devices to showcase it. Since one of the signature characteristics of tablets is that they don’t have a keyboard, non-keyboard affordances have to be invented for various operations. Many of them could be triggered by various types of touch gestures, but the hardware buttons themselves were also pressed into use:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n
Button<\/th>\nAction in Windows 8<\/th>\n<\/tr>\n
Power<\/kbd><\/td>\nTurn screen on and off<\/td>\n<\/tr>\n
Windows<\/kbd><\/td>\nGo to Start screen<\/td>\n<\/tr>\n
VolumeUp<\/kbd><\/td>\nIncrease volume<\/td>\n<\/tr>\n
VolumeDown<\/kbd><\/td>\nDecrease volume<\/td>\n<\/tr>\n
Power<\/kbd> (hold)<\/td>\nShut down<\/td>\n<\/tr>\n
Power<\/kbd> (long hold)<\/td>\nEmergency power-off<\/td>\n<\/tr>\n
Windows<\/kbd>+VolumeUp<\/kbd><\/td>\nOpen\/close screen reader<\/td>\n<\/tr>\n
Windows<\/kbd>+VolumeDown<\/kbd><\/td>\nScreen shot<\/td>\n<\/tr>\n
Windows<\/kbd>+Power<\/kbd><\/td>\nCtrl<\/kbd>+Alt<\/kbd>+Del<\/kbd><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

In Windows 10, the requirement that tablets provide a Windows button on the chassis was removed, which means that the actions previously assigned to the Windows key were lost, and the ones deemed most important were reassigned.\u00b9<\/p>\n\n\n\n\n\n\n\n\n\n\n
Button<\/th>\nAction in Windows 10<\/th>\n<\/tr>\n
Power<\/kbd><\/td>\nTurn screen on and off<\/td>\n<\/tr>\n
VolumeUp<\/kbd><\/td>\nIncrease volume<\/td>\n<\/tr>\n
VolumeDown<\/kbd><\/td>\nDecrease volume<\/td>\n<\/tr>\n
Power<\/kbd> (hold)<\/td>\nShut down<\/td>\n<\/tr>\n
Power<\/kbd> (long hold)<\/td>\nEmergency power-off<\/td>\n<\/tr>\n
Power<\/kbd>+VolumeUp<\/kbd><\/td>\nScreen shot<\/td>\n<\/tr>\n
Power<\/kbd>+VolumeDown<\/kbd><\/td>\nCtrl<\/kbd>+Alt<\/kbd>+Del<\/kbd><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Given that you can count on only three buttons (power, volume up, and volume down), the set of available combinations is rather limited, and it’s hard to claim that any of them are “intuitive” beyond the power button actions.<\/p>\n

Bonus chatter<\/b>: If you employ the “long hold” emergency power-off hotkey, the system tries to capture diagnostic information before the BIOS kills the power. These dump files are used by the Windows team to identify and fix the root causes for system lock-ups.<\/p>\n

Windows recognizes a long power button hold at seven seconds, and the UEFI forces a power-off at ten seconds. Windows therefore has three seconds to collect whatever information it can before the UEFI pulls the plug. If you get a message from Windows acknowledging your emergency power-off request but asking you to release the power button, please do so if you can. This gives the kernel more time to capture the diagnostic information. Once the information is gathered, the kernel will turn off the system power.<\/p>\n

\u00b9 If you compare the two tables, you’ll find that the lost chassis hotkeys are “Open the Start menu” and “Open screen reader.” These two access points were moved to on-screen affordances and no longer need special hotkeys. The taskbar Start button opens the Start menu, and the lock screen Accessibility button lets you turn on the screen reader when signing in. (For opening the screen reader after signing in, you can use the Ease of Access \/ Accessibility section of the Settings app.)<\/p>\n","protected":false},"excerpt":{"rendered":"

Operating within the constraints of the system.<\/p>\n","protected":false},"author":1069,"featured_media":111744,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[2],"class_list":["post-107827","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-history"],"acf":[],"blog_post_summary":"

Operating within the constraints of the system.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/107827","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/users\/1069"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/comments?post=107827"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/107827\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media\/111744"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media?parent=107827"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=107827"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=107827"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}