jv16 PowerTools 2017 Update Released – Version 4.1.0.1728

mihaibarbulescu

An updated version of jv16 PowerTools 2017 has been released. The latest version number is 4.1.0.1728.

To update right now, you should download the latest version from our website and install it from scratch or even on top of any already installed version of jv16 PowerTools 2017.

If you are still running jv16 PowerTools X, jv16 PowerTools 2014 or any earlier version, please note that these older products are no longer maintained or updated and may not be fully compatible with most recent updates of Windows.

To get the best experience from our work please install jv16 PowerTools 2017 and make sure that you set it to a new directory (do not install in the same directory as jv16 PowerTools X, jv16 PowerTools 2014 or any earlier versions).

The latest version can be downloaded here: https://www.macecraft.com/download/

Change Log – What’s New

(compared to jv16 PowerTools 2017 build 4.1.0.1703)

Here is a complete list of bug fixes and improvements that we did since jv16 PowerTools 2017 – Version 4.1.0.1703 was released on Thursday, April 13th, 2017:

Bug Fixes

Fix: The software’s executables are again signed with a code signing certificate (the previous certificate expired).

Fix: Pictures AntiSpy can display an error message about EFOpenError (in the case it cannot access a picture file).

Fix: The Main Window can display an error message “Control pnlHomeHost has no parent window.”

Fix: The Clean and SpeedUp My Computer can dispay an EAccessViolation error message when fixing the found errors.

Fix: When jv16 PowerTools is installed, it’s possible the GUI mode in Quick Tutorial will have neither options selected by default.

Fix: Fixed a typo from the English User Interface that said “Licensesd” instead of “Licensed”.

Fix: The Clean And SpeedUp My Computer can display an error message relating to “edb.chk” file.

Fix: The Clean And SpeedUp My Computer can go back and forth between the “Performing final analysis” and the list of currently running scan modules.

Fix: Using the software with a translation, especially German, can make some of the tab caption texts not to be fully displayed due to lack of space on screen.

Fix: Find My Licenses tool can display an incorrect date of the license purchase for very old order (before 2016).

Fix: My Account and Find My License tools can in some rare cases display a data download error even if there is a valid internet connection.

Fix: Opening the Main Window can display an Access Violation error message relating to GetItemCount.

Feature Improvements

Improvement: The Initial Setup runs up to 30% faster.

Improvement: The Software Uninstaller runs up to 20% faster.

Improvement: The Clean and SpeedUp My Computer runs up to 5% faster.

Improvement: In the case user attempts to license the software with an incorrect name, such as only using their first name or a nickname, the software now displays a better error message. We require our users to use their full name when licensing the software. If you have licensed the software with a nickname or with your first name only, please contact our support to add your full name to record so you can use the software correctly.

Improvement: The software will automatically clean old debug data saved to its Backups folder.

Improvement: Improved compatibility with Roxio and Corel products.

Improvement: The Clean and SpeedUp My Computer will now display an additional confirmation before restarting user’s computer. Before, a tick in a checkbox was enough to confirm the computer restart which could cause an unwanted system reboot.

Improvement: The software now automatically scans the computer for any temporary files created and accidentally left over by jv16 PowerTools itself.

Join the public discussion about the latest version of jv16 PowerTools 2017 right now by replying to this forum thread and letting us know how the latest version works for you.

In case of any problems in buying or applying your license, due to exchange of private information being required, please contact us by opening a support ticket with our help desk: https://macecraft.zendesk.com/hc/en-us/requests/new

doctor9fan

Edit. Installed over beta version fine. Scan is so much faster.

Via support I downloaded the beta version to see if the Corel & Roxio fix worked, is it recommended to uninstall that in order to install the official release version or can I just install over the beta?

Thanks.

mrtee

Just got the email on the new version, installed and ran it. No one had better complain about speed now and that is from mrtee! Fantastically short diagnose and run time. You done good! Kudos, congrats and all that other kind of good stuff. jmho

cousintim

Updated to the new version on my test machine. Clean and SpeedUp My Computer ran much faster, around 100 seconds. Program launch seems a bit slow but reasonable. I may reinstall on my production machine. Overall, good job. Your focus on speed and performance has paid off.

balloon66

Entry missing

After Installation of JV16 Powertools 4.1.0.1728 there is no entry in Windows Control Panel/ Programm and Features (Windows 10 Pro Creators update, clean install) for JV16 Powertools. Please correct this.

cousintim

balloon66 wrote
Entry missing

After Installation of JV16 Powertools 4.1.0.1728 there is no entry in Windows Control Panel/ Programm and Features (Windows 10 Pro Creators update, clean install) for JV16 Powertools. Please correct this.

Also missing for me on W10 Pro 1703. New install of PT (not update).

arctucas

I thought maybe you finally had gotten it right with this version, until I used the Registry Finder to try and delete some entries.

All I got was errors about failed to backup. The strange thing is; I deliberately chose to NOT BACKUP.

So, using the only version that actually works (X), I deleted the entries.

jv16

balloon66 wrote
Entry missing

After Installation of JV16 Powertools 4.1.0.1728 there is no entry in Windows Control Panel/ Programm and Features (Windows 10 Pro Creators update, clean install) for JV16 Powertools. Please correct this.

Did you choose to install the entry to the Control Panel when installing jv16 PowerTools? It is an optional feature, because some of our users complained a software designed to clean the Windows registry should not by default add anything to the Windows registry. That's why this is an optional feature.

jv16

AndreasEF wrote
Also with me the new version now finally (tested on 2 computers with different hardware and software)

What still bother me is the fact that the program in its program directory in the folder "Backups" over 40 text files generated with every cleaning!

Well, this is debug data that is created to the Backups folder. This data helps us to diagnose any possible issue that may occur during the use of the software. If you don't like this, you can clean the Backups folder after each use.

jv16

Arctucas wrote
I thought maybe you finally had gotten it right with this version, until I used the Registry Finder to try and delete some entries.

All I got was errors about failed to backup. The strange thing is; I deliberately chose to NOT BACKUP.

So, using the only version that actually works (X), I deleted the entries.

Does this occur with any registry entries or with all?

arctucas

Not all, but the great majority.

jv16

Arctucas wrote
Not all, but the great majority.

Can you give some examples? We are trying to reproduce the problem but have not been able to do so.

arctucas

jv16 wrote
Arctucas wroteNot all, but the great majority.

Can you give some examples? We are trying to reproduce the problem but have not been able to do so.

As I recall, it was PCMark10 that I had the errors with.

jv16

Arctucas wrote
I thought maybe you finally had gotten it right with this version, until I used the Registry Finder to try and delete some entries.

All I got was errors about failed to backup. The strange thing is; I deliberately chose to NOT BACKUP.

So, using the only version that actually works (X), I deleted the entries.

Thank you for reporting! We were finally able to reproduce and fix the problem. The problem was very difficult to pinpoint because this issue only occurs with specific registry keys, not with all.

What happens is that with some keys, the user is asked whether they really want to remove this registry key as it looks dangerous to remove. However, even if the user says "yes", the internal safety mechanism of PowerTools kicks in and does not allow the key to be deleted and this leads to the "failed to backup" error - even with the user having chosen not to create a backup in the first place.

We fixed the issue by three methods:

1) There was a bug that caused an unnecessary "Removing this registry key can be dangerous, are you sure you want to continue" confirmation from the user for registry data that is safe to remove.

2) If user gives a confirmation to delete data that looks dangerous to delete, PowerTools will from now on proceed and delete it.

3) Finally, the error message has been changed from "Failed to backup" to "Failed to remove".

The very same issue also exists in PowerTools X, but since its detection of what registry data is not safe to remove is not as accurate and on the other hand, it does not seem to be affected by the bug number 1, removing this data with PowerTools X seems to work even with the bugs 2 and 3 in there.

These fixes will be included to the next released build, thank you very much for reporting!