New
#11
I'm on 1809 17763.134, maybe that's why I see a different screen?
You are correct. I've got the same build as you -- same screen. By the way, 1809 messes with the Defender definition update timestamp inside the program as it's off by several hours. The CU to .134 did not fix this issue. Timestamp in Windows Update is accurate. WD definition timestamp in 1803 is also correct.
I did my first full scan with Windows Defender on 1809, What the heck is this result lol
This was on Desktop machine, haven't tried one on the laptop yet or 3rd Desktop--aka Mom's PC, hers still running Avast currently til time to maybe switch it, but nervous a bit on switching it
Does One File scan work properly on Windows 10 1809 as well? First time used it for over a month, prior to that was only about 2 weeks at a time
Notice after i scanned 2 files one at a time, it took away the Threats Found -7447 message.
Looks like an uninitialized counter to me. Instead of zeroing it before starting, it was left with whatever value it had in it thus the large negative number. The compiler should have caught that or at least flagged it.
Yeah well for now left Defender activated, nearly switched back to Avast Free, since that was sorta alarming when first saw, but with negative number, and no performance problems decided to leave alone for now, and continue using Defender at this point. Still one household Desktop to possibly switch over to Defender if i choose to