Microsoft is scrambling to patch a micro swarm of bugs caused by its own security updates, including a Windows reset and recover fail error.

The issue affected some users after they installed the August 2025 security update and was patched August 19, but a hard drive corruption issue is yet to be fixed.

In an out-of-band update for the recover bug, Microsoft said it had affected devices running Windows 10 and Windows 11, versions 23H2 and 22H2, advising that those unaffected need not install the patch.

It has not yet acknowledged the bug causing data corruption and failures for some SDD and HDD drives, reportedly brought on by the KB5063878 security update and KB5062660 preview updates.

Failing drives

That issue, first raised by a PC hobbyist online, reportedly caused drives to disappear and SMART data to become unreadable after users installed the updates, with no workaround.

The user said their tests showed the errors occur on SSDs with 60% storage used during file transfers greater than 50GB, with no known way of recovering data from a corrupted partition.

See also: Windows kernel bug exploited in the wild for two years

According to reports, Microsoft is working on a fix with Phison, the manufacturer of some of the affected drives. In the mean time, users are best advised to avoid completing large downloads in one go.

In another odd twist to the tale, the Taiwanese company has warned that a document floating among its customers purporting to detail the affected controller models has been falsified.

Copilot also playing up

The embarrassing couple of days have not been helped by reports Microsoft took a year to fix a Copilot error that led to inaccurate audit logs.

According to Zack Korman, CTO at cybersecurity company Pistachio, Redmond’s flagship AI helper was able to access documents without updating the audit log.

While the problem has now been resolved, Korman found it had first been brought to the company in 2024, but only received a fix August 17 2025 after he disclosed the issue.

As users were not informed of the error, or the fix, Korman claimed it “raises serious questions about what other problems Microsoft chooses to silently sweep under the rug.”

The link has been copied!