Why does AdwCleaner say adware in C:\Device?

[CW58]

I have no known problems but thought I'd scan to be sure. No way I'm going to let AdwCleaner mess with this folder without knowing more.

What might this be telling me and does it seem odd? 

Windows 10 Version 1809 Build 17763.805

Thank you!

 

[Malwarebytes]

***This is an automated reply***

Hi,

Thanks for posting in the AdwCleaner Help forum.
In order to help us assist you to resolve your issue, please post or attach your latest AdwCleaner log files with your post. https://support.malwarebytes.com/docs/DOC-3347

Someone will reply shortly, but in the meantime here are a few resources which may help resolve your issue:

• AdwCleaner user guide
• A malicious element isn't being detected? Submit the sample here!
• Need help with another Malwarebytes product or malware removal?
  • Click here for home support
  • Click here for business support
  • Click here for malware removal help

Thanks in advance for your patience.

-The Malwarebytes Forum Team

 

 

 

 

[Gt-truth]

check whether this folder is empty or not first before doing anything else .sometime Adwcleaner will detect an empty folder .if it is an empty folder then this can be safely removed .

create your system restore point first .

Go to C:\ and look for that folder and check if it has 0 KB in the size .

[exile360]

I'm guessing that folder is a known install location created by adware which would be why it is detecting it.  That said, it likely would be a good idea to check the folder and see if anything is contained in it (I'm guessing not since ADWCleaner isn't showing any traces/files being detected within the folder).  It may just be left over from something that was installed on the system but has since been removed.

[CW58]

There is one and only one file named C:\Device\HarddiskVolume1\Boot\BCD

I renamed it BCD.txt so I could attach it along with the logs.

Thanks for any insight into what is going on here.

 

 

AdwCleaner[S00].txt AdwCleaner_Debug.log BCD.txt

[jboursier]

Hello,

@CW58 Thanks for checking with us!

Can you share the output of the command `bcdedit`:

1. Open the Windows start menu,
2. type `cmd.exe`
3. Right click on the `cmd.exe` item that shows up > `Open as administrator`
4. In the black window that opens, type `bcdedit` and press <Enter>

Please then share the output.

Regards,

[CW58]

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {e8efce09-6a55-11e8-a2d3-fa064ac7a786}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \WINDOWS\system32\winload.exe
description             Windows 10
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {d48a364e-16b8-11e9-b411-c6f82bdd0914}
displaymessageoverride  Recovery
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {e8efce09-6a55-11e8-a2d3-fa064ac7a786}
nx                      OptIn
bootmenupolicy          Standard

[jboursier]

Hello,

Thank you for the feedback and sorry for the delay.

We published an update, it will be picked up automatically at the next scan and will make this detection disappear.

Thank you for the report,

[CW58]

Thank you for the quick response. I just reran the scan and it completed normally with no problems reported.

I assume the program was finding a problem where there really was no problem.