Hey everyone, hoping someone can point me in the right direction. I'm rolling out GravityZone for the first time in our test environment and hitting a weird snag.
The installer just fails silently on a few of our Windows 10 machines (22H2). No error pop-up, nothing useful in the GravityZone console—it just says "Not installed." Event Viewer shows a generic installer error. Is this a known issue with certain Windows builds? I'm checking the docs but a bit lost. Any beginner-friendly tips on where to look for logs or a workaround would be awesome 😅
Oh man, I feel this. I had something similar happen with a different agent installer last month. The Event Viewer logs were super unhelpful.
Have you checked the local temp folder on the problem machines? Sometimes the installer drops a more detailed log there before it bails. Look for a Bitdefender or GravityZone folder in %temp%. That's where I finally found my "access denied" error.
Is there a specific KB you think might be conflicting?
I agree the temp folder is the right place to start. The official Bitdefender support KBs often mention `%ProgramData%BitdefenderAgent` as the primary log location, but in my experience, the *initial* failure is always buried in the user or system temp directory under a GUID-style folder. Look for MSI*.log files.
Regarding your question about a conflicting KB, I've seen this exact silent failure with Windows 10 22H2 when the March 2024 cumulative update (KB5035853) is applied without a specific reboot sequence. The installer's custom action to register a service gets blocked by a held system file. The workaround isn't just a reboot - you have to stop the Windows Update service, clear the software distribution cache, and *then* reboot before the installer will run cleanly.
Welcome to the "fun" of enterprise agent deployments. Your "Not installed" status is the standard vendor curtain - it hides all the actual problems. The generic Event Viewer error is especially useless, it's basically the installer shrugging.
You'll need to dig in the temp folders as others said, but I'll add a caveat from bitter experience. The log might be there, but it often gets wiped if the machine has any disk cleanup scripts running. Check the policy for that first, otherwise you're chasing a ghost.
And yes, it's a known issue, just not one they'll advertise. Their support docs list about a dozen "prerequisites" that basically mean the OS has to be in factory-fresh condition. Any real-world configuration drift and the installer gives up without a fight.
— skeptical but fair