JosefNemec/Playnite · critical · Exception

Database version {Settings.Version} is not supported.

Error message

Database version {Settings.Version} is not supported.

What it means

Thrown as a generic Exception by GameDatabase.OpenDatabase() when the existing database's stored Version is greater than NewFormatVersion (the maximum version the running Playnite instance supports). This prevents opening a database created by a newer Playnite version with an older client, which would risk data corruption or misinterpretation of unknown schema fields.

Source

Thrown at source/Playnite/Database/GameDatabase.cs:538

            {
                File.Delete(FilesDirectoryPath);
            }

            if (!dbExists)
            {
                FileSystem.CreateDirectory(DatabasePath);
                FileSystem.CreateDirectory(FilesDirectoryPath);
            }

            if (!dbExists)
            {
                Settings = new DatabaseSettings() { Version = NewFormatVersion };
            }
            else
            {
                if (Settings.Version > NewFormatVersion)
                {
                    throw new Exception($"Database version {Settings.Version} is not supported.");
                }

                if (GetMigrationRequired(DatabasePath))
                {
                    throw new Exception("Database must be migrated before opening.");
                }
            }

            LoadCollections();
            LoadUsedItems();

            // New DB setup
            if (!dbExists)
            {
                // Generate default platforms
                var platforms = Emulation.Platforms.Where(a => a.IgdbId != 0).Select(a => new Platform(a.Name) { SpecificationId = a.Id }).ToList();
                if (platforms.HasItems())
                {

View on GitHub (pinned to 5911f4e964)

Solutions

  1. Upgrade Playnite to at least the version that created the database (check Settings.Version and install the matching or newer Playnite release).
  2. If downgrade is required, export the database data from the newer version (backup/JSON export), create a fresh database with the older version, and re-import.
  3. Start with a new empty database in the older Playnite version if the old data is not needed.
  4. Check the database settings file to see the stored version number and compare it against the installed Playnite version's changelog.

Example fix

// before — older Playnite opens newer DB
gameDatabase.OpenDatabase(); // throws if Settings.Version > NewFormatVersion

// after — check version compatibility and guide user
if (gameDatabase.Settings.Version > NewFormatVersion)
{
    Dialogs.ShowMessage(
        $"Database version {gameDatabase.Settings.Version} requires Playnite " +
        $"version {gameDatabase.Settings.Version} or later. Current supports up to {NewFormatVersion}.");
    return;
}
Defensive patterns

Strategy: validation

Validate before calling

if (gameDatabase.Settings != null && gameDatabase.Settings.Version > NewFormatVersion)
{
    logger.Error($"Database version {gameDatabase.Settings.Version} exceeds supported {NewFormatVersion}.");
    Dialogs.ShowMessage($"This database was created by a newer Playnite version. Please upgrade Playnite.");
    return;
}

Prevention

When it happens

Trigger: Opening a database created by a newer Playnite version with an older/downgraded Playnite install. The Settings.Version field in the database settings file is read and compared against NewFormatVersion; if higher, the error fires.

Common situations: User downgraded Playnite (e.g., from a beta to stable, or from v10 to v9) without reverting the database. A database was copied from a newer Playnite install to an older one. A beta tester's database has a version number the stable release doesn't recognize.

Related errors


AI-assisted analysis of JosefNemec/Playnite@5911f4e964 (2026-08-13). Data as JSON: /api/errors/15da8f25ef6f8edf. Report an issue: GitHub.