Microsoft: June 2026 Windows updates break Recycle Bin prompts
Microsoft confirms a bug in the June 2026 Windows updates where the Recycle Bin’s delete confirmation shows internal filenames (e.g., $Rxxxxx.ext) instead of the original names for permanently deleted items; the Recycle Bin and restore still display the original name. The issue affects all supported Windows client and server releases after the June 2026 updates (including Windows 11 26H1/25H2/24H2/23H2, Windows 10 22H2 and LTSC editions, and Windows Server 2012–2025). A fix is being developed for a future update, with a temporary workaround available for businesses via Microsoft Support for Business.
MICROSOFT JUNE 2026 WINDOWS UPDATES BREAK RECYCLE BIN PROMPTS
OverviewMicrosoft has confirmed a confusing bug introduced with the June 2026 security updates that affects the Recycle Bin prompt when permanently deleting a single item. In this scenario, the confirmation dialog displays the internal Recycle Bin filename (for example, $Rxxxxx.ext) instead of the original, user-friendly filename. The Recycle Bin itself shows and restores the item using the original filename, but the deletion confirmation message can be misleading and confusing for users.
What happens
- When a user chooses to permanently delete a single item from the Recycle Bin, the dialog presents an internal, system-generated filename rather than the file’s original name.
- Restoring the item from the Recycle Bin continues to use and display the original filename.
- The issue appears across multiple Windows editions and builds after applying the June 2026 updates, leading to potential confusion during file management tasks.
Affected systemsThe bug is reported to affect all supported Windows releases across both client and server platforms following the June 2026 security updates. The complete list of affected 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
Official stance and current statusMicrosoft has acknowledged the behavior and noted that engineers are actively working on a fix. A resolution is planned for a future Windows update and will be rolled out to affected systems when available. In the interim, users should be aware that the Recycle Bin continues to display and restore files with their original names, while the deletion confirmation dialog may show the internal filename.
Workarounds for businessesFor organizations affected by the issue, Microsoft has indicated the existence of a temporary workaround. To apply this workaround within an organization, the recommended path is to reach out to Microsoft’s Support for Business. A tailored workaround can be provided to mitigate the impact until a formal update is released. This approach is aimed at minimizing user confusion and ensuring uninterrupted file deletion workflows in business environments.
Related Windows update and compatibility notesThe June 2026 updates have been associated with other issues as well:
- Earlier in the week, Microsoft confirmed problems that block third-party applications from launching or from opening Office documents (Word, Excel, PowerPoint, Access, etc.) after installing the June 2026 updates.
- More recently, Microsoft issued a fix for a separate problem where the June 2026 security updates could fail to install on Windows Server 2016 systems that did not have the May KB5087537 installed.
- Additional context around the broader update cycle indicates Microsoft continues to address a range of compatibility and stability concerns as part of the June 2026 release wave.
Notes and context
- The Recycle Bin’s internal naming behavior only appears in the deletion confirmation dialog; standard operations within the Recycle Bin (viewing, restoring, or deleting items permanently from within the bin) continue to function using the correct, original filenames.
- Microsoft’s ongoing investigations emphasize that the issue is not isolated to a single build or edition but spans multiple supported Windows versions after applying the June 2026 security updates.
Related articles (for further reading)
- Microsoft confirms April Windows updates cause backup failures
- Microsoft fixes Windows update failures linked to WUSA installer
- Microsoft fixes BitLocker recovery bug on Windows Server 2025
- Recently leaked Windows zero-days now exploited in attacks
- Microsoft fixes Remote Desktop warnings displaying incorrectly
Security and IT teams are encouraged to monitor the official Windows Release Health dashboard and Microsoft Support channels for the latest guidance and the rollout schedule of the forthcoming fix. In the meantime, awareness of the dialog’s wording and the distinction between the displayed internal filename and the original filename can help reduce user confusion when managing files after the June 2026 updates.