**Microsoft** has confirmed a confusing **Windows** bug that causes different filenames to appear in the confirmation dialog when deleting a file from the Recycle Bin. "When permanently deleting a single item from the Recycle Bin, the confirmation dialog displays the internal Recycle Bin filename (for example, $Rxxxxx.ext) instead of the original filename," the company explained in a Thursday update to the Windows release health dashboard. "The Recycle Bin itself correctly displays the original filename, and restoring the item also restores it using the original filename." ### Widespread Impact Across Windows Versions While **Microsoft** didn't share how widespread this known issue is, it stated that it affects all supported **Windows** releases across both client and server platforms after installing the June 2026 security updates. The complete list of affected **Windows** versions includes: * Client: **Windows 11**, version 26H1; **Windows 11**, version 25H2; **Windows 11**, version 24H2; **Windows 11**, version 23H2; **Windows 10**, version 22H2; **Windows 10 Enterprise LTSC 2021**; **Windows 10 Enterprise LTSC 2019**; **Windows 10 Enterprise LTSB 2016** * Server: **Windows Server 2025**; **Windows Server 2022**; **Windows Server 2019**; **Windows Server 2016**; **Windows Server 2012 R2**; **Windows Server 2012**. ### Awaiting a Fix, Workaround Available for Enterprises **Microsoft** has indicated that its engineers are actively working on a fix for this bug, which will be delivered to affected systems in a future **Windows** update.  For businesses experiencing this issue, **Microsoft** has provided a temporary workaround. Organizations can contact **Microsoft's Support for business** to implement this mitigation. ### Recent Windows Issues This Recycle Bin issue is one of several problems **Microsoft** has addressed recently. Earlier this week, the company confirmed an issue that prevents third-party applications from launching **Word**, **Excel**, **PowerPoint**, **Access**, and other **Office** applications (or opening documents) on **Windows** systems after the June 2026 updates. More recently, on Thursday, **Microsoft** also resolved a known issue that caused the June 2026 security updates to fail on **Windows Server 2016** systems lacking the May **KB5087537** security update.