An updated version of jv16 PowerTools is now released. The version is 7.3.1.1392 and it can be downloaded from here:
https://jv16powertools.com/downloads/jv16pt_setup.exe
This version includes many performance improvements, user interface improvements, some accuracy improvements and fixes to a few bugs. The bug fixes are mostly cosmetic. However, there was one bug that prevented the program being used in some systems. This is the 'The ordinal 4369 could not be located in the dynamic link library' error message that showed up on some systems when trying to start jv16 PowerTools. The bug prevented some users from using the app, but there was no data loss or damage to systems. Nevertheless, this issue is now also fixed.
The bulk of the improvements in this version are relating to making the program work faster and better. For example, the average time it previously took to run a Software Uninstaller scan was 42 seconds, thanks to the speed improvements in this version, it's now down to 30 seconds.
jv16 PowerTools Change Log Since 7.3.1.1372
Improvements:
1) Improved the accuracy of System Cleaner's 'Registry error relating to' feature. Previously it could list data such as 'Registry error relating to Microsoft', which doesn't really provide you any value.
2) Reduced the system resources usage of the jv16 PowerTools Widget.
3) Improved the accuracy of detecting the names and icons of running apps in the Dashboard and the Widget.
4) Minor improvements to the overall accuracy of System Cleaner and Software Uninstaller.
5) The program now opens up faster. In most systems, the difference is negligible but in systems in which the starting time has been slow, it is now up to 25% faster.
6) Software Uninstaller scan now works faster, on average it now takes 30 seconds, previously with the last version it took 42 seconds.
7) Some of the confirmation message boxes now show the expected answer by highlighting the default option.
8) Comes with many updated translations, including Dutch, Finnish and Swedish.
Fixes:
1) The program could display 'The ordinal 4369 could not be located in the dynamic link library' error message. This was a rare bug, only affecting specific systems. So far, we received seven reports of this issue. However, in the affected systems, this bug made it impossible to use the app.
2) The program could display an 'access violation' error message when performing the System Cleaner scan.
3) System Cleaner could get stuck on displaying the 'updating the results list ...' at the status bar. This was a cosmetic issue, however. This message being visible did not prevent you from using the app in any ways.
4) If you unselected all but one category from the System Cleaner results, the user interface could enter a loop where the results list got emptied, then updated correctly, emptied again, and so on.
5) System Cleaner scan's starting screen could remain on screen for too long, incorrectly letting the user to think the scan might not be starting correctly. This was entirely a cosmetic issue.
6) Installation of jv16 PowerTools didn't always create a System Restore Point.
7) Scrolling the navigation panel could fail and possibly show an 'out of range' error message.
8) The final screen of Software Uninstaller could have the checkboxes in wrong locations, especially if the tool is used more than one time per session.
9) Clicking the Close button of System Cleaner could cause the program to display 'access violation' error message.
10) The program could generate an empty file called 'jv16 PowerTools Version Checker' to its installation directory.
11) Starting System Cleaner with any browsers running will cause the program to show a confirmation whether browser can be closed to allow browser data cleaning. However, if you chose 'cancel' from this confirmation box, it could cause the program to hang for a few seconds, incorrectly display the scan progress screen and only then return to the dashboard.
12) Dashboard's RAM section displayed the amount of RAM available to Windows. This could be a smaller number than the actual amount of installed RAM, which caused some confusion. This is now fixed and the dashboard will now display the total amount of installed RAM.
13) The text of the circular progress element in the progress screen, such as when scanning the system, could sometimes be drawn to the left side of the screen.
14) Sometimes the program failed to correctly fetch the icon of a running application, causing the CPU or RAM listing areas of the Dashboard to show either a missing or incorrect icon.
15) Scrolling the Dashboard's list up and down immediately after the program has started, could cause the scrolling not to be smooth and the CPU usage high for a few seconds.
Known issues
None.