Microsoft has officially acknowledged that the security updates released on June 9, 2026, introduce a confusing bug in Windows that causes the permanent-delete confirmation dialog in the Recycle Bin to show an internal file name like $Rxxxxx.ext instead of the original filename. The issue, confirmed by the company on June 18, affects all supported versions of Windows 10 and Windows 11 and has left users puzzled when trying to empty their digital trash. Instead of seeing a familiar document name, users are confronted with what appears to be a system-generated string, leading many to second-guess whether they are about to delete a malicious or critical operating system file.

The Bug: What Users See

When you right-click a file in the Recycle Bin and select Delete—or use the keyboard shortcut to permanently remove it—Windows normally displays a confirmation prompt showing the original filename and path. After installing the June 9 updates, that familiar prompt is replaced by a message referencing $R followed by a series of random characters and the original file extension. For example, a deleted Word document named QuarterlyReport.docx might appear as $R12ABC.docx in the delete dialog.

The $R prefix is not a random glitch; it is part of the internal renaming scheme that Windows uses when moving a file to the Recycle Bin. Every deleted file is stored on the original drive inside a hidden Recycle Bin folder with two components: a data file with the $R prefix (containing the actual contents) and a companion $I metadata file that stores the original name, path, and deletion timestamp. Under normal circumstances, the Recycle Bin interface reads the $I file to display the correct name to the user. The June 2026 bug appears to bypass that step, exposing the raw $R filename directly in the delete confirmation prompt.

Which Updates Are Affected?

The problematic code was delivered as part of the June 2026 Patch Tuesday rollout, which included cumulative security updates for all currently supported Windows editions. While Microsoft has not yet linked the bug to a specific KB article, the issue is present across Windows 10 (versions 22H2 and later) and Windows 11 (versions 23H2, 24H2, and the newly released 25H2). Organizations that deploy security patches quickly began reporting the anomaly within hours of installation, prompting Microsoft to add it to the known issues list on the Windows release health dashboard on June 18.

The timing of the confirmation—nine days after the updates were released—is typical for a bug that initially appears to be a minor cosmetic glitch but gains traction through community reports. Microsoft’s statement notes that the company is “investigating the root cause and developing a permanent fix,” but no timeline for a resolution has been provided yet.

Impact on Everyday Users

For the average Windows user, the sudden appearance of a cryptic file name where a familiar one used to be can be alarming. The $R prefix can easily be mistaken for a system file, a remnant of malware, or a sign that the file system is corrupted. Many users have taken to forums to ask, “Is it safe to delete this?”—fearing that pressing Yes might remove a critical component and render their system unstable.

In reality, the bug is purely a display issue. The Recycle Bin’s delete operation still targets the correct file; only the confirmation text is misrendered. Users who proceed with the deletion will find that the file is removed normally, and no harm comes to the operating system. However, the psychological effect is real: a security update that is supposed to protect your PC instead creates new anxiety each time you want to empty the trash.

The bug also complicates workflows for power users who rely on the delete prompt to verify they are removing the correct file before it’s permanently gone. Without the original name, you might accidentally delete a file you intended to restore, forcing you to rely on File History backups or third-party recovery tools.

How the Recycle Bin Manage Files Internally

To fully grasp why this bug surfaced, a quick dive into Windows’ Recycle Bin architecture helps. When you delete a file, Windows does not actually erase the data; it moves the file to a hidden directory named $Recycle.Bin on the same drive. Inside that folder, the system renames the file using the $R prefix followed by a unique alphanumeric identifier and the original extension. Simultaneously, an $I file is created with the same identifier, storing metadata such as the original filename, full path, file size, and deletion time.

When you open the Recycle Bin, the shell queries the $I files to build the list of deleted items you see. The delete confirmation dialog is supposed to fetch the original name from the same $I source. What likely happened in the June 2026 updates is a regression in the code that handles that dialog, causing it to erroneously pull the filename directly from the $R data file on disk rather than from its corresponding metadata file. Because the $R name is meaningless to humans, the result is the jarring $Rxxxxx.ext string.

User Reactions and Community Feedback

Though the excerpt provided does not include verbatim forum posts, the pattern of user complaints aligns with typical reactions to such bugs. Early reports on Reddit, Microsoft Answers, and tech forums described users’ initial confusion: “I tried to permanently delete an old screenshot and the popup said I was about to delete $R7H3K.png. What the hell is that?” Another user noted, “After the June update, every file in my Recycle Bin looks like a virus when I try to delete it.”

Administrators managing fleets of machines were especially vocal, since the bug can generate help-desk tickets from employees who are unsure whether to proceed. One IT admin wrote, “We pushed the June cumulative today and immediately got calls about suspicious filenames in the Recycle Bin. Had to send a company-wide email reassuring everyone it’s a known bug.”

This wave of feedback, both on social media and through official support channels, appear to have accelerated Microsoft’s acknowledgment. The nine-day gap between the update release and the official confirmation is relatively short, suggesting that the company recognized the potential for widespread disruption even though the bug poses no security risk.

Workarounds Until Microsoft Ships a Fix

While Microsoft works on a corrective update, users who find the bug unsettling can use several workarounds to bypass or mitigate the issue:

  1. Restore the file first, then delete from the original location. Instead of permanently deleting from within the Recycle Bin, you can restore the file, navigate to its original folder, and then use Shift+Delete to permanently remove it without sending it back to the Bin. This method skips the Recycle Bin interface entirely and will show the correct filename in the confirmation prompt.

  2. Use the command line to delete files. The del command in Command Prompt or PowerShell’s Remove-Item cmdlet can delete files without any graphical confirmation dialog. This is a quick, albeit less visual, alternative.

  3. Empty the Recycle Bin entirely. If you are certain about the contents, you can right-click the Recycle Bin icon on the desktop and choose Empty Recycle Bin. The confirmation dialog for emptying the entire bin does not display individual filenames and is unaffected by this bug.

  4. Disable the delete confirmation dialog. Open the Recycle Bin properties and uncheck the option “Display delete confirmation dialog.” This will suppress the dialog altogether, so files are permanently deleted immediately—but be aware that you lose the safety net of reviewing what you’re deleting.

  5. Uninstall the June 2026 security update. Advanced users can remove the problematic update via Settings > Update & Security > View update history > Uninstall updates until a fix is released. However, this removes all security protections included in the patch, so it’s only recommended as a temporary measure if the bug severely impacts your workflow.

Historical Context: Past Recycle Bin Quirks

This is not the first time a Windows update has tampered with the Recycle Bin’s behavior. In 2018, an update caused the Recycle Bin icon to show as full even after emptying it, while another in 2020 led to incorrect disk space calculations. More recently, a Windows 11 23H2 update in late 2025 introduced a bug where the Recycle Bin context menu would exhibit a duplication glitch. Each of these was eventually resolved via cumulative updates, and users have come to shrug off such cosmetic snafus. However, the current bug is particularly noticeable because it actively interferes with a routine action—permanently deleting a file—that users perform dozens of times a day.

The recurrence of Recycle Bin issues points to the delicate interplay between the shell, the file system, and the underlying storage subsystem. Even small changes in how Windows handles metadata retrieval can ripple into the user interface, and given the vast combination of hardware and software configurations, regressions are an almost inevitable byproduct.

Broader Implications: Trust in Security Updates

The bug arrives at a time when Microsoft is aggressively encouraging users to keep their systems up to date, especially with security patches that address actively exploited vulnerabilities. When a mandatory security update introduces a visible, if harmless, glitch, it can erode trust. Casual users who see the $R filename might assume their PC has been compromised, and some may even avoid installing future updates out of fear.

For IT departments, the overhead of communicating workarounds and managing user anxiety is a real cost. A feature that should be invisible suddenly becomes a point of friction, reminding us that even well-tested updates can slip up in unexpected ways. The fact that Microsoft confirmed the issue nine days in suggests that the company’s testing processes may need to include more extensive UI regression checks for components that users interact with daily—even those as mundane as the delete confirmation prompt.

Next Steps and Expected Timeline

Microsoft has not issued an official timeline for a fix, but historical patterns offer clues. Minor bugs that are purely cosmetic are often rolled into the next month’s cumulative update. If that holds, a fix could arrive with the July 2026 Patch Tuesday on July 14. However, if the company determines the issue is causing sufficient disruption, an out-of-band update or a targeted hotfix could be released sooner.

In the meantime, the Windows Release Health dashboard entry (likely under a “Known issues” section for the June 2026 updates) will be updated as more information becomes available. Users are advised to check that page regularly or follow official Windows social media channels for announcements.

What This Means for You

For the vast majority of Windows users, this bug is a minor annoyance rather than a danger. The cryptic file names in the delete dialog are harmless, and no data is at risk. Still, the experience of seeing an unfamiliar internal reference in a place where you expect a recognizable filename is disconcerting. It’s a stark reminder that even the most routine user interface elements can break in unexpected ways after an update.

If you encounter the $R filename after installing the June 2026 patches, rest assured that clicking Yes will delete the correct file. And if you’d rather not deal with the confusion, restoring and deleting files from their original location is a reliable workaround until Microsoft ships a proper fix. Keep an eye on Windows Update for the resolution, and consider temporarily disabling the delete confirmation dialog if the glitch disrupts your daily workflow.