Some Files Cannot Be Scanned - Device Error (Help!?)

Avast Free Antivirus / Premium Security
1

I hope I am posting this in the correct part of the forum; If not, please forgive me.

I have been having some issues with my computer lately, specifically with an Avast error notice I received today after a scan.

This morning i had two viruses, one found in the fullscan, and one found during the following bootscan. They were removed. But before and after they were removed (two different scans) i had an error that stated the following:

"SOME FILES COULD NOT BE SCANNED:

C:\Users\XXXXXXX\AppData\Local\Temp\foxtab\thumbsRCT(-actual file name-)

Status: Error: The request could not be performed because of an I/O device error (1117)"

What does this mean??

I restored my computer to a previous date, cleared out the cache in my browser, and did a third scan. I got the same error.

I do have an add-on in my firefox browser that is called Foxtab, but it is disabled, because I disabled it a couple of weeks ago.

I have had some issues with my computer in the past, but nothing has been wrong since I sent for recovery disks, and recovered my whole computer (after some virus that took some important files with it when they were removed, making my computer crashdump and lag a lot).

I have Windows 7 home premium on an HP notebook computer.

One final note, I have no idea how I got these viruses whatsoever…Avast never alerted me to anything while browsing since my recovery.

Thank you very much for any help!

2

I am not completely sure, but the error (1117) sounds like a problem with accessing the file - possibly a problem with the hard disk.
I would probably suggest trying to run a disk check (including a surface check).

3

Oh, ok! What is a disk check?

4

disc check

computer/c/(right click)properties/tools/error checking

5

Update:

I did a disk check, with the box to fix stuff automatically checked if anything was found that needed fixing, and I guess it came back as fine, because it ran it, started up, and nothing popped up whatsoever (not even results or anything…). It showed results at the end of it, but the screen went away.

After that, I did another full-scan with Avast. SAME ERROR came up on the same file.

Is this something that would be fixed with a registry cleaning? Is that folder what a “registry” is? Should I figure out how to “clean the registry” and see if that folder is cleaned out?

Thanks

6

No, the file has nothing to do with registry.
Btw, what is this “actual filename”? I’m asking because I’d like to know if its just a file (that exists on the filesystem), or if it might be an archive and a path inside of that archive.

7

its a string of letters and numbers, and its only one of many in that folder. but that one specifically is hanging up the scan i guess.

im not sure what to do :- /

8

Can you post a screenshot of the results window?

9

Its a temp file (whatever the name).

Why don’t you just delete the file? If it give you problems, change the permissions from read only.

Temp files aren’t necessary to run anything on the computer, they are left over from installation, windows activity, etc. (though I leave the WPDNSE file in temp, it is created every boot up - on Vista).

If you can’t delete, come back and give error message.

10

Is it possible I can just delete the entire folder of Foxtab?

As I said, Foxtab was an addon I had on my browser, found here:
https://addons.mozilla.org/en-US/firefox/addon/foxtab/

As far as I am aware, that’s what that folder is from. Furthermore, I had it disabled for the past 3 weeks or so. On an updated note, I’ve actually removed it from my addon list (not just left it there and disabled as it was). Nothing has changed, the files are all still there in the appdata folder.

I just found it very odd that it was saying some sort of “I/O” error that I’ve never heard of. I have been worried there is something wrong with my computer itself, because I don’t know what the heck that error means.

Are you sure if I were to do any deleting of the stuff in there, that my computer would remain ok? Of course, worst case senario, if it XXX my computer up, I have recovery disks to wipe and reinstall my entire computer. I just wish I knew more about this stuff so I could fix it rather than have to resort to such extreme measures.

11

anyone have any ideas?

12

Maybe?

13

I still need help with understanding this.