jv16 PowerTools 2014 Release Candidate 2

parkd1

Just ran the Registry Cleaner and no crash but not on my computer. It is in the shop. Think I have a bad video card and not at home so can not check on the gf's laptop. I am at my Mom and Dad's place till my car is fixed. Just tried it on their lap Windows 8 64bit so far so good. Can try on my dads' computer if needed. It is Windows 7 64bit. The screen still flashes when I scroll with the arrows. This was all done using jv16 Private Build 3.

jv16

siliconman01 wrote
Windows 7 x86 Professional, MS Office 2010, Jv16 Private Build 3

In the attachment are 2 keys that are falsely detected for Microsoft Office 2010. jv16 registry cleaner is not properly interpreting what "Office." is.

@"C:\Program Files\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Office.\osetupui.dll",-201

The file osetupui.dll is found in folder C:\Program Files\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Office.en-us\osetupui.dll

jv16 Registry Cleaner is set to most aggressive

This is now fixed, thank you for reporting! The fix will be included to the next released build.

jv16

siliconman01 wrote
This is on Windows 8 x64 Pro, Windows 7 x86 Pro, jv16 Private Build 3.

Under Settings>Advanced, the setting "If data cannot be removed, do not attempt to remove it on system startup" will not stay check marked or set.

As a question to jv16,

"if the above settings is set ON, will it keep jv16 registry cleaner from forcing a reboot to remove a specific registry key"?

If the above setting is ON, then the program does not setup any registry data to be removed during next system reboot. If the setting is OFF (by default it is), the program automatically tries to remove any data it fails to remove, during the next system reboot. User is only asked if he wishes to reboot now, not whether he wishes the data to be removed during next system reboot.

jv16

siliconman01 wrote
siliconman01 wroteThis is on Windows 8 x64 Professional. The registry cleaner hangs up when it encounters a permissions problem when deleting a key. Shown is one key that causes this hang. The response by jv16 is erratic. A couple of times it acted like it was successful in setting up to delete the key on reboot. It recommended a reboot. On reboot, I saw a CMD window flash by. The result of that CMD window was that it did not delete the registry key. It caused me to start having to re-enter the login password...which I had bypassed as the preference for my system. I had to go back into User Account and uncheck "User must enter a user name and password to use this computer".

http://www.macecraft.com/forum/viewtopic.php?f=10&t=5392&start=15#p32769

This is still not fixed in Private Build 3. It does force a reboot and then CMD window runs. It still wipes out the setting in User Account Control that allows the system to boot on up without having to enter the log-in password. Plus it did something that causes program SnagIt 11 to crash. SnagIt 11 had to be uninstalled and re-installed.

This should also now be fixed, thank you for reporting! The fix(es) will be included to the next released build.

jv16

FYI: http://www.macecraft.com/forum/viewtopic.php?f=10&t=5398

jv16

The final version of the PowerTools 2014 has been now released, for more information and the download link, please see:

http://www.macecraft.com/jv16-powertools-2014-released/

This topic has now been locked. If you wish to discuss about the beta testing program or the free licenses being issued, please use topic:

http://www.macecraft.com/forum/viewtopic.php?f=10&t=5417

« Previous Page