After applying an Atmosphère patch to your Switch, the real danger isn't a console that won't boot—it's getting it permanently banned by Nintendo. This page details what triggers a ban, the signs of a flagged console, and the steps to reduce (without ever eliminating) the risk, including how to choose a dedicated microSD card.
Nintendo bans the console itself using its burned-in identifiers. Resetting the system, changing accounts, or reformatting the microSD card will not reverse a ban.
Even when following all precautions, ban waves have affected consoles that were never linked to pirated games. You can reduce the risk, but you can't eliminate it.
The standard setup: all modified content lives on an emuMMC that is cut off from Nintendo's servers by a blocking DNS. The original sysMMC remains strictly official.
Nintendo can ban the console itself, using hardware identifiers sent with every connection. A ban cannot be reversed, and Nintendo is not required to offer an appeal process. The Nintendo Account may not be affected, but the console itself will lose online access for good—even with a different account. For basic concepts (patch, RCM, Atmosphère, emuMMC), see the Basics page.
There is no official list—Nintendo never publishes its detection rules. The table below summarizes behaviors recognized by the community as the most frequent causes, from most certain to most likely.
| Behavior | Ban Risk | Reversible? |
|---|---|---|
| Connecting online from a modified sysMMC | Very High | No |
| Launching a pirated title then connecting online | Very High | No |
| Cheating online (memory editors, trainers) | Very High | No |
| Copying console identifiers (deviceid/prodid) from another machine | Very High | No |
| Installing titles via Nintendo's CDN (online NSP/NCD) | High | No |
| Connecting online from an emuMMC without a blocking DNS | High | No |
| Restoring a modified save and then cloud syncing | Moderate | No |
| Protected emuMMC (blocking DNS), connected official sysMMC | Low | Never zero |
| Modified console never connected to any network | Very Low | Never zero |
How can you tell if a console is already banned, or in the process of being banned? The signs below are the most frequently reported symptoms. No sign proves the absence of a ban: Nintendo sometimes applies bans in delayed waves, so a flagged console might remain silent for weeks before it's banned.
No combination eliminates the risk entirely, but this procedure massively reduces the probability of a ban. It assumes you have an unpatched console (see the checker) on which you are installing Atmosphère via a prepared microSD.
Safety Checklist: Dedicated emuMMC ✅ · Blocking DNS active on emuMMC ✅ · sysMMC never modified ✅ · Telemetry disabled ✅ · microSD not shared ✅ · Pirated titles offline ✅ · Official connection only from sysMMC ✅. One unchecked box = a real risk.
False. The microSD card's file system has no connection to the identifiers sent to Nintendo. exFAT even increases the risk of card corruption; FAT32 remains recommended.
False. 90DNS blocks known domains, but Nintendo can add new endpoints, and a DNS leak (from a misconfigured or manual Wi-Fi setup) is enough to expose the console. The DNS reduces risk, it doesn't eliminate it.
False. Bans often arrive in delayed waves. Nothing happening today guarantees anything for tomorrow—which is why it's crucial to never let your guard down.
False. The ban is hardware-based: the console remains banned with any account. Trying to bypass it using identifiers from another console actually increases the risk.
No method is guaranteed. This page is provided for educational purposes, for modifying hardware you own; illegal copying of games is neither covered nor encouraged here. If online access is essential to you, keep an unmodified console for that purpose.
Sources consulted on September 6, 2026: switch.hacks.guide · Atmosphere-NX · 90DNS · Switch Hackable Serial List