If you are seeing the error message "IOS_FS: Failed to write new FST" while using the Dolphin Emulator, it typically indicates that the emulator is being blocked from saving or modifying files in its user directory. This error often pops up during startup or when trying to save game data, and it is usually related to file permissions or interference from security software. What Does This Error Mean?
The "FST" refers to the File System Table, which Dolphin uses to track metadata and access control lists for content stored on the virtual Wii NAND. When Dolphin cannot write this file, it fails to update your virtual console’s internal memory, leading to lost saves or persistent error popups. Common Causes
Antivirus Interference: Many security suites, including Windows Defender, use a feature called "Controlled Folder Access" that blocks unknown applications from writing to the "Documents" folder where Dolphin defaults its data.
Folder Permissions: The Dolphin folder may be set to "Read-Only," or the user may lack administrative rights to modify files in that directory.
Cloud Syncing Issues: Applications like Microsoft OneDrive often sync the "Documents" folder, which can lock Dolphin's files while they are being uploaded, causing a write failure.
Portable Mode Complications: If you are running Dolphin in "Portable Mode" (with a portable.txt file in the folder), the emulator may struggle if placed in a protected directory like C:\Program Files. How to Fix the "Failed to Write New FST" Error 1. Configure Windows Defender / Antivirus
The most common solution is to allow Dolphin through your security software.
Go to Windows Security > Virus & threat protection > Manage settings.
Scroll to Controlled folder access and click Manage Controlled folder access.
Either turn it off entirely or click Allow an app through Controlled folder access and add Dolphin.exe.
Alternatively, add the Dolphin folder to the Exclusions list in your antivirus settings. 2. Run as Administrator
Sometimes the emulator simply lacks the necessary permissions to write to its own folder. Right-click your Dolphin.exe file.
Select Run as administrator. If this stops the error, you can permanently set this by right-clicking the file, going to Properties > Compatibility, and checking Run this program as an administrator. 3. Relocate the User Folder
If OneDrive or folder permissions continue to cause issues, you can move the user data folder out of "Documents".
The error "IOS_FS: Failed to write new FST" in the Dolphin emulator typically indicates a file permission or access conflict. It occurs when the emulator attempts to update the Wii's internal file system (File System Table or FST) but is blocked by the operating system or third-party software. Primary Causes
Antivirus Interference: Programs like Windows Defender or Avast often block Dolphin's ability to write to protected folders like "Documents".
Insufficient Permissions: If the Dolphin directory or its user data folder is set to "Read-only," it cannot save necessary configuration or FST files.
Controlled Folder Access: A Windows Security feature that specifically prevents applications from modifying files in standard user folders.
Pathing Conflicts: Issues can arise if the Wii NAND or user config files are stored in a location the emulator cannot consistently access. Recommended Solutions
The following methods have been verified by the community to resolve this error: Configure Antivirus Exceptions:
Add the Dolphin executable (Dolphin.exe) and the Dolphin Emulator user folder (usually in Documents) to your antivirus exclusion list.
Disable Controlled Folder Access in Windows Security under "Virus & threat protection settings". Adjust Folder Permissions:
Right-click the Dolphin installation folder and the "Dolphin Emulator" folder in Documents. dolphin ios-fs failed to write new fst
Select Properties, uncheck Read-only, and ensure your user account has Full Control under the Security tab. Run as Administrator:
Right-click the Dolphin shortcut or .exe and select Run as administrator to bypass standard permission restrictions. Relocate User Data:
Some users resolve this by forcing Dolphin to store data in the AppData folder rather than Documents. You can do this by creating a blank file named portable.txt in the same directory as your Dolphin.exe.
Alternatively, simply renaming the "Dolphin Emulator" folder in Documents to "Dolphin" can sometimes trigger a reset that clears the error, though this may reset your settings. Update Dolphin:
Ensure you are using the latest Development or Beta version. Older stable versions (like 5.0) are prone to bugs that have since been patched.
Are you seeing this error while launching a specific game or does it happen as soon as you open the emulator?
If you imported a NAND dump from a real Wii console or downloaded a pre-made NAND from the internet, it likely contains corrupted system files or leftover configuration files (like SYSCONF) that conflict with Dolphin's emulation.
The cleanest fix is to let Dolphin generate a fresh NAND:
Documents\Dolphin Emulator\Wii~/.local/share/dolphin-emu/Wii (or similar, check Help > User Data in Linux)Wii.Wii_OLD (or move it to your desktop as a backup).Tools > Import Wii Save later.If the game file is incomplete or has read errors, Dolphin may fail to parse the disc structure. When it tries to write an FST based on bad data, the write operation can fail with this generic error.
Dolphin Emulator is one of the most popular and powerful emulators for playing Nintendo GameCube and Wii games on non-native hardware. Available on Windows, macOS, Linux, and even Android, it has also been ported to iOS (primarily through sideloading methods like AltStore, SideStore, or TrollStore). However, iOS users occasionally encounter a cryptic, frustrating error when trying to launch a game or manage virtual console titles:
"dolphin ios-fs failed to write new fst"
This error typically prevents games from booting, corrupts save states, or halts the emulation process entirely. If you are seeing this message, you are not alone. This article will explain what the error means, why it occurs specifically on iOS, and how to fix it—ranging from simple troubleshooting to advanced file system repairs.
Windows Security > Virus & threat protection.Dolphin.exe to "Allowed apps").A failing hard drive or file system errors can cause this. Run a disk check:
chkdsk /f C: (Replace C: with your game drive letter).The dolphin surfaced at dawn, metal-gray back slicing through glassy water as if the sea had been cut clean. It wasn't a creature of myth; it was a name stitched into half-forgotten logs on a ship's server: Dolphin — a slender submersible probe that translated currents into code, mapping the ocean's memory into filesystems and coral into directories.
On its first mission, Dolphin dove with calm certainty. Its sonar hummed like a lullaby, and the engineers watched the telemetry bloom on their screens: directories of plankton counts, nested folders of temperature gradients, little files that were the sea's fingerprints. The probe wrote everything, reliable as tide.
But one evening, under a low moon, Dolphin returned with a new error: ios-fs failed to write new fst. The console flashed in dull red. The words meant little to the crew at first — a dry, technical hiccup — until the data scientists opened the logs and found something stranger than corruption: gaps where whole swathes of reef data used to be, silences where songfish should have sung.
They repaired cables, rerouted power, and rebooted systems. Dolphin dove again, but the error returned like a stubborn bruise. "Failed to write new fst" — the filesystem table, the index that tells the machine where the sea's memories live. Without it, the files existed but had no name, no address, drifting like messages in bottles without recipients.
On the third dive, an old engineer named Maris volunteered to ride Dolphin's diagnostic thread. She had once been a poet before she learned to speak in kernel panics and checksums. In the control room, with warm coffee turning cold in her hands, she scrolled through the probe's last transmissions. Among the binary waves, she found odd packets: patterns that didn't match sensors. They were rhythmic, almost musical — a sequence that repeated like whale song, but compressed, encoded inside routine telemetry.
Maris hunted through the code and found comments left by the probe's creator — fragments of philosophy about place and belonging: "A filesystem is an island; an fst is the map." The probe, the notes suggested, tried to write a map for a place that refused to be mapped.
Dolphin's dives had begun to cross into regions where reefs grew like cities, labyrinths of life so dense the usual mapping heuristics failed. The coral rearranged itself nightly; fish migrated in new patterns; the seabed rose and fell like breath. A static fst could not capture this living geography. When the probe attempted to freeze the map into structure, the sea protested. The write operation failed because the destination was not merely storage—it was a participant.
Maris proposed a different approach: let the filesystem be fluid. Instead of forcing a single fst, they would write many small, ephemeral tables and stitch them with timestamps and melodies — small maps that welcomed change. They pushed a soft patch to Dolphin: write snapshots, not maps; add hashes that allowed overlap and conflict; accept missing entries as signals, not errors.
On the following dive, the consoles were quiet with a new kind of attention. The probe sang back a stream of micro-fst fragments, each labeled with the moon's phase and a recorded current. Sometimes two fragments contradicted; Dolphin logged both, marking them with the ocean's timestamp. The error message never appeared again. "Failed to write new fst" reappeared only once more, as if the sea, polite and mischievous, had checked whether they still remembered how to listen. If you are seeing the error message "IOS_FS:
Weeks later, when the team examined the assembled archive, the data wasn't neat. It had overlaps, echoes, and gentle contradictions. But in the chaos, patterns emerged no static table would have shown: how a reef shifted with a night of warm water, how a sudden storm rewrote the seabed's ledger, how shoals nested and then dissolved. The many small fst fragments became a chorus.
Maris wrote an afterword in the log: "We learned the sea will not be tamed by a single table. Memory here is collaborative. The ocean writes back." The world took that lesson in modest ways; different teams adopted the idea, and other probes were taught to listen for protest instead of forcing shape.
Sometimes, late at night, the console that once flashed the red error still glowed in the lab. New engineers would gather, tell the story of Dolphin and the failed write, and listen to the recorded packets that sounded suspiciously like music. They called it the ocean's file-system: a living archive that refused to be pinned, and a machine that learned to be humble enough to share stewardship of memory with the sea.
The error message became a small monument: not a failure, but the moment someone learned to stop writing and start reading.
Troubleshooting Dolphin: How to Fix "IOS_FS: Failed to Write New FST"
The error "IOS_FS: Failed to write new FST" in the Dolphin Emulator can be incredibly frustrating, often popping up repeatedly and preventing games from launching. This issue typically indicates that the emulator is being blocked from writing to its own system or user files. Here is how you can resolve this and get back to gaming. 1. Disable "Controlled Folder Access" (Windows)
The most common culprit is Windows Defender's "Controlled Folder Access" feature, which blocks apps from modifying files in protected directories like Documents. Open Windows Security > Virus & threat protection.
Click on Manage settings under "Virus & threat protection settings."
Scroll down to Controlled folder access and click Manage Controlled folder access.
Either toggle it Off entirely or click Allow an app through Controlled folder access to add Dolphin.exe to the whitelist. 2. Add an Antivirus Exclusion
Third-party antivirus programs (like Avast or Bitdefender) often flag Dolphin’s constant read/write actions as suspicious.
Open your antivirus settings and find the Exclusions or Exceptions list.
Add both the Dolphin installation folder and the Dolphin Emulator user folder (usually located in Documents or %AppData%) to the list. 3. Relocate the User Folder
If file permissions in your Documents folder are corrupted or locked by a cloud service like OneDrive, moving the user directory can fix the problem. Open Dolphin and go to File > Open User Folder. Close Dolphin.
Move the entire Dolphin Emulator folder to a different location (e.g., directly onto your C:\ drive or another internal disk).
To tell Dolphin where the new folder is, you can create a blank file named portable.txt in the same directory as your Dolphin.exe. This forces Dolphin to use its local folder for all settings and saves. 4. Check for Disk Errors
Occasionally, this error is caused by minor file system corruption on your drive.
Right-click your SSD/HDD in File Explorer and select Properties. Go to the Tools tab and click Check under "Error checking."
Follow the prompts to Scan and repair drive if any issues are found. Summary Checklist Whitelist Dolphin.exe in Windows Security.
Disable real-time protection temporarily to see if the error persists.
Check OneDrive to ensure it isn't "syncing" and locking your Documents folder.
Run as Admin (only as a last resort, as this can sometimes cause other permission issues). Phase 3: Revert to Stock NAND (If using
Which version of Dolphin are you currently using, and are you on Windows or Android? How to Fix Dolphin issue: IOS_FS: Failed to write new FST
hey guys what's up and welcome back today in this video I'm going to show you how to fix this issue while opening dome in your PC. YouTube·TeckBeen Gaming Tips Error when starting Dolphin emulator in Launchbox: "IOS_FS
The error "IOS_FS: Failed to write new FST" in the Dolphin Emulator typically indicates a file system permission conflict where the software is unable to commit changes to its internal virtualized file system. This issue is most commonly triggered by external security software or restrictive OS-level folder permissions preventing Dolphin from updating its configuration or Wii NAND files. Core Causes of FST Write Failures
Security Software Interference: Windows Defender's "Controlled Folder Access" or third-party antivirus suites (like Avast or Bitdefender) often flag Dolphin's frequent read/write operations to the Documents folder as suspicious behavior.
Read-Only Permissions: If the Dolphin installation directory or the user data folder is set to "Read-Only," the emulator cannot generate the temporary or permanent File System Table (FST) files needed for operation.
Cloud Syncing Conflicts: Services like Microsoft OneDrive may attempt to sync the Dolphin Emulator folder in real-time, locking files and preventing the emulator from renaming or writing new data.
Directory Path Issues: Long file paths or running Dolphin from restricted system directories (like Program Files without admin rights) can lead to write failures. Proven Resolution Strategies Grant Security Exclusions:
Navigate to Windows Security > Virus & threat protection > Manage settings.
Under Exclusions, add the Dolphin executable and the Dolphin Emulator folder (typically found in %AppData% or Documents) to the whitelist.
Alternatively, disable Controlled Folder Access in Windows settings to allow Dolphin full write access to user directories. Adjust Folder Permissions:
Right-click your Dolphin Emulator folder and select Properties.
Uncheck the Read-only box and ensure your user account has Full Control under the "Security" tab. Implement Portable Mode:
To bypass "Documents" folder permission issues entirely, create a blank text file named portable.txt in the same directory as the Dolphin.exe.
This forces Dolphin to store all settings and NAND data locally within its own folder, rather than in the system's protected user directories. Rename User Folders:
In some cases, simply renaming the Dolphin Emulator folder to just Dolphin in your Documents can resolve pathing conflicts, though this may reset your settings. Technical Impact
While the error is often described as "annoying" but not always fatal to emulation, it can lead to more severe issues such as:
NetPlay Desyncs: Mismatched FST data between two clients can cause immediate disconnection in multiplayer.
In-Game Crashes: Certain titles like Super Mario Sunshine may experience increased instability if they cannot properly write to the emulated file system.
Boot Failures: In extreme cases, Dolphin may fail to launch entirely until the write block is removed.
The error ios-fs failed to write new fst in Dolphin Emulator indicates a problem with the emulated Wii System Menu trying to update the File System Table (FST). This usually happens when you are installing a WAD (Wii Channel), updating the Wii System Menu version, or attempting to save settings within the Wii Menu.
Because the Wii Menu expects hardware characteristics that standard computer file systems don't have, Dolphin struggles to simulate the "write back" process to the virtual NAND.
Here is a step-by-step guide to troubleshooting and fixing this issue.
If the solutions above did not work, you are dealing with a deeper issue. Try these advanced tactics.
