Clipboard File Clip Points at Nothing? How to Fix Broken Paths

File Explorer copy does not put the file’s bytes on the clipboard. Microsoft Learn describes CF_HDROP as the locations of existing files. A history tool that “remembers files” usually remembers those strings. When the file is renamed, the USB drive is gone, or a zip preview cleaned up its temp extract, the string still looks like a clip. Paste or drag then does nothing useful.

A file-aware history should fail visibly. Silent empty drops are how people blame Windows or the destination app. This page is the troubleshooting map: why paths rot, how to confirm it, and what good failure looks like.

The payload was never the file

Microsoft Learn: CF_HDROP is a DROPFILES structure plus a double-null-terminated list of fully qualified paths. DragQueryFile reads names. CFSTR_FILENAME is an older single-path format superseded by HDROP. In all of those cases the clipboard holds locations.

If E:\camera\DSC_1001.JPG is copied and then E: is ejected, the list is still the same characters. There is no bitmap backup inside Win+V. Microsoft’s history would not have listed the file anyway: history is text, HTML, and bitmap, 25 items, 4 MB, unpinned items cleared on restart.

Windows Clipboard History Does Not Store Files. Why You Cannot Drag Old Clipboard Files Into Explorer.

Why the path dies

USB and other removable volumes

The drive letter or volume GUID is part of the path. After eject, or after Windows assigns a different letter next plug-in, the saved string is wrong. Replug and check the letter in Explorer’s address bar before trusting the clip.

Rename and move

HDROP does not track an object ID. Rename report.pdf to report-final.pdf and the old clip is a 404. Move the file to another folder and the same thing happens. Explorer’s own same-session paste works because you usually paste before you reorganize.

Delete and Recycle Bin

A deleted file may still exist at a Recycle Bin namespace path. That is not the original HDROP string. Restoring in Recycle Bin can bring the file back to the old path; do not assume a manager can follow the recycle entry. The exact Recycle Bin path format is easy to get wrong — if uncertain, restore in Explorer and copy again.

ZIP preview and other temp extracts

Opening a compressed folder and copying a child can point at a temporary extract. The first paste works. Later, Windows has removed the temp file. Copying From a ZIP Preview vs Extracting First.

Browser downloads and some “Copy image” implementations also drop a file under a temp or cache directory. Those directories are not a library.

Network and cloud placeholders

A UNC path (\\server\share\file.docx) fails when the VPN is down, the share is renamed, or credentials expire. A OneDrive online-only file can exist as a placeholder; paste may trigger a download or fail if the cloud file is gone. Network Drives and Clipboard File Lists.

Substituted drives, junctions, and subst

subst drive letters and junction points can vanish after logoff. If a Win32 edge case is unclear, copy from the canonical path shown in Explorer after a reboot rather than trusting yesterday’s letter.

How to confirm the clip is a dead path

1. Paste into a new Explorer folder. A missing source produces an Explorer error, not a new file.
2. Paste into Notepad. If nothing appears, it was not Copy as path. If a quoted path appears, that is text — check whether that path still opens from Win+R.
3. Open Win+V. A missing card is expected for files. A present card that looks like a thumbnail may be a bitmap you copied from a preview, not the file.
4. In a file-aware manager, read the stored path. Try that path in Explorer’s address bar.

Do not invent a registry key to “fix HDROP.” The path is either valid or it is not.

What good failure looks like

A file-aware history that wants to be trustworthy should:

• Show a broken state on the card (missing-file glyph, “path not found,” dimmed drag).
• Refuse to start a drag that would publish a list of paths the process already knows are gone — or start the drag and let Explorer error, but still mark the card.
• On a multi-file stack, identify which member is missing. One dead USB file should not look like the whole stack failed without names.
• Offer Reveal in Explorer when the parent folder still exists.
• Offer Remove so stale cards do not linger as fake assets.
• Never replace a missing file with a zero-byte dummy of the same name. That creates a worse lie.

Microsoft Learn does not specify a “broken clip” UI. The above is product hygiene, not an API. The API fact remains: CF_HDROP is for existing files. Publishing a list of known-missing names is allowed by the format and unhelpful to the user.

Repair options

How to Keep File Copies After a Restart is the policy that avoids most of this: persist files, not clips, when the object must survive.

If the job is a same-session paste, skip the manager and use Explorer: How to Copy Multiple Files and Paste Them Somewhere Else.

Images versus files

A bitmap in history can still paste after the original PNG is deleted, because the pixels were copied. That card is not a path. It still dies on restart if unpinned, and it never joined history if it was over 4 MB. Do not diagnose a missing-file drop as a 4 MB problem or a 4 MB miss as a broken path.

Maximum Practical Size for Clipboard Images.

Worked examples

USB camera card. Copy E:\DCIM\100CANON\IMG_2044.JPG at lunch. Eject the card. After dinner a manager still shows a thumbnail if it cached pixels — or a file card if it stored the path. Drag to Explorer. Explorer errors. The repair is plug the card in and, if Windows assigned F: this time, copy again from the new letter. Do not edit the old string by guesswork unless the letter is confirmed in the address bar.

Renamed client folder. C:\Work\Acme\v3\deck.pdf becomes C:\Work\Acme\v4\deck.pdf after a tidy-up. Every HDROP from yesterday is dead. Search Explorer for deck.pdf inside Acme, then copy. A shelf that offers Reveal will fail on the old parent and should say so.

OneDrive renamed in the cloud. The local path includes the tenant name. A rename of the library or a reset of the sync client changes C:\Users\alex\OneDrive - Contoso\.... Cards that stored the old prefix all break together. That looks like a mass clipboard failure. It is one root-path change.

Temp extract from a zip. The first paste created a good file on the Desktop. The clip still points at %TEMP%\.... Use the Desktop file. Delete the stale card.

These four cases are the same bug: the string aged. The UI should make that boringly obvious.

Optional shelf behavior

A local shelf such as Edge-Drop can keep file stacks in view so stale items are noticed before a client demo. Visible cards fail better than an invisible HDROP from two hours ago. That is an optional convenience. It does not make a USB path immortal.

Related reading

• Copying From a ZIP Preview vs Extracting First
• Network Drives and Clipboard File Lists
• Why You Cannot Drag Old Clipboard Files Into Explorer
• How to Get a Screenshot Into Photoshop Without Recopying

Sources

• Shell Clipboard Formats (Microsoft Learn) — CF_HDROP transfers locations of existing files; CFSTR_FILENAME is a single fully qualified path.
• Standard Clipboard Formats (Microsoft Learn) — HDROP handle; DragQueryFile to read names.
• Using the clipboard (Microsoft Support) — history does not list files; 25 / 4 MB / restart rules.
• File Explorer in Windows (Microsoft Support) — copy/paste as Explorer operations that need a live source.
• Handling Shell Data Transfer Scenarios (Microsoft Learn) — existing files should be offered with CF_HDROP.

Copy. Stack. Drop.

Transform your clipboard into an interactive edge shelf. Stack, pin, and drag assets into any app with zero friction.

Download for Windows Get from Microsoft Store

How to Install Guide · First 10 Minutes Guide · Drag & Drop Guide · Edge-Drop vs Win+V · Support