Why Can't You Drag Into an Elevated (Admin) Window?

Drag a file from Explorer or a clipboard shelf onto Notepad running as administrator and nothing happens. No error dialog. The cursor may show a “no drop” glyph, or it may look fine and still fail. This is User Interface Privilege Isolation (UIPI), part of how UAC protects elevated windows. It is not a broken HDROP and not a 4 MB history limit.

Microsoft documents integrity levels: lower-integrity processes must not drive higher-integrity ones. Drag-and-drop is a stream of window messages. Those messages do not cross the elevation boundary the way people expect.

The split

Microsoft Learn, “How User Account Control works”:

• Integrity levels measure trust.
• A high integrity app performs tasks that modify system data.
• A low integrity app is more restricted (browsers are the classic example).
• Applications with lower integrity levels cannot modify data in applications with higher integrity levels.

A normal Explorer window and a typical clipboard app run at medium integrity. An app you launched with Run as administrator (or that always elevates) runs at high. UIPI exists so a compromised medium process cannot send synthetic input or drop files into an admin tool as a privilege-escalation trick.

Power Automate troubleshooting on Microsoft Learn names UIPI as the reason UI automation fails when the target is elevated. The same wall stops a hover shelf.

This article will not list unofficial ChangeWindowMessageFilterEx recipes as something users should apply to production admin tools. Punching holes in UIPI is a developer decision with security cost. Microsoft’s documented user fix is: do not mix elevations.

What you will see

Failure is often silent. That is why it feels like a clipboard bug.

Ctrl+V can still work when drag does not, if the elevated app reads the clipboard rather than accepting a drop. Clipboard access rules are not identical to UIPI message filtering. When a specific elevated app still cannot paste, run the source elevated too or save a file and use the admin app’s File > Open.

Why Some Apps Accept Paste but Reject Drag.

Why it feels like a clipboard bug

The user copied a file. The shelf shows it. The installer is on screen. The drop does nothing. Win+V is also empty of the file. Three “clipboard” surfaces failed, so the ticket says clipboard is broken.

Two different mechanisms failed:

1. History never stores files.
2. UIPI blocked the drag.

The live clipboard may still hold HDROP. Ctrl+V in a non-elevated Explorer folder is the control test. If that paste works, the list is fine.

Confirm elevation is the cause

1. Look at the target title bar or taskbar icon for the admin shield, or try a command that only works elevated.
2. Drag the same file from Explorer to a non-admin Notepad. If that works, HDROP is fine.
3. Open a second Notepad as administrator and drag again. If that fails, it is UIPI.
4. Win+V staying empty is unrelated: history does not store files. History is text, HTML, bitmap, 25 items, 4 MB, unpinned items cleared on restart.

What to do instead

Prefer File > Open in the elevated app. Browse to the file. No drag is required.

Paste at the same elevation. If you must use the clipboard, copy in an Explorer window you started elevated (only if you already accept that risk) and paste into the elevated app.

Do not elevate the clipboard manager just to make drops work. Running a history tool as admin means it sees more and, if exploited, can do more. That is a worse trade than using File > Open.

Do not disable UAC to “fix drag-and-drop.” That is not a clipboard setting.

Drop onto a medium-integrity staging folder, then open the file from the admin app. Using the Clipboard as a Temporary File Staging Area.

Keyboard attach and Open dialogs remain available when drag is the wrong interface. When Drag-and-Drop Is the Wrong Interface.

Mapped drives and admin tokens

An elevated process can see a different set of mapped drive letters than the normal Explorer window (the “split token” / enable-linked-connections topic). A path of Z:\file.bin that works in normal Explorer may not exist for the admin app. Use UNC (\\server\share\file.bin) or a local path. Network Drives and Clipboard File Lists. If the exact Group Policy name for linking connections is what you need, look it up in current Microsoft documentation rather than copying an old registry rumor.

Internal drags are not a workaround

Dragging a card inside a clipboard UI (reorder) never needed UIPI to talk to another process. Dragging out does. A pretty HTML5 ghost that works inside the shelf can still die at the admin border. Internal Drag vs External Drag in Clipboard UIs.

Installers, terminals, and other usual targets

The elevated windows people actually hit:

• MSI / setup.exe file-entry fields. Drag a downloaded installer from a shelf into an already-elevated setup UI. Fails. Browse.
• PowerShell or CMD run as administrator. Dropping a script to run it fails. Type the path or cd there. Paste of text (the path string) often still works: Copy as path, Ctrl+V into the console.
• Regedit. Do not drag random files into it. Use Export/Import.
• Task Manager (often elevated on some configurations) is not a drop target for files in any useful way.

Copy-as-path plus keyboard paste is the accessibility-friendly escape hatch whenever UIPI blocks a drag. The path is text. History can store it. The file still has to exist when the elevated process opens it.

If both source and target are elevated, drag may work and is still a bad habit: the shelf then runs with admin rights. Keep daily clipboard tools medium-integrity.

Remote desktop “admin session” and “user session” can recreate a similar wall. When a drag works on the console and fails in RDP, check elevation and clipboard redirection separately. Do not assume UIPI is the only filter.

Optional tools

A local shelf such as Edge-Drop will hit the same UIPI wall as Explorer when the target is elevated. That is expected. The product is not broken. Use File > Open, or keep the destination unelevated when possible.

FAQ

Can UAC be turned off to fix this? Do not. The wall is there to stop medium-integrity code from controlling admin windows.

Will running the shelf as admin fix drops? It may, and it enlarges the blast radius of a clipboard tool. Prefer File > Open.

Does this affect Win+V? Only indirectly. History still does not store files, elevated or not.

That limit is unpacked in Should File Clips Store a Copy or a Reference?.

Related reading

• Internal Drag vs External Drag in Clipboard UIs
• Should File Clips Store a Copy or a Reference?
• Why You Cannot Drag Old Clipboard Files Into Explorer
• How to Get a Screenshot Into Photoshop Without Recopying

Sources

• How User Account Control works (Microsoft Learn) — integrity levels; lower cannot modify higher.
• UIPI issues with UI automation (Microsoft Learn) — UIPI blocks cross-elevation UI; elevated target is a listed cause.
• DoDragDrop (Microsoft Learn) — OLE drag-and-drop entry point the source process runs.
• Using the clipboard (Microsoft Support) — history limits; unrelated to UIPI but often blamed.
• Shell Clipboard Formats (Microsoft Learn) — HDROP still only describes files; it cannot bypass integrity checks.

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