How to Update Switch Firmware With Atmosphere: Complete Step-by-Step Guide

How-to-Update-Switch-Firmware-With-Atmosphere-Complete-Step-by-Step-Guide.png

Updating Nintendo Switch firmware while using Atmosphère CFW requires a different process from updating a stock Switch. You need to make sure that your installed Atmosphère, Hekate, Fusee, emuMMC, and homebrew components support the firmware version you want to install.

The safest approach is to update Atmosphère and Hekate first, confirm that CFW boots correctly, update sysMMC, and then update emuMMC separately if you use one.

Quick Answer: To update Switch firmware with Atmosphère, first confirm that the target firmware is supported by Atmosphère and Hekate. Back up your microSD card, update Atmosphère, Fusee, and Hekate, test CFW, update sysMMC, dump that firmware from your own Switch, then install it on emuMMC using Daybreak. Do not update Nintendo firmware before CFW compatibility is confirmed.

Atmosphère 1.11.2 and Hekate 6.5.3 support Nintendo Switch firmware through 22.5.0. Firmware 23.0.0 is not yet supported, so Atmosphère users should not update to it yet.


Table of Contents

Check Atmosphere Compatibility Before Updating Switch Firmware

Before installing any Nintendo Switch firmware update, check whether your target firmware works with both:

  • Atmosphère
  • Hekate
  • emuMMC
  • Important sysmodules
  • Homebrew applications
  • Custom themes

This compatibility check is the most important part of the process.

At the time of writing:

ComponentCurrent VersionSupported Firmware
Atmosphère1.11.2Up to 22.5.0
Hekate6.5.3Up to 22.5.0
Nintendo Switch Firmware 23.0.0—Not yet supported

Atmosphère 1.11.2 added basic support for HOS 22.5.0, while Hekate 6.5.3 also added support for 22.5.0 and matching emuMMC compatibility.

If Nintendo releases a newer firmware than Atmosphère switch and Hekate support, stay on your current firmware until compatible versions are released.


What You Need Before Updating Switch Firmware With Atmosphere

Prepare the following before starting:

  • Nintendo Switch running Atmosphère
  • Compatible Atmosphère release
  • Compatible Hekate release
  • Updated Fusee payload if required
  • microSD card backup
  • Hekate boot access
  • Homebrew Menu
  • Daybreak for emuMMC updates
  • Enough SD card space for firmware files

Your microSD card will typically contain:

SD:/
├── atmosphere/
├── bootloader/
├── switch/
├── emuMMC/
└── hbmenu.nro

If you do not use emuMMC, your setup may not contain the /emuMMC/ directory.


Back Up Your Switch Before Updating Firmware

Before replacing CFW files or installing new firmware, copy your important microSD card data to a PC or external drive.

Back up:

/atmosphere/
/bootloader/
/switch/
/emuMMC/

Also keep important configuration files such as:

/bootloader/hekate_ipl.ini
/exosphere.ini

A backup makes recovery much easier if the update causes:

  • Atmosphère boot failures
  • Hekate configuration problems
  • Incompatible sysmodules
  • Theme crashes
  • Corrupted SD card files
  • emuMMC problems

If you already have a NAND backup, keep it stored separately from the active microSD card.


How to Update Switch Firmware With Atmosphere

For most Atmosphère setups, the correct order is:

  1. Check firmware compatibility.
  2. Back up the SD card.
  3. Update Atmosphère.
  4. Update Fusee.
  5. Update Hekate.
  6. Disable incompatible themes or sysmodules.
  7. Boot and test Atmosphère.
  8. Update sysMMC firmware.
  9. Dump the updated firmware.
  10. Install the firmware on emuMMC with Daybreak.
  11. Reboot and verify the new firmware.

Step 1: Update Atmosphere Before Switch Firmware

Download the newest Atmosphère release that supports the firmware you plan to install.

Copy the Atmosphère release files to the root of your microSD card.

If prompted, choose merge/replace.

The NH Switch Guide recommends updating Atmosphère before updating system firmware and overwriting the existing files with the new official release.

A typical updated SD card looks like:

SD:/
├── atmosphere/
├── bootloader/
├── switch/
└── hbmenu.nro

Do not update Nintendo firmware yet.

First make sure the CFW components themselves are compatible and current.


Step 2: Update Fusee if Required

Atmosphère releases can include a newer:

fusee.bin

If you boot Atmosphère through Fusee, replace the old payload with the version released alongside your Atmosphère build.

Atmosphère 1.11.2 specifically requires users to update Fusee when upgrading.

An outdated Fusee payload can cause:

  • Black screen
  • Atmosphère boot errors
  • Payload version mismatch
  • CFW failing to start

Keep Atmosphère and Fusee from the same release.


Step 3: Update Hekate

Download the latest compatible Hekate release.

Copy:

bootloader/

to the root of your microSD card.

Choose merge/replace.

Do not delete the old bootloader folder first because it may contain:

  • hekate_ipl.ini
  • Custom boot entries
  • Payloads
  • Configuration files

The official Hekate update instructions specifically recommend merging the new bootloader directory rather than deleting the existing one.

Hekate also includes:

bootloader/update.bin

If that file is newer than the initially injected Hekate payload, Hekate can automatically load the newer build.


Step 4: Disable Outdated Themes and Sysmodules

Before installing a newer Switch firmware, check third-party modifications inside:

SD:/atmosphere/contents/

Firmware updates can break:

  • Tesla overlays
  • Overclocking sysmodules
  • Controller modules
  • Network modifications
  • Custom themes
  • Background services
  • Firmware-specific plugins

If you are unsure whether a modification supports the target firmware, disable it before the first boot.

This helps separate a genuine firmware or Atmosphère problem from an incompatible third-party module.


Step 5: Boot Atmosphere and Test CFW

Before updating Nintendo firmware, boot your existing system using the new Atmosphère and Hekate files.

From Hekate, select your normal CFW environment:

Atmosphere PKG3 emuMMC

or:

Atmosphere PKG3 sysMMC

Open:

System Settings → System

You should see AMS in the system-version string.

For example:

22.5.0 | AMS 1.11.2 | E

AMS confirms that Atmosphère is running, while E indicates emuMMC. A sysCFW environment normally shows S.

Test:

  • Hekate
  • Atmosphère
  • Homebrew Menu
  • Main homebrew apps

Only continue once CFW boots normally.


How to Update sysMMC Firmware With Atmosphere

The correct method depends on whether your Switch uses a modchip or an unpatched RCM-based setup.

For a Modchipped Nintendo Switch

For major firmware updates, the NH Switch Guide recommends updating through OFW/Stock.

From Hekate:

Home → Reboot → OFW

Then open:

System Settings → System → System Update

If OFW does not boot correctly, use:

Hekate → Launch → Stock sysMMC

instead.

Updating major firmware through stock firmware on a modchipped console helps maintain expected e-fuse behavior and reduces the chance of incomplete system updates.


For an Unpatched V1 Switch

For an unpatched Switch using Atmosphère, you can boot:

Hekate → Launch → Atmosphere PKG3 sysMMC

Then go to:

System Settings → System → System Update

and install the supported firmware normally.

If AutoRCM is enabled, the NH Switch Guide notes that updating through normal Stock/OFW can disable AutoRCM. Updating through sysCFW avoids that specific behavior.


Does Updating sysMMC Also Update emuMMC?

No.

sysMMC and emuMMC have separate firmware installations.

For example, your console can have:

sysMMC: 22.5.0
emuMMC: 21.2.0

at the same time.

Updating sysMMC through Nintendo’s System Update does not automatically update your emuMMC.

If you use emuMMC, update it separately.


How to Update emuMMC Firmware With Atmosphere

A common approach is:

  1. Update sysMMC first.
  2. Dump the installed firmware from your own sysMMC.
  3. Boot Atmosphère emuMMC.
  4. Install the dumped firmware using Daybreak.

The NH Switch Guide documents this as its standard emuMMC firmware update workflow.


Step 1: Dump the Firmware From Your Updated sysMMC

The NH Switch Guide currently documents several ways to dump installed firmware from your own Switch, including:

  • Goldleaf
  • nxdumptool
  • TegraExplorer

Each method creates a firmware directory that Daybreak can install later.

For example, a firmware dump may be stored under:

SD:/switch/Goldleaf/export/update/<firmware-version>/

or:

SD:/tegraexplorer/Firmware/<firmware-version>/

Use firmware obtained from a Switch you own rather than downloading unknown firmware packages.


Step 2: Boot Into Atmosphere emuMMC

From Hekate:

Launch → Atmosphere PKG3 emuMMC

Verify that you actually booted emuMMC by opening:

System Settings → System

The system version should contain:

AMS

and end in:

E

The E confirms that Atmosphère is running on emuMMC.


Step 3: Open Daybreak

Open Homebrew Menu through Album or title override.

Launch:

Daybreak

Daybreak is Atmosphère’s firmware installation utility and is commonly used to update an offline emuMMC.

Select:

Install

Then browse to the directory containing the firmware you dumped from sysMMC.

The NH Switch Guide recommends using Daybreak for this part of the process.


Step 4: Select the Firmware Folder

Choose the directory created by your firmware-dumping method.

Examples include:

sd:/switch/Goldleaf/export/update/22.5.0/

or:

sd:/tegraexplorer/Firmware/22.5.0/

Daybreak will validate the firmware files before continuing.

If the package is incomplete or corrupted, do not proceed until you have a valid firmware dump.


Step 5: Choose Preserve Settings

After Daybreak validates the firmware, select:

Continue

and then:

Preserve Settings

This retains the existing system configuration while updating firmware.

The NH Switch Guide specifically instructs users to use Preserve settings during the normal emuMMC update process.


Step 6: Select FAT32 or FAT32 + exFAT

Daybreak may offer:

Install (FAT32 + exFAT)

or:

Install (FAT32)

If the full option is available, the NH Switch Guide recommends selecting:

Install (FAT32 + exFAT)

Otherwise, select:

Install (FAT32).

This option relates to system filesystem-driver support, not necessarily the filesystem currently used by your microSD card.


Step 7: Install the Firmware and Reboot

Confirm the installation and allow Daybreak to finish.

Do not:

  • Power off the console
  • Remove the microSD card
  • Force-restart during installation

When Daybreak completes, select:

Reboot

Then launch Atmosphère emuMMC again.


Step 8: Verify the Firmware Update

After rebooting, open:

System Settings → System

Check the firmware and Atmosphère version.

For example:

22.5.0 | AMS 1.11.2 | E

This confirms:

  • Firmware 22.5.0 is installed
  • Atmosphère 1.11.2 is active
  • You are running emuMMC

The NH Switch Guide recommends verifying the installed firmware from System Settings after the Daybreak update completes.


Should You Use Daybreak to Update sysMMC?

For the workflow documented by the NH Switch Guide, sysMMC is normally updated first through Nintendo’s System Update, while Daybreak is then used to update the separate emuMMC using firmware dumped from sysMMC.

This keeps the two environments clearly separated:

Nintendo System Update
        ↓
      sysMMC
        ↓
Dump installed firmware
        ↓
      Daybreak
        ↓
      emuMMC

For modchipped consoles, stock/OFW is particularly recommended for major sysMMC firmware updates.


How to Update Switch Firmware With Atmosphere Without Removing the SD Card

Hekate can expose your Switch microSD card directly to your PC.

From Hekate:

Tools → USB Tools → SD Card

Connect the Switch to your PC with a USB cable.

You can then update:

  • Atmosphère files
  • Hekate files
  • Homebrew apps
  • Firmware dump files

without physically removing the microSD card.

The NH Switch Guide uses Hekate’s USB SD access during its Atmosphère and firmware maintenance workflows.

Safely eject the drive before leaving USB storage mode.


Common Problems After Updating Switch Firmware With Atmosphere

Atmosphere Does Not Boot After Firmware Update

First check whether your Atmosphère version supports the newly installed firmware.

Common causes include:

  • Atmosphère too old
  • Hekate too old
  • Outdated Fusee
  • Incompatible sysmodule
  • Custom theme
  • Incomplete Atmosphère update

Start with a clean, current Atmosphère and Hekate setup before re-enabling optional modifications.


Hekate Shows “Unknown pkg1 Version”

An error similar to:

Unknown pkg1 version.
HOS version not supported!

usually indicates that your Hekate build does not support the installed firmware.

Update Hekate to a compatible version.

The NH Switch Guide lists unsupported HOS versions as a common cause of this error.


Atmosphere Shows a Yellow or Blue Screen

A full yellow or blue screen can indicate mismatched Atmosphère files.

This can happen when some older files remain while only part of the CFW package has been updated.

Re-copy the complete official Atmosphère release to the SD card and overwrite the existing files.


Switch Boots but Homebrew Apps Crash

Atmosphère may support the new firmware while individual homebrew applications or sysmodules do not.

Update:

  • Homebrew .nro apps
  • Tesla components
  • Sysmodules
  • Overlays
  • Theme tools

If a crash began immediately after a firmware update, temporarily disable third-party additions from:

SD:/atmosphere/contents/

and test again.


Custom Theme Causes Atmosphere to Crash

Nintendo firmware updates can change HOME Menu components.

An old custom theme may therefore become incompatible after a system update.

Remove the theme and boot Atmosphère again.

Once CFW works normally, install a theme version compatible with the new firmware.


Daybreak Cannot Find the Firmware

Check that your firmware dump folder exists in the path generated by your chosen dump tool.

For example:

SD:/tegraexplorer/Firmware/22.5.0/

or:

SD:/switch/Goldleaf/export/update/22.5.0/

Do not point Daybreak to a ZIP archive. Select the extracted firmware directory containing the actual update files.


Daybreak Shows an exFAT Warning

The NH Switch Guide notes that Daybreak may display:

Warning: exFAT firmware is missing or corrupt

when the source sysMMC does not currently have exFAT drivers installed.

If this matches your configuration, the guide indicates that you can continue with the appropriate FAT32 installation option.


Can You Update Switch Firmware Directly While Running Atmosphere?

Yes, but the correct method depends on the environment.

For an unpatched Switch, the NH Switch Guide supports updating sysMMC while running:

Atmosphere PKG3 sysMMC

through:

System Settings → System → System Update.

For modchipped consoles, major firmware updates should preferably be performed from OFW/Stock instead.

For emuMMC, the standard offline method is to use Daybreak with firmware dumped from your updated sysMMC.


Should You Update Atmosphere Before Switch Firmware?

Yes.

The preferred order is:

Atmosphère → Fusee → Hekate → test CFW → Nintendo firmware

This prevents you from installing a system firmware version before your CFW environment is ready for it.

If Nintendo releases a new firmware and Atmosphère or Hekate does not yet support it, wait before updating.


Do You Need to Update Hekate Before Firmware?

Yes, if your current Hekate version does not support the target HOS release.

The current Hekate 6.5.3 release supports Horizon OS through 22.5.0, including matching emuMMC support.

Keeping Hekate current also helps avoid errors such as unsupported pkg1 versions.


Do You Need to Update Fusee Before Firmware?

If you use Fusee and your Atmosphère release includes a newer payload, update it.

Atmosphère 1.11.2 specifically requires an updated Fusee payload.

If you boot entirely through Hekate’s package3 configuration, Fusee may not be part of your normal boot path.


Frequently Asked Questions

How Do I Update Switch Firmware With Atmosphere?

First update Atmosphère, Fusee, and Hekate. Verify CFW boots correctly, update sysMMC using the appropriate stock/sysCFW method, then update emuMMC separately with Daybreak if you use one.

Can I Update My Switch Normally With Atmosphere Installed?

Yes, provided the target Nintendo firmware is supported by your Atmosphère and Hekate versions.

Do not install an unsupported firmware simply because Nintendo offers the update.

Should I Update Atmosphere or Firmware First?

Atmosphère first.

Update Atmosphère and Hekate before installing newer Nintendo firmware.

Can Daybreak Update Switch Firmware?

Yes. Daybreak can install a valid firmware package while running Atmosphère and is commonly used to update emuMMC.

Does Daybreak Update emuMMC?

Yes, when you boot into Atmosphère emuMMC and run Daybreak there, the firmware installation applies to that emuMMC environment.

Does Updating sysMMC Update emuMMC?

No. They have independent firmware versions and must be updated separately.

Can sysMMC and emuMMC Have Different Firmware Versions?

Yes.

For example:

sysMMC: 22.5.0
emuMMC: 21.2.0

is possible because they are separate environments.

What Atmosphere Version Supports Firmware 22.5.0?

Atmosphère 1.11.2 added basic support for Nintendo Switch firmware 22.5.0.

What Hekate Version Supports Firmware 22.5.0?

Hekate 6.5.3 with Nyx 1.9.3 supports HOS 22.5.0 and corresponding emuMMC functionality.

Can I Update to Switch Firmware 23.0.0 With Atmosphere?

Not currently if you need Atmosphère CFW. As of September 2026, the NH Switch Guide states that firmware 23.0.0 is not yet supported by Atmosphère 1.11.2 and Hekate 6.5.3.

Will Updating Firmware Remove Atmosphere?

A Nintendo firmware update does not normally delete Atmosphère from your microSD card, but installing unsupported firmware can prevent your existing Atmosphère version from booting.

Will Updating Firmware Delete My Homebrew Apps?

A normal firmware update does not normally remove .nro applications stored in:

SD:/switch/

However, some apps may need updates to work correctly with newer firmware.


Conclusion: How to Update Switch Firmware With Atmosphere

Learning how to update Switch firmware with Atmosphere mainly comes down to using the correct update order and keeping every CFW component compatible.

Start by confirming that Atmosphère and Hekate support the firmware you want to install. Back up your SD card, update Atmosphère, Fusee, and Hekate, then boot and test CFW before changing the Nintendo system firmware.

For sysMMC, use the appropriate stock or sysCFW update method for your console. If you use emuMMC, remember that it has its own firmware version. Dump the updated firmware from your own sysMMC and install it on emuMMC using Daybreak.

The safest workflow is:

check compatibility → update Atmosphère → update Fusee → update Hekate → test CFW → update sysMMC → dump firmware → update emuMMC with Daybreak → verify the new version.

Following that sequence reduces the most common problems, including unsupported HOS errors, Atmosphère boot failures, outdated payloads, broken sysmodules, and emuMMC firmware mismatches.

Latest post:

More Posts