Fix ERROR_GRAPHICS_DATASET_IS_EMPTY (0x0026234B)

Cause #1: Corrupted or incompatible GPU driver

This is the big one. ERROR_GRAPHICS_DATASET_IS_EMPTY happens because the graphics driver can't supply the display metadata Windows Mixed Reality needs. I've seen it most on systems that just did a Windows update or updated their GPU driver from the manufacturer's website without doing a clean install. The driver loads, but the display dataset is missing or corrupt.

The fix: Uninstall your current GPU driver completely using Display Driver Uninstaller (DDU). Don't bother with Device Manager uninstall — it leaves crap behind that causes this exact error. Reboot into Safe Mode, run DDU, uninstall the driver, then reboot normally and install the latest driver from NVIDIA, AMD, or Intel. For Intel integrated graphics (common on laptops), grab the driver directly from Intel's site, not Windows Update.

After the clean install, reboot one more time and test WMR. In my experience, this alone fixes the error 8 out of 10 times.

Cause #2: Corrupted Windows Mixed Reality software stack

If the driver reinstall didn't work, the WMR portal itself might be hosed. This happens after a botched Windows feature update or if you've uninstalled/reinstalled the Mixed Reality Portal manually. The dataset error often shows up right when you launch the portal — it can't find the metadata files that describe the headset's display.

The fix: Reset WMR completely. Open PowerShell as admin and run:

Get-AppxPackage -Name Microsoft.MixedRealityPortal | Remove-AppxPackage

Then reinstall it from the Microsoft Store. Don't skip this — a simple repair doesn't clear the corrupt dataset. After reinstalling, when you launch the portal, it'll re-download the headset's display configuration fresh from Microsoft's servers. That's key.

One more thing: if you're on Windows 11 22H2 or later, check that the "Windows Mixed Reality" optional feature isn't broken. Go to Settings > Apps > Optional features and make sure it's listed. If it's missing, add it back. I've seen Windows updates remove this feature silently.

Cause #3: Headset firmware or hardware connection issue

Less common, but I ran into this on a Samsung Odyssey+ last year. The headset itself wasn't reporting its display EDID correctly over HDMI or DisplayPort. This can happen if the cable is loose, the connector is dirty, or the headset firmware got corrupted during an interrupted update.

The fix: First, physically reseat all cables — both at the headset end (if detachable) and at the PC. Shut down the PC, unplug everything, wait 30 seconds, then reconnect firmly. For the Samsung Odyssey and HP Reverb G2, check that the USB and video cables are fully seated — they click into place.

If that doesn't work, update the headset firmware. For WMR headsets, firmware updates come through Windows Update. Go to Settings > Windows Update > Advanced options > Optional updates and look for any driver or firmware updates for your headset. Install them, reboot, test again.

As a last resort, try the headset on a different PC. If the error follows it, the headset's display controller might be toast. But I've only seen that twice in 14 years — it's rare.

Quick-reference summary table

Bottom line: Start with the GPU driver. That's where 90% of these errors live. If you're still stuck after trying all three, check the Windows Event Log under System > Display for any related error codes. I've seen a few cases where a failing USB controller on the motherboard caused this — but that's a rare edge case. Try a different USB 3.0 port first.