The Bug in Brief
Microsoft has confirmed a confusing Windows bug introduced by its June 2026 security updates that affects the Recycle Bin deletion confirmation dialog across all supported Windows client and server releases.
When a user attempts to permanently delete a single item directly from the Recycle Bin, the confirmation dialog displays an internal temporary filename — such as $RF3K7A2.docx — instead of the file's original human-readable name. The net effect is a dialog box that is essentially meaningless: you're being asked to confirm deletion of a file you can't identify by name.
Microsoft confirmed the behavior is limited to the confirmation prompt itself. The Recycle Bin still correctly shows the original filename at rest, and restoring the file also uses the correct original name. The bug is cosmetic in nature but creates real-world risk of accidental permanent file deletion.
Affected Versions
The bug impacts every supported Windows release following the June 2026 security update cycle:
Client Editions
| Version | Build |
|---|---|
| Windows 11 | 26H1, 25H2, 24H2, 23H2 |
| Windows 10 | 22H2, Enterprise LTSC 2021, LTSC 2019, LTSB 2016 |
Server Editions
| Version |
|---|
| Windows Server 2025 |
| Windows Server 2022 |
| Windows Server 2019 |
| Windows Server 2016 |
| Windows Server 2012 R2 |
| Windows Server 2012 |
The update associated with the regression is KB5094125, part of the June 2026 monthly security rollup.
What Microsoft Said
Microsoft acknowledged the issue in a support document and confirmed that engineers are actively working on a fix. No specific date was given for when a corrected update would ship. The company noted that enterprise customers can contact Microsoft Business Support for access to a temporary workaround — no public workaround is currently available to general consumers.
"The Recycle Bin itself correctly displays the original filename, and restoring the item also restores it using the original filename." — Microsoft
The statement makes clear this is a UI-layer bug rather than data corruption — but that framing offers little comfort when you're trying to decide which file you're deleting.
Why It Matters
While this is a functionality bug rather than a security vulnerability — no CVE has been assigned — the practical consequences deserve attention:
- Accidental file deletion risk: Users confirming a deletion without knowing what file is involved are more likely to click through, potentially deleting files they intended to keep
- Enterprise impact: In managed environments with large-scale Recycle Bin cleanup workflows or policies, the broken dialog creates operational confusion
- No immediate fix path: With no public workaround and only a vague "future update" timeline, affected users must either avoid permanently deleting files via the Recycle Bin dialog or engage enterprise support
Workaround Options
Until a patch ships, users can reduce exposure in a few ways:
- Use Shift+Delete instead — permanently deleting a file directly (bypassing the Recycle Bin) still shows the correct filename in its own confirmation prompt
- Right-click → Properties before deleting — verify the filename in Properties before deleting via the Recycle Bin dialog
- Enterprise customers — contact Microsoft Business Support for access to the temporary workaround Microsoft has prepared but not publicly released
The Patch Tuesday Problem
This incident highlights a recurring tension in Windows update management: monthly security rollups bundle stability fixes with security patches, meaning that accepting security updates sometimes introduces new functional regressions. For IT administrators who disable automatic updates to control rollout timing, this is a familiar trade-off — but one that puts individual users in a difficult position when there's no mechanism to selectively decline a buggy patch without forgoing security fixes.
Microsoft has not committed to issuing an out-of-band fix, suggesting the resolution will arrive in the July 2026 Patch Tuesday cycle at the earliest.