BCML Cemu Settings Could Not Be Found

BCML shows “BCML Cemu Settings Could Not Be Found” when it can’t read Cemu’s settings.xml, often due to a wrong folder path, a missing file, or blocked access.

BCML is meant to be simple. Set your paths, remerge, play. When it throws a “settings could not be found” message, it usually means one small piece of setup is off, not that your whole mod stack is ruined.

This article starts with quick checks you can run in minutes, then moves into the cases that waste the most time, like multiple Cemu folders, portable installs that were moved, and permission mismatches.

Why BCML Can’t Find Cemu Settings

BCML reads Cemu’s config so it knows where to export the merged graphics pack. On most installs, that config is a file named settings.xml in the same folder as Cemu.exe. If BCML can’t read it, it stops and shows the error.

If you want a fast clue, look at what changed right before the error started. A Cemu update, a folder move, or a drive letter change are the usual triggers.

These are the usual causes.

Cemu path points at the wrong folder — BCML is set to a shortcut target, an old version folder, or a nested folder that doesn’t contain settings.xml.
settings.xml doesn’t exist yet — a fresh Cemu folder may not create it until you run Cemu once and exit normally.
Cemu folder was moved — the file exists, but BCML still points at the old location.
Access is blocked — Windows permissions, antivirus actions, or mismatched admin settings can stop reads.
BCML settings are damaged — BCML stores its configuration in a local settings.json and can forget paths when that file breaks.

BCML Cemu Settings Could Not Be Found Fix Checklist

Run these in order. Most people are done before step five.

Open Cemu once — Launch Cemu, let it reach the main window, then close it from the menu so it writes settings.xml.
Find the real Cemu.exe — In the Windows file browser, open the folder that contains Cemu.exe. Skip desktop shortcuts.
Check for settings.xml — In that same folder, confirm settings.xml exists after you ran Cemu.
Set the Cemu folder in BCML — In BCML settings, point to the folder that contains both Cemu.exe and settings.xml, then save.
Remerge your mods — Click Remerge so BCML rebuilds the merged graphics pack output with the corrected path.

If you still see “bcml cemu settings could not be found” after this, the issue is usually a mismatched install, a broken settings file, or access rules getting in the way.

Read the full error text in BCML

BCML usually shows a short banner, then a longer traceback if you open details. That longer text helps you pick the right fix. If you see “No such file” or “FileNotFoundError,” you are still dealing with a path or missing settings.xml. If you see XML parsing text, the file exists but may be damaged, empty, or locked while Cemu is running. Close Cemu, rebuild settings.xml, then set the folder again in BCML.

Copy the path shown in the error — Paste it into the Windows file browser to confirm it points at the folder you expect.
Check the filename it wants — BCML is usually looking for settings.xml. If it references a different file, you may be pointing at a wrapper app, not Cemu itself.
Note when the error appears — If it pops up only during Remerge, focus on export paths and permissions. If it appears on launch, focus on the Cemu folder setting first.

Confirm The Cemu Folder BCML Must Read

BCML doesn’t care where your game files live. It cares where Cemu stores settings.xml. The path in BCML must be the folder that directly contains Cemu.exe and settings.xml, not a parent folder and not a subfolder.

Common wrong paths that look right

Shortcut confusion — A shortcut can target a different folder than the one you open day to day.
Nested extract folders — Some extracts create Cemu\Cemu\Cemu.exe. The inner folder is the one BCML needs.
Two installs on disk — One Cemu is in Downloads, another is in Games, and BCML is pointed at the older one.

Sanity-check your folder in one glance

Item	Where you should see it	What to verify
Cemu.exe	Cemu install folder	It launches Cemu normally
settings.xml	Same folder as Cemu.exe	It exists after one clean run
graphicPacks	Often inside the Cemu folder	BCML output lands inside it

If settings.xml is missing, fix that first. If it exists, but BCML still won’t accept the path, the next section is the usual fix.

Create Or Repair settings.xml When It’s Missing Or Broken

A missing settings.xml normally means Cemu never wrote it in that folder, or Cemu can’t write there. BCML will keep showing the error because it has nothing to read.

Extract Cemu fully — Don’t run it inside a zip viewer. Put it in a normal folder and launch Cemu.exe from there.
Exit Cemu from the menu — Use File then Exit so the config writes cleanly.
Move Cemu out of protected folders — Avoid Program Files. A simple path like C\Games\Cemu is easier for write access.
Check antivirus history — If settings.xml keeps disappearing, review quarantine logs and allow the folder.

If the file exists but looks damaged, rebuild it. BCML’s troubleshooting notes mention XML errors tied to corrupt Cemu settings. Make a copy of settings.xml, delete the original, then run Cemu once so it recreates a clean file. Set the Cemu folder again in BCML and remerge.

If you want to be extra careful, open the new settings.xml in a text editor and confirm it’s not blank. A zero-byte file can happen after a crash or a forced shutdown.

Good reference pages for this workflow include the official BCML troubleshooting file on GitHub and the BCML help page on ZeldaMods. You can link them in your notes: BCML trouble.md and ZeldaMods BCML help.

Reset BCML Settings When It Won’t Keep Your Paths

Sometimes Cemu is fine and the folder path is correct, yet BCML still acts like it can’t find settings.xml. That often points to BCML’s own settings being stuck or corrupted. The BCML maintainer has suggested moving the BCML settings folder aside so the app rebuilds it.

Where BCML stores settings on Windows

BCML keeps its user config under your Windows profile, in a folder named bcml inside Local AppData. Resetting it forces BCML to run setup again and lets you re-enter clean paths.

Open the Run dialog — Press the Windows button and R, type %LOCALAPPDATA%, then press Enter.
Find the bcml folder — Look for a folder named bcml.
Rename it as a backup — Change bcml to bcml_backup so you can roll back if needed.
Start BCML again — BCML will rebuild settings.json and prompt you for paths.
Re-enter folders and remerge — Set game, DLC, update, and Cemu folders again, then remerge.

This reset changes only BCML’s configuration. Your mod archives on disk are still there. You may need to re-add mods into BCML’s list, depending on how your install was set up.

Fix Multi-Drive, Portable, And Admin Mismatches

When the checklist and resets don’t do it, your setup is usually split across drives, moved around a lot, or running with mixed permissions. These setups can work fine, yet they fail when one piece points at yesterday’s location.

Split-drive installs

If Cemu is on one drive and BCML is run from another, link behavior can be unreliable. The ZeldaMods BCML help page suggests using the option to run without a Cemu install and disabling links for the master mod in some split-drive cases. That keeps exports working when hard links aren’t available across drives.

Keep Cemu on a fixed drive — Avoid removable paths that change letters.
Keep your folder names simple — Short, clear paths reduce setup mistakes.
Use the no-Cemu option when links fail — It can prevent link errors on split drives.

Portable Cemu folders that were moved

Cemu is often run as a portable folder you can move anywhere. If you moved it, BCML won’t follow. Open BCML settings, set the Cemu folder again, then remerge so the export path matches the new location.

Admin and permission mismatches

If Cemu runs with admin rights and BCML does not, they can end up with different access to the same files. BCML’s troubleshooting notes mention launch issues tied to this mismatch, and the same mismatch can also block file reads. Match the permission level for both apps.

Check Cemu compatibility settings — Right-click Cemu.exe, open Properties, then Compatibility, and see if admin mode is enabled.
Match BCML access — If Cemu is set to admin mode, start BCML the same way, or remove admin mode from Cemu.
Restart both apps — Close both, reopen, then remerge.

Verify export and activation inside Cemu

Sometimes the error shows up alongside a second problem, mods not taking effect. That’s often an export mismatch. You export to one Cemu install, then you launch a different one, so you never see the merged pack.

Make sure the Cemu folder you open for play is the same folder BCML is set to. Then confirm that BCML’s merged output exists inside that Cemu folder’s graphicPacks directory.

Open Graphic Packs — In Cemu, right-click Breath of the Wild, then open Graphic Packs.
Find the BCML pack — Look for a BCML entry or a BCML rules folder in the list.
Enable it — Make sure it’s checked so the merged output is active.

If you don’t see it, remerge in BCML, then reopen the Graphic Packs window. BCML’s docs also state you don’t need to launch the game from BCML for mods to apply, you just need the merged pack present and enabled.

Final Pass Checklist To Keep It Stable

Once you clear the setup snag, keep things steady so the error doesn’t return after a folder move or update.

Save a screenshot of your BCML settings page before changing anything.

Stick to one Cemu folder — Keep a single install location and avoid scattering test builds.
Run Cemu after updates — Open and exit once so settings.xml exists for that build.
Update BCML after moving Cemu — Any move to a new drive calls for repointing the Cemu folder.
Remerge after changing paths — Treat Remerge as the apply step.
Backup BCML config before big changes — Renaming the bcml folder is a quick safety net when you experiment.

If you ever see “bcml cemu settings could not be found” again, start with the fix checklist, then reset BCML settings if it won’t keep your folders. That sequence matches the official troubleshooting guidance from the BCML project and the ZeldaMods help page.