file corruption Archives

Winsage

November 18, 2025

Microsoft fixes Windows 10 update flaw

Jack Bicer, the director of vulnerability research at Action1, advises IT leaders to ensure the latest servicing stack update (SSU) is installed before reapplying a patch after Microsoft’s patch release on November 17. He recommends troubleshooting steps for system file corruption, including: 1. Temporarily disabling non-Microsoft services and startup applications through a Clean Boot. 2. Manually installing the update by downloading the .msu package for KB5068781 from the Microsoft Update Catalog and using the command wusa.exe .msu /quiet /norestart. 3. Verifying the build number with the winver command, targeting build numbers 19045.6575 (22H2) or 19044.6575 (21H2).

Winsage

November 15, 2025

I’m finally switching to Windows 11, but not for the reason you think

Approximately 40% of Windows 10 users have upgraded to Windows 11, driven by the end of support for Windows 10 on October 14 and various practical considerations. The author upgraded to Windows 11 after acquiring an OLED monitor, as Windows 11 handles HDR significantly better than Windows 10. The introduction of Auto HDR in Windows 11 enhances the visual appeal of older games, while the HDR calibration app is incompatible with Windows 10. The author also faced persistent issues with their Windows 10 installation, such as file corruption and poor microphone quality, which prompted the switch. The end of critical security updates for Windows 10 further influenced the decision to upgrade, making Windows 11 the necessary choice to ensure better performance and security.

Winsage

October 28, 2025

Windows 11 Will Start Memory Scans After BSOD to Prevent Future Issues

The latest update for Windows 11 introduces a memory diagnostic feature aimed at improving system reliability and addressing blue screen of death (BSOD) issues. Users will receive a notification suggesting a memory scan after a bug check, which can be scheduled to run during the next reboot. The scan takes about five minutes and notifies users of any memory issues found post-reboot. This feature is currently available to Windows Insiders in the Dev and Beta channels through specific Insider Preview Builds but does not function on Arm64 PCs, machines with Administrator Protection, or BitLocker setups without Secure Boot. The feature simplifies the troubleshooting process and helps prevent severe complications like program crashes or system freezes.

Winsage

September 9, 2025

This Windows 11 repair trick fixes nearly every Windows problem

File corruption is a common issue in computing that can lead to problems such as the Blue Screen of Death (BSOD) and slowdowns. Windows provides built-in tools like System File Checker (SFC) and Deployment Image Servicing and Management (DISM) to address these issues, which can function offline. Users are advised to download fresh Windows installation files as ISO images for Windows 10 and 11 for troubleshooting. DISM can assess and repair Windows image files using a live USB, with a specific command format to run it. After using DISM, it is recommended to run SFC at least twice to ensure all issues are resolved. DISM can also service and prepare .wim or .vhd/vhdx format Windows images for virtual environments. Using DISM and SFC offline can restore computer functionality more efficiently than a complete reinstallation.

Winsage

September 2, 2025

Microsoft denies allegations of recent Windows security update corrupting PC storage: ‘After thorough investigation…’ – The Times of India

Microsoft stated that the Windows 11 24H2 security update (KB5063878) is not linked to reported failures of SSDs and HDDs. After investigating user complaints about data corruption and drive malfunctions, Microsoft found no connection between the update and hard drive failures. Their telemetry data and internal testing showed no increase in disk failures or file corruption since the update's release. Japanese users initially reported SSD failures during intensive write operations on drives over 60% full. Similar issues were reported with various storage devices, including Corsair Force MP600, Maxio SSDs, SanDisk Extreme Pro, Kioxia Exceria Plus G4, Kioxia M.2, and drives with InnoGrit and Phison controllers. Some affected drives regained functionality after a restart, while others remained inaccessible. Phison acknowledged the situation and is working with Microsoft to resolve the issue. Users with drives over 60% capacity are advised to avoid downloading, copying, or writing large files until the cause is identified.

Winsage

August 30, 2025

Microsoft swats down reports of SSD failures in Windows — company says recent update didn’t cause storage failures

Microsoft has clarified that Windows update KB5063878 is not linked to reported solid-state drive (SSD) failures. An investigation found no connection between the update and the types of hard drive failures mentioned on social media. Testing involving 21 different SSDs indicated that various brands were affected, but many drives recovered after a system restart, except for the Western Digital SA510 2TB model. Phison could not replicate the issue after extensive testing and recommends installing heatsinks on SSDs for heavy storage tasks. Microsoft reported no increase in disk failure or file corruption during internal assessments. Despite this, some users on social media claim their drives failed after installing the update. Users are advised to monitor their SSDs and report any issues to both the SSD manufacturer and Microsoft.

Winsage

August 20, 2025

New Windows 11 update may corrupt your SSD

The Windows 11 KB5063878 update, released on August 12th, has raised concerns about potential corruption issues affecting Solid State Drives (SSDs), particularly in Japan. Users have reported that files and drives became inaccessible after installing the update. The update was intended to reset device certifications for Windows Secure Boot, but user experiences indicate that substantial data writing to the drive can lead to it disappearing from the operating system. A reboot may result in Windows being unable to read the partition, and the SSD’s SMART features may become non-functional. A Japanese PC enthusiast noted that the likelihood of system file corruption increases when approximately 50GB of data is written to a drive that is at least 60% full. Specific SSD brands, including Corsair, Phison, Fikwot, and Maxio, have been highlighted as potentially more vulnerable. It has been suggested that the update may introduce a bug affecting long sequential writes, causing the operating system to lose track of the drive. Users are advised to back up data and consider pausing updates if they have not yet installed KB5063878, while those who have should keep updates enabled to receive fixes promptly.

Winsage

August 19, 2025

A Windows 11 update bug is breaking SSDs – here’s what you can do to prevent it

Microsoft's August update KB5063878 for Windows 11 has raised concerns among users regarding SSD storage devices, with reports indicating that certain SSDs may become undetectable by the system, potentially leading to file corruption. Initial reports suggest the issue occurs when SSDs are about 60% full after writing around 50GB of data, particularly affecting SSDs with Phison NAND controllers. Affected users have reported similar experiences on social media and Reddit, with indications that some HDDs may also be impacted. Microsoft has not confirmed any flaws associated with the update, and users are advised to consider postponing its installation. Additionally, some users faced error codes during installation, particularly via Windows Server Update Services, which Microsoft has since resolved. There are also reports of an error related to the "Microsoft Pluton Cryptographic Provider," which does not affect current functionality. Microsoft is encouraging Windows 10 users to upgrade to Windows 11 before the end of support in mid-October and has warned about the expiration of Windows Secure Boot certificates in June 2026.

Winsage

August 18, 2025

Latest Windows update is borking storage drives for some users

Recent updates for Windows 11 and Windows 10 have caused significant stability issues linked to a bug in the Microsoft Defender update, making some solid-state drives (SSDs) and hard drives (HDDs) unreadable. The issue was first reported by a user on Twitter and affects drives that contain the Windows operating system, leading to potential system failures. The problem is particularly prevalent in the latest 24H2 versions of Windows 11 and several updates for Windows 10. It appears to be associated with certain drives using a specific NAND controller from Phison. The bug is triggered during heavy write sessions to NVMe SSDs and HDDs, especially when writing or backing up data exceeding 50 gigabytes. The range of affected drive models is unclear, and users are uncertain about potential solutions, including firmware updates.

Winsage

August 18, 2025

Microsoft Windows 11 24H2 Update May Cause SSD Failures

Microsoft released a Defender security update during the August 2025 Patch Tuesday, targeting the Lumma stealer and other malware, which included the Windows 11 24H2 cumulative package (KB5063878). Early installations faced an error code, 0x80240069. Testing revealed that some solid-state drives (SSDs) became inaccessible and displayed unreadable SMART telemetry after sustained sequential writes of about 50 GB. A Japanese tester, NichePCGamer, documented failures in 21 different drives during tests involving large file transfers, particularly when controller utilization exceeded 60%. Failures were noted in several Phison-based NVMe models and other drives, with symptoms often reappearing after a reboot. Users are advised to back up data and avoid lengthy transfers on systems updated to KB5063878 while investigations continue.