Alert-Do not update to RM11.0.1.716

[shorelaran]

This "bug" with RM 11.0.1.716 seems to be system specific. I've tested the said version on a Windows 7 system and the Compact Registry bug did not occur.

It would be best that you provide your system specs to the Admins so that they can try to isolate the problem. Also about the disk sectors that Magician is talking about could be connected to the problem.

The "Registry Compact" is actually a defragmentation of the registry hive files thus it has something to do with the disk sectors.

[HiSpeed]

No shorelaran, it's a bug occurring when the registry is already compact.
RM ask to compact when the registry has less than 1% to gain...

[loyall]

Although it has not been mentioned in this thread the bug that affects the "compact registry" command also affects the "bleach free space" command. I still advise those who have not already done so to refrain from updating to RM 11.0.1.716 until those bugs have been corrected.

[Magician]

AS I mentioned to Loyall previously, the bug

"occurring when the registry is already compact.
RM ask to compact when the registry has less than 1% to gain... "

is a known issue but does not affect the way the product performs. It occurs in a few cases only but we will be looking to address this issue in the near future.

Kind Regards,

Magician

[loyall]

Magician said above "[The bug]is a known issue but does not affect the way the product performs."

I must disagree with your statement. The bug prevents the user to achieve a rating of good system health. Additionally, while we may hope that the registry has secretly been compacted, the bleach free space command does not appear to work at all, although it is difficult to know for sure.

[loyall]

RM Dashboard.JPG This the screenshot Magician requested on the on the other thread. For some reason I can upload it to this thread but not to the other thread. Go figure!

[loyall]

Magician,
I realize that you are an unpaid volunteer for PCTools and I appreciate your contribution, but you are inconsistent and you contradict yourself. To wit: you told HiSpeed the following
Hey Hi speed,
I've just got back to our team and the compacting issue is a bug. We're looking into fixing the issue soon but in the meantime below is the workaround.

Workaround:
Reboot machine and then run a Compact.
Now Compact shows numbers and ask for a reboot.
Check system health after reboot.
Status changed to GOOD with no actions listed below
In regards to the temp files not deleted by RM in the registry, I am still awaiting on a reply regarding the issue.

Cheers,
Magician

So now you are refusing to call this problem a bug.
Also as HiSpeed and I have both told you, your workaround does not work. The only thing that seems to work is to wait until the registry is less than 100% compact, at which point the RM software will ask for a reboot and system health can return to "good." But as long as the registry is 100% compact, system health remains poor. That is the BUG

[loyall]

Bumped for attention

[Magician]

Hello Loyall,

I've just spoken with QA and we will be looking to address this bug in future builds of RM.

Regards,

Magician

[loyall]

Has the restore point bug that appeared in version RM11.0.0.277 been corrected in version RM11.0.1.716? In other words is it safe to optimize windows in the latest version?