stapp

CLOSED Scan problem with 8668

Recommended Posts

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

Share this post


Link to post
Share on other sites

By the way.. today after a cold boot this morning (Fastboot disabled) forensic logs still show that scan as running :lol:

Share this post


Link to post
Share on other sites

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.

 

 

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.