Author Topic: some files could not be scanned  (Read 10594 times)

0 Members and 1 Guest are viewing this topic.

Offline fragman

  • Jr. Member
  • **
  • Posts: 42
some files could not be scanned
« on: April 24, 2010, 04:35:32 PM »
After a Quick Scan, these three items show up in the scan results

C:\Documents and Settings\All Users\Application Data\Microsoft:b3duoHyJck0DzQ2upPM2g6F7X
Error: The directory name is invalid (267)

C:\Documents and Settings\All Users\Application Data\Microsoft:FYb38Qirt4oU1hhEAjfMv3sFcnN
Error: The directory name is invalid (267)

C:\Program Files\Common Files\System:Microsoft:BTrSSOzxJG8sCusXNWr6bapT93w
Error: The directory name is invalid (267)

I've tried chkdsk c:/r and sfc scannow and these items still remain. It's a bit of a mystery. Any help?
Dell Laptop Pentium M / 2GB RAM / Windows XP Home SP3 / Avast! Free 8.0.1489 / MBAM Free / Windows Firewall / Internet Explorer 8

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 70677
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: some files could not be scanned
« Reply #1 on: April 24, 2010, 05:52:04 PM »
Which OS?
Win 8.1 [x64] - Avast PremSec 21.5.6354.BCi [UI.646] - EEK - Firefox ESR 78.11 [NS/uBO/PB] - TB 78.11
Avast-Tools: Secure Browser 91.0 - Cleanup 21.1 - SecureLine 5.12 - Driver Updater 21.1 - CCleaner 5.82
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Offline fragman

  • Jr. Member
  • **
  • Posts: 42
Re: some files could not be scanned
« Reply #2 on: April 24, 2010, 08:38:28 PM »
Windows XP SP3
Dell Laptop Pentium M / 2GB RAM / Windows XP Home SP3 / Avast! Free 8.0.1489 / MBAM Free / Windows Firewall / Internet Explorer 8

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 70677
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: some files could not be scanned
« Reply #3 on: April 24, 2010, 08:47:24 PM »
The directory name is invalid (267)

Well, the comment above is true...
Do you see it in explorer the same way?
What help do you need?
asyn
Win 8.1 [x64] - Avast PremSec 21.5.6354.BCi [UI.646] - EEK - Firefox ESR 78.11 [NS/uBO/PB] - TB 78.11
Avast-Tools: Secure Browser 91.0 - Cleanup 21.1 - SecureLine 5.12 - Driver Updater 21.1 - CCleaner 5.82
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Offline fragman

  • Jr. Member
  • **
  • Posts: 42
Re: some files could not be scanned
« Reply #4 on: April 24, 2010, 11:06:41 PM »
Is there a way to make the directory name valid?
Dell Laptop Pentium M / 2GB RAM / Windows XP Home SP3 / Avast! Free 8.0.1489 / MBAM Free / Windows Firewall / Internet Explorer 8

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 70677
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: some files could not be scanned
« Reply #5 on: April 24, 2010, 11:14:42 PM »
Is there a way to make the directory name valid?

Sure. You can just rename it, but since i don't know where this comes from, you better be careful.
I've never seen entries with ':' in the path... Better check your system first.
Use free Mbam to check for malware and post back the results.
http://www.malwarebytes.org/mbam.php
asyn
Win 8.1 [x64] - Avast PremSec 21.5.6354.BCi [UI.646] - EEK - Firefox ESR 78.11 [NS/uBO/PB] - TB 78.11
Avast-Tools: Secure Browser 91.0 - Cleanup 21.1 - SecureLine 5.12 - Driver Updater 21.1 - CCleaner 5.82
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11798
    • AVAST Software
Re: some files could not be scanned
« Reply #6 on: April 24, 2010, 11:15:51 PM »
According to the name, it's not just the folder name - it's an alternate data stream, associated with the folder.
But it certainly is weird... don't know why avast! should report the stream, but simultaneously find it invalid (the displayed name doesn't contain any special characters, so if it's complete, it should be OK). Besides, there's no reason any ADS should be present, of course...
I might guess a filesystem problem, but if chkdsk doesn't report anything...

Offline fragman

  • Jr. Member
  • **
  • Posts: 42
Re: some files could not be scanned
« Reply #7 on: April 25, 2010, 12:34:13 AM »
I ran MBAM with not detections. This sure is puzzling. Maybe I shouldn't be concerned.
« Last Edit: April 25, 2010, 04:16:51 AM by fragman »
Dell Laptop Pentium M / 2GB RAM / Windows XP Home SP3 / Avast! Free 8.0.1489 / MBAM Free / Windows Firewall / Internet Explorer 8

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 70677
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: some files could not be scanned
« Reply #8 on: April 25, 2010, 12:56:09 AM »
I ran MBAM with not detections. This sure is puzzling. Maybe I shouldn't be concerned.

Maybe..!!?? I am not sure, sorry... :(
Never saw anything like this.
Be proud, your machine is unique. ;)
asyn
Win 8.1 [x64] - Avast PremSec 21.5.6354.BCi [UI.646] - EEK - Firefox ESR 78.11 [NS/uBO/PB] - TB 78.11
Avast-Tools: Secure Browser 91.0 - Cleanup 21.1 - SecureLine 5.12 - Driver Updater 21.1 - CCleaner 5.82
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 85146
  • No support PMs thanks
Re: some files could not be scanned
« Reply #9 on: April 25, 2010, 02:09:45 AM »
I ran MBAM with not detections. This sure is puzzling. Maybe I shouldn't be concerned.

Why should you be concerned, since the avast scan is only saying that the file couldn't be scanned (for whatever reason) not that it is infected.

So if it isn't infected, just can't be scanned, I wouldn't expect MBAM to find it is infected.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 21.5.2470 (build 21.5.6354.675) UI 1.0.646/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline mdubin

  • Jr. Member
  • **
  • Posts: 26
Re: some files could not be scanned
« Reply #10 on: April 26, 2010, 01:21:18 AM »
I just downloaded Avast! Free yesterday and I got the same thing at the end of a full and quick scan where it said some files could not be scanned. It showed Error 267 Directory Name is Invalid. The directory name is C:\WINDOWS: 2B2696B30AD92EF4. This is a mystery to me since I could not find this in Explorer under C:\WINDOWS. I run Windows XP Pro SP3.

Note: This message did not occur when I did a Boot scan.
« Last Edit: April 26, 2010, 01:23:22 AM by mdubin »

Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11798
    • AVAST Software
Re: some files could not be scanned
« Reply #11 on: April 26, 2010, 02:18:51 PM »
fragman, when did this start appearing in the scan report? Was it there since you installed avast!, or did it appear just recently?

Offline fragman

  • Jr. Member
  • **
  • Posts: 42
Re: some files could not be scanned
« Reply #12 on: April 26, 2010, 04:12:05 PM »
Hello igor

After installing 507 free and after the very first quick scan, I got this error message. I started using Avast free after being away for several months. The error message also appears after full and explorer scans. Thanks...
Dell Laptop Pentium M / 2GB RAM / Windows XP Home SP3 / Avast! Free 8.0.1489 / MBAM Free / Windows Firewall / Internet Explorer 8

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 85146
  • No support PMs thanks
Re: some files could not be scanned
« Reply #13 on: April 26, 2010, 04:35:02 PM »
You could also run a scan using SuperAntiSpyware (SAS) as that also scans alternative data streams, so it would be looking in the same areas and see if there are any reported issues there. However I don't know if SAS reports things that it has been unable to scan.

SUPERantispyware On-Demand only in free version.
Don't worry about reported tracking cookies they are a minor issue and not one of security, allow SAS to deal with them though. - See http://en.wikipedia.org/wiki/HTTP_cookie.
Also available a portable version of SAS, http://www.superantispyware.com/portablescanner.html, no installation required.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 21.5.2470 (build 21.5.6354.675) UI 1.0.646/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline fragman

  • Jr. Member
  • **
  • Posts: 42
Re: some files could not be scanned
« Reply #14 on: April 26, 2010, 06:17:27 PM »
Hello DavidR

Thanks for the portable SAS link. I ran it using default quick scan with latest definition and no threats were detected. Also, I ran a cmd prompt with one of my error files as suggested in another post and results showed an invalid file.
Dell Laptop Pentium M / 2GB RAM / Windows XP Home SP3 / Avast! Free 8.0.1489 / MBAM Free / Windows Firewall / Internet Explorer 8