Advancing Windows driver security: Removing trust for the cross-signed driver program
Microsoft announces the removal of trust for all kernel drivers signed by the deprecated cross-signed root program, enhancing Windows security by enforcing that only drivers signed through the Windows Hardware Compatibility Program (WHCP) are trusted by default. This change will take effect with the April 2026 Windows update for Windows 11 versions 24H2, 25H2, 26H1, and Windows Server 2025, aiming to reduce attack surfaces while maintaining compatibility for essential cross-signed drivers through an allow list.
Repeated prompt "Some information has changed" when reconnecting to mobile hotspot
Problem Description When attempting to reconnect Windows 11 to a personal mobile hotspot, the connection frequently fails to connect automatically. Instead, Windows displays the following prompt: "Some information has changed since the last time you connected. We need additional information to complete the connection." (自上次连接后，某些信息已更改。我们还需要一些信息才能完成连接。) The system forces re-entering the Wi-Fi security key every time, even though the SSID, password, and security type on the phone have not changed. Steps to Reproduce Turn on the personal mobile hotspot on the smartphone (WPA3-Personal). Connect the Windows PC to the hotspot, check "Connect", and verify successful connection. Disconnect or disable the mobile hotspot. Turn on the hotspot again later and try to reconnect from Windows. Windows fails the handshake and displays the "information has changed" prompt requiring manual password entry. Observations & Potential Causes Forgetting the network via `Settings > Network & internet > Wi-Fi > Manage known networks` temporarily resolves the issue for one session, but it recurs on subsequent reconnections. Device & OS Environment OS Version: Windows 11 Insider Preview (Build 26340.9577) Network Adapter: [Intel Wi-Fi 6E AX210 160MHz] Hotspot Device: Android 16 Smartphone Hotspot WPA3-Personal 5GHz
File History problems after installing KB5124008, KB5126052,KB5126146, KB5122878, and KB890830
This morning, I ran Windows Update on two Windows 10/11 computers, but the file history feature stopped working completely after the update. Previously, after updating KB5120249 and KB5101684, files could still be backed up to the D: drive normally. The "Last Backup" time in "File History" is not updating correctly. Newly created or saved Word documents, pictures, videos, etc., still show "No previous version available" in "Content → Previous Versions". No folders were corrected; their dates are automatically updated. After running Windows Update again today, the file history feature stopped working on both computers. The File History panel pops up but cannot be used, prompting for a hard drive connection. (The hard drive is connected and I've confirmed it can read and write.) resulting in an "InconsistentState" entry in C:\Users\User\AppData\Local\Microsoft\Windows\FileHistory\Configuration. I'm very angry. If Microsoft doesn't address this, I'll keep complaining. If anyone else has encountered the same situation, please leave a comment below. You can also check Microsoft Q&A or the Microsoft Community Hub. The five updates installed are: September 8, 2026—KB5122878 (OS Builds 19045.7725 and 19044.7725) September 8, 2026-KB5126146 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 22H2 2026-09 Security Update (KB5124008) (26200.9445) 2026-09 .NET Framework Security Update (KB5126052) Windows Malicious Software Removal Tool x64 - v5.145 (KB890830) Deleting the %LocalAppData%\Microsoft\Windows\FileHistory folder also failed. Furthermore, "File History" itself is not listed in Microsoft's "Deprecated Features List." While other backup features suggest that Microsoft has no plans to discontinue it. Microsoft is going to pretend it doesn't exist. These worked normally before the update but stopped working afterward. This is to inform other users experiencing the same problem.
Why Metro design should make a grand return
Metro UI wasn’t just a design language. It was a declaration. It respected motion, space, clarity, and user autonomy. It gave us live tiles that pulsed with relevance, panoramic pivots that guided flow, semantic zoom that revealed structure, and full-screen hubs that anchored experience. It was unapologetically modern, minimal, and meaningful. Then came the drift. Fluent UI buried Metro under acrylic, chrome, and overlays. It softened the edges, blurred the motion, and diluted the clarity. What was once a bold interface became ornamental. Metro was never about decoration—it was about discipline. Im still using Metro UI in my projects, not because I need too, because i like how it looks, but you created fluent design, that ruined it all. Microsoft, you knew Metro was good. You launched it with pride. You made it the face of Windows Phone, Zune, Xbox, and Windows 8. You called it “authentically digital.” You were right. So stop burying it. Stop apologizing for it. Stop pretending Fluent is a replacement. It’s not. Bring back Metro UI: As a first-class design option With full support for live tiles, semantic zoom, and panoramic navigation Without overlays, blur, or ornamental drift Not as nostalgia. As correction. Metro was clarity. Metro was discipline. Metro was good. Let it speak again.
