This is not related to the keys in the registry.
Yes, that is exactly what I was trying to say in the previous comment. The problem is not related to the registry keys. The updates deliver just the keys, nothing else. It is true, that the update through avastemupdate does set the aswVmm\parameters\QualityCompat key, while the VPS update does not.
without a micro patch obtained through avastemupdata update via WSUS or WU does not work
There is no micro patch applied. The avastemupdate utility upgrades itself first, then the new one applies the registry keys. Nothing else is patched.
That is why more debug data from your WU/WSUS configuration was requested, so it would show us why the update is not offered.
>HKLM\SYSTEM\CurrentControlSet\services\aswVmm\Parameters\QualityCompat - Reg_Dword "1"<
And in our case this was the problem.
This is Avast's registry key. You should not set the value manually. If you have added it manually, check also, that you have OtherVMMs key present, otherwise you might get BSOD after restart!
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\aswVmm\parameters]
"OtherVMMs"=hex(7):61,00,76,00,67,00,76,00,6d,00,6d,00,00,00,61,00,73,00,77,00,\
76,00,6d,00,6d,00,00,00,00,00
"QualityCompat"=dword:00000001
I will get back as soon as I know more what the key is meant for.