Windows 11 25H2 monthly cumulative updates repeatedly break my Storage Spaces volume
On Windows 11 25H2, every monthly cumulative update since 26200.8737 makes my Storage Spaces parity volume fail to mount - it shows as RAW / "corrupt and unreadable." The pool and disks are healthy and the data is intact (read-only chkdsk finds zero problems), and uninstalling the update restores the volume every time. Happened in July (KB5100998 / KB5121767) and again today (KB5120998). I'm now stuck on build 26200.8737 because I can't take any newer update without losing the drive. Feedback Hub report got no traction; MS support just pointed me back to Feedback Hub In July the corruption was reported in the NTFS reparse index, and I had ~100k OneDrive Files-On-Demand placeholders on that volume. I thought I had moved OneDrive off it, but the files remain. Im in the process of moving/deleting all files related to OneDrive off the Storage Space volume and will report back. Anyone else seeing this, and is there a permanent fix?
Why hasn't Microsoft fixed the issue with the July update causing problem with file history logging?
"I've been feeling really upset these past few days. Ever since my laptop installed update KB5101684 on July 29, File History has been malfunctioning. While files successfully back up to the D drive, the backup timestamp does not update. Furthermore, newly created or saved files (like Word documents, images, and videos) still show 'No previous versions available' under Properties → Previous Versions, and folder modification timestamps are unexpectedly altered even when no actual data inside the folders has changed. Even more concerning, my Windows 10 22H2 desktop started experiencing similar File History sync issues after installing KB5120249 on August 12, 2026. I have already chatted with live support; they said they would investigate my issue, but who knows how long that will take, and they even told me to reinstall the OS. I refuse to reinstall it—especially since I don't even know how to fix it—and I'm worried it will never get fixed. As a global operating system giant, please immediately have your development team investigate the File History and timestamp logic issues in these updates, and roll out a hotfix as soon as possible instead of just telling consumers to reinstall to dodge the problem. Please face up to your software quality defects and provide a concrete fix!" If you're experiencing the same issue as me, could you please refer my question to Microsoft? I would greatly appreciate it.
Clearing the download and install list
I have a new install of windows 11 home, and manually installed drivers and such before connecting to the Internet. I also disabled drivers in Windows update. Windows update still wants to replace my 2 month old Ethernet driver with one from 2021. How do I get rid of this, and why is it pulling driver updates when that setting has been disabled? I've tried stopping services and renaming the two folders and the list of updates to download is still intact. The wusahowhide tool says nothing can be hidden. I had to reinstall because windows messed up my drivers while they were disabled. How to I actually stop it from thinking it knows best when it obviously doesn't and get rid of this download?Title: Severe Font Rendering Issue After Installing KB5122385 and KB5120998 on Windows 11 25H2
Hello Microsoft Team, I would like to report a significant font rendering issue that appeared immediately after installing Windows updates KB5122385 and KB5120998. Issue Description After installing these updates, text rendering became noticeably degraded across multiple web browsers, including: Google Chrome Microsoft Edge Mozilla Firefox The issue included: Blurry text rendering. Distorted fonts. Reduced text sharpness and clarity. Overall degradation of readability and user experience. System Information Operating System: Windows 11 Version 25H2 Processor: Intel Core i9-13900HK Memory: 32 GB RAM Graphics Adapter: Intel Iris Xe Graphics Graphics Driver Version: 32.0.101.7088 Troubleshooting Performed I spent a considerable amount of time diagnosing the issue and tested several common solutions, including: Resetting Windows font settings to default. Reconfiguring and recalibrating ClearType. Disabling Hardware Acceleration in the affected browsers. Restarting the system multiple times. Reviewing display and graphics-related settings. None of these actions resolved the problem. Verified Resolution After extensive testing, I determined that the only solution that completely restored normal font rendering was: Uninstalling KB5122385. Uninstalling KB5120998. Restarting Windows. Immediately after removing these updates, font rendering in Chrome, Edge, and Firefox returned to normal. Text became sharp, clear, and properly rendered again. Request for Investigation Based on my testing, there may be a compatibility issue within Windows components responsible for font rendering, text display, graphics handling, or related system functions introduced by these updates. Because the issue affects multiple browsers, including Firefox, it does not appear to be limited to Chromium-based browsers and may be related to Windows itself. I recommend that the Windows engineering team investigate this issue, as other users may be experiencing: Blurry text. Distorted fonts. Reduced display quality in browsers. The need to remove Windows updates as a temporary workaround. The issue was consistently reproducible on my system, and uninstalling the updates was the only action that restored normal behavior. Thank you for your time and attention. I hope this report helps identify and resolve the root cause of the problem. Best regards, Hossam Soliman
New hard drives not found when installing window 11. Tried everything!
I have a computer that has no hard drives in it. So i bought a new Kingston NVMe M.2 disk. Installed it and I found the disk in BIOS. I have a bootable USB made with the mediacreator from microsoft that i know works because i used it two days ago on my son's new computer. I boot up with the windows 11 usb and when i come to select disk there is no disks. I read that i need to disable VMD in the bios and i do. Still no disks. It say i need to load drivers for Intel Rapid Storage Technology (RST). I found it from the manufacturer's drivers page. I press load drivers and I can't find anything. Nothing shows up in the list. No drivers! I read that i need to download SetupRST.exe from Intel and extract the files with powershell. I need to add the .inf, .cat, .sys files on the windows usb. I do, and nothing shows up when load drivers. And disks don't show up. I tried installing a second Intel ssd drive with sata. I see both the disks in BIOS but not with the windows 11 installer. I have no idea what to do now. It's an older computer from 2023 so I can't take it back to the shop for free help. I have installed windows hundreds of times and never run into this many problems. Its so strange Sorry for my bad English, but I hope i described my problem correctly Specs Acer Predator Orio 3000 Intel Core i5 - 13400F PO3-650 Kingston NV3 PCIe 4.0 NVMe M.2 500GBFile History Broken After KB5101684 & KB5120249?
Hello everyone,(Note: I previously posted this issue on several community channels and feedback hubs, but only received a few hundred views and a few responses. Because this issue severely impacts daily backups on multiple machines, and there has been no clear official response, I am summarizing and refining the technical details here to help other IT users and track the scope of this issue.) This is not spam. Others also reported an anomaly in the file history log when updating security patch KB5101650 on July 14th. I am tracking a file history error that exists on two completely different hardware configurations. Both machines were running perfectly before installing these updates, requiring no manual folder redirection or configuration changes. Affected Environments: Laptop: Windows 11 25H2 → KB5101684 (Installed July 29, 2026) Desktop: Windows 10 22H2 → KB5120249 (Installed August 12, 2026) Observed Symptoms: Copying physical files to the backup drive (D drive) still works normally. The Last Backup timestamp in File History in Control Panel remains unchanged. Newly created files (Word documents, images, videos) consistently display No previous version available under Properties. The automatic backup correction dates for some unbacked-up files and folders (desktop, favorites) have also changed. Temporary Workaround: To force a logger restore: Open Control Panel > File History > Select Choose Drive in the left-hand menu. Reselect your existing backup drive and save. If you encounter the exact same file history failure on Windows 10 or 11, click I'm having this problem too and leave your system version information. Collective data is our best tool for pushing Microsoft engineering to release official patches.Are file history records still in use?Protest and appeals against Microsoft's technical support team
KB5101684 and KB5120249 both state that this update fixes an issue that affects File History automatic backups to network shares using Server Message Block (SMB). Backups did not work because Windows displayed a false invalid credentials error when connecting to SMB shares. Fixing this issue leads to the following problems. File History Issue Symptoms Affected Systems: Windows 11 25H2 (after installing KB5101684) and Windows 10 22H2 (after installing KB5120249). Key Anomalies: Data successfully backs up to the D: drive, but the Last backup timestamp in the Control Panel fails to update. Newly created or edited files (such as Word documents, images, and videos) display There are no previous versions available under Properties → Previous Versions. Temporary Workaround: Users must manually navigate to Control Panel → File History → Select drive, re-select, and confirm the D: drive to temporarily restore normal functionality. Before updating these two, I never deleted system folders, login files, or messed with settings. Protest and Appeal to the Microsoft Technical Support and Development Teams To the Microsoft Support and Engineering Teams: As long-time, loyal users who heavily rely on built-in Windows backup mechanisms, we are profoundly disappointed and frustrated that recent updates—specifically KB5101684 for Windows 11 and KB5120249 for Windows 10—have broken the File History feature, freezing backup timestamps and rendering Previous Version completely useless. File History is far from being an obsolete or unused feature. For countless professionals, students, and everyday users who prefer or require local data protection as a critical safeguard against file corruption, accidental deletion, and ransomware, this is an essential line of defense. However, after installing official cumulative updates, two entirely independent computers—neither of which had altered system registries or deleted system folders—simultaneously suffered the exact same failure. This proves beyond a doubt that the updates introduced a regression or damaged the underlying sync mechanisms. What is even more infuriating is: A Complete Lack of Official Communication: Users facing these update-induced silent failures are left stranded in community forums without any official acknowledgment or explanation from Microsoft. Ignored Feedback: Detailed reports submitted through the Feedback Hub, complete with cross-computer diagnostic comparisons, have met with radio silence. We hereby formally demand that the Microsoft technical team: Acknowledge and Investigate Immediately: Treat the regression caused by KB5101684 and KB5120249 on File History, VSS (Volume Shadow Copy Service), or directory indexing as a high-priority bug and launch an immediate investigation. Provide a Fix and Clear Transparency: Roll out a definitive patch in the upcoming security or optional updates to resolve the frozen Last backup indicator and broken previous versions, and provide a clear public statement to affected users. If Microsoft continues to neglect this essential feature or turns a blind eye to its decline, we will have no choice but to continuously escalate this issue through all available official support channels, technical forums, and community networks until this critical bug is thoroughly investigated and resolved. Since most people use File History, if you have the same issue as me, don't worry, feel free to leave a comment.
WMIC Deprecation: Why remove it entirely instead of providing a backward-compatible stub?
I am writing to express my frustration regarding the recent removal of the Windows Management Instrumentation Command-line (`wmic`) tool from recent Windows 11 builds. Like many IT professionals, I maintain dozens of legacy batch scripts that rely on `wmic` for basic system queries (such as pulling the local date and time). Automatically removing this tool breaks decades of established scripts, causing unnecessary downtime and forcing us to rewrite code that has worked flawlessly for years. While I understand the push to modernize and transition administrators toward PowerShell and CIM cmdlets, removing the executable entirely feels like a heavy-handed approach. **A Proposed Solution:** Instead of a hard break, why couldn't Microsoft replace the legacy `wmic.exe` with a lightweight stub or alias? This stub could accept the traditional `wmic` command-line arguments, translate them, and delegate the work to the modern PowerShell/CIM equivalents under the hood. Backward compatibility has always been one of Windows' greatest strengths. Please consider adding a compatibility layer for fundamental system tools before deprecating them completely, rather than breaking the IT infrastructure that relies on them.
