Author Topic: Error 42006 Question!  (Read 7830 times)

0 Members and 1 Guest are viewing this topic.

Voltrux

  • Guest
Error 42006 Question!
« on: November 18, 2013, 07:18:11 PM »
Good afternoon members of the community! I'm having this error with avast and would like to have some help please.
Error: 42006
C: \ Users \ ... \ SkyDrive: ms-properties
C: \ Users \ ... \ Images: ms-properties
C: \ Users \ ... \ Documents: ms-properties

Offline bob3160

  • Avast √úberevangelist
  • Probably Bot
  • *****
  • Posts: 47865
  • 63 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re: Error 42006 Question!
« Reply #1 on: November 18, 2013, 07:31:41 PM »
Free avast! Security Seminar: http://bit.ly/2N1eaR2  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 11 Pro v22H2 64bit, 16 Gig Ram, 1TB SSD, Avast Free 22.12, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq -- My Online Activity https://bit.ly/BobGInternet

Joe Siegler

  • Guest
Re: Error 42006 Question!
« Reply #2 on: December 18, 2013, 07:09:47 AM »
I've got this error too.  I've been getting it for a few weeks now.   I looked at that thread, doesn't seem to have anything that would solve the problem.

I know they can be ignored, but the fact that they're here makes a full system scan NOT show up as a clean one, and I'd really like my report to show that.  Capt anal and all that.  Plus the company I work for (since I do remote work) periodically asks for system virus scan reports, and I don't like sending them in with "Some files cannot be scanned".

The two files that throw the 42006 error on EVERY SCAN are:

C:\Users\Joe\SkyDrive\Documents:ms-properties
C:\Users\Joe\SkyDrive:ms-properties

It wasn't always this way - I used to get clean scans, but at some recent date (that I have no idea when) these two started happening.  I rarely to never use Skydrive.  I don't want to completely remove it, might have some future scenario where I'd need to use it, but I'd really like Avast not to show this on every scan report.   Any ideas?
« Last Edit: December 18, 2013, 07:12:38 AM by Joe Siegler »

Offline bob3160

  • Avast √úberevangelist
  • Probably Bot
  • *****
  • Posts: 47865
  • 63 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re: Error 42006 Question!
« Reply #3 on: December 18, 2013, 10:28:46 AM »
Looking at your screenshot explains the reason for the exception.
I don't understand how you expect avast! or any other program to give you a different answer.
If you don't want the error message, exclude the folder from your scan.

Free avast! Security Seminar: http://bit.ly/2N1eaR2  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 11 Pro v22H2 64bit, 16 Gig Ram, 1TB SSD, Avast Free 22.12, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq -- My Online Activity https://bit.ly/BobGInternet

EventHorizon

  • Guest
Re: Error 42006 Question!
« Reply #4 on: February 06, 2014, 05:14:11 AM »
...or you can simply right click the SkyDrive folder in your Users directory, and select "Make available offline". This will clear up that error (as it did for me). Unless you are keeping a lot of files there I prefer to keep a local copy AND make sure that it is scanned regularly as well rather than exempting the folder or other modifications to my AV config.

Joe Siegler

  • Guest
Re: Error 42006 Question!
« Reply #5 on: February 06, 2014, 08:37:29 PM »
...or you can simply right click the SkyDrive folder in your Users directory, and select "Make available offline". This will clear up that error (as it did for me). Unless you are keeping a lot of files there I prefer to keep a local copy AND make sure that it is scanned regularly as well rather than exempting the folder or other modifications to my AV config.

I'll try that.   

Thing is, Avast didn't always do this.  I had Skydrive on there for awhile, and all of a sudden it started failing my scans.  That was the whole reason behind me doing this.