Windows Smart App Control Blocks Flair 7 After Update¶
Networking / InTime Resolved All rigs
Summary¶
Windows Smart App Control (SAC), a security feature that blocks unsigned executables and DLLs, can silently prevent Flair 7 from running after a Windows update. The two affected files are filmbox.dll and libcurl.dll — both used by Flair 7 but not code-signed. Flair Classic is unaffected because it uses a different process for FBX.
Symptoms¶
- Flair 7 fails to start after a Windows update
- Classic opens normally; only Flair 7 is broken
- No obvious error message — Flair 7 simply does not open
- Issue appeared after a Windows Security or feature update
Root Cause¶
Windows Smart App Control verifies that executables and DLLs are signed by a trusted publisher. Flair 7 includes filmbox.dll and libcurl.dll which are not code-signed. After a Windows update that enables or tightens SAC enforcement, these DLLs are silently blocked and Flair 7 cannot load.
Flair Classic uses a different FBX loading path and does not load filmbox.dll, so it continues to function.
Resolution¶
Disable Smart App Control¶
- Open Windows Security → App & browser control → Smart App Control settings.
- Set Smart App Control to Off.
- Restart the PC.
- Flair 7 should now open normally.
Re-enabling SAC without reinstalling Windows
SAC can be re-enabled via a registry edit (without a full Windows reinstall), per community testing. However, re-enabling SAC will block Flair 7 again. For a Flair PC, leaving SAC permanently disabled is the recommended state, as MRMC-supplied software may contain other unsigned components.
SAC cannot be turned off in certain modes
On some Windows 11 builds, SAC can only be disabled if it was never turned on (it enters a permanent "on" state after being used). If SAC is stuck on, a Windows reinstall may be needed. This is another reason to keep Flair PCs air-gapped from the internet and to disable Windows Update.
Evidence from Community Chat¶
"Microsoft did it again: filmbox.dll and libcurl.dll can't be verified by Windows as safe." — Niko (2026-03-18)
"So take care if you update Windows, Flair 7 is not working. No problems with Classic." — Niko (2026-03-18)
"The problem is that the files are not signed. The fix is to deactivate Smart App Control." — Niko (2026-03-18)
"Reactivating SAC is possible and not necessary to reinstall Windows — there's a trick with registry edit." — Niko (2026-03-19)
"Flair 7 uses a different process for FBX than Classic." — MRMC Support (2026-03-18)
See Also¶
- NET windows updates intime — Windows updates as a broader risk to Flair/InTime
- NET win11 intime upgrade — Other Windows 11 compatibility issues with Flair
WhatsApp Excerpts¶
- 2026-03-01 03:27 - ~ Marcin Biegunajtys: Yeah, I’ve been needing to constantly only do 2-3 keys here and there, so ability to manipulate waypoints in view space would solve a lot of fiddling around.
- 2026-03-01 03:31 - ~ Marcin Biegunajtys: Correct, I use those all the time, super useful. I’m talking when I need to adjust 2 or 3 keyframes and they happen to be off axis (not 0, 90, etc straight line), and if I needed to raise or lower, or push pull, but staying in line with the move that was built. Right now I believe that because we’re in world axis, moving the axis immediately wants to solve a new solution and it often adds weird s curves
- 2026-03-01 05:18 - ~ Ryan Maslyn: ~ MRMC Support added ~ Ryan Maslyn
- 2026-03-01 22:46 - ~ Niko: Beziers can give you more control of the path and timing, sometimes very useful