Issues Fixed (since the original Beta6 release)
Known issue fixed: Anti-Malware feature is not yet ready for testing.
Note: If you want to test the Anti-Malware feature and make sure it can detect something, you can use the test file from http://www.eicar.org/anti_virus_test_file.htm
Issues Reported (numbers continue from previous version)
119. Registry Cleaner: Tools-->Compare results... aborts itself every time (message=: Operation aborted.). __ 678 x64 w7 |.| 932 x86 w7
Issues Reported (new numbers)
1. Unit Test feature reports errors relating to "TestRNG"
2. Unit Test feature reports errors relating to "TestTBackupManager"
3. File Recovery can show an errir message: "The following information must be provided in order to start: At least one search argument, you can use Files to find, Search by size and/or Search by date tabs." - there is no Search by date tab.
4. System Cleaner tool's window doesn't have a tool caption, nor does the tool exist in English.lng at all
5. The size and position of some or all tool windows are not correctly remembered.
6. Initial Setup creates an empty SysCache.dat file
7. Registry Cleaner does not run (probably related to issue number 6).
8. Any of the file tools can report the following error message: "AssertEx1 (RS) FAILED! Desc="TDebugLog.AddLogEntry, Entry="Start: Procedure TFileViewForm.OnGetInfo..".
9. Registry Info tool crashes to "Access violation at address 00863DD8" if Aborted, or if the tool has been fully run and then the tool window is closed.
10. "Disable performance counters" tweak does not work with the System Optimizer.
11. Unit Testing Tool can crash to EOutOfMemory while performing the "SafetyNet.IsDangerousRegKey" test.
12. Unit Testing Tool can report errors relating to "Error: TestRDA FPO item ..." and "Error: TestRDA: FPO rate of X is larger than accepted!".
13. When Unit Testing Tool's RegistryDataAnalyzer Test started for the first time, it activated my 3 1/2" drive again and again. I could stop it by inserting a disk.
Issues Not Reported AFAIK
1. If a new version of the program is available, and you start Help > Check for updates right after starting the program, you might see a message "You are currently using version "{1}". A newer version "{2}" is available. Would you like to get more information about the new version?". If you click Yes, the already opened Check for Updates windows will close, start again and check again for a new version. The second time the popup does not occur.
2. The Check for Updates window lacks its icon.
3. File Tool's File Analyzer feature doesn't look right, all the text captions are wrong and do not originate from the English.lng
4. Mass File Renamer's Convert Case feature cannot be accessesd because the box is too small.
5. File Encrypter tool contains an incorrectly named button (Abort button says "AbortBtn").
6. File Organizer tool contains an incorrectly named button (Add button says "AddBtn").
7. Automation Tool: If you click Delete but then select No, the automation task is not deleted, but clicking Delete again doesn't do anything, the task is not deleted nor is the confirmation ever shown again.
8. If you abort the History Cleaner, it can crash to Access Violation.
9. Running Unit Testing Tool can cause the GUI to freeze for long periods of time.
10. "RegistryDataAnalyzer" test in Unit Testing Tool seems to do nothing, and causes the tool to freeze for long periods of time.
11. File Tool's Columns > Checksums features do not work, no CRC32, SHA1 or MD5 of the files is ever displayed on screen.
12. If there are problems with connectivity, the Anti-Malware feature can be incorrectly installed and trying to use it causes the program to crash.
13. After Anti-Malware feature has been once installed, it can no longer be updated (i.e. it doesn't ever receive any information about updated signature files).
Improvements Done
1. Improved the Check for Updates window content handling.
2. It's now possible to send messages over the Internet to the Main Window of PowerTools, without the need of user clicking to Help > Check for Updates.
3. Increased the size of the Unit Testing Tool's window.
4. Clicking Abort now closes most of the tool windows - there is no need to show an empty list of results to the user if the user has clicked Abort.
5. Improved the detection of incorrect / corrupted translation file.
6. The program now saves a separate Debug Log of the first run, in order to catch any possible bugs that occur during the Initial Setup.
7. Added debug code in order to better track any "AssertEx Failed!" error messages.
8. Added more debug to better detect problems with FileCache and SysCache creation and loading.
9. Added a SelfTest feature to the Unit Testing Tool, it will detect any missing or corrupted files from PowerTools' installation directory.
10. Improved the amount of information the Anti-Malware tool's Update feature gives during the update process.
