Microsoft has officially acknowledged a bizarre bug introduced by its June 9, 2026 security updates that causes the Windows Recycle Bin to leak internal file names. Instead of showing the friendly name like Quarterly-Report.docx, the delete confirmation dialog now reveals a cryptic $R12345.docx. The company confirmed the issue on June 18 via the Windows Release Health dashboard, and it affects all supported versions of Windows 10 and Windows 11.
Users first noticed the glitch shortly after installing the June 2026 Patch Tuesday updates. When attempting to send a file to the Recycle Bin, the standard “Are you sure you want to move this file to the Recycle Bin?” dialog incorrectly substitutes the actual file name with the system’s internal $R identifier. For example, deleting presentation.pptx might prompt the user to confirm deletion of $R89ABCD.pptx. The bug is purely cosmetic—the file still lands in the Recycle Bin correctly and can be restored, but the wrong name can spark confusion, especially when deleting multiple files at once.
The problem stems from how the Windows shell translates Recycle Bin entries. Since Windows 95, the Recycle Bin has stored deleted files as pairs of hidden files: a $R file containing the actual data and a $I file holding the original name, path, and deletion timestamp. This double-file structure preserves metadata while allowing the original name to be restored. Under normal operation, the confirmation dialog reads the friendly name from the $I companion. The June security updates appear to have broken that lookup, causing the dialog to display the raw $R filename instead.
Security updates are the prime suspect because Microsoft explicitly ties the bug to the June 9 release. Patch Tuesday deliveries often include changes to core system components, and a change in how the shell handles calls to the Recycle Bin namespace could easily result in such a regression. While Microsoft hasn’t disclosed the root cause, the timing suggests that a fix for a security vulnerability inadvertently introduced this interface quirk. For example, a hardening of file name resolution might have blocked the shell from reading the companion $I file under certain conditions, leaving only the raw $R name visible.
The bug has been reported across multiple Windows editions, including Windows 10 22H2, Windows 11 23H2, and the latest Windows 11 24H2. Enterprise and consumer users alike have taken to forums to share screenshots of the strange dialog boxes, often fearing malware or file corruption. The consistency of the reports indicates a broad, update-related issue rather than isolated configuration problems.
Microsoft’s official notice, posted on June 18, confirms the behavior and states that the company is “working on a resolution.” No workaround is provided in the release health entry, but the company often suggests interim measures until a cumulative update fixes the issue. Typical guidance for Recycle Bin glitches includes disabling the delete confirmation dialog entirely or using Shift+Delete to permanently bypass the Recycle Bin. For users who rely on the confirmation prompt, the only reliable workaround is to ignore the garbled name, as the file still moves to the Recycle Bin as expected. Power users can verify this by checking the Recycle Bin after deletion—the file will appear with its correct original name inside the bin.
This is not the first time the Recycle Bin has been the center of a Patch Tuesday storm. In 2021, a Windows 10 update caused some users’ Recycle Bins to lose their ability to restore files, and in 2020, a bug prevented the icon from refreshing its full/empty state. The internal $R filename, while less destructive, is particularly jarring because it exposes a piece of Windows’ under-the-hood machinery that most users never see. For IT professionals and system administrators, $R files are familiar from scenarios like data recovery or forensic analysis, where scanning a corrupted drive reveals these temporary names. For everyday users, however, the sight of a dollar-sign file name can be alarming.
Despite the unsettling appearance, no data is at risk. Files deleted while the bug is active are still stored correctly with their $I metadata intact. Restoring a file from the Recycle Bin brings it back with its original name and path. The only practical impact is a temporary loss of clarity during the deletion step. If a user is deleting a batch of files and relying on the dialog to confirm which file is which, the $R names offer no help. This could lead to accidental deletions, but since the Recycle Bin keeps items until manually emptied, recovery is straightforward.
The bug highlights the complexity of Windows updates, where even minor security improvements can have unexpected side effects on decades-old UI elements. Microsoft’s monthly updates often contain hundreds of changes, and thorough testing of every dialog box across all supported configurations is a monumental task. The company has refined its approach over the years with increasingly sophisticated Insider preview rings and automated testing, but regressions still slip through. The good news is that the bug’s cosmetic nature means Microsoft can address it without the urgency of a out-of-band patch; the fix will likely land with the next scheduled quality update.
For the time being, users who are unsettled by the $R names can take several steps to reduce their exposure. Turning off the delete confirmation dialog is the simplest: right-click the Recycle Bin icon, select Properties, and uncheck “Display delete confirmation dialog.” This skips the prompt altogether and sends files directly to the bin. Those who prefer a safety net can switch to using Delete while holding the Shift key, which permanently deletes files without going through the Recycle Bin at all—though this forfeits the chance to restore them later. A more conservative approach is to delete files via the context menu on the Recycle Bin’s folder view, but that’s less convenient for daily use.
Another angle worth considering is whether the bug hints at a deeper security vulnerability that the June updates attempted to fix. If the patches altered how the shell parses file names in protected directories to prevent name-based attacks, the $R display issue could be a symptom of a more deliberate change. For example, a common exploit vector involves tricking users into deleting malicious files disguised with fake extensions. By tightening how Windows handles file metadata in the Recycle Bin flow, Microsoft might have inadvertently broken the friendly-name lookup. The company has not disclosed any CVEs directly related to this behavior, so it remains speculation.
Looking ahead, Microsoft’s track record suggests a cumulative update will arrive within a few weeks. The July 2026 Patch Tuesday is the most likely delivery vehicle. If the bug generates enough user complaints, a monthly preview update could arrive earlier. Enterprise customers with Software Assurance can also request a hotfix through their support channels, though the low severity of the issue probably doesn’t justify that route for most organizations.
In the meantime, the Windows community is having a field day with the exposed internal file names. Memes comparing $R files to government codenames and conspiracy theories about Windows “spying” on deletions have cropped up on social media. The incident serves as a reminder that even the most mundane operating system components work in ways that can surprise—and occasionally amuse—users when things go slightly wrong.
For those who want to track the official resolution, Microsoft’s Windows Release Health entry for this issue will be updated at https://learn.microsoft.com/en-us/windows/release-health/. The dashboard provides status changes and, once a fix is released, links to the update packages. IT managers should plan to test the fix in their environments before broad deployment, as it will likely involve another round of security-related file system adjustments.
Ultimately, the $R filename bug is a harmless but visible reminder that software updates can have unintended consequences. While it doesn’t compromise system security or file integrity, it underscores the importance of Microsoft’s transparency and rapid response when things go awry. Windows users can breathe easy knowing their files are safe, even if the dialog box is speaking in code.