stapp 160 Posted May 26, 2018 Report Share Posted May 26, 2018 Win 10 using 8668 after autoupdate to new build. After having build on machine for half an hour or so, I decided to do a manual malware scan via GUI menu. The scan ended almost immediately. I asked to view logs for scan via scan window, and got a popup saying I couldn't look at the log as it wasn't available. So I opened general logs and it just says the scan is still in progress (and is still stuck saying this) Included are debug logs , db3 logs, and 2 screenshots. a2service_20180526043820(1728).zip Link to post Share on other sites
stapp 160 Posted May 26, 2018 Author Report Share Posted May 26, 2018 I can open logs from GUI but scan is still showing as scanning. Seems to be stuck on memory? Link to post Share on other sites
stapp 160 Posted May 27, 2018 Author Report Share Posted May 27, 2018 By the way.. today after a cold boot this morning (Fastboot disabled) forensic logs still show that scan as running Link to post Share on other sites
Frank H 110 Posted May 28, 2018 Report Share Posted May 28, 2018 As expected we'll check your logs stapp Link to post Share on other sites
Frank H 110 Posted May 30, 2018 Report Share Posted May 30, 2018 we've checked your logs and we see that the scan crashes, which caused the abnormal termination of it. The culprit is unknown though. if you are able to replicate, we will dive into this deeper, as for now it seems to be a one time issue. Link to post Share on other sites
Recommended Posts