Avast keeps blocking something called machinecode.dll in Glary, which has never happened before. Then, even when I temporarily disable Avast’s shields, Glary won’t open because, it tells me, machinecode.dll is missing. So I reinstall Glary, and it works fine – but only if Avast’s shields have been disabled. As soon as they’re re-enabled, the problem begins all over again.
Haven’t seen this before. It’s the same version of Glary that I’ve had for a while, and the problem has persisted now through two cycles of Avast definition updates.