Jump to content

V 7.0.0.0 database update issues


Recommended Posts

Version 7.0.0.0 is having database update issues.

This database loaded at 07:41 Sunday  which finds no problems.

# AdwCleaner 7.0.0.0 - Logfile created on Sun Jul 23 07:41:17 2017
# Updated on 2017/17/07 by Malwarebytes 
# Database: 07-23-2017.2
# Running on Windows 7 Professional (X64)
# Mode: scan
# Support: https://www.malwarebytes.com/support

This is the database loaded after the above run at 07:45 Sunday and is using an earlier database which finds many FP's. (185 all related to Spyblaster)

# AdwCleaner 7.0.0.0 - Logfile created on Sun Jul 23 07:45:02 2017
# Updated on 2017/17/07 by Malwarebytes 
# Database: 07-16-2017.1
# Running on Windows 7 Professional (X64)
# Mode: scan
# Support: https://www.malwarebytes.com/support

What is going on?

Previous v 6 had no issues like this.

 

 

Link to post
Share on other sites

Still same number of FPS. Not the latest database still.

 

# AdwCleaner 7.0.1.0 - Logfile created on Tue Jul 25 06:33:33 2017
# Updated on 2017/05/08 by Malwarebytes 
# Database: 07-16-2017.1
# Running on Windows 7 Professional (X64)
# Mode: scan
# Support: https://www.malwarebytes.com/support

AdwCleaner_Debug.log

Edited by mightaswell
Link to post
Share on other sites

1 hour ago, mightaswell said:

With both the Win 10 PC and Win 7 laptop I get a file "latest.json"

You have to copy those information and post them here in your thread... like I did it here.

Edited by MKDB
Link to post
Share on other sites

  • 2 weeks later...

Have not been able to get Adwcleaner to update to the latest database.  However when I run latest Beta Version 7.0.2.0  as per

Step 1 

# AdwCleaner 7.0.2.0 - Logfile created on Fri Aug 04 06:02:44 2017

# Updated on 2017/29/08 by Malwarebytes

# Database: 07-31-2017.1

# Running on Windows 10 Pro (X64)

# Mode: scan

Then if I run version 7.0.1.0  afterwards as per this  -  the latest data base is used.

Step 2

# AdwCleaner 7.0.1.0 - Logfile created on Fri Aug 04 06:04:08 2017

# Updated on 2017/05/08 by Malwarebytes

# Database: 08-03-2017.1

# Running on Windows 10 Pro (X64)

# Mode: scan

 

 Running 7.0.1.0 AGAIN gives this. NOT the latest data base. This is reproducible

Step 3

# AdwCleaner 7.0.1.0 - Logfile created on Fri Aug 04 06:13:49 2017

# Updated on 2017/05/08 by Malwarebytes

# Database: 07-31-2017.1

# Running on Windows 10 Pro (X64)

# Mode: scan

 

Adwcleaner will not use latest database till the sequence steps 1 followed by step 2 is performed

This is very strange and seems to indicate a problem with the programme.

AdwCleaner_Debug.log

Edited by mightaswell
Link to post
Share on other sites

Further to topic: I find that sometimes 7.0.2.0 beta doesn't update database correctly especially if it warns that the programme is out of date and after declining the subsequent run will provide an earlier database. However a further subsequent run will often then update the database correctly. Still a hit or miss matter but more often than not the most recent database is being used in the beta 7.0.2.0. 

AdwCleaner_Debug.log

Link to post
Share on other sites

Thank you @fr33tux 

When running Version 7.0.1.0 on Win 7 laptop for the first run of the day today the programme immediately says "updating database" but  it really does not successfully do so. Running programme again immediately it will report "checking database" and then followed by "updating database" and it then correctly uses  the more recent database.

 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.