Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 09/27/2018 in all areas

  1. Thanks. Whole problem lies in Microsoft Win8.1+ (and higher) bug (errr, they called it "feature by design"), that it does not report all CPU-supported features when Hyper-V is enabled (i.e. when Hyper-V is disabled, it reports "Skylake-based processors", but when Hyper-V is enabled, it reports "Core 2 Duo 8000 series"). I will try to develop some workaround but I must ensure that it does not influence backward-compatibility.
    2 points
  2. I've pinned this topic until it is fixed, so others with the same problem know about it.
    1 point
  3. I do remember that the issue you were talking about was with Malwarebytes not Avast. The person who had it reported it to Malwarebytes but they weren't able to reproduce the issue so he wrote about it here and he found out that it was due to oleaut32.dll.
    1 point
  4. No problem. And thank you for the explanation! Interesting that to know that Windows does this. At any rate, thanks again for your time and attention to this matter-- can't wait for your next update. I'd say my donations were definitely well worth
    1 point
×
×
  • Create New...