Win7 Registry Size

In message , Rene Lamontagne
writes:
On 12/05/2017 7:04 AM, Ed Cryer wrote:
[]
Well you fellows got my curiosity up about registry cleaners.
I have never used one, So having a 1 day old Macrium backup I
decided to have a look.

I exported the registry to a blank folder and checked it's size it
was 377 MB.
Ran Ccleaner registry cleaner and it took 4 passes before it
reported no errors'
Exported it again and found the new clean size to be(drum roll) 383 MB!
[]
Case Closed.

Rene

Maybe Ccleaner has done you a favour. I've never seen it do multiple
passes, and I'd guess it was repairing something that might have been
about to crash your system. 6MB added to shore up a shaky wall.
Ed

I dunno Ed, I have never used a registry cleaner and this was just an
experiment to see what happened but I always assumed they were supposed
to remove overburden.
This system has always been quick and smart and using this registry
cleaner doesn't seemed to have hurt or helped it any, I'm just very
surprised that it added instead of subtracting.

Rene

It's also possible that it would have gone from 377 to 383 MB during
that session even if you _hadn't_ run the cleaner - in other words, the
increase may not be due to the cleaner. I'd suspect it wasn't, in fact;
we can argue for ever as to whether cleaners do any good or actually do
harm, but I don't think they will _increase_ it.

The defragger someone mentioned, now that sounds as if it should be both
worthwhile and harmless, if the registry is really a file system (an
obfuscated one, as Paul puts it).

I've _never_ thought the registry a good idea. Common libraries, i. e.
the .DLL system, yes (though that has its problems when backward
compatibility is compromised), but - apart from the undetectable
advantage of loading from RAM rather than disc - I've never seen its
advantage over .ini files, for software settings.
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Feudalism : It's your count that votes.