If you permanently deleted a file from the Recycle Bin last month and saw a prompt asking to confirm deletion of something like “$R7A3B2C.doc” instead of your actual document name, you weren’t alone. Microsoft’s July 14, 2026 cumulative update (KB5099414) for Windows 11 23H2 stomps out a confusing UI bug introduced in June’s security patches that swapped original filenames for internal Recycle Bin codes.

A Jarring Glitch in the Recycle Bin

The bug surfaced for some users after installing the June 9, 2026 security update (KB5093998). When they selected a file in the Recycle Bin and chose “Delete” to permanently remove it, the confirmation dialog didn’t show the familiar filename. Instead, it displayed an internal identifier—a string beginning with “$R” followed by a hash and the correct extension, such as $R123456.docx. This made it impossible to verify which file was about to be erased, causing alarm for anyone deleting sensitive documents or trying to clean up with certainty.

The anomaly was only skin-deep. The Recycle Bin’s list view continued to show the proper file names, and restoring a file brought it back with its original name intact. Even the permanent deletion itself worked correctly—the file was gone for good. As Microsoft later confirmed, this was purely a presentation error in the confirmation dialog, not a data-loss or corruption risk.

What Went Wrong with the Delete Dialog

Windows stores deleted files inside the Recycle Bin under internal names. The system maps these back to the user-friendly original names when displaying items in File Explorer. After the June patches, that mapping failed in one specific scenario: the prompt that appears when you permanently delete a single item from the Recycle Bin. Instead of the original name, the dialog showed the raw, internal $Rxxxxx.ext string.

The bug didn’t affect multi-file deletions, nor did it alter the behavior of the Recycle Bin’s file list or restore function. Still, the experience was jarring. A user trying to double‑check they were deleting the right file would see an unrecognizable code, undermining confidence in the OS.

Who Got the Fix and When

The correction isn’t confined to a single patch. Microsoft addressed the glitch across several Windows versions through different cumulative updates, with staggered release dates:

  • Windows 11 24H2 and 25H2 received the fix earliest, via KB5095093 on June 23, 2026—an optional preview update that later rolled into July’s Patch Tuesday.
  • Windows 11 23H2 gets the fix with July 14’s KB5099414, which bumps the OS build to 22631.7376. Microsoft’s release notes explicitly list the Recycle Bin dialog issue as resolved in this update.
  • Windows 10 22H2 is served by KB5099539 (also July 14), and Windows Server 2022/2025 receive analogous patches in their July servicing stacks.

The July 2026 security updates are cumulative, so installing the latest patch for your version of Windows delivers the fix automatically. For Windows 11 23H2 users, KB5099414 is the key. If you’re on a newer release (24H2 or 25H2), you likely already have the fix if you installed the June 23 preview or the July cumulative update.

What This Means for You

For most home and small-business users, the takeaway is simple: after applying the update, the Recycle Bin’s permanent-delete dialog will once more show the file’s original name. No extra configuration is needed. You can resume deleting with confidence.

If you’re an IT administrator managing fleets, you’ll want to verify that devices are current. Because the bug only affected the UI, there’s no need to run recovery tools or modify Group Policy. However, the patch cadence matters for deployment planning:
- Devices on Windows 11 23H2 must receive KB5099414 or a later cumulative update.
- Devices already on 24H2/25H2 should be checked for KB5095093 (or any update from July onward).
- Windows 10 and Server installations have their own KB articles—confirm via Microsoft’s release health dashboard or WSUS.

A practical step is to check the OS build number (winver or Settings > System > About). For 23H2, build 22631.7376 or higher indicates the fix is in place.

Steps to Resolve and Verify

  1. Install the latest cumulative update through Windows Update, WSUS, or Microsoft Update Catalog. For Windows 11 23H2, that’s KB5099414.
  2. Restart your PC after installation—the fix takes effect immediately.
  3. Test it: Move a test file to the Recycle Bin, then try to permanently delete it. The confirmation dialog should show the file’s actual name, not the $R code.

If you’re still seeing the cryptic string after updating, ensure the system rebooted fully. If the problem persists, the update may not have applied correctly; check Windows Update history for error codes and consider downloading the standalone package from the Microsoft Update Catalog.

The Bigger Picture

This bug is a reminder that even minor UI misfires can erode trust, especially when Windows’ own interface obscures critical information. The Recycle Bin’s internal naming isn’t new—it’s been part of the OS since the Windows 95 era—but the June 2026 updates inadvertently disrupted the layer that keeps those internals hidden from users.

Microsoft’s rapid patch cycle for 24H2/25H2 shows an increasing willingness to ship out-of-band fixes for quality issues, a practice that accelerated after the rocky Windows 11 launch. However, for those still on 23H2, the wait until July 14 was longer. With 23H2 Enterprise and Education reaching end of servicing on November 10, 2026, organizations still running that version should prioritize a move to a current release to avoid gaps in both security and quality fixes.

For now, the Recycle Bin glitch is resolved. If you skipped the June updates or hesitated, there’s no longer a reason to hold back—installing the July update patches this annoyance and dozens of other security vulnerabilities.