A CrisisOfTruth.org investigation · Documented with machine-generated records

Disclosure: The author of this page is the customer in the dispute it describes. Statements attributed to HP are drawn from HP's written communications and the author's contemporaneous notes, all of which have been provided to the proceedings listed below. HP is invited to respond; any response received will be published here in full.

The Drive That Vanished

I shipped my laptop to HP for repair. It came back missing a 4TB drive. HP said it was never there. The machine's own operating system says otherwise.

The Facts

What happened

In May 2026 I sent my HP ZBook G7 to HP's mail-in depot repair service, using shipping HP arranged. The laptop contained a Crucial P3 4TB NVMe drive I installed in September 2025.

When the laptop came back on June 29, the drive was gone.

When I reported it, HP's representative told me the company is “not responsible” for my hardware while it's in their shop. HP's case manager then went further: the service center's inspection report, he said, showed the laptop arrived with only a 2TB drive. In other words — the drive I was asking about had never been there at all.

I asked to see that inspection report. And the intake photographs. And the chain of custody records. HP refused to produce any of them, calling them “internal business records.”

Hold that thought: HP denied my claim by citing records it will not show anyone.

The Timeline

Nine and a half months, five records, one gap

Sep 18, 2025 Drive installed. Windows records FirstInstallDate.
May 19, 2026 Windows last records the drive present and functioning (LastArrivalDate). Final boot in my possession.
HP custody begins — no records produced
~May 20, 2026 Laptop ships to HP via HP-arranged carrier.
May 27, 2026 HP service center intake. HP's report claims only a 2TB drive present.
Jun 29, 2026 Laptop returned. Drive gone. LastRemovalDate: empty.

Eight days separate the last recorded heartbeat of the drive and HP's intake claim. The laptop shipped about a day after that last boot, so for roughly seven of those eight days it was in HP's custody or HP's shipping chain, not mine.

The Evidence

What the machine says

I spent five years running the evidence-based case system at a metropolitan police department. Chain of custody isn't an abstraction to me — it's a discipline. So when HP's report and my own knowledge disagreed, I did what any investigator does: I went to the records neither side controls.

Windows keeps them automatically, for every device installed on the machine.

Exhibit A — The three timestamps

DEVPKEY_Device_FirstInstallDate   9/18/2025 2:13:49 AM
DEVPKEY_Device_LastArrivalDate    5/19/2026 11:17:29 AM
DEVPKEY_Device_LastRemovalDate    (empty)

Installed September 2025. Last seen alive May 19, 2026. And the empty field matters as much as the filled ones: Windows never witnessed a removal, which means the drive came out while the machine was powered off. Its last boot in my possession was May 19, with the drive present.

Exhibit B — The phantom device

FriendlyName : NVMe CT4000P3SSD8
Problem      : CM_PROB_PHANTOM   (Code 45)
Present      : False

The drive is still registered in the laptop's device tree as a “phantom” — Windows' record of installed hardware that has been physically removed. You cannot phantom a drive that was never there.

Exhibit C — Two weeks before shipment

[Boot Session: 2026/05/06]
sto: SCSI\Disk&Ven_NVMe&Prod_CT4000P3SSD8  -> GenDisk [disk_install.NT]
sto: Driver Version New = 10.0.26100.8328

On May 6, Windows enumerated the drive and updated its driver — routine maintenance on a device that, per HP, didn't exist.

Exhibit D — Independent corroboration

My Acronis backup software separately documents the drive as a backup source in this laptop, with successful backups right up to shipment. Two unrelated software systems, one story.

The Policy Problem

A process that cannot verify itself

Set my drive aside for a moment. Look at the structure:

A company takes physical custody of your device — including the shipping. It generates the only intake records. It disclaims responsibility for what's inside. And when its records are questioned, it refuses to show them to anyone, while still citing them to deny your claim.

Custody
they hold it

Records
they write them

Responsibility
they disclaim it

Disclosure
they refuse it

↓ ↓ ↓ ↓

Every link controlled by one party

Every link in that chain is controlled by one party, and that party has declared itself unaccountable. Whatever you believe happened to my drive, a process built this way cannot verify itself and cannot be verified by anyone else. It only works as long as customers cannot prove what was in their own machine.

I could prove it. Most people wouldn't know they can.

Evidence standard for this page: Documented — the drive's presence, HP's denial, HP's refusal to produce records. Not claimed — who took it, or that theft occurred. This page never alleges what it cannot prove. The structure speaks for itself.

Case Status

Where it stands

Closed by HPFormal demand sent by certified mail July 8, 2026.HP declared the matter closed.
PendingClaim filed in Minnesota Conciliation Court.
FiledComplaint — Minnesota Attorney General.
FiledComplaint — Arizona Attorney General.
FiledComplaints — Better Business Bureau & Federal Trade Commission.

This page will be updated as each proceeding resolves. Last updated: August 1, 2026.

The Payload

Protect yourself before you ship

If you send any computer in for service, do this first. It takes ten minutes and it's free.

Photograph everything. The machine open, serial numbers visible, drives in their bays. Timestamped.
Export the device records. In PowerShell: Get-PnpDevice -Class DiskDrive and Get-PnpDeviceProperty for install and arrival dates. Save the output off the machine.
Keep purchase receipts for any components you added.
Image your drives before shipment — for the data, and because the backup log itself documents what hardware existed.
Put every conversation in writing. Phone calls don't exist. Emails do.
If something goes missing: written demand, certified mail, deadline. Then file — small claims (~$75), your state AG, the FTC. Companies count on you giving up. The paperwork says you won't.

Methodology

All machine records reproduced on this page were exported from the serviced unit without alteration and are preserved in full. Source exports available on request. This page follows CrisisOfTruth.org's evidence standard: documented facts are labeled as such; inferences are labeled as such; nothing is alleged that cannot be shown.