Has anyone else had trouble installing Bitdefender GravityZone on a fresh Windows 11 Pro 26H2 virtual machine through Ninja? The package downloads successfully, but installation fails with an "OS not supported" message. The linked "here" text isn't actually clickable and doesn't provide a list of supported operating systems. I'm wondering whether Bitdefender's package hasn't been updated for the new build, whether Ninja is reporting the issue incorrectly, or whether this is specific to using a VM. Existing machines aren't being upgraded to 26H2 yet, but we're testing it for new deployments.
4 Answers
Try installing the Bitdefender agent manually outside Ninja first. That should help determine whether the problem is with the GravityZone installer itself or Ninja’s deployment process.
This sounds like Bitdefender’s installer is rejecting the new Windows build number rather than Ninja having a deployment problem. Check the GravityZone operating-system support list directly, and keep 26H2 out of wider deployment until Bitdefender confirms support.
We’re holding off on upgrading existing systems, but we’re testing 26H2 on new installs. I mainly wanted to see whether others were seeing the same behavior or if the VM was causing it.
Some Bitdefender integrations have historically lagged behind new Windows feature releases. If the standalone installer also fails, it’s probably an unsupported-build check in Bitdefender’s package. Opening a vendor ticket is the right move while waiting for an updated installer or support confirmation.
I’ve opened a ticket with Bitdefender. I was checking whether this was a broader issue before assuming it was just my test VM.
A manual install is the quickest way to narrow this down. If it works manually but not through Ninja, investigate the Ninja package or deployment script; if it fails with the same message, Bitdefender likely needs to add Windows 11 26H2 to its supported-build list.
I haven’t tried a manual installation yet, but I’ll use that as the next test.