-
Posts
-
By Usama Jawad96 · Posted
Microsoft: Windows 11 24H2 is our most reliable version of Windows yet by Usama Jawad A little while ago, Microsoft released a major, but optional, feature update for Windows 11, version 24H2 in the form of KB5062660. It brings agentic search in settings, Recall for customers in the European Economic Area (EEA), new Click to Do actions, and more. Alongside, it also announced some changes to the operating system, powered by the Windows Resiliency Initiative. There are two enhancements in tow for the latest Windows 11 build. The first is Quick Machine Recovery which leverages the always-available Windows Recovery Environment (WinRE) to detect, diagnose, and fix critical issues encountered during boot time. Then, fixes are delivered through Windows Update and applied, reducing the overall downtime and the dependency on IT teams. The idea behind Quick Machine Recovery is to have a system which allows devices encountering boot failures to recover gracefully from their error state with minimal disruption, while also offering granular controls for IT admins. IT personnel have the ability to disable this feature altogether or use it to manage the self-healing mechanism, as well as scan and reboot intervals. The feature is enabled by default in Windows 11 Home, but disabled in Pro, Education, and Enterprise SKUs. IT admins have the ability to enable it through Intune or Policy configuration service provider (CSP). In terms of what's next for Quick Machine Recovery, Microsoft will be focusing on support for Windows Server, more connectivity options, and enhanced IT admins tools. In addition, the latest update to Windows 11 also packs the new BSOD, which should now be referred to as the Black Screen of Death. We have talked about this in detail before, but Microsoft has emphasized that this is more than a simple aesthetic redesign. The new BSOD is made with user experience in mind so that it is less visually disruptive, while still providing critical troubleshooting information (such as a hexcode) in a concise manner. Microsoft says that it has improved crash dump collection in Windows 11, version 24H2 to the point that customers now spend 2 seconds on this screen rather than 40. All of this feeds into Microsoft's narrative that explicitly says that Windows 11, version 24H2 is its most reliable version of Windows yet. It notes that unexpected failure rates which trigger BSOD have dropped by 24%, compared to Windows 11, version 22H2. Interestingly, it has not made a comparison to version 23H2, which suggests that the difference compared to last year is probably negligible - or at least not enough to boast about. -
By Sladen · Posted
Quick Machine Recovery was off by default on my install. -
By Usama Jawad96 · Posted
GitHub customers rejoice as Command Palette deprecation is delayed by Usama Jawad GitHub Command Palette was announced back in 2021, and has been in preview ever since. For those unaware, this capability allows you to launch a search bar UX through the Ctrl + K shortcut, which offers you suggestions based on your current context. So you can quickly clone repositories, edit pull requests (PRs), and more directly through your keyboard, without navigating through cumbersome nested menus. Almost a week ago, GitHub announced that it is deprecating Command Palette due to low usage and popularity. This led to major backlash from the development community who criticized the move, noting that a preview feature that is disabled by default will obviously have low usage. Many customers cited its usefulness, noting that Command Palette has no alternative that is as powerful, and it's unfair for the company to remove a product due to low adoption, especially since it had not been marketed. Now, GitHub has decided to reverse course on its earlier decision (thanks, The Register) and delayed the deprecation of Command Palette indefinitely. It has updated its previous blog post and shared an identical announcement on a dedicated GitHub thread to indicate that after listening to customer feedback and specialized use-cases, it has realized that its own usage metrics do not reflect the current popularity of Command Palette. It understands that the tool is critical in many workflows and that it needs to re-evaluate its overall approach to navigation. During this period of assessment, GitHub Command Palette will continue to be available, much to the joy of GitHub customers, who have responded very positively to the thread. That said, it is important to note that GitHub's wording is a bit vague, and it doesn't concretely say that Command Palette is here to stay. It's possible that the company re-evaluates its usage metrics sometime in the future and reaches the same conclusion that it did last week. -
By kiddingguy · Posted
I'd say "no thank you" to Recall. Let's turn it off as quicly as possible when installed. And Microsoft -please- don't let a "bug" re-install/re-configure it again. -
By kiddingguy · Posted
Let's just wait until Patch Tuesday and have most of the bugs on this KB/download be taken care of & ironed out.
-
-
Recent Achievements
-
SmileWorks Dental earned a badge
Week One Done
-
vZeroG went up a rank
Community Regular
-
Snake Doc earned a badge
Collaborator
-
Snake Doc earned a badge
Week One Done
-
Johnny Mrkvička earned a badge
One Month Later
-
-
Popular Contributors
-
Tell a friend
Recommended Posts