<snip quotes>
I dont know if the others are just as confused as me. But you clearly wrote its a limitation of windows xp? Sorry but if windows xp has a limitation of not recording the boot time scan on the scan history section of avast, what is that got to do with windows 10? The other person whom shares the same issue as me is on a windows 10 machine.
<snip>
This topic isn't just about win10 but about this 17.2.2286 update, it is about all supported OSes.
You need to read further back, as this was a communication between Asyn (that is why I quoted him.
Some were asking if the scan history entry was created I reported that it wasn't creating a Scan History. Asyn said it was in win10. After further investigation I/we determined that the fact it wasn't creating a scan history entry was because it is apparently a limitation of XP. So it is about confirming that some OSes (XP) won't create a scan history entry.
I still dont think you understand the issue here, the issue is the log is not being made on windows 10 OS, why are u mentioning windows xp? XP has nothing to do with the issue, as Asyn said the log is created in the scan history section of avast in a windows 10 machine BUT THREE PEOPLE have confirmed it is not. So your statement here:
"This topic isn't just about win10 but about this 17.2.2286 update, it is about all supported OSes." And you said "So it is about confirming that some OSes (XP) won't create a scan history entry."
These statements are contradictory since you saying certain OSes wont record the log and only mention XP? if that was the case why is it Asyn has a log in his windows 10 machine yet three people dont on the same windows 10 OS? This is not certain (OSes) as you call it but a issue with windows 10. I proved the previous verison of avast did indeed record the log i even attached a pic. So its not the OSes as you claim. I dont know why ur emphasis is on (Oses) when u clearly talking about xp not recording the log IF YOU WERE TO test the older version of avast on WINDOWS 10 you will see a log. YOU CLEARLY stated a windows xp machine wont create a log. The issue IS NOT WITH WINDOWS XP its with windows 10.
...
Sorry I am not being rude, please forgive me if i am. Here is a simplified version of the issue, as windows XP has no bases on on the issue:
1) Three windows 10 machines not login the scan
2) Asyn has a pic of the log being recorded on a windows 10 machine.
Clearly there is a bug if asyn claims there is a log being made on the windows 10 machine yet three people dont have the log the test you did on windows xp is pointless as the issue is ON A WINDOWS 10 MACHINE.
