c:\$windows.~BT\Sources\SafeOS\...\

system · 2015-08-31T01:26:56.000Z

ran quick scan on laptop using Avast. scan came back with a warning message:

c:$windows.~BT\Sources\SafeOS.…\abortpxe.com error: file cannot be accessed

c:$windows.~BT\Sources\SafeOS.…\startnet.cmd error: file cannot be accessed

c:$windows.~BT\Sources\SafeOS.…\wdscapture.inf error: file cannot be accessed

system information

OS Version: Microsoft Windows 8.1, 64 bit
Processor: Intel(R) Pentium(R) CPU 2020M @ 2.40GHz, Intel64 Family 6 Model 58 Stepping 9
Processor Count: 2
RAM: 3985 Mb
Graphics Card: Intel(R) HD Graphics, -2039 Mb
Hard Drives: C: Total - 458597 MB, Free - 316336 MB;
Motherboard: Gateway, EG50_HC_CR
Antivirus: Avast Free Antivirus

can anyone verify if these files are Windows system related? if so, why are they not accessible to scanning?

Thank you for your assistance on this item.

Asyn · 2015-08-31T04:39:09.000Z

Nothing to worry, those are the update files for W10.

Pondus · 2015-08-31T05:43:50.000Z

How do I handle files that avast! can’t scan? https://blog.avast.com/2014/02/28/how-do-i-handle-files-that-avast-cant-scan/

system · 2015-10-10T18:49:14.000Z

I have the same problem as Pondus but I also get a message that files beginning in amd64microsoft windows cannot be accessed. Is this the same problem?

Asyn · 2015-10-10T19:00:02.000Z

Pondus doesn’t have a problem, he just provided a link.
So, I’m not really sure what you mean…??

DavidR · 2015-10-10T19:54:06.000Z

katreed post:4:

I have the same problem as Pondus but I also get a message that files beginning in amd64microsoft windows cannot be accessed. Is this the same problem?

If the path follows the same general format, but the file name is different, it still relates to copying the files to your system as and when you decide to update to win10.

This file is there presumably to cater for different CPUs AMD or Intel.

system · 2015-10-10T22:25:32.000Z

Sorry my questoin related tothe first post from persnlshopping… When I do my scan I get the same warning message that the files cannot be accessed.
the files listed begin with 64microsoft and the $windows BT/Source. Do I get this because I am still using Wiondows 7?

DavidR · 2015-10-10T22:44:20.000Z

katreed post:7:

Sorry my questoin related tothe first post from persnlshopping… When I do my scan I get the same warning message that the files cannot be accessed.
the files listed begin with 64microsoft and the $windows BT/Source. Do I get this because I am still using Wiondows 7?

If you have a qualifying OS for the free upgrade to win10 (and you appear to have), then on your normal windows updates you will have received one that effectively is in preparation to upgrade to win10. Now you may not have been aware of that that KB was for, but in effect you reserved/agreed to upgrade to win10. So MS went ahead and downloaded all of the GBs of stuff in readiness of your upgrade to win10.

So yes it could be related, but it could also be MS downloading lots of files to cope with many eventualities, OS you have or CPUs, etc.

bob3160 · 2015-10-10T22:45:43.000Z

katreed post:7:

Sorry my questoin related tothe first post from persnlshopping… When I do my scan I get the same warning message that the files cannot be accessed.
the files listed begin with 64microsoft and the $windows BT/Source. Do I get this because I am still using Wiondows 7?

You get it for the reason stated. The explanation as to what to do about those files was posted by Pondus in the link he supplied.

Announcements