Skip to content

Flair 7.30 Beta Hangs Then Crashes on Windows 10 + AMD GPU

Summary

An offline Flair install on a Windows 10 gaming PC with an AMD GPU stopped starting: Flair 7.30 beta (release dated 5 Feb 2026) hangs for roughly 60 seconds on every launch, then crashes, apparently while drawing. Every other version installed on the same machine works fine. Graphics driver changes and resolution changes did not resolve it; restoring an ini backup from a working version also did not help. The only working fallback found was reverting to a previous Flair version.

Symptoms

  • Flair 7.30 beta hangs for about 60 seconds on every launch attempt, then crashes.
  • Crash appears to occur during a drawing/rendering step.
  • Every other Flair version installed on the same PC launches and runs fine.
  • Machine is a Windows 10 gaming PC with a "heavy duty" AMD GPU.
  • Trying different graphics drivers does not resolve it.
  • Trying different display resolutions does not resolve it.
  • Restoring a known-good flair.ini from a working version does not resolve it.
  • Multiple PC restarts do not resolve it.

Community Guidance

[OPEN] No Confirmed Fix — Revert to a Previous Version

Community — 23 June 2026

"My offline flair on windows just refuses to start today. Have a ton of previs today and can't figure out what's going on. It just hangs for 60 seconds and crashes on every boot... Win10 gaming PC with an heavy duty AMD GPU. Tried different graphics drivers and resolution. Seems like it crashes on drawing."

No working fix was found in this thread — the operator fell back to an older Flair version to keep working. If you hit this on 7.30 beta specifically with an AMD GPU on Windows 10:

  1. Try reverting to the last known-working Flair version rather than continuing to troubleshoot 7.30 beta under time pressure.
  2. If you have time to investigate further, this looks worth a formal bug report to MRMC/Multidyne (Flair report line) given the AMD-GPU-specific pattern and the "crashes on drawing" symptom — a full driver reinstall (not just switching driver versions) and a clean AMD driver uninstall via DDU may be worth trying, though neither was confirmed in this thread.

confidence_score: 0.55