Support

Collect logs

Use launcher reinstall steps and collect the required CSS Launcher and CSS 737 logs for support requests.

Updated Latest published version

If the aircraft loads without initialized CSS 737 Classic systems, check license status and antivirus blocking. If multiple systems behave erratically, uninstall and reinstall via CSS Launcher. Include CSS Launcher\CSS_Launcher_Log.txt and Community\css-core\log.txt with support requests.

Check license and antivirus state

The manual links a non-initialized aircraft state to CSS 737 Classic systems not initializing. Start by checking license status and whether antivirus software blocks CSS Launcher processes.

Reinstall if systems behave erratically

If multiple aircraft systems behave erratically, uninstall and reinstall the aircraft through CSS Launcher before escalating.

Attach the correct logs

The launcher log is located at CSS Launcher\CSS_Launcher_Log.txt. The CSS 737 log is located at Community\css-core\log.txt. Submit both together with support requests.

Related articles

Continue through the launcher workflow or jump to the next support step.

Back to all articles

Need support?

Collect the article context and logs first, then open support.

Get support

Source: CSS Launcher User Manual, Rev. 5 — December 2025.