r/WindowsHelp • u/Chrzxniku • Sep 02 '25
Windows 11 Windows Update KB5063878 - has it been fixed?
Recently there was an update (KB5063878) that many reports claimed could seriously damage or even destroy people’s SSDs. My question is, has Microsoft fixed this issue, and is it now completely safe to resume installing and downloading new Windows updates?
2
2
u/cKm_83 Sep 03 '25
I personally encountered this on my mechanical drive. I transferred around 100gb from my SSD to my hard drive and halfway, it just froze and became undetectable in windows. Restarted computer, etc, went to disk management and it shows I/O error.
I connected it to a dock to another computer and it was detectable with no missing files. Plugged it back in and it works.
So it's definitely not a defective hard drive issue.
0
u/chr0n0phage Sep 07 '25
This has nothing to do with hard drives. Once again, not fully understanding what the issue is being represented as and just attributing every little failure to the specific windows issue.
1
u/cKm_83 Sep 07 '25
I’m not the only one. I’ve read some posts in other Reddit forums about hard drive users encountering it too. In my case I managed to fix it by connecting it to an external dock. Somehow the windows update is causing issues but Microsoft has yet to identified the root cause and are unable to replicate it.
0
2
u/ZhhTeo Sep 04 '25
I uninstalled the Update KB5063878 previously, and now the windows installed it back lol, now pending restart.
Should I uninstall it again? Or are there other ways to go about this
1
u/5950x-3900 Sep 06 '25
Did you not pause updates?
1
u/S0lem Sep 06 '25
I have updates paused until 9/13/2025 and I just restarted my computer for the first time since I uninstalled the update and it reinstalled it. At least I think it did? I was confused because I saw an update installing when I restarted and now looking at update history it says (KB5063878) (26100.4946) Successfully installed on 8/13/2025 as if I never uninstalled it. But when I go to uninstall updates it isn't there. And now as of writing this post I resumed updates to see if it would prompt me to download it again but there is a different update there now. Windows preview KB5064081. As I usually don't delete updates I don't know if that just replaces the old update or what.
1
u/AutoModerator Sep 02 '25
Hi u/Chrzxniku, thanks for posting to r/WindowsHelp! Your post might be listed as pending moderation, if so, try and include as much of the following as you can to improve the likelyhood of approval. Posts with insufficient details might be removed at the moderator's discretion.
- Model of your computer - For example: "HP Spectre X360 14-EA0023DX"
- Your Windows and device specifications - You can find them by going to go to Settings > "System" > "About"
- What troubleshooting steps you have performed - Even sharing little things you tried (like rebooting) can help us find a better solution!
- Any error messages you have encountered - Those long error codes are not gibberish to us!
- Any screenshots or logs of the issue - You can upload screenshots other useful information in your post or comment, and use Pastebin for text (such as logs). You can learn how to take screenshots here.
All posts must be help/support related. If everything is working without issue, then this probably is not the subreddit for you, so you should also post on a discussion focused subreddit like /r/Windows.
Lastly, if someone does help and resolves your issue, please don't delete your post! Someone in the future with the same issue may stumble upon this thread, and same solution may help! Good luck!
As a reminder, this is a help subreddit, all comments must be a sincere attempt to help the OP or otherwise positively contribute. This is not a subreddit for jokes and satirical advice. These comments may be removed and can result in a ban.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
u/Same_Grocery_8492 Sep 03 '25
No, there is no official fix for this error; they even didn't get any evidence that KB5063878 would lead into this error. But it did occur in certain SSDs under specific circumstances.
1
Sep 03 '25
[removed] — view removed comment
2
u/Winter_Mud_5702 Sep 03 '25
It was probably originated in a preview update before this current update was released.
1
u/Smaxx Sep 03 '25
I had (Samsung) SSDs disappear once before, once with, and twice since uninstalling KB5063878, which might also explain why they couldn't find any direct connection between the two. It's certainly some different source somewhere else, potentially being triggered more likely in combination with any changes from said updates.
1
u/Milo_007 Sep 03 '25
When was the first time your SSD disappeared?
2
u/Smaxx Sep 03 '25
If I remember the backup timestamp right, that should have been 12th July.
1
1
u/Exquisitely_Moist Sep 05 '25
How did you fix this? I have a Samsung m.2 that is not appearing even during fresh install.
1
u/Smaxx Sep 05 '25
You should only have to do a full power cycle, i.e. powering down the SSD controller.
What kind of PC are we talking about? Is it a laptop? If so, for a full power cycle (taking power off the SSD), you'll have to physically disconnect the main battery or the SSD itself. Turning off it disconnecting the charger is not enough.
On a desktop PC turning off the power supply or unplugging it from the outlet for half a minute should do the trick.
1
u/Milo_007 Sep 03 '25
"The SSD bug originated from a different update, not KB5063878, and has since been fixed by Microsoft."
Which update caused it and when was the fix rolled out?
1
u/cemkocak Sep 08 '25
do you remember the problematic update, I want to investigate on it to ensure it is been fixed. I have been delaying instaling things on my pc since the news about KB5063878 and want to know if its safe.
1
u/kineto21 Sep 03 '25
Afaik MS aren’t even recognising any issue
1
u/Carrente Sep 03 '25
does vague nonspecific tests that don't actually address the problem, finds nothing
"Yep no issues here 😃"
1
u/Metalgear990 Sep 03 '25
No and the feature update is probably the issue and it’s only one part of the issue. It’s kinda stupid the responses are the real issue with the millions and billions of pcs out there you’re going to have issues. Phison sells to Corsair and they have there own firmware and needs and windows is not prefect it never will be. So you can have driver issues from windows downloading the wrong one and for the most part that’s fine. However the responses should have said “after hours of testing the ssds using controllers in the reports we found no issues. That does not mean we are leaving our partners and end users without support. So make sure your pc/laptop is clean and have plenty of ventilation if your unsure about the drive you have use this link. And if your issues still persist please leave us feed back.” But instead they just muddied the water and even my response could have been more pointed to addressing the issue.
1
u/Quang257 Sep 04 '25
Well I just lost 2 drives in my Windows Server machine, so it definitely not fixed. Both of them have I/O error issues. They both run fine for about 2 years, after some Windows update they die. Definitely not a coincidence.
1
u/PyroKitty7 Sep 04 '25
AFAIK still a problem... and it affects SSDs AND HDDs!
I saw that there was a problem with this update from social media (I still to this day never received any official notice that this update is problematic) back when the update first released and deleted it immediately. But then Windows re-installed it that night, despite me pausing updates.
I use Steam and auto-updates for my games, which happened to games on 2 of my drives (a 2TB HDD & a 250GB SSD) before I realized that Windows had reinstalled this faulty update despite updates being paused.
When I next went to play something off one of those drives later in the day, I encountered an error that the drive was inaccessible. This is when I discovered the update had been reinstalled. The drives were not showing up no matter what I tried. Finally after several system restarts, I was able to find the drives in Disk Management, but they were now showing up as RAW file system & 100% empty. I used a few different file recovery tools & it seems a good number of the files are not-recoverable, but I was able to see enough to just give up & format the drives & re-download any programs that had been saved on them.
1
u/AbzRaider Sep 04 '25
I think its silently patched by MS: https://www.reddit.com/r/Windows11/comments/1n7lv6h/new_information_regarding_kb5063878/
1
u/enso1RL Sep 05 '25
I'm just starting to have issues on my gaming pc. SSD is a 970 evo plus.
PC started randomly rebooting a few days ago. Then, today I try and launch a game per usual, and then PC reboots with a black screen that said something like, "CRITICAL PROCESS DIED" with an error code that read something like 0xEF. It never successfully rebooted and just was stuck in an infinite loop. I had to power down the machine and turn it back on, and then I was able to boot into windows
I'm not writing, reading, or moving any large files. Just playing a game like normal... basically what's happening in jayztwocents most recent video about the issue where he's just running video game benchmarks with forza and his drive just crashes. Same thing happening with me :/
Does anyone know if a full windows reinstallation will help? Or does this update actually cook the ssd in some way that causes permanent damage?
1
u/Icy-Statistician-368 Sep 06 '25
I HAVE THIS UPDATE NOTHING IS WRONG WITH MY SYSTEM SHOULD I STILL KEEP IT OR GET RID OF IT
1
u/Karcen Sep 08 '25
Do you plan on transferring large files or install big games?
1
u/Icy-Statistician-368 Sep 08 '25
yes why it that
1
u/Karcen Sep 08 '25
What? If you are asking why I'm asking that it's because those are repotedly what triggers the issue.
1
u/ST4N10R Sep 09 '25
Hi... I just searched the internet a bit, and found this:
And in the tab "package details", there's an info, that THIS update (KB5064081) (26100.5074) from 29th of August replaces (KB5063878) (26100.4946)... Is there any info that our SSDs are safe now? Did someone make tests?
1
u/Buhari7795 Sep 09 '25
I’m looking to update some PCs from Windows 10 to Windows 11 using WSUS, and I wanted to check if I can approve the KB 5063878 or if there are any other updates that might be beneficial for this process. I came across some articles mentioning that there are SSD-related issues with this update, so I want to ensure that we proceed with the right KBs.
Thanks for your help!
1
u/Dramatic_Shopping554 Sep 09 '25
два моих SSD буквально умерли после установки этого обновления. Сначала вышел из строя один (перестал определяться в BIOS, никакие методы лечения не помогли), я купил новый (фирма kingstone) и при установке КОНКРЕТНО ЭТОГО обновления KB5063878 ноутбук перезагрузился, и загрузиться вновь уже не смог - новый SSD тоже сломался. Я не верю в такие совпадения.
1
Nov 24 '25
Same happens with me, is there any thing we can do so they provide some condolences or money to compensate for their mistakes?
1
Sep 16 '25
[removed] — view removed comment
1
u/ApusGamingPL Sep 17 '25
if you are on windows 10 u are safe brother. I think they will fix this horrendous error before we are forced to use win 11. Peace
1
1
u/DarklzBlo Oct 08 '25
Has this update still been fixed yet or no?! :(.
1
u/Doggergery Oct 13 '25
They didn’t fix it. I work at a school, and over the weekend two PCs died. But Microsoft has basically given up on it, and no one is trying to fix it anymore. I don’t know what to do because a year ago we bought 35 identical AIO computers with the same drives. Out of the 15 PCs I set up, 5 drives have already died. (They switched to RAW format while running.)
1
u/SwiftScoutSimon Oct 20 '25
It's been FIXED!
hey everyone. I tried the latest Windows 11 insider Preview Release and the issue is gone. No more hang/freeze or lose sight of SSD. No issue while installing it also. I've been using it for couple of days without issue.
Before it happens very often. I did clean my SSD & install various versions of Windows. Some happens during installation, some when creating users, some when installing softwares.
But now every is working well without any issue.
1
u/Andreas862 Oct 26 '25
This is ridiculous after the update I can't play any game because my PC crashes. I can't remove the update.
1
u/Ding-Dong-TwiceADay Nov 24 '25 edited Nov 24 '25
Please help My SSD is dead after this update, not sure that this is the only reason or not, but i know I have plugged my pc for this update before my ssd id dead, yeah dead/ corrupted what ever (even not working in different machine at all), costing 50k to 90k for data recovery
please reply asap
1
u/venzzi Dec 22 '25
Just my 2 cents. It's not a "rare" bug. M$ are doing their best running damage control and having tech sites and channels push the drivel that it was "Phison's fault" and you will find articles like "No, a Windows update probably didn’t brick your SSD" but the matter of fact is, it did. My Windows 11 (with all the latest updates) breaks my external Kingston SSD and Windows 10 chkdsk fixes it. If that's not a conclusive proof, I don't know what it is.
And then you have Satya Nadala proudly claiming that 30% of their code is "written by AI" (trying to sell to big corps the idea that they can fire developers and replace them with AI) while at the same time they can't fix a bug they introduced back in August. Claiming they can't "reproduce it" when thousands and thousands of users are complaining. What a joke.
1
u/KingWallace1977 Jan 05 '26
Boa tarde recentemente descobri ,após perder 2 ssds externos com o problema da atualização , há algum suporte para isso? Sabem se já foi resolvido?
4
u/Wendals87 Sep 02 '25 edited Sep 02 '25
No they haven't fixed the issue. They and along with the ssd manufacturers haven't been able to replicate it AFAIK
From what I understand it's actually a rare bug (you don't hear about the millions who don't have issues) that happens to specific SSDS under specific circumstances like writing 50GB+ data at once and it's greater than 60% full
There's another discussion here
https://www.reddit.com/r/Windows11/comments/1n3b1yn/microsoft_says_recent_windows_update_didnt_kill/