All I had to do was uninstall (or roll-back) the 22621.1631 update. This restored my system back to 22621.1555 and enabled Win+X functionality. I am also starting to lose interest in the mid month update-previews. My systems run quite well with 22621.1555.
Since which version, MSFT change the default action for 'Use PrntScrn button for snip' is on (earlier it was off)? I recently made a clean installation of 22623.1555 & that toggle is still off there. I am sure I've read that changelog in a recent builder but can't exactly remember that exact release so asking. Is that a 22624 branch-specific feature? or newer LCU 1610/1631 is required for that
offtopic but 22623.1555 is very incorrect build for clean install 1. 1555 is for Retail channel only, so it should be 22621.1555 2. beta LCUs before 1555 were on 22624 and not 22623, 22623 is done and you should be on 22624.1546 or 22624.1610 the print screen key was changed in 22624.1546 build on Beta channel, you can get it on Beta channel build 22624.1610
Forgot to mention in my earlier post, I did the testing on VM, my actual H/W is running on 22621.1555 I wanna check the new default toggle /option for PrntScr, so for now, that's available in 22624 beta branch, gonna wait for backporting. Thanks.
i can confirm alt-printscreen works after disabling toggle, but had to re install onedrive to get it to save screenshots
Alt-PrintScreen works perfectly for me without having to install OneDrive, you paste it into Word or Power Point and since there are gures on the hard drive as xxx.jpg, Save image as
Sorry but you posted this "I can confirm Alt-PrintScreen works after disabling Toggle, but I had to reinstall OneDrive for it to save screenshots" and now you change and say this "I wanted the Save Screenshot feature to OneDrive that's all"
i disabled new toggle to get old functionality back, one drive was broke, cant be any clearer than that i meant save screenshots to onedrive, anyone with common sense can work that out.
I have deactivated Printing, defenfer I do not install it, I have removed it from installation (NTlite) ... and many more things and it works fine for me without having to re-install OneDrive and I do not have so many problems and I have several PCs with a different compilation on each one and without failures like the ones you mention
have you done any tweaking or modification to the OS usually when people start shopping or removing services later on they run into issues like this where other services stop running.
Yes, I have done some tweaks with 3rd party apps like Explorer Patcher, open-shell-menu, 8gadgetpack, Stardock Windowblinds, and Winaero. But none of these tweaking programs affected Win+X when I updated to 1485 and 1555. It just happened with 1483 and 1631. So Win+X is not a consistent problem. At first, I thought it might be open-shell-menu, but now I'm thinking it might be Stardock Windowblinds or Explorer Patcher. The only way to know is to remove them all and reinstall 1631. EDIT: After further experimentation, I discovered that Explorer Patcher v22621.1413.54.5 is no longer compatible with Windows 11 22621.1631. When Explorer Patcher is uninstalled, the Win+X functionality works fine in 22621.1631. However, one is stuck with a Windows 11 style taskbar.
fileexplorer.exe unknow error when setting minimal boot safemode with msconfig, error appears when trying to log in, shift-alt delete to cancel error before you can log in, but everything is write protected Would never of found this error as i dont use this method, it was recommended to do it this way to stop matdebug.logs from accumulating in temp folder,
like staying on public release so I fresh install 22621.1555 and did notice it is snappy and no NMVe SDD slow down
I am trying to perform the following upgrade of the live Win11 OS using W10UI and I am not sure about the best way to proceed: OS upgrade: 22000.1696 => 22621.1555 .NET upgrade: 4.8 => 4.8.1 It looks like .NET 4.8 is no longer supported with builds 22621 (there are no 4.8 updates available in MS Update Catalog) so I have no choice but to upgrade both the OS and .NET. Can all the updates listed below be processed in one swoop or do you need to run W10UI twice? ======================================================= kb5022360 - Feature Upgrade (21H2 to 22H2) kb5025239 - SSU 22621.1550 + LCU 22621.1555 kb5011048 - NDP481 Base kb5025182 - NDP35-481 CU Preview // ignored kb5012170 - Secure Boot DBX (already present in 22000.1696) kb5019178 - Intel CPU Microcode (not important) kb5026039 - OOBE (not applicable to live OS) ======================================================= Update/Edit: kb5022360 is not a "Feature Upgrade" and will not work. Feature Upgrade using only KB files and W10UI is not possible. Two working solutions are provided in post #4717 below.