Author Topic: c:\$windows.~BT\Sources\SafeOS\...\  (Read 14795 times)

0 Members and 1 Guest are viewing this topic.

Offline persnlshopping

  • Newbie
  • *
  • Posts: 3
c:\$windows.~BT\Sources\SafeOS\...\
« on: August 31, 2015, 03:26:56 AM »
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\...\abortpxe.com                            error: file cannot be accessed

c:\$windows.~BT\Sources\SafeOS\...\startnet.cmd                              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

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.

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 72814
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: c:\$windows.~BT\Sources\SafeOS\...\
« Reply #1 on: August 31, 2015, 06:39:09 AM »
Nothing to worry, those are the update files for W10.
Win 8.1 [x64] - Avast PremSec 21.10.6772.IBC [UI.679] - EEK - Firefox ESR 91.3 [NS/uBO/PB] - TB 91.3.2
Avast-Tools: Secure Browser 96.0 - Cleanup 21.3 - SecureLine 5.14 - Driver Updater 21.3 - CCleaner 5.87
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 37129
Re: c:\$windows.~BT\Sources\SafeOS\...\
« Reply #2 on: August 31, 2015, 07:43:50 AM »
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/


Offline katreed

  • Newbie
  • *
  • Posts: 3
Re: c:\$windows.~BT\Sources\SafeOS\...\
« Reply #3 on: October 10, 2015, 08:49:14 PM »
 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?

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 72814
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: c:\$windows.~BT\Sources\SafeOS\...\
« Reply #4 on: October 10, 2015, 09:00:02 PM »
Pondus doesn't have a problem, he just provided a link.
So, I'm not really sure what you mean...??
Win 8.1 [x64] - Avast PremSec 21.10.6772.IBC [UI.679] - EEK - Firefox ESR 91.3 [NS/uBO/PB] - TB 91.3.2
Avast-Tools: Secure Browser 96.0 - Cleanup 21.3 - SecureLine 5.14 - Driver Updater 21.3 - CCleaner 5.87
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Online DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 85947
  • No support PMs thanks
Re: c:\$windows.~BT\Sources\SafeOS\...\
« Reply #5 on: October 10, 2015, 09:54:06 PM »
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.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 21.9.2494 (build 21.9.6698.703) UI 1.0.672/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline katreed

  • Newbie
  • *
  • Posts: 3
Re: c:\$windows.~BT\Sources\SafeOS\...\
« Reply #6 on: October 11, 2015, 12:25:32 AM »
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?

Online DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 85947
  • No support PMs thanks
Re: c:\$windows.~BT\Sources\SafeOS\...\
« Reply #7 on: October 11, 2015, 12:44:20 AM »
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.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 21.9.2494 (build 21.9.6698.703) UI 1.0.672/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline bob3160

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 46288
  • 61 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re: c:\$windows.~BT\Sources\SafeOS\...\
« Reply #8 on: October 11, 2015, 12:45:43 AM »
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.  :)
Free avast! Security Seminar: http://bit.ly/2N1eaR2  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 11 Pro v21H2 64bit, 16 Gig Ram, 1TB SSD, AvastOmni 21.6, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq