Insights · guide
Launch an XR project automatically after a reboot
Drafted with Insight · edited by The WE ARE VR team
development

A reboot should be boring.
I wrote this because XR computers often restart during venue setup. A startup shortcut can save time, but it can also launch yesterday’s broken build.
What's the problem?
Automatic startup sounds simple: the computer boots, then your XR project opens. That is useful for installations, demos and repeat activations across Jozi.
The trouble starts when startup is controlled at the computer level. A Windows Startup folder shortcut, for example, does not know whether a project is ready. It only knows which file to open.
Developers then replace a build during testing and forget about the shortcut. The next reboot launches an unfinished menu, an expired test scene or a build pointing at the wrong headset. At a venue, that mistake becomes a queue while someone searches for a keyboard.
A global startup setting creates another problem. Teams may use one machine for several commissions. Project A needs automatic launch for a museum installation. Project B is still being tested. One computer-wide switch cannot express that difference safely.
[The computer is being obedient, which is rarely comforting during setup.]
What's the solution?
Use a per-project startup switch.
This is a setting stored with each project. When enabled, the project manager launches that specific project after the computer starts. When disabled, the machine boots normally and waits for you.
Deez Project Manager added a per-project “Run on startup” toggle on 8 November 2026. The useful part is not the toggle itself. It is the habit around it.
Keep startup disabled while a project is being built. Enable it only after naming and testing a known-good build. A known-good build is the exact version your team has approved for public use.
For example, imagine a six-headset activation in Rosebank. The operator computer runs a spectator view and controls each session. Once the approved build passes testing, you enable startup for that project only. You then restart the computer from the Windows menu and watch the complete sequence.
Check that the project manager opens, selects the correct project and launches the correct executable. Confirm that audio uses the intended device. Make sure the headset reconnects without manual clicks. Finally, close the application and verify that staff can still reach the desktop if something fails.
Do not test by closing and reopening the project manager. That skips the slow hardware detection and login behaviour that happen during a real boot.
Also leave one clear escape route. Staff should know the keyboard shortcut, admin action or physical button that stops automatic launch. Write it on the setup sheet beside the machine name.
The smallest safe rule is this:
Enable startup for approved event builds, not active development projects.
What's next?
- Choose one XR project that genuinely needs automatic launch. Leave every other project disabled.
- Label its approved build with a date or version, enable startup, then perform two full reboots.
- Give the event lead a one-line recovery instruction and test it before leaving the venue.
Share your startup checklist or ask us about a stubborn Jozi venue setup.
The WE ARE VR team
