Well, I see that the “as soon as Monday” release, isn’t. Still looking at v11.7 in the distribution packages. Why isn’t there an official response to this? Sure seems like someone is sitting on their hands about owning this and then marshaling the dev team to roll that build back officially until they get working code. That they let this slip through without catching this (fairly obvious bug, too) implies that things are loose, which for an AV threat company, is scary.