Microsoft’s June 9, 2026 monthly security update introduced an unusual glitch that may unsettle users who rely on the Recycle Bin’s permanent delete confirmation dialog. Instead of displaying the familiar original name of a file about to be erased forever, the dialog now sometimes shows an internal placeholder—typically beginning with “$R” followed by a random-looking string. The company acknowledged the issue in a support note published shortly after the update’s release, confirming the behavior affects Windows 11 devices, and possibly certain Windows 10 builds still receiving security patches.

The bug does not alter the actual deletion process; files are still removed correctly and irreversibly. However, the misleading filename leaves users uncertain about what exactly they are about to delete, breaking a basic trust mechanism that has existed for decades. For individuals and IT administrators who frequently clear out the Recycle Bin, the mismatch introduces hesitation and, in worst cases, could lead to accidental permanent loss of important data if the user assumes the dialog refers to something else.

What Exactly Is Happening?

When a file is sent to the Recycle Bin, Windows renames it internally to prevent naming conflicts. The system assigns a name in the format $RXXXXXX.ext, where XXXXXX is a short alphanumeric sequence and .ext is the original file extension. Alongside this, a paired $IXXXXXX.ext file is created to store metadata—including the original name, original path, and deletion timestamp. Normally, when a user right-clicks a file in the Recycle Bin and selects “Delete” (or presses Shift+Delete), the confirmation dialog retrieves the original name from the associated $I file and shows it to the user.

After applying the June 9, 2026 updates, this retrieval fails in some scenarios. Instead of the human-readable original name, the dialog displays the raw $R identifier. The bug seems intermittent; multiple users on forums and social media reported that it happened with certain files but not others, and a second attempt sometimes showed the correct name. Microsoft’s initial investigation points to a race condition in the updated shell component responsible for parsing the $I metadata, likely introduced by a code change intended to improve Recycle Bin performance or security auditing.

The issue was first spotted by Windows Insiders shortly before the public release, but reports at the time were ambiguous. A few Reddit threads mentioned “weird filenames” during Recycle Bin cleanup, though most users attributed it to corrupted system files or third‑party shell extensions. It wasn’t until the June Patch Tuesday deployment reached a broader audience that the pattern became clear and Microsoft officially confirmed it.

Which Windows Versions Are Affected?

Microsoft’s known‑issues bulletin specifically lists Windows 11 versions 23H2 and 24H2 as impacted. Windows 10 22H2, which still receives security updates under extended support agreements, may also exhibit the glitch depending on the specific cumulative update package installed. The offending updates are:

  • KB5039212 for Windows 11 version 23H2 (build 22631.3737)
  • KB5039211 for Windows 11 version 24H2 (build 26100.840)
  • KB5039213 for Windows 10 version 22H2 (build 19045.4474) – reported inconsistently

Server editions appear unaffected, likely because the Recycle Bin confirmation dialog behaves differently on Windows Server by default. Enterprise customers who rely on Group Policy to suppress delete confirmations entirely will not see the bug, but the underlying file‑name resolution failure could theoretically impact auditing tools that depend on the same Windows Shell APIs.

Community Reaction and Workarounds

Within hours of the update’s release, Windows enthusiasts and IT support communities lit up with complaints. “I almost deleted a project folder because the dialog said I was removing $RL9A2T7.docx – I had no idea what that was,” wrote one user on a popular tech forum. Another recounted a near‑miss at a small law firm where the office manager nearly emptied the Recycle Bin during routine maintenance, only stopping because the garbled names raised an alarm.

Several makeshift workarounds surfaced before Microsoft issued official guidance:

  1. Restore the file first, then delete permanently outside the Recycle Bin. Restoring a file moves it back to its original location with its original name, after which a standard Shift+Delete bypasses the Recycle Bin entirely and shows the correct name in the confirmation. This method works but is cumbersome when cleaning many files.
  2. Use the command line or PowerShell. Running del or Remove‑Item directly on the Recycler folder bypasses the GUI dialog, but requires knowledge of the hidden C:\$Recycle.Bin structure and carries a higher risk of accidental mass deletion.
  3. Switch to a third‑party file manager. Tools like Total Commander or Directory Opus use their own delete dialogs and are not affected. However, deploying such software enterprise‑wide just to dodge a confirmation dialog is impractical.
  4. Disable the confirmation dialog entirely. Setting the Recycle Bin property to “Don’t move files to the Recycle Bin” forces permanent deletion immediately, which avoids the bugged dialog but also removes the safety net of the Recycle Bin.

Microsoft’s Response

On June 10, 2026, Microsoft published a support article confirming the behavior and explaining its root cause. The company stated that a fix is being developed and will be delivered in an upcoming out‑of‑band update, likely within a few weeks. In the meantime, the article suggests users who are uneasy with the misleading dialog can employ the first workaround above—restoring the file before deletion—or temporarily configure the Recycle Bin to bypass confirmation.

A Microsoft spokesperson added: “We understand the confusion this may cause and are actively working on a resolution. The dialog does not affect the actual deletion operation; the file that is removed is the one the user selected, regardless of the name displayed.” For enterprise customers, a Known Issue Rollback (KIR) via Group Policy is expected to arrive even sooner, allowing affected devices to revert to the old behavior without uninstalling the entire security update.

Technical Deep‑Dive: Why $R Names Appear

To understand why the bug manifests, it helps to know the inner workings of the Recycle Bin since Windows 95. When a file is deleted, FileDelete or the modern equivalent in the shell invokes SHFileOperation. The file is moved to the hidden Recycler (or $Recycle.Bin on NTFS) directory under a newly generated $R name. Simultaneously, a companion $I file is written containing the original path and name in Unicode. This metadata file is what allows the Recycle Bin view to show the original filenames and the “Restore” function to work.

When a user empties the Recycle Bin or deletes individual files from it, the shell iterates through the $R files. For each, it attempts to open the corresponding $I file, parse the original name, and display it in the confirmation dialog. The June 2026 updates changed how this iteration synchronizes access to the metadata files, likely to address a long‑standing edge case where rapidly deleting many files could momentarily show a blank or stale name. The new code contains a timing flaw: under certain system loads, the $I file isn’t read in time, and the dialog falls back to displaying the $R identifier as a placeholder.

The bug is also sensitive to storage drive speed. Complaints were more frequent on devices with older SATA SSDs or spinning hard drives, where I/O latency is higher. NVMe drives seemed less affected, which aligns with the race‑condition hypothesis. Antivirus real‑time scanning can exacerbate the delay, as the $I file is momentarily locked for scanning, causing the shell to time out and fall back to the $R name.

Historical Context: Similar Shell Bugs

This is not the first time Windows has suffered from Recycle Bin naming glitches. In 2019, a Windows 10 feature update caused the Recycle Bin icon to not refresh after emptying, leaving users with an icon showing files that were already gone. In 2021, a cumulative update introduced a problem where the original file name was truncated beyond 40 characters in the confirmation dialog. The current bug, while visually more alarming, does not break functionality, and history suggests Microsoft will roll out a fix promptly.

Still, the bug’s timing is unfortunate. June 2026’s Patch Tuesday addressed several critical security vulnerabilities, including a zero‑day in the Windows Print Spooler. Many organizations rushed to deploy the update without thorough testing, only to encounter the Recycle Bin issue during routine operations. IT admins expressed frustration, as the glitch undermines end‑user confidence at a time when security patches are supposed to increase stability.

How to Check If You Are Affected

Users who have installed the June 2026 updates can easily verify the bug. Place any test file into the Recycle Bin, open the Recycle Bin, right‑click the file, and choose “Delete”. If the confirmation dialog shows a name starting with $R, the bug is present. If it shows the original file name, your system may be unaffected, or the race condition simply didn’t trigger in that instance. Note that the bug can appear intermittently, so repeating the test a few times with different file types is advisable.

For managed environments, system administrators can query the Recycle Bin behavior remotely using PowerShell:

$shell = New-Object -ComObject Shell.Application
$recycleBin = $shell.Namespace(0xA)  # 0xA is the Recycle Bin
$items = $recycleBin.Items()
foreach ($item in $items) {
    Write-Host $item.Name
}

In affected systems, the name property may occasionally return the $R identifier when queried, though this is less common than the UI dialog misfire.

Looking Ahead: Upcoming Fix

Microsoft’s engineering team reportedly identified the faulty code change and is testing a corrected version of the shell32.dll library. The fix will be delivered via a cumulative update preview in the last week of June 2026, with broader deployment in the July 2026 Patch Tuesday. For organizations using Windows Server Update Services (WSUS) or Microsoft Endpoint Manager, groups can be set to “Test” rings to receive the preview early.

A Known Issue Rollback (KIR) policy for domain‑joined Windows 11 machines will be available through a special Group Policy administrative template. Admins can download the template from the Microsoft Download Center and configure it to revert the Recycle Bin dialog to its prior behavior without removing any other security fixes. That approach is recommended for mission‑critical workstations where user trust in the delete process is paramount.

Recommendations for Users and IT Pros

Until the official fix arrives, weighing the inconvenience of the bug against the serious security flaws patched on June 9 is essential. Disabling the Recycle Bin entirely or bypassing the confirmation dialog removes the visual confusion but also eliminates a layer of protection. For most home users, the safest path is to take an extra five seconds: if the $R name appears, cancel the deletion, restore the file, check its contents, and then delete it permanently via Shift+Delete.

IT departments should communicate the bug to employees through a quick email or intranet post. A simple message—“You may see odd filenames when deleting from the Recycle Bin; it’s a known visual bug and doesn’t affect which file gets deleted”—can prevent panic and help desk calls. For large fleets, deploying the KIR as soon as it becomes available will eliminate the issue entirely without waiting for the next cumulative update.

Power users can temporarily replace the default delete dialog with a script that restores files before deletion, but this is likely overkill for a transient cosmetic bug. The bug underscores a larger lesson: even mature operating systems can introduce surprising regressions, and thorough testing of every user‑facing dialog remains essential—no matter how small it may seem.

The June 9 update incident will likely be a short‑lived footnote in Windows’ long history, resolved within weeks. For now, the mildly unnerving sight of a gibberish $R filename in a familiar dialog serves as a reminder that internals are never far below the surface of even the most polished user interfaces.