Strange result of 1st scan: "Unable to scan: The directory name is invalid"

[arlecchino]

I just this evening installed Avast! (4.8 Home Edition) and ran a "standard" scan. When I came back in later to check the results, the scan had finished, but the following appeared in the "Results of Last Scan" window, which was showing on the monitor:

"C:\Windows:DB00D3770E582EB1 | Unable to scan: The directory name is invalid."

The portion on the left appeared under the heading "Name of file"; the portion on the right appeared under the heading "Result."

I opened Windows Explorer and looked at the directories listed under the C:\ drive, but didn't see the directory that Avast! was referring to. I then did a search in Windows by entering just a portion of the name--E582EB1--but the search returned nothing.

Does anybody know whether this is a false reading? Or is there actually a directory on my computer somewhere that Avast! is unable to scan and that I can't see? (Incidentally, I do have Windows Explorer set to "Show hidden files and folders.")

Thanks for any help.

[Lisandro]

The : is strange (an invalid) in the middle of the name...
What if you run:
chkdsk /R
schedule the check on next boot, boot...?

[arlecchino]

Did the chkdsk/r as suggested.

Just ran the Avast! scan again in standard mode: same result as before.

 

[DavidR]

Is there actually a folder called Windows:DB00D3770E582EB1 in the c:\ drive ?

If so it is somewhat suspicious, a simple test trying to create a folder of that name in C results in a windows error and it drops the : colon from the folder name (see images).

[Lisandro]

Sorry arlecchino, the problem is that folder with a colon in the name as I've posted before.
In fact, the folder shouldn't be there, it can't... but why avast is detecting it is the mystery.
I won't worry about that result (seems an avast fault), just let only "infected file" to be reported and not "errors".

[igor]

Please go to avast! settings and enable the creation of the report file; let any kind of errors be included in the report. Then, run the scan again - and after it's done, post the corresponding part from the report file here.
Thanks.