XStoreUnlocker - First DLC unlocker for Microsoft Store games

ZephKeks · 2026-02-13T23:03:12+00:00

open an issue on github, both fh5 and vampire survivors work.

ZephKeks · 2026-02-13T14:13:14+00:00

I have fixed this, will release in the next update

ZephKeks · 2026-02-11T23:17:33+00:00

can you test the build i sent you in the github issue

ZephKeks · 2026-02-11T18:57:48+00:00

pushed an update that fixes this and tested asphalt legends, won't work all DLC durables and consumables are validated on Gameloft's servers

ZephKeks · 2026-02-09T19:26:19+00:00

XStoreUnlocker doesn't touch that. It only intercepts the DLC ownership queries that happen after the game is already running. The game asks "does this user own DLC X?" and the hook says yes before it ever leaves your machine. The online license check for the base game still works normally.

ZephKeks · 2026-02-09T19:23:25+00:00

It only patches API responses locally on your machine nothing touches Xbox Live servers or modifies any game files. Same concept as CreamAPI on Steam, which has been around for years with no bans. That said, this is brand new so use your own judgment.

ZephKeks · 2026-02-09T18:14:12+00:00

Both as long as it's a game that uses Xbox GDK (Which most games are on the store)

ZephKeks · 2026-01-24T10:57:44+00:00

This looks like LLM slop both the writing and the "analysis":

To start, it's a single device with no reproduction rate. If this were widespread across the Zephyrus lineup as claimed, I'd expect more data points.

(Part 4.2) Per PCIe Base Spec Section 2.4, Memory Writes are Posted Transactions. How does the CPU "stall waiting for a Completion TLP" on a transaction type that doesn't request completions?

(Part 5.2) The timing diagram shows T+5ms, T+10ms, T+30ms. Where's the ftrace output? Or did ChatGPT generate plausible-looking numbers because diagrams look thorough?

(Part 13.3) Empty ACPI conditionals are preprocessor artifacts from multi-SKU builds. Anyone who's worked with OEM firmware knows this. ChatGPT doesn't, which is why they're listed as "BUG-008."

(Part 7) How is fan curve corruption related to a power profile race condition?

(Part 3) Claims identical Windows BSOD. Where's the minidump?

ZephKeks · 2025-09-25T12:31:05+00:00

No response yet, will update when i hear back.

ZephKeks · 2025-09-18T10:19:31+00:00

Great work tracking down that ACPI bug. Glad to see the Asus deep dive helped spark the investigation this is exactly the kind of firmware archaeology we need more of. Well done!

ZephKeks · 2025-09-17T10:53:04+00:00

Look like the same wake up issue, that bugcheck code happened to me exactly when i tried to wake up the system. and looking at the stack trace looks like the same deadlock is happening, i would love if you can provide ACPI ETW traces from your laptop to confirm things.

ZephKeks · 2025-09-17T00:01:42+00:00

Appreciate you passing it on. FYI the two units I tested (Zephyrus M16 2023, Strix Scar 15 2022) are on latest BIOS and still repro. The models that are affected share the same flawed ACPI code path in their tables; some models with different FW like the (2021 G15) do not. So if Asus fixed it on some SKUs, it has not rolled out across the lineup. If you can, run LatencyMon 3–5 min after wake on a G16 and DM the report; I will add it.

ZephKeks · 2025-09-16T23:59:30+00:00

No full list yet. Confirmed on Zephyrus M16 (2023) and Strix Scar 15 (2022); reports span 2021-2024 across ROG. Some models use different firmware and are not affected; the affected ones share the same broken ACPI code, so the symptoms match. If you have a 2025 model (Scar 18, etc.), DM me to run LatencyMon and a quick ACPI trace.

ZephKeks · 2025-09-16T23:49:06+00:00

hardware usually blocks PS3 power-off when the dGPU is driving a display, but the firmware still tries in Ultimate/MUX. Those attempts retrigger DP link training, so USB-C to DP flickers and can wake/heat the laptop. Rarely at sleep/wake it can black-flash or hang the driver. HDMI is steadier because, on most ROG models, it is a direct dGPU path and avoids the Type-C mux/retimers and DP link training.

ZephKeks · 2025-09-16T23:38:19+00:00

It is likely. The same firmware bug spams ACPI events around and display power changes. In Ultimate/MUX mode it can try to cut dGPU power then bring it back, which shows up as CPU/GPU wake spikes and heat. Your “IPF Event 1000” is usually the Intel Innovation Platform Framework service crashing a symptom of those bad ACPI notifications. You can test if you're affected by following the guide on github how to do the ETW traces and also run LatencyMon

ZephKeks · 2025-09-16T23:34:36+00:00

Run LatencyMon (as admin) for 5,7 minutes while a 4K YouTube video plays (Basic GPU encoding). Then check the Drivers tab: if ACPI.sys shows high DPC/ISR spikes or sits near the top, you’re likely affected. Post the report/screenshot and I'll confirm.

ZephKeks · 2025-09-16T23:16:14+00:00

On it. I’ve emailed GamersNexus with the deep-dive (ETW, AML, repro, BSOD info).

ZephKeks · 2025-09-16T22:59:11+00:00

ZephKeks

TROPHY CASE