Is there an issue with Update KB5063878?
Is there an issue with Update KB5063878?
Hi, I'm trying to figure out if the Windows updates were removed properly after uninstalling those KB files. The uninstall list still shows them, but they don't show up in the update history.
Following the detailed update by @popatim, which I hadn't previously known about, I've conducted my own investigation. Before any widespread removal of KB5063878 and KB5062660, it's crucial to grasp what factors are at risk and the circumstances that might lead to drive corruption.
According to BleepingComputer, the problem appears primarily to impact users working with extremely large files—tens of Gigabytes—or those extracting big compressed archives containing numerous substantial files, especially on drives already over 60% full. This scenario is unlikely to affect most home users.
The same source also indicates that the issue may be linked to drives equipped with Phison or InnoGrit controllers. The major manufacturers using these controllers include Corsair Force MP600, Maxio SSD, SanDisk Extreme Pro, Kioxia Exceria Plus G4, Kioxia M.2, though any device using either controller could be affected.
From the article...
The central point appears to be the handling of large files. As long as this isn't part of your routine, the reported problem shouldn't pose a significant threat. I've been using KB5063878 since August 13th and KB5062660 since July 23rd, and I haven't encountered any issues. All my data is either backed up locally or in the cloud, so I have no intention of removing these updates. Personally, I believe most home users don't need to uninstall them either.
Stay calm and continue your work.
It's astonishing now. The creator says the issue happens solely due to using the Engineer Sample Firmware from Psion.
🔗 Watch here: https://www.youtube.com/watch?v=-taUZP9F12Y
So if this is confirmed, the issue would stem from a development firmware that shouldn't have reached consumer drives at all, not from a Windows update (the update itself triggered it, but the version was never meant to be deployed on people's computers).
But jaytwocents will never admit it. He continues to blame Microsoft, insisting it was their fault—because clearly, Microsoft engineers should always ensure updates match every sample firmware version used by manufacturers for testing.
This person now lacks credibility. For months they've been insisting Microsoft is responsible for the problem, ignoring feedback, disregarding update notices, and even claiming they could reproduce the issue. They saw it as the ideal scandal to gain attention, and it succeeded. Now most people on social media believe Microsoft is at fault, though in reality, they probably had little to do with it, and the issue might have affected only a few drives—unless Phison made a significant error by releasing test firmware that was widely used.
The issue with some content creators is that they focus mainly on gaining engagement. If they reduced their video output about specific companies, I believe they would lose a significant audience. Alternatively, they might lack the necessary content to meet deadlines, leading to videos that only briefly mention details about drivers, updates, or products they dislike.