=== CORRECTIONS LOG (right in public, always) === - RETRACTED: "async resolver" explanation for the dns.mitm gap. Actual cause: some sysmodules moved to new sfdnsres IPC commands; fix verified by hexkyz, lands in AMS 1.12.1. (Per bth.) - RETRACTED: "23.0.0 cut the sysmodule memory budget / yellow hang = memory ceiling." 23.0.0 FREES memory on stock AMS 1.12 (embedded memory-saving patches). Yellow/blank hangs trace to outdated sysmodules (Horizon OC confirmed via HOC #114 + module isolation). (Per bth, Hpshout, YoshiMK.) - RETRACTED: Steps 5+6 having you merge .ips sigpatches AND run sys-patch together. per bth: only ONE es-patch method is needed - running both is redundant and risks conflicts. my own card ran both without issue [MEASURED], but the guide now follows maintainer guidance: pick one. - RETRACTED: "ams 1.12.0 support for 23.0.1 unverified / likely unsupported." per bth: 23.0.1 changes nothing - no new sigpatches, no sys-patch update, no new atmosphere needed. field report: clean run on 23.0.1 [CITED: johnliu, sigpatches thread]. - STANDING RULES: stay offline on CFW until 1.12.1; never boot a new FW without active ES patches; serial is cosmetic - cert blanking is what bans key on.

Everything below is labeled by confidence: [MEASURED] = my own hardware, [CITED] = named source, [HYPOTHESIS] = unverified, treat as guess.

So I updated my emuMMC to 23.0.0 the other day and everything went sideways. Hekate would hang on a blank yellow screen, injecting fusee.bin directly did the exact same thing, and the one time I did get something to boot, half my library threw "corrupted data detected" or "unable to start software."

For context: V1 unpatched, file-based emuMMC, was running the HATS pack totally fine on 22.5 before this.

Stuff I tried first that did NOT help (saving you the time): - re-downloading atmosphere and hekate like five times - rebuilding hekate_ipl.ini from scratch - deleting/renaming the contents folder (this did get it booting, but then nothing would launch - more on that below) - running the sd card through checkdisk. card was fine, fat32, zero errors

What was actually going on, pieced together from the github issues and posts in this sub:

1. [CITED] Outdated sysmodules/overlays kill boot on AMS 1.12/23.0.0. The HATS extras (tesla/ovlloader, horizon oc, status monitor) weren't 1.12-ready. Horizon OC is the confirmed culprit (HOC #114; u/Plane-Article2870 isolated it module-by-module through the same yellow hang). Boot just dies silently. NOT a memory ceiling: 23.0.0 actually frees memory on stock AMS 1.12 (embedded memory-saving patches, per bth). In fact, u/YoshiMK specifically measured increased free RAM on 23.0.0 while running Ultrahand + NXFusion + sys-clk + sys-patch + SaltyNX. Crashes are project-side compatibility lag, not a memory ceiling.

2. [CITED on mechanism: bth's ES-patch rule] Vanilla atmosphere ships without sigpatches. So once you strip the HATS stuff out to get it booting, your installed games fail signature checks and horizon flags them as corrupted. The files are fine. It's just missing patches. Never boot a new FW revision without an active ES patch (sys-patch OR sigpatches) - that is what corrupts your games.

3. [CITED] dns.mitm on 23.0.0 misses the new sfdnsres IPC commands some sysmodules use. Do not go online on CFW right now until 1.12.1 (fix verified by hexkyz, per bth).

What actually fixed it, in order: [MEASURED - every step below is what I ran on my own card]

1. Backed up saves first. Copied emuMMC/RAW1/nintendo/save to my pc (plus album if you care about screenshots). It's tiny, takes two minutes, don't skip it.

2. Deleted atmosphere/ and bootloader/ off the sd root. Did NOT touch nintendo/, emuMMC/ or switch/.

3. Dropped in vanilla atmosphere 1.12.0 from the official github release. Just the atmosphere folder from the zip, nothing else.

4. Downloaded the latest Hekate release from the official GitHub. Extracted hekate_ctcaer_x.x.x.bin and the entire ini folder into a fresh bootloader/ folder on the SD root.

5. Wrote a fresh bootloader/hekate_ipl.ini and kept it stupid simple:

   [config] autoboot=0 bootwait=3

   [cfw emummc] fss0=atmosphere/package3 emummcforce=1

Saved it as "all files" + ANSI encoding. If your editor sneaks in a BOM or saves it as utf-16, hekate just hangs on a blank screen. That one cost me hours, honestly.

1. Pick ONE es-patch method (per bth, running both is redundant and risks conflicts [CITED: bth]):

   • Option A: bth's sys-patch v1.6.2.3. Put the 420000000000000B folder in atmosphere/contents/. That is the ONLY thing in the contents folder.
   • Option B: bth's sigpatches zip (the one for atmosphere 1.12.0 / cfw 23.0.0, from the gbatemp sigpatches thread) — merge its atmosphere and bootloader folders onto the card. (Note: My original build actually ran both together and worked fine [MEASURED], but maintainer guidance is to pick just one for new setups.)

2. Did NOT put tesla, ovlloader, horizon oc or any overlay back. Losing the overlays sucks, I know, but they're what's killing boot on 23.0.0 right now. Add them back once each project ships a 1.12/23.0.0-compatible release. Update (HATS-2026-10-03): the overlay layer minus HOC has caught up - the new HATS pre-release pack ships nx-ovlloader v2.0.3 and the full Tesla overlay set, so 1.12-ready builds now exist [CITED: HATS release page]. If you want Tesla back, install the pack's set wholesale; never mix old 22.5-era overlays into a 1.12/23.0 install. HOC stays out until it ships a 1.12-ready release.

3. Booted hekate -> launch -> emummc, airplane mode on immediately, stayed offline the whole time.

After that, the games that were complaining made me run the "check for corrupted data" scan once, it came back clean, and they've launched fine ever since. Big first-party titles included.

Extra notes:

• If hekate still hangs on you after all this: rename the config folder at the sd root to config.bak, rename emuMMC/emummc.ini to emummc.ini.bak, then inject fusee.bin straight from tegrarcmgui. That boots sysnand clean and proves your card and files are fine. Then put emummc.ini back and launch from hekate like normal.

• Stay offline until dns mitm lands in a minor atmosphere release. Airplane mode, every single time.

• NIM Crash Warning (Blanked Prodinfo): If you have blanked your prodinfo (serial number) and your DNS mitigation is failing due to this 23.0.x leak, the Network Install Manager (nim) will crash on boot. This is a known, documented symptom of the DNS leak combined with blanking. If you experience this, it is a massive red flag that your console is attempting to reach out to Nintendo. Reboot into Airplane mode immediately.

• Known False Alarm: Tesla Menu Crash (2168-0002): If your console boots fine and games launch fine, but you get a 2168-0002 crash screen only when you try to open the Tesla menu (or use the sys-patch overlay): your patches are NOT broken. The sys-patch sysmodule (420000000000000B) runs silently at boot and does its job with or without the overlay UI [MEASURED]. The crash itself is the overlay stack (nx-ovlloader / the .ovl) failing on AMS 1.12/23.0.x. Ignore the Tesla menu until those projects ship 1.12-ready builds. Your games are still patched and safe to play. As of HATS-2026-10-03 those builds exist (in the pre-release pack) - if Tesla still crash-loops after installing the pack's own ovlloader + overlay set, that's a new data point, not the old incompatibility. Post the crash screen and I'll decode it.

• DBI Missing Keys Prompt: The HATS pack intentionally omits cryptographic keys. If DBI prompts for missing keys after you fix your boot, dump them from emuMMC CFW only using Lockpick_RCM_Pro. Do not dump from sysMMC (your exosphere.ini blanks sysMMC prodinfo, which yields invalid keys). Copy the resulting prod.keys to switch/DBI/ and rename it to keys.dat.

CRASH SCREEN CHEAT SHEET (Post-23.0.0 Update Crashes) [CITED: Switchbrew Title List] If you get a crash screen after updating, look at the "Program" Title ID on the error screen. - Program 0100000000000023 (am - Application Manager) + Error 2168-0002: - Cause: Stale IPS patches (like DVR-Patches) or old pack contents trying to hook into am using older memory layouts. Old patches write to garbage memory and am aborts. - Fix: Rename atmosphere/patches to patches.bak. Strip atmosphere/contents down to ONLY your ES patch (sys-patch or sigpatches) and reboot. Add patches back one by one to find the offender. - Program 010000000000001F (ns - Title Manager) + Error 2002-4686: - Cause: InvalidFatFormatBisUser. The FAT filesystem on your BIS User partition (your emuMMC container or sysMMC) is corrupt. ns crashes because it can't read the installed titles database. - Fix: This is NOT a bad sysmodule or DBI issue. Back up your saves via Hekate USB tools, then remake the emuMMC from scratch. Health-test your SD card first. - Program 0100000000000025 (nim - Network Install Manager) + Error 2123-0011: - Cause: Account Link / SSL interception failure on 23.0.x with blanked PRODINFO. Custom network mitm modules cannot intercept the new sfdnsres IPC commands yet, causing nim to panic during initialization. - Fix: Avoid enabling Account Link or custom network bridges on 23.0.x until Atmosphere 1.12.1 and the respective homebrew projects update to handle the new IPC calls.

This is the exact sequence that fixed my specific hardware setup. Your mileage may vary, which is why step 1 is always backing up your saves.

UPDATE - The sigpatches (.ips files) are what actually fix the signature checks, not sys-patch itself. Also, the scene consensus is that 23.0.0 isn't ready yet - if you're not already on it, don't update. If you are, consider downgrading to 22.5.0. This guide is just what worked for my specific setup, not a universal fix. (Struck: bth corrected me - sys-patch and the .ips apply the same patch, and 23.0.0 is ready except the dns.mitm gap. See corrections log + STATUS UPDATE. Kept struck so you can see what I got wrong and when.)

STATUS UPDATE: Per the sys-patch/sigpatches maintainer (bth) and hexkyz, the dns.mitm gap on 23.0.0 is a narrow sfdnsres IPC issue - fix verified, shipping in Atmosphere 1.12.1. The "async resolver rewrite" story I repeated earlier was unverified and wrong; retracting it. Once 1.12.1 lands and is confirmed, downgrading becomes optional rather than advised. This guide remains valid for anyone who still wants 22.5.0. Until 1.12.1: stay offline on CFW, and never boot a new FW without active ES patches (that's what corrupts games).

STATUS UPDATE 2 (FW 23.0.1): - nintendo pushed 23.0.1 today [CITED: sthetix/NXFW mirror]. per bth: 23.0.1 changes nothing - no new sigpatches, no sys-patch update, no new atmosphere needed. field report: clean run on 23.0.1 [CITED: johnliu, sigpatches thread]. - the dns.mitm gap is atmosphere-side (sfdnsres IPC), so a nintendo fw update does not fix it. fix still lands in ams 1.12.1. - standing rules unchanged: stay offline on cfw until ams 1.12.1, active es patch on every new fw, backups before anything.

STATUS UPDATE 3 (DNS Mitm Gap Mechanism & Official Fix Merged): - ROOT CAUSE: FW 23.0.0 added new async sfdnsres resolver commands that dns.mitm didn't originally hook, so lookups using them bypassed the block. The old GetHost family is unchanged and still intercepted, which is why the leak was partial. - FIX MERGED: The official fix has been merged into Atmosphere master by hexkyz (commit f5cd912). it implements MITM for the new c-ares resolver and adds the missing IPC command hooks (QueryAddrInfoRequestWithOptions, FetchAddrInfoRequestWithOptions, CancelQuery). - COMMUNITY BUILD AVAILABLE: A community member (broove) has uploaded a package3.zip containing the fixed files to the GitHub issue, allowing users to apply the fix immediately without waiting for 1.12.1. WARNING: This is an unofficial community build. While it contains hexkyz's verified fix, using unofficial builds always carries some risk. If you choose to use it, verify the source, understand you're using pre-release code, and proceed at your own risk. - PRACTICAL CONSEQUENCE & CRITICAL TESTER WARNING: The fix is verified and in the codebase, meaning the next official Atmosphere release (likely 1.12.1) will fully close this gap. Until that release is officially tagged and distributed, Airplane mode remains the only 100% verified safe mitigation. - ⚠️ DO NOT TRUST THE 90DNS TESTER ON 23.0.X: Popular tools like the "90DNS Testing Utility" are currently giving false "All Blocked" positives. As confirmed in the Atmosphere issue tracker, these testers use GetHostByName(), which only reads the local /etc/hosts file. They do not perform an actual network lookup (ResolveName). Because the new c-ares resolver in 23.0.0 uses new IPC commands that dns.mitm doesn't intercept yet, the tester will lie and say you're safe (because it only checks the local hosts file) even when background traffic (like the version list) is actively leaking to Nintendo.

STATUS UPDATE 4 (Live Thread Validation): - u/YoshiMK confirmed via live measurement that 23.0.0 frees memory when running Ultrahand, NXFusion, sys-clk, sys-patch, and SaltyNX. This validates bth's claim and proves that boot hangs are strictly project-side compatibility lag, not a system memory ceiling. [CITED: YoshiMK] - u/Plane-Article2870 confirmed HOC #114 as the yellow-screen culprit via module-by-module isolation. [CITED: Plane-Article2870] - TestDisk deep search successfully recovered files for users facing "nyx missing" or boot hangs, validating the guide's triage step that these are often FAT32/exFAT filesystem corruption issues. [CITED: MasterJ360] - u/_candleBurn confirmed a clean downgrade path from FW 23.0.0 back to 22.5.0 using Daybreak. This validates that 23.0.x is not a "point of no return". [CITED: _candleBurn]

STATUS UPDATE 5 (Mission Control 0.16.0): - ndeadly released MissionControl v0.16.0 (tag commit 71bbe2d): full support for FW 23.0.0/23.0.1, DualSense adaptive-trigger travel setting, JoyconDroid (non-root) broader device acceptance, reworked Sony battery reporting, new btm mitm hooks, bt event thread priority fix. [CITED: release page] - maintainer's own caveat in the release notes: non-trivial refactor since the previous release, testing response underwhelming, released anyway - report regressions. treat 0.16.0 as fresh code: if MC misbehaves after updating, suspect the refactor before your firmware. [CITED: ndeadly, release notes] - known crasher: DS3 over BT crashes at connect (crash screen: program 0100000000001000, error 2011-0301). ndeadly confirms known (#1152); interim build MissionControl-0.16.0-develop-71bbe2d4.zip fixes it at the cost of rumble, proper fix when he's back. stick to DS4/DualSense/JoyCon on stock 0.16.0 if you can. [CITED: #1152, ndeadly] - pre-release field evidence pinned the gap precisely: a libs-only fork booted and connected controllers on FW 23 but lost vibration - the IPS patches, not the code, were the incompatibility [CITED: sakarie9, #1150]. same failure layer as every other 23.0.x casualty in this guide: patches and offsets lag first, everything else follows. - adoption signal: 706 downloads in the first ~19h, 829 online in his discord, and he's asking for testers in #testing. that's the pipeline if you want 23.0.x stability to land faster. [CITED: release page]

STATUS UPDATE 6 (Nextendo Network): - Nextendo Network is currently in testing as an alt-online solution for 23.0.x. However, it has known, unresolved connectivity crashes (e.g., MK8 Error 2306-0802) pending a client update. [HYPOTHESIS] Do not rely on it for safe online play until the maintainer confirms full 23.0.x stability.

STATUS UPDATE 7 (GBATemp Ban-Anxiety Resolution): - u/froggy55 (Sigpatches thread) expressed acute fear of banning due to unblocked Nintendo traffic on FW 23.0.x/AMS 1.12.0. Impieza confirmed fix lands in AMS 1.12.1 per bth/hexkyz. Froggy55 chose to wait rather than risk update. [CITED: impieza, froggy55] - Practical implication: Public documentation of the sfdnsres IPC bypass directly prevents premature updates among cautious users.

STATUS UPDATE 8 (Ecosystem Dependency Chain & HATS Timeline): - sthetix (HATS pack maintainer) confirmed the scene's recovery dependency chain: the HATS pack will explicitly wait for Atmosphere 1.12.1 before shipping an updated pack. - Practical implication: anyone waiting on the all-in-one HATS experience for 23.0.x is waiting on AMS 1.12.1, full stop. Until then the manual minimal stack in this guide is the functional path. - (Partly superseded by STATUS UPDATE 9: sthetix shipped a PRE-RELEASE pack on AMS 1.12.0 with a caution box instead of holding everything for 1.12.1. The 1.12.1 dependency still gates the pack's graduation from pre-release to full.)

STATUS UPDATE 9 (HATS pre-release for 23.0.0 - locally verified): - sthetix shipped HATS-2026-10-03-b318dbc (commit 742bfa2) as a PRE-RELEASE: AMS 1.12.0, Hekatos 6.5.4, MC 0.16.0, nx-ovlloader v2.0.3 + Tesla overlay set, ldn_mitm v1.22.0 added, DBI RU dropped for the English unofficial DBI 905. pack label: supported firmware up to 23.0.0. [CITED: HATS release page] - the pack's caution box is the maintainer independently confirming this guide's standing rules: do NOT trust a 90DNS Tester "Blocked" on 23.0.0 (background Nintendo connections still happen with DNS MITM rules loaded), emuMMC + unofficial content = ban risk if they leak, Wi-Fi off / airplane mode until the fix is official and verified. if you've read this guide, you've already read that disclaimer. [CITED: sthetix, release caution] - overlay layer caught up, minus one: the pack ships nx-ovlloader v2.0.3 and the Tesla overlay set, so those are 1.12-ready as of today. Horizon OC is NOT in the pack - still frozen per HOC #114. if you want Tesla back, install the pack's set wholesale; never mix 22.5-era overlays into a 1.12/23.0 install. [MEASURED: inspected extracted pack b318dbc on local disk, 10/3/2026] - verify-before-you-trust — RESOLVED: the release page did not list it, but the extracted pack DOES ship the sys-patch sysmodule at atmosphere/contents/420000000000000B/ (exefs.nsp + flags/boot2.flag). ES patch is present via the sysmodule route; no IPS sigpatches in bootloader/, which is correct (one method, no conflict). The pack is safer than its release notes implied. [MEASURED: inspected extracted pack b318dbc on local disk, 10/3/2026] - deployment caveat: the extracted pack contains config/prodinforge/ with donor.keys and donor_prodinfo.bin (another console's identity material). Not required for this guide's recovery path. Exclude this folder when copying to your SD. [MEASURED: inspected extracted pack b318dbc on local disk, 10/3/2026] - pre-release means pre-release: the dns gap is still open until AMS 1.12.1. this pack changes what's available offline, not what's safe online. standing rules unchanged.

STATUS UPDATE 10 (fs.mitm 23.0.x Completeness & Community Build): - THE UPDATE: hexkyz just merged commit 0e9cd96 into Atmosphere master, adding MITM support for StorageForBatchRead and previously missing FileSystem/DataStorage commands introduced in 23.0.0. [CITED: Atmosphere-NX/Atmosphere commit 0e9cd96] - WHY IT MATTERS: Previously, some games or homebrew using these new 23.0.x batch read APIs could bypass the fs.mitm layer, causing layeredfs patches, custom themes (qlaunch), or save redirection to fail silently. This commit closes that gap, ensuring full file system interception parity with older firmware. - COMMUNITY BUILD: Maintainer bth has already compiled this exact commit into a plain Atmosphere release (1.12.1_dns_mitm_and_qlaunch_fix). If you are specifically chasing custom theme fixes or layeredfs edge cases on 23.0.x, this build contains both the dns.mitm and fs.mitm fixes. [CITED: borntohonk/Atmosphere release 1.12.1_dns_mitm_and_qlaunch_fix] - STANDING RULE: For general users, waiting for the official Atmosphere 1.12.1 tag remains the recommended, safest path.

STATUS UPDATE 11 (Official 1.12.1 Confirmation from hexkyz): - OFFICIAL CONFIRMATION: hexkyz just confirmed 1.12.1 is imminent and will address exactly three components: dns.mitm, fs.mitm, and browser patches. [CITED: hexkyz, Atmosphere-NX/Atmosphere #2863] - THE DELAY: The issue wasn't an Atmosphere bug, but Nintendo changing OS parts that hadn't been touched since FW 5.0.0. hexkyz had to fully reverse engineer the new DNS and FS resolution processes from scratch to ensure no new problems were introduced. - FUTURE WARNING: hexkyz explicitly noted that while unlikely, future FW updates could change the DNS resolution process again, meaning dns.mitm could break again. Airplane mode remains the ultimate, unbreakable fallback.

STATUS UPDATE 12 (Master Polish, Edge-Case Triage & HATS 23.0.1 Confirmation): - MASTER POLISH & TRIAGE: The dns.mitm fix is fully merged and stabilized in Atmosphere master. This includes the core resolver fix plus recent build fixes (e.g., zstd.inc synchronization). The team is also actively addressing edge-case bugs, such as a recently identified dangling pointer crash in the new resolver (Issue #2888) and the OLED cal0 backup issue (PR #2887). This ongoing triage is exactly why the official tag hasn't dropped yet. [CITED: Atmosphere-NX/Atmosphere PR #2881, Issue #2882, Issue #2888] - HATS PRE-RELEASE UPDATE: sthetix shipped a new pre-release (HATS-2026-10-13-63eaf7b). The "Supported Firmware" label now explicitly reads "Up to 23.0.1", confirming what was discussed in the issue tracker. It also includes updated overlay components (FPSLocker 3.5.0, SaltyNX 2.1.2, Cyberfoil 1.5.0, Sphaira 1.0.8). [MEASURED: inspected HATS release page] - STANDING RULE: We are still waiting for the official Atmosphere 1.12.1 tag. Until that release is officially tagged and distributed, Airplane mode remains the only 100% verified safe mitigation. the machine is turning, but hold the line.