Outline ·
[ Standard ] ·
Linear+
Anyone SSD ROSAKKKKKKKK after UPDATES
|
JohnLai
|
Aug 25 2025, 06:34 PM
|
|
QUOTE(acbc @ Aug 25 2025, 03:53 PM) MSI Spatium SSD died today. Totally undetectable. Wasted 1TB for nothing. Luckily no important data inside. Put it at other mainboard/enclosure, run Testdisk to fix the partition, the boot back using windows recovery setup and run BCD repair on it. bootrec /rebuildbcd
|
|
|
|
|
|
JohnLai
|
Aug 25 2025, 07:02 PM
|
|
QUOTE(JohnL77 @ Aug 25 2025, 06:58 PM) How to rollback the update? Kena my first Win 11 BSOD after installing this update. Luckily still managed to reboot. wusa /uninstall /kb:5063878 Then use wushowhide to hide the update.
|
|
|
|
|
|
JohnLai
|
Aug 25 2025, 07:13 PM
|
|
QUOTE(JohnL77 @ Aug 25 2025, 07:06 PM) Huh? How to do that? I noticed Win 11 don't have System Recovery anymore in Settings. Wtf la Microsoft? Should I worry about this issue if so far my SSD hasn't been bricked yet? I'm worried that trying to rollback the update might cause issues instead? Also how to check whether my SSD is affected? Better remove the update, you might never know it will accidentally trigger the bug. Run command prompt as administrator. Run the command : wusa /uninstall /kb:5063878 Reboot. Then http://download.microsoft.com/download/f/2...howhide.diagcabRun it and hide KB5063878, alternatively delay the windows update by 35 days at update settings? Note: You can just run the Recovery from bootable windows 11 installer via USB drive.
|
|
|
|
|
|
JohnLai
|
Aug 25 2025, 09:47 PM
|
|
.......are we still in 'how to fix the ssd borked by the update' or not?
|
|
|
|
|
|
JohnLai
|
Aug 25 2025, 10:04 PM
|
|
QUOTE(Ichibanichi @ Aug 25 2025, 04:37 PM) Mine M.2 Sata SSD 256GB gone. Purposely bought a enclosure for testing and hope someway to salvage it. PC unable to detect but lappy managed to detect but when initialize result error  Put it at other mainboard/enclosure, run Testdisk to fix the partition, the boot back using windows recovery setup and run BCD repair on it. bootrec /rebuildbcd *Not sure how did I miss your post, but you can try this, assuming if it still appear at BIOS detection stage properly.
|
|
|
|
|