XAML Archives

Winsage

July 7, 2026

Windows 11 24H2 and 25H2 Issue Causes Black Screen, Start Menu Failure, and Taskbar Crashes

Microsoft has addressed critical user interface failures affecting Windows 11 versions 24H2 and 25H2 in enterprise environments, documented under update advisory KB5072911. These issues arise from cumulative updates released after July 2025, including KB5062553 and KB5065789, primarily impacting enterprise-managed systems and virtualized environments. Users may experience black screens, unresponsive Start menus, and taskbar failures following updates, particularly in non-persistent environments like Virtual Desktop Infrastructure (VDI). Core components such as Explorer.exe and XAML-dependent applications may fail to initialize or crash due to a timing issue in the update process, where required application packages are not properly registered. Microsoft has released updates starting June 23, 2026, under KB5095093 to address these issues and recommends temporary workarounds for affected systems, including manual registration of missing packages and deploying logon scripts in non-persistent environments. Organizations are encouraged to install the latest updates and review their update procedures to prevent future disruptions.

Winsage

July 6, 2026

Microsoft finally fixes bug that broke all major Windows 11 core UI components on some PCs

Microsoft introduced an update to the out-of-box experience (OOBE) for Windows 11, identified as KB5095189, targeting versions 25H2 and 24H2. This update includes enhancements and fixes, coinciding with additional updates KB5102558 and KB5095615 from the June C-release preview update (KB5095093). A major fix addresses a storage issue caused by the Capability Access Manager process, which was consuming significant disk space. Another fix resolves a malfunction affecting Shell components, impacting the Start menu, Search bar, Settings, Taskbar, and File Explorer, primarily on provisioned PCs due to compatibility issues with XAML. This bug had been present since July 2025 and is being resolved with updates released starting June 23, 2026 (KB5095093), with full deployment expected in the following month. Users are advised to use previous workarounds until the fix is fully available. Further details can be found in support article KB5072911 on Microsoft's website.

Winsage

June 24, 2026

A bunch of bugs that broke PowerToys have been squashed

PowerToys has updated to version 0.100.1, fixing critical bugs from version 0.100.0 that affected core features. - Color Picker: Resolved a bug causing the main window to appear within the zoomed-in picker view. - Command Palette: Corrected initialization of Run history in Ahead-of-Time builds, fixed "???" display in Performance Monitor after restart, adjusted Hibernate command to use the Sleep icon, and limited "pin to dock" dialog to enabled displays. - Keyboard Manager: Addressed remapped modifier keys being delivered as system-key events. - Power Display: Fixed monitor power-state control not waking monitors from standby and resolved display detection and brightness control issues on dual-GPU laptops. - PowerToys Run: Improved discovery of Visual Studio Code workspaces. - Quick Access: Fixed crashes in the Quick Access flyout due to unhandled XAML exceptions. - Shortcut Guide: Resolved a crash in the sidebar navigation, corrected number-key rendering in shortcut manifests, and updated bundled manifests for consistent rendering. - ZoomIt: Fixed a race condition in audio initialization for video recording.

Winsage

June 4, 2026

Microsoft is rewriting Windows 11 shell in native code, killing the web slop slowing your PC

Microsoft is enhancing Windows 11 by reducing reliance on web-based components, which have caused performance issues. The user interface framework WinUI will now be referred to simply as "WinUI," indicating no plans for a WinUI 4, to reassure developers. Microsoft is integrating WinUI into the Windows 11 shell more rapidly, moving away from web components. A specialized team is focused on creating "100% native" Windows applications, starting with an overhaul of the Start menu from React Native to WinUI components. Performance, memory optimization, and quality control are top priorities for the WinUI team. A new system compositor is being introduced to improve UI performance, and enterprise-focused DataGrid and Charting controls are being added to WinUI. Microsoft is expanding open-source development for WinUI, allowing public testing and contributions. Migration support between WinForms and WinUI is being enhanced for legacy applications. An experimental project called Microsoft UI Reactor is introduced to simplify native application development using C#. This shift towards native development aims to improve performance and efficiency for all Windows users.

Winsage

May 29, 2026

Microsoft admits modern Windows 11 apps actually resize worse than the old ones, fix coming this summer

Microsoft is working on a solution to address the black tearing issue during window resizing in WinUI 3 applications on Windows 11, with a rollout expected to begin this summer. March Rogers, Microsoft’s Partner Director of Design, confirmed that the Windows team is testing smooth resizing code on native inbox applications before extending the update to the Windows App SDK. The transition to WinUI 3 aims to replace inefficient web applications and improve user experience, with significant components like the Start menu and system-level dialog boxes being upgraded to WinUI 3. Additionally, Microsoft has launched Windows App SDK 2.0 to encourage third-party developers to adopt native app development, addressing previous issues such as bugs and lack of visual features.

Winsage

May 29, 2026

Microsoft admits modern Windows 11 apps actually resize worse than the old ones, fix coming this summer

Microsoft is working to improve the user experience of WinUI 3 applications by addressing the issue of black tearing during window resizing. A fix is planned to be rolled out over the summer, as confirmed by March Rogers, Microsoft’s Partner Director of Design. Currently, WinUI 3 apps exhibit noticeable tearing during resizing, unlike UWP applications that resize smoothly. The Windows team is testing the smooth resizing code on native inbox apps before its broader rollout. Additionally, Microsoft is transitioning away from web-based architectures to enhance native app development, with plans to migrate the Windows 11 Start menu and system-level dialog boxes to WinUI 3. The company aims to rebuild trust with third-party developers through the Windows App SDK 2.0, which introduces new features and simplifies the development process for native applications.

AppWizard

May 27, 2026

MAUI is Getting Android Material 3 Support in .NET 10

.NET MAUI is introducing Material 3 support for Android applications, allowing developers to integrate the latest design aesthetics with a single MSBuild property. Material 3, also known as Material You, includes features such as dynamic color schemes, refreshed control shapes, and enhanced customization. Developers currently using MAUI have been working with Material Design 2, but with the upcoming release of .NET 10 in November, they can easily upgrade to Material 3 by updating their app projects and adding a few lines of XAML code. Microsoft has provided a sample Material 3-styled app that demonstrates the new design elements across various controls, including SearchBar, Entry, DatePicker, Picker, Slider, ProgressBar, RadioButton, CheckBox, Switch, Button, and ImageButton. This sample supports both dark and light themes. Microsoft plans to expand Material 3 support to additional controls and aims to make it the default styling for MAUI applications.

Winsage

May 7, 2026

Microsoft admits Windows 11 is still built on 90s-era Win32, and no one saw it coming

Users engage with the Win32 API when right-clicking files or launching desktop applications in Windows 11, a technology that has persisted since Windows 95. Microsoft’s Chief Technology Officer, Mark Russinovich, noted that the longevity of Win32 was unexpected, as it was not part of the company's original vision for the future. Despite attempts to replace Win32 over the past two decades, many users still have more Win32 applications than modern alternatives. Microsoft has introduced several frameworks to replace Win32, including MFC, WinForms, WPF, WinRT, and UWP, but none have fully succeeded. Developers have shown a preference for RAM-intensive web applications over native ones due to concerns about the stability of Microsoft's frameworks. Microsoft has introduced WebView2 to embed web technologies in desktop applications, leading to increased memory usage. In response to user needs, Microsoft is shifting back to native applications with WinUI 3, aiming to modernize Windows 11 while retaining access to Win32 infrastructure. The company is gradually replacing legacy Win32 UI elements with WinUI 3 components, improving performance and user experience.

Winsage

May 6, 2026

Microsoft confirms Windows 11’s File Explorer is sluggish, and preloading isn’t the only fix coming

Microsoft has increased its public relations efforts to highlight enhancements in Windows 11, announcing performance and reliability fixes following an update from Marcus Ash, the Windows Insider lead. Tali Roth, Microsoft’s Head of Product for Windows Shell, addressed user dissatisfaction with the preloading of File Explorer, which is seen as a resource-intensive solution that does not resolve underlying performance issues. Critics argue that while preloading improves initial launch times, it consumes an additional ~35MB of RAM and does not eliminate delays in folder navigation and other functions. In response to the criticism, Roth explained that Microsoft employs a multi-faceted strategy for improving File Explorer, which includes targeted optimizations to the launch sequence, removing unnecessary processes, and addressing deeper foundational issues. These improvements are being rolled out incrementally, with recent Insider builds showcasing enhancements like reduced visual glitches and a modernized Properties dialog.

Winsage

May 4, 2026

Windows 11’s Windows 95-era File Explorer Properties dialog is getting replaced with modern version and dark mode

Microsoft is replacing the legacy File Explorer Properties dialog box in Windows 11 with a modern version powered by WinUI 3. This change aims to improve the performance and reliability of Windows 11. The current Properties dialog does not support dark mode, which has been an issue for users. Recent findings from Windows 11 Insider builds indicate that Microsoft is actively developing a new file properties dialog. Strings for “DeletedFileProperties” have been discovered, suggesting the old dialog will be replaced. Microsoft is also modernizing outdated Windows 8 UI elements within Windows 11. The introduction of the WinUI 3 properties dialog is expected to enhance File Explorer's performance by streamlining its hybrid codebase. Users can anticipate gradual updates throughout 2026, with a rollout to the Experimental channel expected later this year.