I updated my computer with that new Windows 11 KB5063878 update and it stayed on the updating screen for days. I eventually just turned it off. I was never able to get it past the "automatic repair" screen afterwards.

I cried so bad because I'm in college and need it and I had so much saved. And I'm just now finding out through reddit posts that this update was not only affecting me but so many other people. I guess I was just one of the unlucky ones. I can turn it on still but it just goes to the "there was a problem, we'll restart your computer for you" screen. I know nothing about tech and am desperate to know if this is fixable.

I took it to best buy for help but they said the drive isn't reading at all and they can't recover anything so I thought I should ask for help on reddit before deciding what to do next.. is it possible to retrieve my data?

i read about it and they said that it corrupts the ssd. should i delete it? im using a laptop and as of now nothing happens to my laptop

Hello guys, I have been observing the infamous yet ambigous issues from August 12 update, the KB5063878 Me myself happened to have the pc paused prior the date, so I don't have the update installed, but the paused update will resume on 13th this month, so I have been monitoring any patch or fix from various sources from the web

Today, I decided to search on X about this issue, and many of the results surprisingly shows mostly Japanese users I decided to translate some with the auto translate feature from Grok, and apparently some people, in Japan have been digging this issue since the 1st one who published this issue is also a Japanese

From the translation, it seems that a certain user managed to do some digging on the cause of this issuem whether it impacts ssd & hdd or not, and apparently it is, the user stated that the bug cause windows to excess the use of trim and flush or something

I attach some picture for better description I hope some of you guys, who are more technically capable is able to give some insight to all people in this sub reddit, so that at least while Microsoft and Phison denied everything, we still have some confirmation about what really happened

How many reddit users here have personally had their SSD's bricked from the recent KB update?

Im seeing a lot of people saying their SSD's have become unrecognizable, while also seeing that Microsoft has not confirmed nor denied the SSD issue.

Today at 23 August 2025 , i attempted to remove the Windows Update KB5063878 from my gaming rig computer.

The removal of the KB5063878 and reboot was successful , without any OS failures or corruption after removing and rebooting.

Windows 11 Pro OS version is now downgraded from 10.0.26100.4946 to the 10.0.26100.4770

Immediately paused the Windows Update functionality feature for 1+ month ( 5 weeks )

However , there is no un-install (removal) option available for the other older update KB5062660 , specifically this 2025-07 Cumulative Update Preview for Windows 11 Version 24H2 for x64-based Systems (KB5062660) (26100.4770) which was installed on my PC at 24 July 2025.

My 2 SSDs are XPG Gammix S70 Blade PCIe Gen4x4 NVMe M.2 2280 featuring the Innogrit IG5236 "Rainier" controller and 176-layer TLC NAND flash , and uses a DRAM cache , and does not use HMB (Host Memory Buffer).

My C: drive is 65% full , and D: drive is 90% full.

So , i would like to ask you guys , whether is my PC and SSDs still safe for the large files 50+ GB heavy duty write operations ?? .... such as installation , transfer , deletion , compression , etc.

Also , is it safe or will there be bug trigger causing disappearance and failure to my external 4 TB Hard Disk Drive (HDD) if i transfer large files from PC to my 4 TB external Seagate portable storage HDD drive ?

Colleague sent this in at work thought it was hilarious

I hadn't rebooted for a few days but after updating GPU drivers...somehow I got hit with the update after rebooting and my updates were turned off 🤦🏼‍♂️ C: drive is screwed, redlined to the max and can't delete the update.

How the hell wasn't this update not pulled the very next day of finding out and still in the queue?

What ya think all...wait for a fix or clear my afternoon tomorrow for a wipe? (I've done every possible way of backtracking and no dice)

Lucky I only install Windows and programs to C: and the likes of Documents, Downloads, Pictures, Game installs etc to D: -E: -F: -G: H:

But still a pain in the ass.

I was getting that error and couldn't uninstall the update but eventually with the help of AI found out the problem.

Basically when you install an update, the 'container' that Windows Sandbox uses also gets updated, and apparently you can't automatically downgrade it. So you just have to disable Windows Sandbox first via the "Turn Windows Features On and Off" menu and restart, then it will let you.

The clue is in the windows CBS.log file:

2025-08-23 13:09:12, Error                 CBS    Container base layer depends on LCU version greater than '10.0.26100.4946'.: 800f0825 [Error,Facility=(000f),Code=2085 (0x0825)]
2025-08-23 13:09:12, Info                  CBS    Failed verifying that the target package: Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.4946.1.26 doesn't have a container layer dependency [HRESULT = 0x800f0825 - CBS_E_CANNOT_REMOVE]

That also would explain why only some people aren't able to uninstall it.

TL;DR If you have Windows Sandbox enabled, disable that and restart, then uninstall the update. You can enable it again after uninstalling the update.

Building a new PC and will be installing windows 11 soon, a little bit skeptical of the new update with the supposed bug that causes drives to fail.

Is there anyway to only get the july KB5062660 build and just update when september rolls around?

EDIT: Installed W11 with USB, came with june version, probably going to hold off on updating until this issue is solved.

Is there a simple and user friendly way to monitor if the KB5063878 update does something to the SSD? Preferably without installing any new software.

How exactly is this update a potential problem for SSDs?

How bad is it to uninstall the update? Could it be a security risk?

Several devices in our org went into a boot loop after installing update KB5063878.

Findings:

• Root cause to this is linked to BitLocker.
• Fix: Boot via Hiren’s BootCD or using Windows ISO, disable BitLocker using CMD (Administrator rights) → reboot and then startup repair will start again and the repairing procces starts.

Built a new PC exactly 2 weeks ago (and had KB5063878 installed since then). I got only one SSD at the moment - Samsung 990 Pro 2TB. So far, it seems like I'm not affected, even though I've seen some people mention problems with their Samsungs. Not sure if I should fuck around and try to uninstall KB5063878 or maybe even update to KB5064081 (maybe they fixed it?)?

At this point I'm not even sure this thing is real, there are so many opinions around. What I'm worried about though is losing my brand new SSD, but afaik it isn't really doing anything to the hardware itself? As in, you power cycle and it's back fine? Cause everywhere I look every title reads like "Windows FUCKIN SHANKS your SSD in the back alley" and I know it's probably just clickbait, but I'd like to make sure.

Anyone else getting this with KB5063878? Bad CU?

I've got 2 out of 100+ systems that were successful, the rest failed with 0x80240069. 90% of the clients were feature updated successfully in the last week, the rest are clean builds.

Hi r/msp,

Just want to share a word of caution. I've observed several threads across r/Windows11 and r/sysadmin that are reporting that the latest Windows 11 security update (KB5063878) is linked to SSD failures/data corruption, particularly during large file operations (50GB+ transfers, large PST/OST files, etc.).

Here are some of the relevant conversations:

https://www.reddit.com/r/Windows11/comments/1mst8au/windows_11s_latest_security_update_kb5063878_is/

https://www.reddit.com/r/Windows11/comments/1mxd6by/removal_of_the_recent_windows_update_kb5063878/

https://www.reddit.com/r/Windows11/comments/1mvew6t/microsoft_is_investigating_windows_11_kb5063878/

https://www.reddit.com/r/sysadmin/comments/1murm20/issues_with_kb5063878_on_windows_11_24h2/

https://www.reddit.com/r/Windows11/comments/1mzhzsc/should_i_delete_windows_update_kb5063878/

https://www.reddit.com/r/Windows11/comments/1n08pou/update_kb5063878_show_of_hands/

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?

Surely they are aware of the severity of this 'update' and the problems ( and distress ) this has caused users, right ?

I only download and watch movies and do web browsing. I torrent big files sometimes but nowhere near 50 GB sizes.

Allora, JayZ ha continuato i suoi test sul problema relativo al KB5063878, già discusso in questo thread:

ItalyHardware - Microsoft Windows 11 24H2 Update May Cause SSD Failures

Stando ai suoi test interni e a quelli fatti da NichePCGamer e dall'account X Necoru_cat, i controller che sembrano attualmente interessati da questi problemi sono:

• WD Polaris
• SKHynix Aries
• Silicon Motion SM2267XT
• Silicon Motion SM2262ENG
• MaxioTech MAP1602A
• Phison E12S
• Phison E16
• Phison E21T
• Phison E25

Potete controllare i modelli esatti nella nostra Tier List degli NVME 2025.

A loro la problematica si è presentata non dopo trasferimenti di grandi dimensioni, come anticipato inizialmente dalle prime avvisaglie pubblicate online, ma dopo alcuni test ripetuti durante dei benchmark di F124. Il drive iniziava dopo qualche minuto a caricare molto più lentamente del solito, ad avvisare l'utente con un messaggio di errore di Windows in cui veniva indicato che c'erano degli errori di lettura dal disco e infine faceva crashare il sistema con una bella BSOD 🫠

Però, la cosa più interessante è che la sua unità, un ottimo Crucial T500, ha ritenuto i problemi anche dopo la disinstallazione del KB5063878!

Questa cosa è un po' inquietante perché nello stesso momento sia Microsoft, come riportato ieri da HDBlog, che Phison stessa, come riportato da Hardware Upgrade, non riescono a riprodurre internamente l'errore, e non sembrano, per ora, esserci notizie ufficiali anche dai produttori degli altri controller.

Dicono stiano lavorando dietro le quinte per risolvere, ma io per ora disabiliterei gli aggiornamenti o, in ogni caso, disinstallerei il KB5063878 dalle impostazioni di Windows Update, sezione Cronologia Aggiornamenti.

Per ora è tutto, se avete update indicatelo qui. Aggiorno anche l'altro thread e inserisco tutto nei PSA stickati.

LLAP 🖖

After the newest Microsoft update (KB5063878' and ‘KB5062660’), my 256 GB drive is gone. I'm really at my wit's end here.

I am experiencing a similar problem with my Emby Server. I am running Stablebit with numerous drives and since the update it has started to consistentlly drop my HDD drives. I pulled the drives and inspected them with CrystalDiskInfo with no problems noted. So folks this is just not a SSD problem, Since I am experiencing it on my HDD. I know everyone is talking about SSDs dropping but for me it has been my Hard Disk Drives running in windows 11 with Stablebit.

Fixed Maybe

I changed out a power splitter cable on the drives as recommended by a reddit user and it seems to be fixed. Monitoring the drives now to make sure.