We already wrote about an SSD that vanishes from BIOS, about a short NVMe that dies after sleep, and about a Phison controller stuck in ROM mode. This page is the WD Black SN850X version of that moment: the drive drops out after sleep or a power-state change, a forum thread or a support reply points at a firmware flash, and the flash is aimed at the only copy of the files.
An empty slot is not an empty drive
The SN850X is a WD_BLACK M.2 2280, PCIe 4.0 NVMe. Tom's Hardware's review lists the controller as WD's own and the cache as DDR4, across the 1 TB, 2 TB, and 4 TB capacities. It is a drive with its own DRAM. Sleep, hibernate, shutdown, and a cold boot all ask that controller to leave a low-power link state and identify again. Windows Fast Startup and the BIOS power-management defaults are part of the same loop. When the identify never completes, BIOS shows an empty M.2 slot and Disk Management has nothing to list. Nobody read the NAND and found it blank.
The previous WD Black, the SN850, has this shape in print. Sandisk Answer ID 31851, published October 7, 2021 and updated June 24, 2025, is titled for the SN850 not detected on cold boot. The symptom line is that the computer does not see it on a cold boot, and that it does work after a restart. The steps are power off, power on, enter the BIOS, exit, and reboot. The article then says to contact the hardware vendor. That is the SN850, not the SN850X. It is the same family of "the slot is empty until you cycle it," and the published remedy is another cycle.
SN850X owners have described the same disappearance without a matching Sandisk article we can point at. A SanDisk forum thread opened January 1, 2023: the SN850X was gone from BIOS and from Disk Management. A reply on March 2, 2023, on an MSI B550 Tomahawk, says a restart did not bring it back and switching the power supply off and on did. A BleepingComputer thread describes a 1 TB SN850X on a B450 Tomahawk Max that drops out after restart, shutdown, or sleep, and sometimes returns after more restarts. A post on r/gigabyte describes an SN850X that, after resume, logged disk and NTFS errors, showed 1 MB unallocated, and then showed RAW until a forced power-off. Those are user reports, not a lab series. What they share is a drive that fails to stay enumerated across a power-state change. A controller hang can look exactly like that. A dead NAND chip can also leave a slot empty. The empty slot does not tell you which one you have, and it does not tell you the files are gone.
The fix people are sent to is a firmware write
The community path, and the vendor path, land on the same button. Update the firmware in Western Digital Dashboard. A SanDisk forum thread from August 31, 2023 is someone noticing Dashboard offering firmware 620331WD for an SN850X boot drive and a data drive, and asking whether the data would still be there afterward. On September 2, 2023 that poster wrote that they had contacted WD first, and that WD said it should go okay, but to do a backup first. They had a backup. The update then completed for them. The precondition in that reply is the whole point. A backup is a second copy on different media. The stick that just vanished, if it holds the only copy, is not in that position.
WD has not handed retail buyers a changelog that says which build fixes sleep. In a SanDisk forum thread from October 2022, the person asking for SN850X firmware notes posted WD support's reply on November 1, 2022: WD does not release firmware notes for the retail drives, and the updates are usually minor bug fixes. Users have posted strings including 620311WD, 620331WD, and 620361WD. Without notes, a version string does not tell you that the next file is a sleep fix, or that it is safe to apply to a drive that is already dropping off the bus. A BleepingComputer reply on the disappearing SN850X tells the owner to check the firmware. That is the advice this page is about not following while the drive is the only copy.
The app itself has moved, and the warning did not go away. Sandisk Answer ID 52335, published January 23, 2025 and updated June 10, 2026, says support for Western Digital Dashboard has ended. SSD health, firmware versions, and updates moved to SanDisk Dashboard. Hard drives went to a different tool, Kitfox. Answer ID 52308, published October 22, 2024 and updated May 28, 2026, is what Sandisk tells you to do when the Dashboard firmware download fails: pull a .fluf address out of the dashboard log and install that file from the Tools page, in Safe Mode if the app will not start. That is still a firmware write. It is a worse moment to do it, because you are already in the failure the automatic update could not finish.
The SanDisk SSD Dashboard manual puts the warning on the firmware section in one sentence: to avoid data loss, back up before updating the firmware. It also says to use only a compatible firmware file if you update from a file on the computer. For the SATA SSDs that manual describes, finishing the update takes a full shutdown and power-on. The SN850X in front of you has already missed a power-state change. Do not boot that stick just so Dashboard can see it. If Windows lives on it, every boot is another trip through the same power states.
The SN850X vanished after sleep and the files are only on that stick? Leave it powered down. A firmware button is not the evaluation.
Erase, sanitize, and PSID Revert sit on the same Tools page
Firmware is not the only control in that window. The SanDisk SSD Dashboard manual's Tools chapter lists Firmware Update, then Secure Erase, Sanitize, Erase Drive, and PSID Revert. The manual's words on those erase commands:
- Secure Erase permanently destroys all user data. The note says it deletes the mapping table and does not erase every written block.
- Erase Drive uses the same description: permanently destroys all user data by deleting the mapping table.
- Sanitize permanently destroys all user data. The note says it deletes the mapping table and erases the written blocks.
- PSID Revert uses the 32-character code printed on the label of a security-capable drive. The manual says it restores factory settings, erases all user data, and leaves the drive unformatted. It is for a locked drive you intend to repurpose.
The mapping table is how the controller turns a file into NAND locations. Deleting it is how a drive that still held data presents as empty. A guide, a forum reply, or a button that says to erase, sanitize, or revert so a firmware update will apply is a wipe. Do not follow it. Do not type the PSID into a revert box because the drive failed to enumerate. The two SN850X sticks in the published case photos have a PSID on the label. That code is not a recovery key.
The same manual also lists a short diagnostic, an extended diagnostic, and Run TRIM Now. TRIM discards blocks the operating system says are free. An extended test is a long read of a drive that just fell off the bus. Neither one tells you whether the files are intact. Skip them on the patient. If the stick reappears as Unknown / Not Initialized, that dialog is Initialize Disk. Confirming it writes a partition table. Format writes a filesystem. CHKDSK /f writes metadata. A 1 MB unallocated sliver after resume, which is what the r/gigabyte report described, is not spare space to format and it is not proof the partition table is gone.
The 24H2 firmware article is a different list of drives
Search for a WD firmware fix and a different incident comes up first. Sandisk Answer ID 51469 is a critical firmware update for a blue screen on Windows 11 24H2, tied to host memory buffer. The products named are the 2 TB WD_BLACK SN770, the 2 TB WD_BLACK SN770M, the 2 TB WD Blue SN580, the 2 TB WD Blue SN5000, and the 2 TB SanDisk Extreme M.2. Updated firmware strings in that article are 731130WD, 281050WD, and 291020WD, depending on the model. The SN850X is not on the list. The article ties that crash to host memory buffer. Tom's Hardware's SN850X specs list onboard DDR4. Same brand, different failure, different file.
The critical line on that article is still the right warning to read: create and verify a backup of the data to another location before updating the firmware. Applying the file, in that article, is a shutdown and a power-on. Microsoft may also block the 24H2 upgrade on the affected models until that update is in. None of that is a reason to feed an SN850X a firmware file from the SN770 table, or to treat a drive that vanished after sleep as if it were that blue screen. Answer ID 52308's manual .fluf install is the same class of write. Close it.
What this is not
A clicking, grinding, or beeping disk is a hard drive. The SN850X does not have heads, and it does not click. Power a clicking drive off and leave it off. That failure is the clicking-drive page, not a Dashboard firmware job.
BitLocker is a different lock. If the volume comes back and asks for a 48-digit key, the key opens ciphertext. It does not repair a controller that drops off the bus. Unlocking, then copying or repairing, runs on the patient. Where Windows may have turned that encryption on without a clear ask is the Device Encryption page. The order when the drive is already unhealthy is image first, then unlock the copy.
A Phison stick that identifies as SATAFIRM S11 is a different firmware panic, on a different controller. A Steam Deck 2230 that dies after sleep is the same class of power-state fault in a handheld, not an SN850X. Pulling the NAND packages off the board is the wrong first move on a modern laptop NVMe, which is the chip-off page. Do not heat the packages because Dashboard could not see the drive.
The public case log has one SN850X job, and it is not a sleep disappearance. DDR-2026-0014 is two 4 TB WD_BLACK SN850X SSDs in a two-bay USB enclosure, striped as one 8 TB APFS volume. Both drives were failing at the NAND. Both were imaged before any reconstruction, and the client got a full recovery of that data. One member had been initialized in Windows. That write put a new partition table on the drive and zeroed the first and last 1 MB. Those regions sat in space the enclosure reserved, outside the stripe, so the volume data was not in them. The case notes say the initialization was harmless only by luck of where it wrote. There is no published intake of a single SN850X that vanished after sleep. We will not invent one. That enclosure outcome is not a prediction about a laptop stick that failed to resume.
What to do right now
- Stop the loop. Do not put the machine back to sleep to confirm the bug. Do not spend the day on shutdowns, BIOS exits, and power-supply switches. One careful power-off, and a look at whether the slot is empty, is the information. After that, extra power-ons are controller time.
- Do not flash. Do not run Western Digital Dashboard, SanDisk Dashboard, or a .fluf install against this stick. Do not download an SN770 or SN580 firmware file because a 24H2 headline said WD. If a screen is already showing a firmware string, photograph it and close the window.
- Do not erase or repair. No Secure Erase, Sanitize, Erase Drive, or PSID Revert. No Initialize, Format, diskpart clean, CHKDSK, Startup Repair, or TRIM. No "scan and fix" in a recovery program aimed at the original.
- If it enumerates and the files are nowhere else, copy them once to different media, as a straight copy, and stop. If the copy errors, the drive drops, or the capacity looks wrong, stop. Do not retry with a fixer, and do not use the successful copy as a reason to flash the original so the problem "won't happen again" before you have checked that the copy opens.
- If it does not enumerate, leave it off. Photograph the BIOS screen that shows the empty slot, the exact model from the sticker if you can see it without powering the machine, and any Dashboard or Event Viewer text you already have. Then it needs an evaluation, not another boot.
The stick can come out of the laptop once, if you can do that without guessing. Do not seat it in a string of USB enclosures to see which one "wakes it up." Pack it the way you would any failed drive — how to ship a failed drive safely. If Windows was asking for a BitLocker key, write down that you have the key. Bring the key. Do not unlock the drive to "make the copy easier" before it leaves.
How a lab handles it
We do not flash the patient because Dashboard is offering a newer string. We do not Secure Erase it, sanitize it, or type the PSID into a revert tool so a firmware file will apply. We do not initialize it, format it, or run CHKDSK against the original.
If the controller will identify, the drive is imaged write-blocked first, as far as it will read, and the file work happens on the copy. Imaging uses the lab tools already named on this site, including the ACE Lab PC-3000. If it will not identify, the evaluation is why the controller is not coming up — power, the board, firmware state — which is the job described on the SSD not detected page. It is not a Dashboard session, and it is not a reason to lift the NAND. A BitLocker key, if you have one, is used on the image.
What that cannot do: put back a mapping table a finished Secure Erase or Sanitize already deleted, a drive a PSID Revert already returned to factory state, or sectors an Initialize plus a format already replaced. A firmware update that was interrupted is its own damage. We will tell you if the copy shows that. We will not promise a flash that the manual warned could lose data left the volume untouched.
The public case log has no SN850X that vanished after sleep. DDR-2026-0014 is the striped enclosure, NAND failure, imaged first. We don't advertise a success rate, and we can't promise a turnaround from the model string. For the work itself, see SSD data recovery.
SN850X vanished after sleep — FAQ
BIOS and Windows do not see the SN850X. Does that mean the NAND is empty?
Dashboard says a firmware update is available. Should I install it?
Sandisk's SN850 article says to power off, enter BIOS, exit, and reboot. Should I keep doing that?
It came back, and Windows wants Initialize, Format, or CHKDSK. Or BitLocker wants the recovery key.
Is this the Windows 11 24H2 firmware update Sandisk posted for WD SSDs?
Something in the case is clicking. Is that the SSD?
I already flashed it, erased it, or initialized it. Is it too late?
Is there an SN850X sleep case in the public log?
A WD Black SN850X that disappears after sleep is often a controller that did not come back. The firmware button assumes you already have another copy. Leave the stick powered down, and start with a free evaluation before anyone flashes, erases, or initializes it.
Request free evaluation →Free evaluation · No data, no fee · Talk directly with a technician.