BambuStudio is slow on Windows? Check your antivirus first.
If BambuStudio on Windows shows any of these symptoms:
- Splash screen frozen for ~10–20 seconds before the main window appears
- Home tab is blank or flickers for a second or two after launch
- CPU pegged and fans at maximum while sitting idle on the Home tab
- The app generally feels sluggish for the first minute
…it is very likely your antivirus, not BambuStudio.
No rhetoric. Just evidence.
Why
Bitdefender (and OEM products that embed it, e.g. NETGEAR Armor
“powered by Bitdefender”) installs user-mode API hooks into running
processes. The hooks add a small amount of overhead to every Win32
call. BambuStudio’s startup and first Home-tab paint issue a huge
number of such calls in a short window, so the overhead adds up to
multi-second stalls and sustained CPU.
This is not a BambuStudio bug. The same symptoms reproduce on the
official v02.06.00.51 release on the same machine. Disabling
wxWidgets changes does nothing; the antivirus is the only factor.
How to confirm in 10 seconds
While BambuStudio is running, open Command Prompt and run:
tasklist /m /fi "imagename eq bambu-studio.exe"
If you see bdhkm64.dll or atcuf64.dll in the list, your
antivirus is injecting hooks into BambuStudio. That’s the cause.
Fix
Add an exclusion for bambu-studio.exe (and the install folder if
your AV supports it) in your antivirus product, then restart
BambuStudio.
- Bitdefender Total Security: Protection → Antivirus →
Settings → Manage exceptions - NETGEAR Armor: uses the same Bitdefender engine — exclusions
are reachable through the Armor app - Most other AVs: look under Settings → Exceptions / Exclusions /
Allowed apps
After the exclusion, the splash dismisses in under a second, Home
paints on the first frame, and CPU/fans behave normally.
What it is not
- Not a wxWidgets bug — both the production build and a build with
upgraded wxWidgets 3.2.10 LTS reproduce when the AV is active,
and both clear when the exclusion is added. - Not a security finding against the AV — it is doing what it is
designed to do; this is just a performance side-effect on a
GUI-heavy app.