Share via

windows defender review a file

Anonymous
2017-09-24T05:07:34+00:00

so this past tues afternoon i got home on computer i got notify action center windows defender wanted to review a file see suspicious send it to microsoft only 2 options were send file or don't send file was long name called ieprotectstream 3ca652151b04a48e958ac7b0dfb177a<-have no clue what this is

anyways i notice in my event viewer after i send it to them i see windows defender has encounter an error trying to upload a suspicious file to further analysis which is that same long file<-can anybody explain to me why that happen

did microsoft not get this file name or what is my windows defender still ok?

i have email ******@submit.microsoft.com early thurs morning if they got it any if i'm ok despite error in event error they still haven't respond back as of yet

i hope somebody will respond back to me asap very concern

Windows for home | Windows 10 | Security and privacy

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

40 answers

Sort by: Most helpful
  1. Anonymous
    2017-09-30T15:17:56+00:00

    I'm saying that the Automatic Maintenance Scan no longer runs on a daily basis, and consequently the Last scan information in the Windows Defender UI, or in the Windows Defender Security Center, is no longer being updated on a daily basis. That’s the new normal behavior (as far as I know), and it’s not the result of running manual scans. The scheduled scan itself has to actually complete successfully in order for the Last scaninformation to be updated, but the completion is failing most of the time, with a Last Run Result of 0x2 in Task Scheduler, and this entry in the MPCmdRun.log file:


    MpCmdRun: Command Line: "C:\Program Files\Windows Defender\MpCmdRun.exe" Scan -ScheduleJob -ScanTrigger 55

     Start Time: ‎Sat ‎Sep ‎30 ‎2017 00:37:12

    Starting RunCommandScan.

    RunCommandScan is using default scan type: 1.

    Scanning path as file: (null).

    Start: MpScan(MP_FEATURE_SUPPORTED, dwOptions=16385, Timeout in days = 1)

    MpScan() started

    MpScan() was completed

    ERROR: MpScan(dwOptions=16385) Completion Failed 80508018

    MpCmdRun: End Time: ‎Sat ‎Sep ‎30 ‎2017 00:37:13


    So the Last scaninformation will normally fail to be updated for several days if you don’t run a manual scan. But if you’re actually saying that the Last scan information is failing to update even when you get a notification that Windows Defender has successfully scanned your device, or when you run a manual scan, then please make that clear, because that’s a different issue.

    GreginMich

    0 comments No comments
  2. Anonymous
    2017-09-30T04:43:11+00:00

    so basically your telling me that despite that i did quick scan 5 days manually and this past monday

    it shouldn't impact the so called automaically maintaince thing well why hasn't last threat scan still saying last scan past monday like i said since i don't have a schedule custom scan it starts a scan ever day at random time

    tell me this do you think that if i go out of town next thurs aka nashville be down there all day when i come back home the last threat scan will  finally update itself on its own?

    clearly something isn't right when scan starts  5,10,20, or 30 mins later i see last threat scan not updating windows defender when i'm at home i turn off my monitor when not using it then turn it back on

    i do the same when i leave the house turn off monitor btw

    now when i got notify once a week that windows defender scans computer few times with summary not finding any threat's usually when i click on it doesn't actually mean it will also update last threat scan which i assumed is normal that i seen in the past

    i know you got a custom schedule scan so i'm guessing when somebody doesn't have one the windows defender scan 0x2 isn't normal?

    i'm a guessing fall creator update comes i will still be experiencing this issue eh

    i guess since in my mind i broke it since 16th i guess i have to do a custom schedule scan so that it will work again?

    i just want computer to do what it did back on 13th and 14th update last  threat scan on its own again so that i don't have to do a quick scan

    the last heath and definitions gets updated everyday its rather strange that the last scan threat doesn't it just on certain days if you leave it alone that is

    i blame myself for this to happen perhaps i shouldn't had touch it back on 16th when i 1st try to do quick scan and left it alone since it was updated weds 13th and thurs 14th when came back home meh

    0 comments No comments
  3. Anonymous
    2017-09-30T04:23:47+00:00

    The actual run time for the Automatic Maintenance Scan is inherently unpredictable, because the scan will only start when the system has entered an idle state. And once started, the scan will be cancelled (not just paused) with any type of user activity – and then be restarted once the system returns to idle. So it’s always possible that a scan will finish belatedly, or won’t finish at all, just because there isn’t sufficient idle time during a work session. This was the only factor that limited the once-a-day frequency of the Automatic Maintenance Scan prior to Version 1607.

    But then with Version 1607, we started seeing this issue where the Windows Defender Scheduled Scan task inexplicably fails with a 0x2 Last Run Result in Task Scheduler and errors indicated in the MpCmdRun.log – and this issue persists in Version 1703. I really don’t know if there’s some kind of method to the Automatic Maintenance Scan’s madness, but it usually does seem to manage to get a scan done every week or so for most of us, and thus generally avoids the “scan now” prompt. And since there hasn’t been any sort of official acknowledgement of an issue here, I think we’re just going to have to accept that this is the new norm.

    Thankfully, scheduled scans aren’t really anything that we need to be overly concerned with now that Defender has real-time protection that's scanning files on-access. Folks who want more reliable automatic scans can just set up their own scheduled task. But careful users should be perfectly fine if they only run a manual scan every now and then, or whenever something looks suspicious. On the other hand, if your browsing habits are putting your PC in the at-risk category, then you should obviously be setting up a better security strategy, and one that includes periodic scans with some of our trusted third-party malware-removal tools – because the more your system gets exposed to malware, the greater the chances that Defender (or any other AV app) will miss something for the lack of a signature – and these third-party tools are specifically designed for removing active malware that’s been missed by your primary AV app.

    As far as I know, running additional scans shouldn’t have any impact on the Automatic Maintenance Scan.

    GreginMich

    0 comments No comments
  4. Anonymous
    2017-09-30T01:03:22+00:00

    it irate me a little when i was trying to explain and my question was kept dodging

    now like i said i do get once a day quick scan saying it scan computer give summary

    can you tell me this please by design when there's a schedule scan everyday at different times half of the time it doesn't really scan last threat scan and update it but it eventually in that giving week it should am i right or am i wrong?

    also do you think that if somebody does quick scan alot because they think after the scan starts they see that last threat scan not being updated and they do it manually will it kill it in the end to not try to update last threat scan on its own anymore or not and 1 should try to stay off computer in hopes that it will eventually work?

    1 last thing is this normal for a windows 10 machine in task schedule windows defender if they don't have custom scan

    in schedule task i see windows defender cache maintenance windows defender cleanup windows defender verification time date saying  the operation completed successful 0x0  and the windows defender schedule scan saying date time 0x2<-this is normal right  or is it suppose to be  0x0 the operation is successful

    for an example tonight windows defender cache maintencae windows defender window defender cleanup window defender verification saying ready today started 6:32:02 operation completed successful 0x0

    while schedule scan windows defender saying ready same date and time and it just saids 0x2

    i don't know if it always been like this by default when there's no custom scan btw

    when i open up windows defender around 7:30 tonight i still see last threat scan was past monday<-when i manually did quick scan

    in the end i'm trying to figure out did i basically break the mode when i 1st started doing quick scan  on 16,17 the next 3 days and this past monday

    i was out of town on 13th i came back home on 14 and the last threat scan was up to date and i believe that night as well i think the last threat scan only get updated every 2 days within a week usually not sure

    i have never attempted to do quick scan when i got into creator's update l just let it do it thing  until on 16th   sat because  i saw last threat scan wasn't updated the following friday and sat night  which i did alot afterwards meaning i did wait for after schedule scan starts to scan but when i open up windows defender that sat night i saw last threat scan was that following thurs night hence did my 1st quick scan

    i don't know why i continue to do this next day the 3 days afterwards i did stop on 19th weds and i did it again past monday quick scan meh

    i don't know if i jinx it  somehow made it no longer work property and may never again or what

    0 comments No comments
  5. Anonymous
    2017-09-29T23:26:04+00:00

    I have no idea why your most recent thread would have been merged here – but with regard to the issue with erratic Automatic Maintenance scans (Original title: windows defender  last threat scan not updating), this is a well-known issue that’s been with us for some time now. I just rechecked things yesterday, and found that not only do we still have this issue in The Creators Edition, but also that my old workaround of changing the user account for the Windows Defender Scheduled Scan task to the local administrator account no longer resolves the issue**:**

    https://answers.microsoft.com/en-us/protect/forum/protect_defender-protect_scanning/how-to-set-up-windows-defender-to-scan-pc/0d2d6ffb-bb94-4cbf-9e12-33aaf1999df1

    Since the issue has purportedly already been escalated to the developers, I’m going to presume that the sporadic Automatic Maintenance Scans are actually by design; and that this is the way that Microsoft wants it to stay. So if you’d rather have reliable daily Quick Scans, then you’ll have to set up your own scheduled task for that purpose. I’ve just updated this thread with information on using the SchTasks.exe command line to schedule dependable daily Quick Scans (with updates):

     https://answers.microsoft.com/en-us/protect/forum/protect_defender-protect_scanning-windows_10/how-do-i-set-windows-defender-to-a-custom-auto/ec19aab4-10ce-4f41-9990-343056fd104f

    GreginMich

    0 comments No comments