How to fix "Internal error: CallSpawnServer: Unexpected response: $0" in Windows?

"Internal error: CallSpawnServer: Unexpected response: $0" is not a Windows error. It comes from installers built with Inno Setup, when the setup tries to start a program for you and its own background helper no longer answers. Run the setup file as administrator first; it then needs no helper at all.

Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What "CallSpawnServer: Unexpected response: $0" means

Many programs, from games sold on GOG to music players and audio tools, use Inno Setup to build their installer. When you start such a setup, Windows shows the UAC prompt and the setup starts a second copy of itself with administrator rights. The first copy, with your normal rights, stays quietly in the background. Inno Setup calls it the spawn server.

The spawn server has one job: when the installer must start a program as you, not as administrator, the elevated copy sends it a message and the spawn server starts that program. In Inno Setup's source code, the function that sends this message is CallSpawnServer. If the reply is not the one it expects, the setup stops with "Internal error: CallSpawnServer: Unexpected response: $0". A reply of 0 means the message was not handled at all, most often because the first copy is gone.

• Spellings people search: callspawnserver unexpected response $0, internal error call spawn server unexpected response $0, and the misprint "Interal error" seen in a developer note.
• In Vietnamese, Indonesian, Turkish and other searches ("đây là lỗi gì", "lỗi gì", "maksudnya"): the answer is the same. The installer's background helper did not answer, and the program may already be installed.
• Close relative: "CallSpawnServer: Unexpected status" comes from the same hand-over and has the same fixes.

Why the installer gets the $0 reply

Most often the first copy of the setup was closed before the end. A developer note shows one way this happens: the installer's own script closes the program by its file name, the setup file has the same name, and the script ends the setup's own helper too. Less often a security program or a task cleaning tool ends the background copy. Rarely the setup runs from a place where Windows cannot keep the two copies talking, for example from inside another app's download window.

How to fix "CallSpawnServer: Unexpected response: $0"

Fixes 1 and 2 avoid the hand-over that fails and help most readers in two minutes. Fixes 3 and 4 deal with the installer itself. Fixes 5 to 7 are for the few cases where something else on the PC ends the setup.

Fix 1. Start the setup file with Run as administrator

2 minutesLow riskEveryone who sees the error, wherever in the install it appears.

Inno Setup's help says that when you start a setup with Run as administrator, it has no chance to run anything with your original rights. Its code then starts programs directly and never calls the spawn server, so the step that returns $0 is skipped.

1. Close the error window and any setup window that is still open.
2. Open the folder where you saved the setup file, usually Downloads.
3. Right-click the setup file and select Run as administrator.
4. Select Yes in the User Account Control window.
5. Go through the setup as before and select Finish.
6. If the program opens at the end, close it once and start it again from Start, so it runs with your normal rights.

Run a setup as administrator only when it comes from the program's maker or a store you trust: it gets full access to Windows. More about this setting: How to run a program as administrator or in compatibility mode

Fix 2. Untick Launch on the last page and start the program yourself

2 minutesNo riskThe error appears after you select Finish on the last page of the setup.

Inno Setup's help says that the check boxes on the last page (the postinstall entries, such as Launch the program or View the README) run with your original rights by default. Those are exactly the entries that go through the spawn server. With the boxes clear, the setup has nothing to hand over.

1. Select OK in the error window. The files are usually already copied at this point.
2. Open Start and look for the program. If it is there, start it: you are done.
3. If it is not there, run the setup again.
4. On the last page, Completing the Setup Wizard, clear every check box, such as Launch or View the README file.
5. Select Finish, then start the program from Start or its desktop shortcut.

Fix 3. Rename the setup file so it differs from the program's name

2 minutesNo riskThe setup file has exactly the program's name, for example Program.exe instead of Program-setup.exe, and Fix 1 did not help.

A developer note describes this error when an installer's script closes the program by its file name and the setup output file was given the same name. The script then ends the setup's own helper. A different file name keeps the helper out of reach. We could not confirm that every installer with this error works this way, but renaming is harmless.

1. Close the error window and every setup window.
2. Open Downloads in File Explorer and select the setup file.
3. Press F2 and add -setup before .exe, for example Program-setup.exe. Press Enter.
4. Right-click the renamed file and select Run as administrator, then Yes.
5. Install as usual.

If File Explorer does not show .exe at the end of file names, select View > Show > File name extensions on Windows 11, or the View tab and File name extensions on Windows 10.

Fix 4. Get a fresh installer from the program's maker

10 minutesNo riskThe error stays after Fixes 1 to 3, or the same setup fails on another PC.

The message is part of the installer that the maker built, so only the maker can change it. A newer installer may be built with a newer Inno Setup or a corrected script. Makers learn about such faults from user reports.

1. Delete the setup file you have.
2. Download the newest installer from the maker's own website or the store you bought the program in, for example the GOG Galaxy library for a GOG game.
3. Run it as administrator, as in Fix 1.
4. If the error stays, write to the maker's support or forum. Give the full error text, the setup file name and version, and the step where it appears.

Fix 5. Close task tools and pause third-party security software for one install

5 minutesLow riskYou use a third-party antivirus, a game booster, a RAM cleaner or a tool that ends background processes, and Fixes 1 to 4 failed.

The spawn server sits in the background with no window of its own, which makes it look like a stray process to tools that end such processes. If something ends it during the install, the next hand-over returns $0.

1. Close game boosters, memory cleaners and task killer tools from the notification area.
2. Open your antivirus and pause its real-time protection for the shortest time it offers.
3. Run the setup as administrator straight away.
4. Turn the protection back on as soon as the setup ends, whether it worked or not.

Fix 6. Install from a clean boot

15 minutesLow riskYou cannot tell which background program ends the setup, or you have no third-party antivirus.

A clean boot starts Windows with only Microsoft services. If the setup works then, a startup program or service was ending the spawn server, and you can switch the others back on one by one to find it.

1. Open System Configuration. Select Search on the taskbar, type msconfig and select System Configuration from the results.
2. Hide Microsoft services. On the Services tab, select the Hide all Microsoft services check box. Only services from other companies stay in the list.

   

3. Disable the remaining services. Select Disable all, then select Apply.
4. Open Task Manager. On the Startup tab of System Configuration, select Open Task Manager.

   

5. Disable the startup apps. On the Startup apps tab in Task Manager, select each item whose status is Enabled and select Disable. Write down or take a screenshot of the items you disable: you need the list to turn them back on.

   

6. Confirm the changes. Close Task Manager. On the Startup tab of System Configuration, select OK.
7. Restart and test. Restart the PC. Windows now starts in a clean boot environment: try again the thing that failed (run the app, install the update, uninstall the program).

These steps were written for Windows 11 25H2 and 26H2. The full page with the other versions and what each result means: How to perform a clean boot in Windows

Fix 7. Repair Windows system files with SFC and DISM

20 minutesLow riskMany different installers fail on this PC, not only this one.

The two setup copies talk through standard Windows window messages. That part of Windows rarely breaks, so this is the last step, not the first. It is worth running only when other installers also fail.

1. Open an elevated command window. Right-click Start and select Terminal (Admin), or type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.

   

2. Run DISM first. Type the command below and press Enter. DISM downloads clean copies of damaged components from Windows Update, so it can take several minutes. Wait until it says The operation completed successfully.

   DISM.exe /Online /Cleanup-Image /RestoreHealth

   

3. Run System File Checker. In the same window, type the command below and press Enter. Do not close the window until the verification reaches 100%.

   sfc /scannow

   

4. Read the result and restart. Compare the last message with the table below this guide, then restart the PC so that repaired files are loaded.

   

These steps were written for Windows 11 24H2 and 25H2. The full page with the other versions and what each result means: Run DISM and SFC to repair Windows system files

If "CallSpawnServer: Unexpected response: $0" is still there

Check first whether the program is already installed: open Start or Settings > Apps > Installed apps and look for it. In many cases the error comes only at the very end, so the program works and only the launch failed.

• Write a setup log. Inno Setup installers accept the /LOG switch. Press Win + R, drag the setup file into the box, add /LOG="%USERPROFILE%\Desktop\setup-log.txt" and press Enter. The log on the desktop shows the last step before the error.
• Send the maker: the full error text, the setup file name and version, your Windows version from Settings > System > About, the log, and which fixes you tried by number.
• Check the file: if the setup did not come from the maker or a known store, scan it with Microsoft Defender before you try again: How to scan for malware with Microsoft Defender

How to keep the CallSpawnServer error from coming back

If you build installers yourself with Inno Setup, give the output setup file a name that is not the same as the program's file name, and do not end processes by that name in the script while the setup is running.

Frequently asked questions

What does "Internal error: CallSpawnServer: Unexpected response: $0" mean?

It means an installer built with Inno Setup asked its own background copy to start a program and got no valid answer. The first copy of the setup runs with your normal rights and starts programs for you; the second copy has administrator rights and does the install. When the first copy is gone, the reply is 0, shown as $0. The program itself is often already installed. Running the setup as administrator, Fix 1 on this page, avoids the hand-over.

Is the CallSpawnServer error a virus?

No. The message is a normal part of the Inno Setup installer engine, which many honest programs use. It tells you that the two copies of the setup lost contact, nothing more. A virus is a separate question that depends on where the setup file came from. If you took it from the maker's site or a known store, there is no reason to worry. If it came from an unknown download site, scan it with Microsoft Defender before you try again.

Where do I click to fix it?

Close the error window first. Then find the setup file in your Downloads folder, right-click it and select Run as administrator, and select Yes in the window that Windows shows. Go through the install again. If the error appeared right after you selected Finish, also clear the Launch check box on the last page before you select Finish. Then start the program from the Start menu. These two clicks are Fix 1 and Fix 2.

Is the program installed after the error?

Often it is. When the error appears after you select Finish, the files were copied before the setup tried to launch the program or open a README file. Open Start or Settings, then Apps and Installed apps, and look for the program. If it is listed and starts, you can ignore the error. If it appears in the middle of the install, the setup may have stopped early; run it again as administrator.

Why does Run as administrator help?

Inno Setup's help explains that a setup started with Run as administrator has no way back to your normal rights. In that case it does not use the background helper at all and starts programs directly. The step that fails with $0 never happens. The only side effect is that a program launched at the end also runs as administrator, so close it once and start it again from Start.

I see this error with a GOG game, MediaMonkey or Cakewalk. Is it the same?

Yes. Users report the same message with GOG game installers, MediaMonkey and Cakewalk, because all of them use Inno Setup. The fixes on this page work on the installer, not on the program, so they are the same. If the newest installer from the maker still fails after Fixes 1 to 3, report it on the maker's forum or support page with the full error text and the setup file name, as Fix 4 says.

What is CallSpawnServer?

It is the name of a function inside Inno Setup, the free installer builder. The function sends a request from the elevated copy of the setup to the first copy, which Inno Setup calls the spawn server, to start a program with the user's original rights. It then waits for that program and asks for its result. Two messages come from it: "Unexpected response" when the first request fails and "Unexpected status" when a later check fails.

Will SFC, driver updates or a new .NET Framework fix it?

Rarely. The earlier version of this page listed them, but the error comes from the installer, not from Windows files, drivers or .NET. The setup engine is a self-contained program that does not use .NET. SFC and DISM are worth a run only when many different installers fail on the same PC, which is Fix 7. Driver and .NET updates were dropped from this page because they do not touch the part that fails.

I searched in another language. Is there a guide in Spanish, Italian or Chinese?

This page is in English only. The error text is the same in every language, because it is an internal message of Inno Setup and is not translated. People search "como resolver", "come risolvere", "böyle hata veriyor" or "これはなんで" and get the same answer: run the setup as administrator and untick Launch on the last page. If a translator tool helps you follow the steps, the buttons sit in the same places. A search for a school e-book installer such as 康軒電子書 leads here when its setup shows this error; the same fixes apply.