Windows 11 24H2 Update Killed My Drive: 2026 Recovery Steps
In this article
If your PC won't boot after the Windows 11 24H2 update, the fault may involve the boot path or the drive itself. The two things that destroy that data are: clicking "Reset this PC" or letting Windows do a clean reinstall, and running repair commands on a drive that turned out to have hardware issues that the update happened to expose. Both are common reflexes. Both are wrong as a first move. The first move is to extract your files via a Linux Live USB or by pulling the drive into another PC, then deal with the broken Windows install separately.
The 24H2 update has caused widely-reported problems through 2025 and into 2026: boot failures on certain SSD controllers, BitLocker recovery prompts after the firmware-related security changes, drive-disappearance bugs where the SSD drops off the PCIe bus, and a few cases of corruption on drives that were already failing before the update. Microsoft has rolled some of these back, but the damage is done on machines that already updated. This guide covers what's happened, what to do first, and when the drive is truly dead vs just confused.
Known 24H2 and 25H1 Boot Issues
Windows 11 24H2 shipped publicly in late 2024. From its first rollout through 2025 and into 2026, several distinct issues caused failed boots, lost data, and BitLocker headaches. Microsoft has acknowledged some of these and pushed patches. Others are still active on machines that haven't yet received the fix. Here's the rough list.
Drive Disappearance on Certain NVMe Controllers
The 24H2 update changed how Windows interacts with NVMe storage at the driver and power-management level. On some SSDs (particularly drives using Phison E16, E18, and certain Silicon Motion controllers), the drive can drop off the PCIe bus during boot. Windows reports the drive as missing, can't find C:, and either blue-screens or boots into a recovery environment that doesn't see the drive. Powering the PC off completely and unplugging for 30 seconds often brings the drive back temporarily. That's a warning sign, not a fix.
BitLocker Recovery Prompts After Update
The 24H2 update changed several TPM-related settings as part of broader security tightening. On machines where BitLocker was enabled (the default on most Windows 11 Pro and many Home installs), the TPM saw a different boot environment than what it had measured before, and refused to release the BitLocker key automatically. Result: a recovery key prompt at boot. A user may see that prompt without having realized that BitLocker was enabled.
Boot Failures After Power Loss During Update
If 24H2 was actively installing when power was lost (battery died, plug pulled, building power outage), the boot configuration ends up half-written. Common symptoms: BSOD on next boot, "Inaccessible Boot Device", or BOOTMGR errors. The OS install is in a half-state.
Driver Mismatches on Some Manufacturer-Customized Builds
HP, Dell, Lenovo, and others ship Windows with customized driver bundles. Some manufacturer-specific drivers (storage controllers, security software, custom power-management) didn't get along with 24H2's updated kernel APIs. After update, the system can't load a critical driver and won't boot. Less common but documented.
Western Digital SanDisk SSD Issues
Reports through 2025 documented that some WD/SanDisk SSDs (particularly the SN850 series) experienced firmware-level problems on certain motherboards after the 24H2 driver changes. Drives reset, threw write errors, or required full repower. Firmware updates from WD addressed many cases. Affected drives that didn't get the firmware fix can still hit the bug. Western Digital's support page has current firmware updates for affected models.
Microsoft's Documentation
Microsoft maintains a release health dashboard for Windows 11 issues at learn.microsoft.com/en-us/windows/release-health/. Worth checking for the most current list of known issues and resolved bugs. Bleeping Computer and Windows Latest have also extensively documented the rollout problems through 2025.
The BitLocker Recovery Key Surprise
This single issue caused more panic than any other 24H2 problem. The pattern: PC was working fine. Update installed overnight. Morning reboot shows a blue screen asking for "Recovery key" with a 48-digit identifier. User has no idea what BitLocker is or where the key would be.
What happened: BitLocker is automatic full-disk encryption that Windows 11 enables by default in many configurations. When you signed in with a Microsoft account during initial setup, BitLocker turned on and uploaded the recovery key to your Microsoft account. The TPM chip on your motherboard tracks the boot environment ("measurements") and releases the BitLocker key automatically as long as the environment matches what it remembers. Major firmware or BIOS changes (which 24H2 made part of its security updates) can change the measurements enough that the TPM refuses to release the key. You then have to provide the recovery key manually.
Why So Many People Didn't Have the Key
BitLocker on Windows 11 doesn't make a big deal of itself. Many users had no warning that encryption was enabled. The recovery key was silently uploaded to their Microsoft account, but they never looked at it or printed it. Some users sign into Windows with a local account and never connect a Microsoft account, in which case BitLocker may have been enabled and the key was saved only to their device. After the update broke things, the device wasn't booting, so the local key file was unreachable.
Where to Find the Key Right Now
In order of likelihood:
- Microsoft account online: Go to account.microsoft.com/devices/recoverykey from any working device. Sign in with the Microsoft account you used on the broken PC. Look for the device. The key is displayed there.
- Work or school Azure AD/Microsoft Entra: If your PC is from work or school, ask IT. The key is in the organization's management portal.
- Printed or saved: Some users save the key as a PDF when first enabling BitLocker. Check cloud storage, OneDrive, Google Drive, USB sticks, or "BitLocker" files in your Documents folder on other devices.
- Sent via email: Some setup flows email the key. Search your email for "BitLocker" or "recovery key".
Which SSDs Got Hit Hardest
Based on 2025-2026 community reporting, the SSDs that had the most 24H2-related problems clustered around a few controller families. This is rough generalization and individual experiences varied, but the pattern is real.
| SSD Family | Controller | Common 24H2 Issue |
|---|---|---|
| Some Crucial P5/P3 | Various Silicon Motion | Drive drops off PCIe during boot |
| Older WD Blue SN550/SN570 | WD in-house controller | Reset loops, boot stalls |
| WD SN850 (early firmware) | WD in-house controller | Write errors, full repower required (firmware fix exists) |
| Sabrent Rocket family | Phison E16/E18 | Drive disappearance under load |
| Some Samsung 980 (early firmware) | Samsung Pablo | Boot delays, occasional drops (firmware fix exists) |
| Patriot, ADATA, Team Group | Various | Less affected, occasional reports |
| Samsung 980 PRO and 990 PRO (current firmware) | Samsung Elpis | Mostly stable |
If your SSD is on this list and you're having 24H2 boot issues, the first thing to check after recovering data is whether your SSD has a firmware update available. Most manufacturers released updates through 2025 specifically to address Windows 11 24H2 compatibility. Samsung's support and Western Digital's support pages both have firmware tools. Crucial and others have similar.
Is Your Data Still There?
A boot-path problem can leave files inaccessible, but the drive may also have hardware damage or overwritten data. Recovery depends on what remains readable.
Factors that affect recovery include:
- BitLocker-encrypted drive with no recovery key. Data is mathematically locked. Recovery is impossible without the key.
- SSD hardware failure on top of the update. If the SSD was already starting to fail, 24H2's increased boot activity may have pushed it over the edge. Now both software and hardware are broken.
- You clicked "Reset this PC". This wipes C: regardless of which "Keep my files" option you picked. The data is gone in the normal sense and only fragmentary recovery is possible.
- You ran chkdsk /r on the drive. If the drive had any issues, chkdsk likely made them worse.
- You let the Windows installer "reinstall" or "format". Same destructive outcome as Reset.
What NOT to Do Right Now
- Click "Reset this PC" in the recovery menu. Both options ("Keep my files" and "Remove everything") wipe data. "Cloud download" is the worst.
- Run "Startup Repair" more than twice. Each attempt writes to the drive. On a drive made shaky by the update, repeated writes can damage things further.
- Format anything when prompted. File Explorer, Disk Management, or the Windows installer can all show "format" prompts. Saying yes to any of them destroys data.
- Run chkdsk without verifying drive health. If the drive is one of the affected SSD families, chkdsk can corrupt the file system further.
- Update the BIOS during this crisis. A failed BIOS update on a struggling PC turns a recoverable problem into a brick.
- Try to "reinstall Windows over the top" without preserving data. The installer can wipe partitions if you pick the wrong option. Even custom install can be destructive.
- Force-power-off the PC ten times in a row. Each forced shutdown on a drive that's already struggling stresses it more. Use proper diagnostic methods instead.
- Click anything in recovery menus without reading every word. Microsoft puts the destructive options near the helpful-sounding ones. Read every dialog twice.
Diagnose Before Touching Anything
Two pieces of information determine your next move:
- Is the drive healthy or failing?
- Is the drive BitLocker-encrypted, and if so, do you have the key?
Both can be answered without modifying the drive. The diagnostic path:
On a working computer, download Ubuntu 24.04 LTS from ubuntu.com/download/desktop. Use balenaEtcher or Rufus to write the ISO to an 8GB USB drive. Boot the broken PC from the USB (boot menu key: F12 Dell/Lenovo/Acer, F11 HP, Esc some HP). Choose "Try Ubuntu".
Open a terminal. Run `lsblk` to list drives. Your internal drive is `/dev/nvme0n1` or `/dev/sda`. Run `sudo smartctl -a /dev/nvme0n1` (substitute the right device). Look for: NVMe critical_warning (should be 0), media_errors (should be 0), reallocated sectors, percentage_used, available_spare. Any critical warnings or media errors mean the drive is failing.
Still in terminal. Run `sudo lsblk -o NAME,SIZE,FSTYPE,LABEL`. Look at the Windows partition (usually the largest one). FSTYPE should show "BitLocker" if it's encrypted. If FSTYPE is "ntfs", the drive is not encrypted and you can mount and copy files immediately.
Drive healthy + not encrypted: copy files via Linux (next section). Drive healthy + encrypted: get BitLocker key first (see below), then copy via Linux with dislocker. Drive failing: stop using it. Image to lab. Drive failing + encrypted: still need key, plus lab work. Drive failing + no key: data is lost.
Recovering Your BitLocker Key
If your drive is BitLocker-encrypted and asking for the recovery key, you need to find that key before any recovery is possible.
Microsoft Account (Most Common)
On any working device, go to account.microsoft.com/devices/recoverykey. Sign in with the Microsoft account associated with the broken PC. You should see a list of your devices, each with its recovery key. The key is a long string of 48 digits in groups of six. There may also be a "Key ID" displayed at the bottom of the BitLocker prompt screen on the broken PC. Match the Key ID to the device on the Microsoft account page.
Work or School Account
Corporate PCs usually have the BitLocker key stored in Microsoft Entra (formerly Azure AD) or Intune. Ask your IT department. They can pull the key from the management portal in seconds.
Manually Saved Locations
Some users save the BitLocker key as a printout, a PDF, a text file on a USB stick, or a file in cloud storage. Search:
- Email inbox for "BitLocker" or "recovery key"
- OneDrive, Google Drive, Dropbox for files named "BitLocker"
- USB drives or external drives for saved key files
- A printed sheet in a desk drawer
- A password manager (1Password, Bitwarden, LastPass)
If You Cannot Find It
This is the worst-case scenario. BitLocker uses AES-256 encryption tied to a key you don't have. The encryption is mathematically unbreakable. No data recovery lab can crack it. No tool exists. The data is permanently inaccessible.
This is why we recommend writing the BitLocker key down and storing it in multiple places. After this lesson, the first thing to do on any Windows machine going forward is to check whether BitLocker is enabled and back up the key.
Extract Your Files via Linux Live USB
Assuming the drive is healthy and either not encrypted, or you have the BitLocker key. You're already booted into Ubuntu from the diagnose step. Now you copy files.
Any external USB drive with enough space. Ubuntu mounts it automatically. It shows up in the Files application.
In Files, click the Windows partition in the left sidebar. It mounts. Navigate to Users, then your username. You can see Documents, Desktop, Downloads, Pictures, Videos, Music. Drag what you want to keep onto the external drive.
In terminal, install dislocker: `sudo apt update && sudo apt install dislocker`. Create mount points: `sudo mkdir /media/decrypted /media/mounted`. Decrypt with `sudo dislocker -v -V /dev/nvme0n1p3 -p"YOUR-48-DIGIT-KEY-HERE" -- /media/decrypted` (substitute your partition device and key). Then mount: `sudo mount -o loop /media/decrypted/dislocker-file /media/mounted`. Browse `/media/mounted` in Files. Copy files to external drive.
Documents, Desktop, Downloads, Pictures, Videos, Music. If you want browser bookmarks and email, also copy AppData/Local and AppData/Roaming (press Ctrl+H to show hidden folders).
Unplug the external drive. Plug into a working PC. Open it. Open a few files (a photo, a document). Confirm copy worked. Only then proceed with fixing or wiping the broken PC.
Pull the Drive to Read Externally
If you can't get the broken PC to boot from a USB (some ultrabooks lock down boot options after firmware updates), pull the drive and read it on a working PC.
What You Need
- Small Phillips screwdriver, maybe Torx T5
- NVMe-to-USB enclosure if your drive is M.2 NVMe (most laptops since 2020). About $20.
- SATA-to-USB adapter or 2.5" enclosure for SATA SSDs. About $15.
- A working PC
The Process
Power off the laptop fully. Unplug the charger. Open the bottom case. Locate the SSD. For M.2 NVMe: a single Phillips screw holds it down. Loosen, lift at a 30-degree angle, slide free. Place in the USB enclosure. Plug into a working PC.
If not BitLocker-encrypted, Windows on the working PC reads it as an external drive. Copy files normally. If BitLocker, Windows prompts for the recovery key. With the key entered, the drive unlocks and you can copy files.
Roll Back vs Recover Data First
Once you've copied your data off, you have options for the broken PC. Microsoft's documented approach is to use the recovery environment to roll back to the previous Windows version (the rollback retains your files in theory). Our advice is different: extract files first, then choose freely.
The Risk With Rollback
Windows update rollback can fail. When it fails, the drive is in a worse state than before. Files may or may not be retained depending on how the rollback fails.
The Better Order
Pull files first via Linux or external. Verify they copied successfully. Then try rollback. If rollback works, great, you have your normal PC back with all data intact. If rollback fails, you have your normal PC back via clean reinstall and you copy the extracted data back. Either way the data is safe.
When Rollback Is Not Possible
After 10 days post-update, the rollback option disappears from the recovery environment. If you noticed the problem more than 10 days after the update installed, rollback isn't available. Your options are clean reinstall or in-place upgrade with the Windows installer (which sometimes preserves files but is unreliable).
Inside the Lab: Post-Update Brick Recovery
For cases where DIY doesn't work, here's the lab process at MDrepairs.
Intake and Diagnosis
We start by reading the drive through a hardware imager, with no boot attempts. We monitor current draw at idle and during reads. NVMe drives that drop off the bus under specific loads will often reveal that behavior to the imaging rig.
Sector-Level Imaging
Full sector copy to a separate lab drive. All recovery work happens on the image. Original gets put aside. For drives with intermittent failure (a 24H2 specialty), we use specialized slow-read settings that give the drive controller time to respond on each read.
BitLocker Decryption
If the drive is BitLocker-encrypted and you supplied the recovery key, we apply it to the imaged copy. Once decrypted, we proceed with normal file system access on the imaged data. Without the key, we cannot proceed.
File System Reconstruction
If the update damaged NTFS metadata (boot files, $MFT, etc.), we rebuild from backup copies that NTFS maintains. Our recovery process handles damaged NTFS, including the specific patterns we see from interrupted updates.
Hardware-Level Recovery for Bricked Drives
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.
How Much Does Post-Update Recovery Cost?
| Scenario | Typical Cost | Why |
|---|---|---|
| You did the Linux rescue yourself | $0 to $50 | USB drives only |
| Lab logical recovery, healthy drive, no encryption | $1,000 to $1,500 | Imaging plus filesystem work |
| BitLocker-encrypted with key provided | $1,000 to $1,500 | Extra decryption step |
| NVMe drive with intermittent failure | $1,000 to $1,500 | Slow imaging with retry handling |
| Original-board / supported controller recovery | $1,500 to $2,000+ | Requires a viable original reading/encryption path; chip-off is not a general fallback |
| BitLocker without the recovery key | Not possible | Encryption is mathematically unbreakable |
The $100 diagnostic is credited toward a successful recovery and is non-refundable once diagnostics start. Approved donor drives or replacement parts are non-refundable once ordered, even if recovery fails. You approve the estimate before recovery work starts. Full pricing.
Stop the Next Update From Doing This
This won't be the last bad Windows update. There will be another. Here's how to make sure you're not caught next time.
Back Up Before Every Feature Update
Feature updates (24H2, 25H1, 25H2) are the riskiest. Before each one, image your drive with Macrium Reflect, Acronis, or Veeam to an external drive. If the update breaks something, you restore the image in 20 minutes and move on.
Save Your BitLocker Recovery Key in Multiple Places
Right now, go to account.microsoft.com/devices/recoverykey and verify the key for every device is there. Print it. Save it to a password manager. Email it to yourself. Three places.
Wait Two Weeks After a Feature Update Drops
The first two weeks of any feature update have the most bug reports. Microsoft pauses rollout on configurations that are hitting problems. Waiting two weeks before installing reduces your risk dramatically. Settings has a "Pause updates for up to 5 weeks" option.
Don't Update on a Drive That's Almost Full
Updates need free space. A nearly-full drive is much more likely to have an update fail mid-install. Keep at least 20GB free on C: at all times.
Check Your SSD Firmware Quarterly
Most SSDs have a manufacturer tool that checks for firmware updates. Samsung Magician, WD Dashboard, Crucial Storage Executive, Kingston SSD Manager. Run them quarterly. Firmware updates often address Windows compatibility issues before the issues hit you.
Watch SMART Data
Install CrystalDiskInfo (free) and run it monthly. A "Caution" warning is your cue to clone the drive to a new one before it gets worse. SSDs almost never fail without SMART showing some warning first, if anyone is looking.
FAQ
Did the Windows 11 24H2 update actually destroy data, or just break booting?
Boot failure and data loss are different problems. Diagnosis must check for hardware failure and corruption before deciding how to attempt recovery.
Why does my PC ask for a BitLocker recovery key after the update when BitLocker was never on?
BitLocker may have been enabled silently when you first signed in with a Microsoft account. Windows 11 enables BitLocker by default in many configurations without making a big deal of it. The recovery key was uploaded to your Microsoft account automatically. Sign in at account.microsoft.com/devices/recoverykey to find it.
If I have my BitLocker key, can I always recover my data?
Chip-off is a possible method for certain supported, unencrypted flash devices, not a universal last resort. Raw NAND needs compatible error correction, descrambling, and controller-layout reconstruction. Modern encrypted SSDs and phones require their original or specifically supported reading/security path; memory removal does not bypass encryption.
Can I roll back from 24H2 to 23H2 to get out of this mess?
Within 10 days of the update, yes. Boot to recovery environment, choose "Go back to previous version of Windows". After 10 days, that option is gone. We recommend extracting data first via Linux, then trying rollback. If rollback fails, you have your data safe and can do a clean reinstall.
Is it safe to install 24H2 right now in 2026?
Most of the original bugs have been patched. The 24H2 build available in 2026 is much more stable than the one that shipped in late 2024. If you haven't installed yet, do a backup first, but it's reasonably safe at this point.
What's "25H1" and is it as bad as 24H2 was?
25H1 refers to feature updates that rolled out through 2025. Microsoft's rollout strategy changed, with more gradual phased deployments. 25H1 has had fewer wide-scale issues than 24H2, but specific configurations still hit problems. The advice is the same: back up first, wait two weeks, watch your drive SMART.
My SSD is in the affected controller list. Should I replace it?
Update the firmware first. Most manufacturers released firmware updates through 2025 specifically for Windows 11 compatibility. If your firmware is current and you're still hitting issues, replacement may be warranted. Replace before the failure, not after.
Does this affect Windows 10 too?
Windows 10 reached end of mainstream support in 2025. It's still receiving Extended Security Updates through 2028, but no feature updates. The 24H2 issues are specific to Windows 11. Windows 10 users on supported hardware avoided this whole episode.
Do you handle mail-in cases from outside New Jersey?
Yes. You generate a free prepaid UPS label on the mail-in form (contiguous US), with signed-for delivery. How to ship for recovery.
How long does post-update brick recovery take?
Chip-off is a possible method for certain supported, unencrypted flash devices, not a universal last resort. Raw NAND needs compatible error correction, descrambling, and controller-layout reconstruction. Modern encrypted SSDs and phones require their original or specifically supported reading/security path; memory removal does not bypass encryption.
If recovery succeeds, do I get a working Windows install or just files?
By default, just the files. You set up a new Windows install on a new drive and copy the recovered data onto it. If you want a bootable image of the original install too, ask during intake. Sometimes possible, sometimes not.
MDrepairs is an independent data recovery lab in New Jersey serving customers nationwide via mail-in. We're not affiliated with Microsoft. We're not affiliated with any SSD manufacturer. We get data off drives that Windows updates have made unusable. That's the job.
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.
