Yep, they skipped System Mechanic 9.5.4 … probably because of my quip that we will have 9.5.4 by Jan. 1.
Last night, around 11:30 pm US Eastern time I got System Mechanic 9.5.5. [By the way, it wasn’t a clean install. As ever, System Mechanic wanted to restart Windows 7 after its install. I said “OK.” But, Windows 7 wouldn’t restart because it said System Mechanic wasn’t closing down. Windows 7 actually has a very eye-catching black-themed screen that informs you of its inability to restart until you force the shutdown of a ‘rogue’ app. — in this case System Mechanic. Once, I forced the shutdown of System Mechanic … Windows 7 restarted and all was well … though System Mechanic did not automatically start-up as it had done in other instances after such a restart.]
So here is the release schedule that I have seen as a ‘loyal,’ fully paid-up legit customer:
System Mechanic 9.5.0 November 27, 2009
System Mechanic 9.5.1 December 3, 2009 (6 days between releases)
System Mechanic 9.5.2 December 10, 2009 (7 days between releases)
System Mechanic 9.5.3 December 21, 2009 (11 days between releases)
<< No System Mechanic 9.5.4. I will miss you. RIP >>
System Mechanic 9.5.5 December 21, 2009 (18 days between releases)
5 releases in 42 days; a new release every 9 days … and that over the holidays. My hat off to you iolo. You have been busy. Thank you … I think.
So far, so good. Ran it a few times. No hangs yet … but it is early days.
I could be wrong but I think this release has a bunch of new tools under ‘Manage System Configuration.’ Looks interesting. But, not going to mess with any of these right now.
I ran System Mechanic 9.5.5 a few times last night and this morning.
I ran ‘Deep Analysis.’ Much to my amusement it did not tell me I had fragmentation on my C-drive. I think the last time around, with 9.5.3, it had claimed I had 10%.
This morning I ran de-frag on both C- and D-. I did get 10% residual fragmentation on C- … though I know that Windows 7 defrag says this drive has 0% fragmentation. That 9.5.5 no longer harps on me having high fragmentation could mean that iolo is finally coming in line with Microsoft’s revised guidelines for disk fragmentation.
Bottom line, I still get the feeling that System Mechanic is operating in ‘lock-down’ mode. I think I have established my credentials as having a fairly good sense of System Mechanic’s cadences. Both 9.5.3 and now 9.5.5 seem unduly restrained. That might not be a bad thing. So rather than being aggressive about identifying border line issues, it appears to stick with what it knows it is really good at: registry errors, registry fragmentation and disk clutter. So, let us see what transpires. I hope 9.5.5 is more stable than 9.5.3. I really would be bummed if I get any more System Mechanic hangs.