Error: File is offline - It is currently not available. (42006)

[REDACTED]

Ok, it works now, thx!

How's that?

I'm not getting it to pull up a new update version...  what got fixed?  Is there some online Avast to PC comm that coordinates stuff in the background....

Inquiring minds wanna know...  '

TIA...

sc

Follow Up - Note that while the Program Version remains the same that produced problem, the Virus Definitions had been updated [ as they should have by now ], but don't see how VD would make the diff, but then whadda I know...  '  Additionally running a Smart & Full Scan did not have the problem, so a beeg Shout Out to Avast getting things fixed in short order...  Still wanna know how that worked if they's anyone who'll take the time to enlighten me... 

TIA...

sc

[sludge7051-x]

Hey sc, all I know is that it works now (Ful Scan), please see screen shots.

The error was that the files on my system were "offline" ? . . . What could that be, some connection block, maybe the Firewall did something?

[REDACTED]

Hey sc, all I know is that it works now (Full Scan), please see screen shots.

The error was that the files on my system were "offline" ? . . . What could that be, some connection block, maybe the Firewall did something?

Hmmmm...

So it's not a patch to Avast, jes a one time glitch [ at least in my case, sounds like yours too... ]...  I was jes going by your observation that it was 'fixed', so tried it and it went fine...  which at first I presumed would show a new Update to program, but all it has 'new' is the latest VDs...

Don't run a FW unless the Windows one is running an I'd have to check that...

My History looks like yours where the previous scan that 'busted' showing 'some files could not be scanned' under the Result column...

Surely someone knows what the issue is and I'd really like to for future ref...  Anybody able to chine in on that?

Reading back thru the thread and Igor's comments doesn't really answer the question leastwise best I can tell wid me po ol pea brain...  '

TIA...

sc

[sludge7051-x]

Wud be interesting 2 know, but not important, hope it doesn't break like that again

[bob3160]

VPS updates can do more than just update virus definitions.
Which is apparently what happened with the last VPS update.
Smile, it's almost Christmas.

[REDACTED]

VPS updates can do more than just update virus definitions.
Which is apparently what happened with the last VPS update.
Smile, it;s almost Christmas.

Reckon we'll go wid dat...  '

Thx...

sc

[Terryrb]

I'd love to jump on the bandwagon and say that the latest release has fixed this 42006 error, but I am still getting these for ~89 files - and have been for about 1 year since I bought my latest Windows 10 machine with Office 365. I note Office 365 because all of the files with this 42006 error are down the C:\Users\terry\AppData\Local\Packages\Microsoft.MicrosoftOfficeHub_8wekyb3d8bbwe\LocalCache path.

Is Office 365 the cause? Why is Avast tagging these and how do I keep them from being reported in the Scan History?

I am running Avast Free Antivirus v 17.7.2314 (build 17.7.3660.226) with virus defs v 171022-0. My Windows 10 is v 1709 (OS Build 16299.19).