Update: We were able to finally reproduce the issue in our lab and it indeed seems it has to do something with our virtualization (possibly clashing with Forza's self-defense mechanisms, unconfirmed yet). Will keep you updated once we know more - until then, please use the fix involving settings VirtualizationMechanisms=0 in avast5.ini to disable it.