Microsoft June 2026 Bug Exposes Recycle Update Filenames

Microsoft has confirmed a new bug, introduced with its June 2026 Patch Tuesday security update, that causes Windows to display internal Recycle Bin filenames instead of their original user-facing counterparts in file-deletion confirmation dialogs.

After installing the Windows security update released on June 9, 2026 (KB5094125), users attempting to permanently delete a single item from the Recycle Bin are greeted with a confirmation dialog showing the file’s internal system name, such as $Rxxxxx.ext, instead of the original filename.

The issue is purely cosmetic in scope the Recycle Bin’s file listing and the restore functionality both continue to correctly display and recover the original filename without any data loss.

Microsoft officially confirmed the bug on June 18, 2026, with the issue tracked against OS Build 26100.32995 under KB5094125. The Known Issue entry was last updated on June 18, 2026, at 19:27 PT.

Affected Platforms

The bug impacts a broad range of Windows client and server versions, including:

• Windows 11: versions 26H1, 25H2, 24H2, and 23H2
• Windows 10: version 22H2, Enterprise LTSC 2021, Enterprise LTSC 2019, and Enterprise LTSB 2016
• Windows Server: 2025, 2022, 2019, 2016, 2012 R2, and 2012

The wide platform spread means the issue affects both consumer and enterprise environments, including long-term servicing channel (LTSC/LTSB) deployments often used in critical infrastructure and regulated industries.

While the bug does not result in data loss, corruption, or any security vulnerability, the exposure of internal Recycle Bin naming conventions ($R prefix format) can cause user confusion, particularly in enterprise environments where help desk staff or end users may be uncertain whether a critical file is being targeted for deletion.

In managed environments, this could also interfere with automated deletion workflows or scripts that parse dialog output.

Microsoft has acknowledged that a workaround is available for enterprise-affected devices, but organizations must contact Microsoft Support for Business directly to obtain and apply it no self-service fix has been publicly released.

The company has stated it is working to ship a permanent resolution in a future Windows update but has not provided a specific timeline.

System administrators are advised to monitor the Windows Release Health dashboard for updates and notify end users of the cosmetic discrepancy to avoid confusion during routine file management.

Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.