jv16 PowerTools 2017 Update Released – Version 4.1.0.1657

mihaibarbulescu

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

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 PowerTools 2017.

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

To get the best experience from our work then 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/

If you have any private questions for us about your product license or technical issues that our staff could assist you with, please open a new support ticket: https://macecraft.zendesk.com/hc/en-us/requests/new

Change Log – What’s New

(compared to 4.1.0.1631)

Here is a complete list of bug fixes and improvements that we did since jv16 PowerTools 2017 – Version 4.1.0.1631 was released on Wednesday, November 23rd, 2016:

Bug Fixes

Fix: Running the Clean and SpeedUp My Computer with very specific system configurations, for instance Windows XP or Windows 8.1 with Microsoft Office installed, can cause Windows no longer to load the Desktop (if this has happened to you, simply restart to Safe Mode and restore the System Restore Point jv16 PowerTools automatically created for you, or use Windows’ Repair Startup feature.)

Fix: After clicking the button to update your data, the My Account window can only flicker and not display any information whether the operation worked or failed.

Fix: The software can display an error message “Cannot create file xxx. The system cannot find the path specified.”

Fix: The software can display an error message of “Cannot open file CVSData.xdat. The file does not exist.”

Fix: Running the Clean and SpeedUp My Computer can cause PowerTools to display an error message: Access violation at address 00021600.

Fix: The Clean and SpeedUp My Computer may disable parts of Corel WordPerfect office suite under some special circumstances.

Fix: In some cases, it is not possible to disable the Startup Timer. You can open the Startup Timer tool and choose to disable it, but the next time you open it, it will say the feature is enabled again.

Fix: Running the File Cleaner in Windows 8.1 with the most aggressive settings and with the option to remove unused fonts, can cause in some systems the File Cleaner to list system font files to be removed.

Fix: Check For Updates can show “n/a” as the latest product version.

Fix: The software can display an error message of “Cannot change Visible in OnShow or OnHide”.

Fix: In some rare cases, the Clean and SpeedUp My Computer may not list any of the found registry errors, if you perform the scan again, only then the found registry errors and leftovers are listed.

Fix: If the Clean and SpeedUp My Computer is set to run in a way it automatically fixes or deletes the found items (not recommended), it does not reboot the computer even if the “Restart computer after done” checkbox is checked.

Fix: Pressing Ctrl + Shift to enable Debug Mode does not work from the software’s main window.

Fix: When trying to disable a specific kind of automatically starting software in Windows 10, the Startup Manager can display an error message of Failed to Access “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\MSConfig\startupfolder\”

Fix: In some systems the Clean and SpeedUp My Computer can take a very long time to run (over 20 minutes).

Fix: Returning back to the results screen of Clean and SpeedUp My Computer from the Custom Fix screen can cause the Delete and Fix buttons to remain hidden.

Fix: When opening the About window, the screen can sometimes flicker and the program returns to the Main Window instead showing the About window.

Fix: Running the Clean and SpeedUp My Computer with the “automatically fix found errors” option shows a “Please select at least one item” error if no errors were found from the registry.

Improvements

Improvement: Software Uninstaller can better detect software installed to the computer.

Improvement: Software Uninstaller is more accurate in detecting the full name and version of installed software.

Improvement: The Clean and SpeedUp My Computer, as well as the File Cleaner, can detect previously cleaned but backed up temp files from the backups directory of jv16 PowerTools X. There is no need to list these, and this no longer happens with this build.

Improvement: File Cleaner’s and File Tool’s Delete On Reboot feature now asks user to reboot the computer after use. Before, user was asked to restart computer only when PowerTools was closed.

Improvement: Added Japanese translation.

Improvement: The Main Window now opens up and loads faster.

Improvement: The Clean and SpeedUp My Computer tool now scans the system faster, especially in cases where the system contains a lot of registry errors.

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.

siliconman01

jv16 4.1.0.1657, Windows 10 x64 Pro Build 14393.576.

This new build appears to be ~45% faster when running CFMC at the most aggressive setting. That's great progress. On my gaming computer that means it performs its work in about 3 minutes now...which is not bad at all.

mihaibarbulescu

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

redseujac

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

redseujac

The important issue reported in the following thread is not fixed in the new version, though it's was promised to be fixed.

Look here: https://www.macecraft.com/forum/viewtopic.php?f=45&t=5875#p35476

The issue also exists in PowerTools X.

mihaibarbulescu

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

mihaibarbulescu

redseujac wrote
The important issue reported in the following thread is not fixed in the new version, though it's was promised to be fiexed.

Look here: https://www.macecraft.com/forum/viewtopic.php?f=45&t=5875#p35476

We will look into it, thank you for hinting this issue.

bonesun

Installed version 4.1.0.1657 in Windows 10 pro anniversary edition.

I'm still asked if I want to restart after every partial fix of the errors identified after a run of "Clean and Speed Up my Computer". And if I attempt to fix all errors in one go, the program restarts my computer without asking. That's very rude of any program and jv16 PowerToolsX didn't do it. As you know, it waited until the program was closed before offering a restart, which is vastly preferable.

Equally irritating, jv16 does not remember my "Speed Up my computer's startup" settings. After every run, I have to re-identify those programs that I don't want jv16 to pause on startup. That's very poor too.

The file extension scan takes an age to run as well, and only ever identifies file types that are guaranteed to reappear. What's the point of that?

As yet, I've identified no benefit from running jv16 2017 in preference to jv16 X.

Good luck fixing it.

All the best...

redseujac

mihaibarbulescu wrote
redseujac wroteThe important issue reported in the following thread is not fixed in the new version, though it's was promised to be fiexed.

Look here: https://www.macecraft.com/forum/viewtopic.php?f=45&t=5875#p35476

We will look into it, thank you for hinting this issue.

Here's another example in attachment.Wrong_registry_paths.jpg

C:\Program Files\jv16 PowerTools 2017\jv16pt.exe listed instead of C:\Program Files (x86)\jv16 PowerTools 2017.jv16pt.exe as really occurring in the registry.

It looks like RC or list engine don't handle correctly some directory names such as Program Files (x86) for an unknown reason.

There are dozens of such errors in the list.

parkd1

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

arctucas

Force Uninstall with Reboot.

No Command Prompt window displayed during the restart.

mihaibarbulescu

Bonesun wrote
I'm still asked if I want to restart after every partial fix of the errors identified after a run of "Clean and Speed Up my Computer". And if I attempt to fix all errors in one go, the program restarts my computer without asking. That's very rude of any program and jv16 PowerToolsX didn't do it. As you know, it waited until the program was closed before offering a restart, which is vastly preferable.

I understand your suggestion and I believe that it is a very good point.

Allowing the user to use jv16 PowerTools 2017 further even after Clean and SpeedUp My Computer was used and all entries marked for cleaning (even if some require a reboot to be removed) might help our user base to get accustomed to all the other tools that the product comes with and not just a single experience.

We will look into this matter in our lab and debate on various ways to add more fluidity to the user experience from Initial Setup up to usage of each of the Main Tools.

Bonesun wrote
Equally irritating, jv16 does not remember my "Speed Up my computer's startup" settings. After every run, I have to re-identify those programs that I don't want jv16 to pause on startup. That's very poor too.

Do you mean that the "Do not optimize at startup" setting by Startup Optimizer does not stick?

Bonesun wrote
The file extension scan takes an age to run as well, and only ever identifies file types that are guaranteed to reappear. What's the point of that?

Are these results persistent at your side? This should not happen as automatically recreated entries are treated in a special way to make the entire scanning process faster on every subsequent analysis.

Bonesun wrote
As yet, I've identified no benefit from running jv16 2017 in preference to jv16 X.

Have a look at the recent test results and compare them to results from recent years. You may find these interesting:

https://www.macecraft.com/benchmark-top-ten-windows-registry-cleaners/https://www.macecraft.com/benchmark-top-ten-windows-registry-cleaners/

https://www.macecraft.com/windows-optimization-software-benchmark-report/https://www.macecraft.com/windows-optimization-software-benchmark-report/

https://www.macecraft.com/registry-cleaner-benchmark-study/https://www.macecraft.com/registry-cleaner-benchmark-study/

redseujac

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

doctor9fan

The latest update is a nightmare, it takes 10 minutes to run a scan but the at the analysing part it starts running the scan again with everything green ticked already, now having problems starting laptop.

Not impressed & will be returning to JV16 X.

claudiumatei

Doctor9fan wrote
The latest update is a nightmare, it takes 10 minutes to run a scan but the at the analysing part it starts running the scan again with everything green ticked already, now having problems starting laptop.

Not impressed & will be returning to JV16 X.

We have received the backups you sent and we are working on it. Thank you for the patience and understanding.

jv16

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

redseujac

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

jv16

redseujac wrote
The important issue reported in the following thread is not fixed in the new version, though it's was promised to be fixed.

Look here: https://www.macecraft.com/forum/viewtopic.php?f=45&t=5875#p35476

The issue also exists in PowerTools X.

Fixed now, thank you for reporting! It took a while to get fixed, because it was a difficult issue to fix and because it is a purely cosmetic problem with no effect on the way the software actually works. The fix will be included to the next released build of the software.

jv16

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

redseujac

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.