Microsoft has added a new known issue to the Windows Release Health Dashboard, confirming that the June 9, 2026 cumulative update KB5094126 can cause the Recycle Bin to display internal file identifiers such as $Rxxxxx instead of the original, user-friendly filenames. The issue, posted on June 19, 2026, is the latest in a string of problems linked to this month’s Patch Tuesday update, which users say also triggers unexpected BitLocker recovery prompts and breaks Microsoft Office applications.

The Recycle Bin bug is more than a cosmetic annoyance. When users attempt to restore deleted items, they are confronted with cryptic strings—for example, $R123456.txt—making it difficult to identify which file is which. Microsoft’s dashboard entry warns that the problem can affect all supported versions of Windows 11 and Windows 10 that have installed KB5094126 or related security-only updates. The company states it is investigating the root cause and working on a fix, with an expected resolution in a future cumulative update. No workaround is currently provided, leaving users to either memorize the corrupted labels or restore files blindly and rename them.

But the Recycle Bin glitch is not the only headache. Within hours of the June 9 rollout, IT administrators and home users flooded community forums with reports of BitLocker recovery screens appearing after the mandatory reboot. Affected devices demand a 48-digit recovery key before Windows will boot, a scenario that can lock users out of their systems entirely if the key was not backed up. While Microsoft has not yet acknowledged this problem on the Release Health Dashboard, the sheer volume of complaints suggests a systemic conflict between the update and certain TPM or Secure Boot configurations. Several system builders note that the issue seems more prevalent on custom-built PCs and laptops with recent firmware updates.

Adding to the frustration, many Office 365 subscribers report that Word, Excel, and Outlook crash on launch or fail to open after installing KB5094126. Error messages range from “The application was unable to start correctly (0xc0000142)” to vague Microsoft Office Click-to-Run configuration failures. A Reddit thread with over 1,500 upvotes details a temporary fix: uninstalling the update, performing an online repair of Office, and then re-applying the update while Office apps are closed. But such workarounds are not viable for enterprise environments where rolling back patches can take days and disrupt security compliance.

What Happens When You Open the Recycle Bin

The $Rxxxxx naming convention is not new to Windows internals. The Recycle Bin stores deleted files by renaming them according to a pattern: $R followed by a hash, while the original filename is preserved in an associated metadata file. When everything works correctly, the shell links the internal name to the user-friendly name. KB5094126 appears to break that shell integration, causing File Explorer to display the raw internal identifier. This leaves users staring at a list like:

$RYS3X9E.jpg
$RTQW1L2.docx
$R78ABCD.pdf

Restoring any of these files does return them to their original name on disk, but the confusion during the restore decision can lead to permanent data loss if users accidentally delete the file from the Recycle Bin to “clean up” the unrecognizable entries. One enterprise user reported that a helpdesk technician cleared out the Recycle Bin remotely, thinking it contained only junk, only to discover they had deleted critical project files.

BitLocker: When a Routine Reboot Turns into a Disaster

For organizations that rely on BitLocker encryption to protect sensitive data, the unintended recovery triggers are particularly alarming. Normally, BitLocker enters recovery mode when it detects a potential attack or fundamental hardware change—such as a BIOS update or disk controller swap. A routine OS update should not cause this. Yet dozens of corporate IT admins posted on the Windows Admin Center forum that domain-joined machines prompted for recovery keys after KB5094126, even though no hardware changes occurred.

Microsoft’s silence on the BitLocker issue is puzzling. The company’s standard protocol is to list known issues within 48 hours of widespread reports, but as of June 20, no dashboard entry exists. This leaves system admins scrambling. The workaround—suspending BitLocker before applying the update—is not always feasible when patches are pushed automatically via Windows Update for Business or WSUS. Worse, some users report that even after entering a valid recovery key, Windows boots but instantly triggers another recovery prompt on the next restart, suggesting the update may corrupt the TPM measurements persistently.

Office Breakage: More Than a Minor Inconvenience

Microsoft Office integration with Windows is deep. The Click-to-Run virtualization layer, background updater, and shared runtime components are sensitive to kernel-level changes. KB5094126 modifies the Windows kernel, win32kfull, and the NTFS driver—areas that can trip up Office’s licensing and sandboxing. Users experiencing Office crashes often see Event ID 1000 in the Application log pointing to msoia.exe or AppVIsvSubsystem32.dll. The only reliable resolution so far is to uninstall KB5094126, but that removes all security fixes for the month, including patches for two zero-day vulnerabilities.

One financial analyst who relies on Excel for real-time stock data found herself locked out of work for a full morning after the update. “I couldn’t even open a blank workbook,” she explained. “The IT team eventually rolled me back to the previous build, but I missed critical market movements.” Such stories underscore how a single flawed cumulative update can ripple through productivity and business continuity.

Microsoft’s Response History and Quality Concerns

This is not the first time a cumulative update has introduced a Recycle Bin filename bug. A similar issue appeared in October 2025 after KB5043290, though it was limited to Insider builds and fixed before a wider release. BitLocker recovery prompts have been a recurring pain point since Windows 11’s launch, often tied to Secure Boot DBX updates rather than OS patches—but the overlap with KB5094126 is hard to ignore.

Critics argue Microsoft’s lack of transparency is eroding trust. The Release Health Dashboard, once a model of proactive communication, now often lags behind user reports by weeks. By the time an issue is posted, system administrators have already spent hundreds of hours on workarounds. The delay in acknowledging the Recycle Bin bug—ten days after the update’s release—means countless end users likely thought their system was corrupted or malware-infected, prompting unnecessary and potentially harmful “fixes” from dubious websites.

Immediate Steps for Affected Users

Until Microsoft releases an official fix, users should consider the following:

  • For the Recycle Bin bug: Do not empty the Recycle Bin if you see $R filenames. You can restore files individually; they will regain their original names on the target location. Use Preview pane or Details pane in File Explorer—sometimes the modification date or file type can help identify the file.
  • For BitLocker recovery: If your device prompts for a recovery key, locate the 48-digit key from your Microsoft account (for personal devices) or your organization’s Active Directory/Azure AD. Once booted, open an elevated command prompt and run manage-bde -protectors C: -disable to suspend BitLocker temporarily, then restart. To avoid the issue before updating, suspend BitLocker via Control Panel > BitLocker Drive Encryption > Suspend protection.
  • For Office crashes: Uninstall KB5094126 by going to Settings > Windows Update > Update history > Uninstall updates. Then repair Office via Control Panel > Programs > Microsoft 365 > Modify > Quick Repair. After repair, you can attempt to reinstall the update with Office apps fully closed, but there is no guarantee the problem won’t recur.

Looking Ahead

Microsoft’s engineering team is reportedly working on an out-of-band patch to address the Recycle Bin display glitch, with rumors of a fix arriving before the end of June. The BitLocker and Office issues, however, remain in limbo. As organizations finalize their fiscal-year budgets and push for Windows 11 24H2 migrations, the stability of cumulative updates becomes a boardroom-level concern. The lesson for IT departments is clear: thoroughly test updates in a pilot group before broad deployment, and keep BitLocker recovery keys and Office installation media within arm’s reach. For the millions of home users who simply click “Check for updates” out of habit, the advice is more sobering: wait a week or two before installing any Windows patch, and always ensure your recovery key is stored somewhere accessible.