Microsoft just handed PC gamers a Trojan horse, and it’s shaped like four old Xbox games.
When Microsoft launched Xbox Backward Compatibility on PC with BLiNX: The Time Sweeper, Conker: Live and Reloaded, Crimson Skies: High Road to Revenge, and Fuzion Frenzy, most people assumed it was exactly what it looked like: an original Xbox emulator bundled inside the Xbox app. That’s not what’s actually happening.
Within hours of the launch, dataminers cracked open the files and found something far weirder sitting underneath. The Xbox emulator running on your PC right now is actually a full Xbox 360 emulator, quietly booting an Xbox 360 environment first, then launching XeFu, the Xenon Fusion emulator that the 360 itself used back in 2005 to play original Xbox discs.
So yeah, it’s an emulator inside an emulator inside your gaming PC. I’ve been following backward compatibility news for a while, and honestly, this is one of those things that sounds almost too convoluted to be real, except it is, and Microsoft built it on purpose.
What is XeFu and why does it matter
XeFu, short for Xenon Fusion, isn’t new. Microsoft built it years ago to let the Xbox 360’s PowerPC hardware run original Xbox games, which were designed for a completely different x86 chip. Michael Brundage, an engineer who worked on the original project, confirmed the emulator executable was literally named xefu.xex. It’s been sitting inside Xbox 360 firmware this whole time, quietly doing its job for two decades.
What nobody talked about is how Microsoft would reuse it for PCs. The discovery came from an X user going by TheLunarixus, who dug through the Windows package for Fuzion Frenzy and found XEX2 and STFS file signatures, plus kernel strings including “XENON KERNEL EXITING. ” Those are 360-era fingerprints, not original Xbox ones. Security researcher Milenko, along with a modder known as Kirby0Louise, went even deeper and confirmed the games ship as Xbox 360 Games on Demand containers, the exact same packaging Microsoft used for digital 360 releases over a decade ago.
Here’s what’s interesting: this isn’t some hacky workaround. It’s the same layered approach Microsoft already uses on Xbox Series X and Series S, where original Xbox titles run through a 360 emulation layer called Xe03, sometimes referred to as Fission. Windows PCs are apparently just inheriting that same architecture. In my opinion, that’s actually a smart move. Why build a brand new original Xbox emulator from scratch when you already have a proven one buried inside 20 years of 360 engineering?
The buried stat nobody’s talking about
This is the part of the story that most people are sleeping on. The team behind the XWine1 translation layer project didn’t just find the 360 emulator sitting there unused. They actually got it running Xbox 360 games instead of original Xbox titles, with what they described as “varying degrees of success.” That’s a real, working proof of concept, not a theory.
Developer Neo Te Aika went further and found that because the games ship as standard Xbox 360 GOD containers, they can be extracted with existing GOD tools and converted into standard Xbox 360 ISOs. That opens up a pathway, at least technically, for other Xbox 360 software to load through Microsoft’s own official emulator. I didn’t expect this angle when I started digging into the story, and that’s exactly why it matters. Microsoft didn’t just build tech for four launch games. It shipped the foundation for its entire 360 back catalog and didn’t tell anyone.
Why Microsoft probably planned this all along
Sources suggest this isn’t an accident Microsoft is scrambling to cover up. The original PC backward compatibility announcement never claimed exclusivity to original Xbox titles. It only promised to “make it easier to play classic Xbox games from the past across PC and handhelds,” language vague enough to leave 360 support on the table the whole time.
It also lines up with earlier reporting. A known leaker going by eXtas1s previously claimed Microsoft was working with the Xenia Canary team, the group behind the popular open source Xbox 360 emulator, on an internal project reportedly called “Xbox Classics.” According to that leak, the plan involves rolling out enhanced versions of Xbox 360 and original Xbox games across PC, Game Pass, and cloud gaming to coincide with Xbox’s 25th anniversary in November 2026, arriving in two separate waves. Titles like Fable 2, Skate 3, and Batman: Arkham Asylum were named as candidates for the upgraded treatment.
If the current trajectory holds, it looks like Microsoft is deliberately staging this rollout rather than rushing it. Ship a small, low-risk batch of four original Xbox games first, let the community quietly confirm the underlying tech works, then formally announce 360 support once the anniversary marketing window hits. I actually think this is the right call from a business standpoint, even if it’s frustrating for anyone who wants Skate 3 running on their gaming PC tomorrow.
What this means for PC gamers
Not every Xbox 360 game is going to boot cleanly through this method right away. Microsoft’s official backward compatibility releases bundle game-specific patches and configuration files alongside the emulator itself, so titles outside the currently supported list may need extra work or might not launch at all. The early community tests reflect that, with mixed success across different 360 titles.
Still, having a legitimate, Microsoft built Xbox 360 emulator already active on millions of Windows machines is a genuinely big deal for game preservation. This is one of those things I genuinely got excited about the moment I saw it, mostly because it sidesteps the legal gray area that’s followed fan made emulators like Xenia for years. If Microsoft leans into this, the Xbox 360 could become one of the most accessible console libraries in gaming history, no rare hardware or dusty second hand discs required, and this Xbox emulator groundwork is exactly how it gets there.
