SanDisk Extreme Portable SSD Corruption: The 2023 Bug and Recovery
In this article
If your SanDisk Extreme Portable SSD, Extreme Pro Portable SSD, or Pro Portable randomly corrupted your files, marked itself read-only, or completely disappeared from your computer, you very likely have a unit affected by the well-documented 2023 to 2024 defect. SanDisk (owned by Western Digital) quietly released a firmware update during the summer of 2023 after widespread reports of catastrophic data loss on the 2TB and 4TB second-generation models. The underlying issue was a defect in how the drive's controller handled wear-leveling and atomic write operations. The drives don't just fail. They actively destroy data that was written successfully. If your drive is still being detected, do not write anything else to it. The next write could be the one that triggers another wave of corruption.
Modern SSD recovery depends on a viable controller and encryption path. The lab assesses original-board repair, controlled reading, and firmware or virtual-translator access supported for the exact device. Independent raw-NAND chip-off cannot bypass encryption, and a lost controller path can make recovery impossible.
What Actually Happened in 2023 and 2024
Starting in early 2023, professional photographers, videographers, and travelers using the SanDisk Extreme Portable SSD V2 began reporting catastrophic data loss. The reports were specific and unmistakable. Drives that had been working fine would suddenly:
- Lose files that had been written successfully days or weeks earlier.
- Mark themselves read-only with no warning.
- Disappear from the host computer entirely.
- Show file system corruption that no repair tool could fix.
- Report wrong capacity (often 0 bytes or a fraction of actual size).
By summer 2023, mainstream tech outlets (The Verge, Ars Technica, Tom's Hardware) had documented the issue. Patreon and YouTube creators reported losing entire production runs. Wedding photographers reported losing entire shoots. Travel photographers reported losing irreplaceable images from once-in-a-lifetime trips.
The technical root cause, as best understood from teardowns and reverse engineering by independent researchers, traced to two issues. First, the drives shipped with a controller and firmware combination that had a defect in handling certain USB write patterns. Specifically, large atomic writes (the kind that happen when you're copying GB-sized video files) could trigger a race condition in the wear-leveling logic. Second, the physical PCB design had a known weakness where the USB-C connector was bonded to the PCB in a way that could fail under stress, but the bigger issue was the firmware defect that corrupted data even on physically intact drives.
The corruption isn't random in the way a normal SSD failure is. It's pattern-based. When the trigger conditions hit, the drive can lose tens of GB of files at once because the metadata structures get scrambled. Worse, the corruption can persist even after the trigger is no longer present, because the wear-leveling tables themselves are corrupted.
Which Models Were Affected
The defect affected specific models and capacities, primarily the second-generation lineup. Here's the breakdown based on field reports and our own lab experience.
| Model | Affected Capacities | Notes |
|---|---|---|
| SanDisk Extreme Portable SSD V2 | 2TB, 4TB | Portable SSD V2 |
| SanDisk Extreme Pro Portable SSD V2 | 2TB, 4TB | Same defect, faster USB Gen 2x2 interface |
| SanDisk Pro-G40 SSD | 2TB, 4TB | Rebrand of Extreme Pro, same controller |
| SanDisk Extreme Portable SSD V2 (1TB) | 1TB | Lower report rate but documented cases exist |
| SanDisk Extreme Portable SSD V1 (original) | Most capacities | Mostly not affected, different controller |
| SanDisk Extreme Portable SSD V3 (post-update) | All capacities | Updated controller and firmware, supposedly fixed |
The 1TB units were less commonly reported but not immune. The original V1 (the first-generation Extreme Portable SSD with the orange clip) used a different controller and is generally not affected.
How to Identify If Your Unit Is Affected
If your drive hasn't failed yet but you want to know whether you're at risk, here's how to check.
Check the Model Number
The model number is printed on the bottom of the drive. Affected V2 units have model numbers in the SDSSDE61 (Extreme) and SDSSDE81 (Extreme Pro) series for the affected capacities. The V1 originals are SDSSDE60 series. If you can't read the label, the firmware version number tells you which generation it is.
Check the Firmware Version
Open the SanDisk Dashboard software (or Western Digital Dashboard, depending on when you bought the drive). It will show the firmware version. Affected drives shipped with firmware in the early 2032 series for the 2TB/4TB Extreme V2. The post-issue update is in a later revision. If your drive is still on the original firmware and the model is one of the affected ones, you're at risk.
Check the Purchase Date
Drives manufactured and sold between late 2021 and mid-2023 are the most likely affected units. SanDisk shifted production to the updated controller/firmware combination in mid-2023. If you bought your drive in 2024 or later, it's most likely a post-update unit.
Check the SanDisk Dashboard for Update Notifications
If the Dashboard shows a firmware update available, that's a strong signal your unit shipped with the defective firmware. Whether to update is a separate question (covered in the next section).
The Firmware Update and What It Actually Did
Western Digital quietly released a firmware update in mid-2023 that they claimed addressed the issue.
- The update reduced but did not eliminate corruption reports. New corruption events on updated drives are less frequent but still happen.
- The update did not fix data already lost. Drives that had already corrupted data did not magically recover after updating.
- The update can occasionally make things worse on a marginal drive. Applying a firmware update to a drive that's already in a degraded state can finish off the controller.
- Western Digital did not issue a recall. Affected users had to opt in to a quiet update process via the Dashboard, with no notification to most owners.
What this means practically: if your drive is working and you have it backed up, applying the update is probably worth it. If your drive is misbehaving (slow reads, intermittent disconnects, occasional missing files), the update is a coin flip. It might stabilize the drive or it might be the last write the drive ever accepts.
If your drive has already failed (won't mount, shows wrong capacity, lost files), don't update firmware. The drive needs lab recovery, not a firmware update.
Class Action Lawsuits and WD's Position
By late 2023, multiple class action lawsuits had been filed against Western Digital and SanDisk in U.S. federal court alleging that the defect was known to the company before customers reported it and that WD failed to issue an adequate recall or remedy. The lawsuits are ongoing as of late 2025 with periodic settlements and procedural updates.
Honest read: if you're affected, your remedies under WD's standard warranty are limited. WD will typically replace the drive (no data recovery) for in-warranty units. Out-of-warranty units get nothing from WD. Whether class action settlements will provide meaningful recovery for data lost is yet to be determined. The settlements that have been preliminarily approved focus on refunds, not data recovery costs.
If you're considering joining a class action, do that separately from your data recovery decision. The standard estimate for recovery is 4–6 weeks, with timing varying by case. Class action settlements move on a multi-year timeline. The two don't intersect.
For more on Western Digital's own support resources, visit WD Support. The Dashboard software and firmware downloads are there.
Symptoms of the Defect
If you're not sure whether your drive's behavior matches the known defect pattern, here's the symptom checklist we use in the lab.
| Symptom | Matches Defect Pattern? | What It Means |
|---|---|---|
| Files written days ago are now missing | Strong yes | Wear-leveling table corruption |
| Drive randomly becomes read-only | Strong yes | Controller safety mode after detected internal error |
| Drive disappears mid-transfer | Strong yes | USB-NVMe bridge or controller reset |
| File system corruption that won't repair | Strong yes | Metadata structures partially scrambled |
| Wrong capacity reported (0 bytes, 31MB, etc.) | Strong yes | Severe controller table corruption |
| Drive disconnects and reconnects rapidly | Moderate yes | Bridge controller issues, possibly defect-related |
| Drive is slow but works (no missing files) | Possibly | NAND wear or thermal throttling, often unrelated |
| Single corrupt file in an otherwise working drive | Possibly | Could be defect or normal wear |
If you're hitting the top three patterns, your drive is almost certainly an affected unit. The corruption isn't random failure. It's a specific firmware-level defect that destroys metadata structures.
What NOT to Do
Affected SanDisk Extreme drives are uniquely fragile. Wrong moves can turn a partial recovery into nothing.
- Write anything to the drive. Every new write triggers wear-leveling, which is the broken subsystem. New writes can scramble what's still readable.
- Format the drive. A full format writes to every block. On these drives, that destroys what could have been recovered.
- Run chkdsk, First Aid, or fsck. These tools assume the drive is normal. On these drives, the "fix" attempts can corrupt more data.
- Update firmware on a failing drive. Firmware updates write to the controller. On a marginal drive, this can finish off the controller permanently.
- Run SanDisk Dashboard's "Erase" or secure-erase. Permanently destroys data.
- Plug it in and out repeatedly hoping it'll work. Each enumeration cycle triggers more wear-leveling work, which is the broken part.
- Run "data recovery software" if the drive is still being detected. The software's repeated read attempts stress the failing controller. More important: writes during recovery scanning (which some tools do) can wipe what's left.
- Send the drive back to SanDisk for warranty replacement. They'll replace it but they won't recover your data. They'll wipe the original. Once you ship it to WD, your data is gone.
Safe Things to Try Before You Call Anyone
The safest moves on a failing SanDisk Extreme are minimal. Don't try too hard. The drive's own controller is the problem, and every interaction stresses it.
If the drive is still being detected and you can see your files, copy the most important files to another drive ASAP. Don't run any "verification" or "repair" tool. Just drag files to another drive. Do this once. Don't keep using the drive after that.
Write down (on paper or another device) exactly what happens when you plug the drive in. Does it appear? Does the capacity look right? Do files open? Are folders missing? This information helps a recovery lab figure out which failure stage you're at without stressing the drive further.
Take a clear photo of the label on the bottom of the drive. The model number, serial number, and capacity tell us exactly which controller and which firmware generation we're working with. Photograph both sides if there's anything printed there.
Try one different USB-C cable on one different port. If the drive behavior is the same, the cable/port aren't the issue. Don't keep cycling. Each cycle is another opportunity for the controller to make things worse.
The Dashboard software talks to the drive's controller. On a failing drive, that interaction can trigger firmware actions that make recovery harder. Skip the Dashboard entirely until after recovery is complete.
If the drive isn't detected at all, stop trying. Call a lab. Repeated power-cycling of these drives when they fail to detect can sometimes finish off the controller's ability to communicate even at a low level.
Is Your Data Recoverable?
Recovery depends on readable data and a supported access path.
| Drive State | Assessment focus | Reading constraint |
|---|---|---|
| Drive detected, files partially visible | Readable files | Image readable data first; perform logical reconstruction on a copy |
| Drive detected, wrong capacity | Capacity reporting | Reported capacity alone cannot establish readable data |
| Drive detected as "Unknown USB Device" | USB identification | The reported name alone cannot identify the failed component |
| Drive not detected at all | Original reading path | Requires a viable original reading/encryption path; chip-off is not a general fallback |
| Drive previously updated firmware, still failed | Firmware history | The update history needs assessment |
| Drive already formatted after failure | Case-specific; depends on surviving data | Format wrote over recoverable structures |
| Drive sent through DIY repair attempts | Prior repair attempts | Depends what was done |
Inside the Lab: How We Recover Failed SanDisk Extremes
The recovery process is more involved than for a typical portable SSD because we have to work around the firmware defect itself.
Step 1: Identify the Exact Model and Firmware Generation
From the model number and serial number, we identify which controller (Silicon Motion or Marvell, depending on production batch) and which firmware revision the drive shipped with. This tells us which lab tools and techniques apply.
Step 2: Image the Drive at the USB Level (if Detectable)
If the drive still enumerates, we image it through a hardware imager that reads sectors carefully and logs every error. We don't ask the drive to do anything fancy. We just read each LBA sequentially and capture what comes back. Bad sectors are retried with different timing parameters.
Step 3: Vendor Tool Diagnostics (Controller Level)
If the drive isn't responding at the USB level, we have lab tools that can talk to the drive's controller directly, bypassing the USB bridge. This requires opening the enclosure and connecting test probes to the controller's debug pins. Once we're connected at this level, we can sometimes restore the controller to a state where it'll respond to reads, even if it won't accept writes.
Step 4: Translation Table Repair
The flash translation layer maps logical sectors to NAND locations. An unexpected disconnect or missing files does not prove a single specific cause or intact memory. Firmware-level reconstruction must be supported for the actual controller and revision; do not generalize from another SanDisk or WD model.
Step 5: Assess Controller and Encryption Limits
For an SSD with a failed controller, the first question is whether the original reading path can be restored. A same-model donor does not automatically decrypt the original NAND. Some legacy unencrypted designs support raw-NAND reconstruction, but that is not a general fallback for modern SATA or NVMe SSDs.
Step 6: NAND Reassembly
The raw NAND data has to be unscrambled and recombined into a coherent logical drive image. This requires knowing the controller's interleaving pattern, ECC correction parameters, and translation table format.
Step 7: Filesystem Recovery on the Reassembled Image
Once we have a coherent image of the logical drive, we recover the filesystem (typically exFAT on these drives). If file structures are intact, we extract files with original names. If structures are damaged, we use raw scanning to find file signatures and reconstruct the directory.
How Much Does SanDisk Extreme Recovery Cost?
This recovery is more expensive than typical portable SSD work because of the firmware-level complexity.
| Recovery Path | Typical Range | Why |
|---|---|---|
| USB-level imaging (drive still talks) | $1,000 to $1,500 | Imaging time, filesystem rebuild |
| Controller debug + FTL repair | $1,000 to $1,500 | Specialized vendor tool work |
| Original-board / supported controller recovery | $1,500 to $2,000+ | Requires a viable original reading/encryption path; chip-off is not a general fallback |
| Severe controller damage, partial recovery | Case-by-case | Depends on NAND condition and damage scope |
SSD recovery cost and timing depend on original-board repair, supported firmware access, and the work needed to extract readable data. A dead encrypted controller can make recovery impossible rather than simply more expensive. Obtain a case-specific diagnosis and quote; chip-off is not a promised fallback.
SanDisk SSD models
| Model | Common Issues | Recovery Approach |
|---|---|---|
| SanDisk Extreme Portable SSD V2 | 2023 defect, controller corruption | Requires a viable original reading/encryption path; chip-off is not a general fallback |
| SanDisk Extreme Pro Portable SSD V2 | Same 2023 defect | Same as Extreme V2 recovery path |
| SanDisk Extreme Portable SSD V1 (original) | Normal SSD failures, no 2023 defect | Standard SSD recovery |
| SanDisk Pro-G40 SSD | Same controller family as Extreme Pro V2 | Similar recovery process |
| SanDisk Professional G-Drive (rebrand) | Mixed, depends on which physical drive inside | Covered in our G-Drive guide |
| SanDisk Ultra Portable SSD | Less commonly failed, standard SATA SSD inside | Standard SSD recovery |
| SanDisk Portable SSD (older USB-A models) | Older, normal failure modes | Standard SATA-based recovery |
The model number on the bottom of the drive tells us exactly what we're dealing with. If you're not sure, photograph the label and we can identify it from there.
How to Stop This From Happening Again
The hardest lesson from the SanDisk Extreme defect is that brand reputation isn't a guarantee. SanDisk had a great reputation when these drives launched. Customers trusted the name. The defect shipped anyway. The structural lesson: never trust any single drive with irreplaceable data.
3-2-1 Backup Rule
Three copies of important data, on two different media types, with one copy offsite. Your laptop's internal drive, a portable SSD or HDD, and a cloud backup like Backblaze or iDrive. If any one fails, you still have two. This is the rule that would have saved every wedding photographer who lost a shoot to the SanDisk defect. More on the 3-2-1 rule.
Don't Use Portable SSDs as the Only Copy of Work Output
The use case where most SanDisk Extreme losses happened: pros using the drive as the working master for a shoot, with no other copy. The shoot happens, files go to the SanDisk, the photographer goes home, the drive fails. There's no copy elsewhere. The work is gone. Always have another copy before deleting the source.
Cloud Backup for Active Projects
Backblaze ($9/month unlimited) backs up everything on connected drives. It runs in the background. Even if your portable SSD fails, you have the data in the cloud. For pros doing $5,000 wedding shoots, the math is obvious.
Verify Backups Work
A backup you never restored from isn't a backup. Once a month, restore a random file from your backup. Open it. Confirm it works. This catches silent backup failures before you need the backup.
Spread Risk Across Brands
If all your backup copies are SanDisk, a brand-wide defect affects all of them. Mix brands. SanDisk and Samsung. WD and Seagate. Crucial and Samsung. Different controllers, different firmware, different failure modes. A defect in one rarely hits the other.
Pay Attention to Firmware Updates
If your drive's manufacturer pushes a firmware update, find out why before applying it. Sometimes it's bug fixes for issues you don't have. Sometimes it's bug fixes for issues that affect you. Read the release notes. Lurk on Reddit's r/datahoarder or your brand's support forum for context.
Don't Buy the Latest Generation Right Away
The SanDisk Extreme V2 defect was visible in the field for months before it became mainstream news. Early adopters bore the brunt. If you're a working pro, wait 6 months after a new portable SSD launches before relying on it. Let other people's data find the bugs.
FAQ
How do I know if my SanDisk Extreme is affected by the 2023 defect?
Check the model number on the bottom of the drive. SDSSDE61 (Extreme) and SDSSDE81 (Extreme Pro) at 2TB or 4TB capacities are the most affected. Drives manufactured between late 2021 and mid-2023 are the highest risk. If your drive is showing any of the symptoms (missing files, wrong capacity, won't mount), the chance it's defect-related is high.
Will the firmware update fix my drive?
If your drive is working and you have a recent backup, applying the update reduces (not eliminates) future corruption risk. If your drive is already showing problems, the update may push it over the edge. We recommend recovery first, then either replacement or careful updating on a clean drive.
Can I get a refund from Western Digital?
WD's standard policy is to replace defective drives under warranty. They don't pay for lost data recovery. Class action settlements are ongoing and may provide some refund or recovery contribution but the timeline is years not weeks. Check class action status periodically if you want to track that.
I shipped my drive to WD for warranty replacement. Can I still get my data?
If WD has the drive, the data is likely gone. WD wipes drives before processing replacements. They may have already destroyed the original. If you want to try, contact WD support immediately and ask about getting the drive back before they process it. Some have been successful, most haven't.
My drive went read-only. Can I copy files off it?
Yes, and you should do that immediately. Read-only mode is the controller's protection state. The drive will still let you read. Copy the most important files first to another drive (not a SanDisk Extreme). Once you've copied what you can, stop using the drive and decide whether to send it for professional recovery of anything you couldn't access.
How long has Western Digital known about this defect?
Field reports started appearing in early 2023. WD acknowledged the issue with a firmware update in mid-2023. Whether they knew earlier internally is part of the class action discovery process. As of late 2025, the lawsuits are still ongoing and the timeline of internal knowledge is disputed.
Does the V3 (post-update) version have the same issue?
The V3 hardware and firmware combination is significantly different and the bulk of corruption reports have come from V2 units. Whether V3 is truly defect-free or just newer (and thus has had less time to manifest issues) is still being assessed by the community.
I have an Extreme Pro G40. Is it affected?
If yours is misbehaving, treat it the same way: stop writing, back up what you can read, send for recovery.
How long does SanDisk Extreme recovery take?
Recovery differs by storage medium. Modern encrypted SSDs need a viable original or supported controller path. Some unencrypted USB flash drives and memory cards permit raw-NAND reconstruction, but only with readable memory and compatible ECC, descrambling, and translation. Chip-off is not a universal recovery method.
What if my drive shows "0 bytes" capacity?
SSD recovery cost and timing depend on original-board repair, supported firmware access, and the work needed to extract readable data. A dead encrypted controller can make recovery impossible rather than simply more expensive. Obtain a case-specific diagnosis and quote; chip-off is not a promised fallback.
Do you ship to people outside New Jersey?
Yes. We work nationally via mail-in. You generate a free prepaid UPS label on the mail-in form (contiguous US), with signed-for delivery. How to ship safely walks through the process.
MDrepairs is an independent data recovery lab serving customers nationwide via mail-in service. We're not affiliated with SanDisk or Western Digital. Our specialty is getting data off devices that have failed, when that's the only thing you actually care about.
When DIY Stops Being Safe
With a SanDisk Extreme Portable SSD, corruption can show up as disconnects, unreadable folders, missing project files, or prompts to format the drive. Stop DIY if the SSD drops offline during transfers, mounts only sometimes, becomes very slow, reports the wrong capacity, or recovery tools repeatedly stall. SSDs are different from hard drives because controller behavior, encryption, TRIM, and firmware issues can limit the recovery window.
Do not reformat the SSD, run repair utilities on the original, or keep copying new files to test whether it is stable. If the footage, photos, or work files matter, disconnect it and get advice before the situation changes. MDRepairs handles portable SSD data recovery cases in a real NJ lab and offers a free phone consult before you decide what to do next. The $100 diagnostic is credited if recovery succeeds and is non-refundable once diagnostics start. Donor drives or replacement parts authorized by you are non-refundable once ordered, even if recovery fails. You review the estimate and approve it before recovery work begins. Customers outside the area can use mail-in SSD recovery nationwide without needing to visit in person.
How MDrepairs can help
Real cases like this come through our New Jersey lab every week. If you are dealing with one now, start here.
- NVMe SSD Data Recovery Recovery from M.2 NVMe drives not detected in BIOS. Learn more
- Samsung SSD Data Recovery Recovery from Samsung 860/870 EVO and SATAFIRM S11 faults. Learn more
- SanDisk Data Recovery Monolithic recovery from SanDisk SD cards, USB and SSDs. Learn more
- SD Card Data Recovery Monolithic chip-off recovery for corrupted and dead SD cards. Learn more
