“Outdated ROM format”

For a version or format mismatch, record the build tag, the displayed game version and whether your own dump is a loose folder or a .nup package. Compare that information with the documented mechanisms below before changing files. These checks distinguish three different problems: a stale version label, package conversion, and platform detection.

What is documented, next door to the question, is how dumps are recognized. Build 54 reads a version from control.nacp or from ResourceSizeTable.Product.NNN so a loose dump does not have to display 1.0.0 forever. Builds 110, 135 and 188 describe the .nup container: pack base, update and DLC, or unpack them back to base, updates and dlc folders. Build 212 is tied to NUP platform detection failing when the base ExeFS is missing. If your list shows a wrong version or refuses a package, those are the notes that exist. They are not a transcript of an “outdated ROM” popup.

A useful follow-up is the exact sentence in the dialog, the build tag, and whether the dump is a loose folder or a .nup file. Until that sentence shows up in a public note, this page stops at the gap.