Using FogBugz On Demand? We've recently rolled out a new sidebar as part of taking FogBugz forward. Please see this article for details on what's new, what's changed, and where you can find all your favorite things.

Windows Setup steps

Setting up FogBugz on a Windows server is as easy as double-clicking the FogBugz-Setup-Version.EXE file (where VERSION is 8.8.53, for example) that we distribute and following the instructions on screen.

FogBugz setup uses a wizard interface to walk you through the setup one step at a time. At any point you can cancel, and it will roll back any changes you have already made.

When you run FogBugz setup, if anything goes wrong during the main phase (in which you see a progress indicator), after the error message is displayed, FogBugz Setup gives up and rolls backwards.

There are command-line arguments to the Setup EXE program which can be used to ignore errors and continue anyway:


Will allow Setup to continue even if it can’t set up a virtual directory in IIS. You will need to create a virtual directory manually and map it to the FogBugz\website directory. Requires FogBugz Setup 3.0.5 or later.


Will allow Setup to continue even if it can’t set permissions for the FogBugz account (that you specify during Setup) to access the FogBugz directory. You will need to grant full permission for the FogBugz account to access the FogBugz directory manually. Requires FogBugz Setup 3.0.7 or later.


Will allow Setup to continue even if it doesn’t pass the Windows version check. This can happen for FogBugz running on Windows 2003 in a different language so that the check for SP2 fails. Requires FogBugz Setup 6.1.11 or later.


Run this on the SQL Server. It will tell Setup to only install the SQL Server components.  This is useful if your SQL Server machine is a different machine than your IIS machine and they are not on the same domain. You may need to change ownership to dbo if you get a security error when connecting FogBugz to the SQL server database; more here.