Microsoft has confirmed that the June 9, 2026 security update KB5094126 is causing an unusual and confusing bug in Windows: when users attempt to permanently delete files from the Recycle Bin, the confirmation dialog displays an internal system name instead of the original filename. The issue, which has been acknowledged on the company’s known issues dashboard, affects both Windows 11 and Windows 10 systems running the latest cumulative update.

The bug manifests specifically when right-clicking a file inside the Recycle Bin and selecting the “Permanently delete” option. Rather than the familiar prompt—“Are you sure you want to permanently delete ‘filename’?”—users instead see a string such as “Are you sure you want to permanently delete ‘$IXXXXXX’?” or a similar hash-like designation. The exact format varies, but it consistently reflects the temporary filenames the Recycle Bin uses internally to track deleted files, not the original names users recognize.

What’s Happening Inside the Recycle Bin

To understand why this bug matters, it helps to know how the Recycle Bin works under the hood. When a file is sent to the Recycle Bin in Windows, the system does not simply move the original file into a folder. Instead, it renames the file to a pair of entries: a data file named $R followed by a unique alphanumeric string and an index file named $I with the same string. The $I file stores the original filename, path, and deletion date, while the $R file contains the actual data. So a deleted photo named “vacation.jpg” might become $R12345 and $I12345 inside the hidden C:\$Recycle.Bin directory.

Normally, when you view the Recycle Bin through Windows Explorer, the shell seamlessly translates those internal names back into their original filenames—using the information from the $I files—so you never see the underlying system naming convention. That translation appears to be exactly what’s breaking with KB5094126. The permanent-delete dialog, which ought to query the shell for the display name, is instead pulling the raw internal identifier. The result is a confirmation prompt that fails to tell you what you’re about to delete, increasing the risk of unintended loss.

Microsoft’s Acknowledgment and Workaround

Microsoft has acknowledged the bug in the official release health dashboard for KB5094126, listing it as a known issue with a status of “Investigating.” The company notes that the problem only occurs with the “Permanently delete” context menu entry inside the Recycle Bin. Deleting files normally by pressing the Delete key (which sends them back to the Recycle Bin again, even from within the Bin) or using the “Empty Recycle Bin” command does not trigger the erroneous dialog. Additionally, the bug does not affect the standard delete confirmation shown when removing files from regular folders—only the Recycle Bin permanent-delete prompt is impacted.

While Microsoft works on a resolution, users can employ several workarounds to avoid confusion:

  • Use keyboard shortcuts: Press Shift+Delete while a file is selected in the Recycle Bin. This forces a permanent deletion and presents the standard confirmation dialog correctly.
  • Empty the entire Recycle Bin: Right-click the Recycle Bin icon on the desktop and choose “Empty Recycle Bin” to clear all items at once without individual prompts.
  • Restore then delete: Restore the file to its original location, then permanently delete it from there (Shift+Delete). This bypasses the Recycle Bin entirely.
  • Command line: Advanced users can use the del or erase command in Command Prompt to remove files directly from the $Recycle.Bin folder, though this requires administrative privileges and careful path navigation.

For most home and office users, the Shift+Delete shortcut inside the Recycle Bin offers the simplest fix. It avoids the right-click menu altogether and presents a clear confirmation with the original filename.

Why a Security Update Broke a UI Element

KB5094126 is a mandatory security update that patches several vulnerabilities, including a critical remote code execution flaw in the Windows Graphics Component (CVE-2026-3871) and an elevation-of-privilege issue in the Print Spooler service. Like most Patch Tuesday releases, it bundles fixes for the operating system kernel, graphics drivers, and user-mode subsystems. Changes to any of these components can inadvertently affect shell behavior, especially dialog box generation. In this case, the culprit appears to be a change in how the Recycle Bin’s namespace extension communicates with the Windows Shell API when constructing a delete confirmation.

This isn’t the first time a security patch has introduced a visual or functional glitch. In recent memory, a March 2025 update caused File Explorer to crash when opening folders with certain video files, and a May 2024 patch temporarily broke the taskbar search highlight. Such regressions underscore the tight coupling within Windows and the challenge of thoroughly testing every UI path across dozens of languages and hardware configurations.

Impact on Everyday Users

While the bug is not destructive—it doesn’t delete files erroneously or corrupt data—it erodes user trust by making a familiar safety check unreliable. For anyone managing dozens of files, seeing an incomprehensible string instead of a filename can cause hesitation or, worse, lead someone to click “Yes” assuming they know what the item is. In shared environments or for users who rely heavily on the Recycle Bin as a holding area, the ambiguity could result in accidental deletion of important documents.

Education and enterprise environments may feel the pinch more acutely. Help desks often instruct users to permanently delete files from the Recycle Bin to free up disk space, and encountering an unrecognizable filename will generate unnecessary support tickets. Some IT admins have already posted in community forums that they are pushing out group policies to advise staff of the workaround until Microsoft delivers a fix.

The Response So Far

Community feedback on Microsoft’s own feedback hub and independent forums has been swift. Many users expressed frustration that a security update, meant to safeguard systems, introduced a novel inconvenience. One user commented, “I thought my PC had been compromised when I saw ‘$IABC123’ in the delete dialog. It’s a relief to know it’s just a bug, but this should have been caught before release.”

Given the nature of the glitch, it is likely that Microsoft will include a fix in an upcoming optional non-security preview update, which typically lands in the last week of June or early July. If the issue is deemed serious enough, the company could push an out-of-band update sooner. In the past, such UI regressions have been resolved within two to four weeks.

How to Check for the Bug and Stay Informed

Users can verify whether their system is affected by sending any small file to the Recycle Bin, opening the Bin, right-clicking the file, and choosing “Permanently delete.” If the confirmation dialog shows a string of characters that isn’t the original filename, the bug is present. To confirm whether KB5094126 is installed, navigate to Settings > Windows Update > Update history and look for the KB number under “Quality Updates.”

Microsoft’s known issues page for KB5094126 will be updated as the investigation progresses. Bookmarking that page or following Windows Update channels on Twitter/X or the Microsoft Tech Community blog is the best way to receive official notification of a fix. In the meantime, the workarounds above should keep workflows smooth.

Looking Ahead

Patch Tuesday regressions are an unfortunate but periodic reality of modern OS maintenance. For its part, Microsoft has invested heavily in automated testing and the Windows Insider Program to catch bugs before they reach production, yet issues like this slip through. The Recycle Bin glitch is a reminder that even small UI-changes can have cascading effects when core subsystems are modified.

The upcoming July 2026 Patch Tuesday will likely bring a resolution, either rolled into the cumulative update or delivered as a standalone fix. Until then, Windows enthusiasts and IT professionals alike will be keeping a close eye on the Recycle Bin’s confirmation dialogs—and hoping the next update doesn’t accidentally rename their desktop icons to GUIDs.