Starts and Saves

Fix a New Campaign Freeze

Full Steam release · Sources checked November 19, 2026

The short answer

Update Imperionis in Steam before retrying New Campaign. The developer published a specific fix for a launch-era startup freeze. On the updated build, continue through commander setup and the first day normally. Esc opens the quit menu in the newer controls update.

On this page

Match the symptom before acting

The reported pattern was specific. A player finished a first run, then the game froze every time they tried to start another. The developer identified that problem, initially suggested Esc, and later told the player to update because a fix had shipped. If a continued campaign loads correctly and only a fresh one stalls, that is the useful distinction to make when comparing your situation with the original report.

A freeze while continuing a campaign is a different symptom. A freeze during a battle is also outside that report. Record where the screen stops before changing any settings. For a fresh start, distinguish a stall before the commander setup, a stall while confirming the commander, and a stall as the first day opens. You will then have something concrete to compare after the update.

Update the build and retry a fresh start

Close the running game before testing the new build. In your Steam Library, select Imperionis and allow any queued download for it to finish. Open the same library entry again. The store lists Imperionis and Imperionis Demo separately, so updating one entry does not confirm the other is current. This startup report concerns the full game.

Select New Campaign and give the game time to reach the commander setup. After you confirm your choices, look for the first day’s event. Make one normal attempt without using the old workaround. These two checkpoints matter because the newer controls notes explicitly address skipping commander setup and the first day while loading. If the game makes it through both screens, the fresh-start path worked on this attempt.

Read the patch history in order

The first Day One announcement described new commander choices, recruitment, and other changes. A follow-up said a build issue had kept some of those changes out of the previous download and that the final Day One build corrected it. A separate announcement then identified the critical new campaign startup fix. This is why a launch-day screenshot or a remembered download does not settle which behavior your installation has.

The developer’s early Esc reply belongs to the freeze thread before the fix. The later controls update says Esc opens a quit menu from the map, camp, events, or battle. It also says repeated presses while loading no longer skip the commander setup or the first day. If a quit prompt appears, read it before choosing what to do. Treat the presence of that menu as a control behavior, and check the actual setup and event to judge startup.

If an updated build still stalls

Write down whether you were starting or continuing, the last screen that appeared, and whether the same attempt stalls again. Include whether you launched the full release or the demo. If you know the build or the date Steam completed an update, include that as well. Post those details in the game’s Steam discussions so the report can be compared with the fixed symptom.

Keep any existing campaign intact while you isolate the problem. The developer said existing campaigns can continue after the Day One update, with fresh commander traits applying only to new runs. If your immediate goal is to identify the files for an existing campaign, use the Windows save-location guide below. Neither the freeze report nor the fix instructs you to remove a save folder.

What to check before you move on

A fresh campaign reaches commander setup, accepts your choices, and presents the first day. If it stops, report the precise stopping point and the Steam edition.

Sources & version

Release notes and developer replies linked below. is the guide’s revision date.