The setup wizard initialization currently happens once the InitMilestone.COMPLETED is reached.

On the first Jenkins startup, there is a risk that some code executed in another thread would call Jenkins#save before the setup wizard is initialized. Such code could be a groovy script, or in a third-party plugin.

In such a case, the Setup Wizard would be initialized with state RESTART and the instance wouldn't be initialized as expected.