Registry Cleaner keeps finding the same registry problems

jayjay

Appears to be a problem with JV16 2014 build 1341.

Running the registry cleaner brings up a number of entries, if I select all the entries and then click fix, all selected items are removed.

Restarting the computer then running the registry cleaner again, the same entries are again shown, exactly the same.

leonardo

W7-x64-SP1 with jv16PT build1341

'Registry cleaner' finds in total 66 items during normal/standard scan, after click 'Fix' with Backup and 'Yes' on the recommended Reboot, it looks that all 66 items are removed.

However after the reboot 'Registry cleaner' finds again all these 66 items. :(

Attached is a zipped list of these 66 items and the made BackUp file.

EDITED: NOT fixed in build 1344

1. jv16PT build 1344 does not issue the recommended reboot request any more.

2. But at reboot the 66 items are still tried to be 'Fix'-ed.

siliconman01

Might want to give build 1344 a try and see if the problem is fixed

leonardo

siliconman01 wrote
Might want to give build 1344 a try and see if the problem is fixed

Thank you siliconmam1, unfortunately NOT fixed in build1344.

johan

Yes the same here all the time also. Please reboot to to remove the registry items. But they are never removed.

mallet

same here

mallet

good day,

any news about this ?

Thanks

jv16

Either the registry data is being automatically re-created by some background software or driver, or the removal fails for some reason. I think the only option is simply to use the Right-Click > Never show again feature to prevent these items from showing up in the results again.

mallet

no, this happens to ALL items

JV2013 removed them

jayjay

jv16 wrote
Either the registry data is being automatically re-created by some background software or driver, or the removal fails for some reason. I think the only option is simply to use the Right-Click > Never show again feature to prevent these items from showing up in the results again.

Strange that the "background software or driver" doesn't have the same effect on JV2012 or JV2013, neither of these versions have this problem. Suggest you look at this problem again as the work around you suggest is ridiculous.

bt

I didn't buy jv16 2014 to be told to ignore errors.

mmouse

I experience the same problem. Run Registry Cleaner, get full page of errors, fix, reboot. Immediately running Registry Cleaner again. The same errors are found.

It just doesn't work. :

Please fix it.

Win 7x64 running version 3.2.0.1351

easternokie

I had the same problem happen also using V3.2.0.1351. 43 items kept repeating. Program confirmed items were removed, but they were not. I used JV 2013 version 3.0.0.1267 and it removed the items.

Windows 7 64 bit.

leonardo

easternokie wrote
I had the same problem happen also using V3.2.0.1351. 43 items kept repeating. Program confirmed items were removed, but they were not. I used JV 2013 version 3.0.0.1267 and it removed the items.....Windows 7 64 bit.

Please add a zipped list of these items to this forum thread as input for the developer (jv16).

Scan result menu -> File -> Save List as.. creates a .txt file with all found items.

easternokie

Here is the list of items removed by JV 2013, but not by JV 2014 you asked for.Entries.zip

leonardo

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.

jayjay

This is the latest reg items that can't be cleaned...There are now 179 hidden items and the list keeps getting added to.

johan

Yes even if you hide them the are back after a reboot, and you are in an endless reboot :

mmouse

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.

siliconman01

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.