Thank you, that's important information - it shows the problem. The 0x00 is a character not "allowed" in key names, since it usually indicates the end of a text. In this case that means it detects keys with a name of zero length, which should be impossible, but has been known to occure. regedit.exe might ignore it - RegAlyzer does not because such invalid uses of 0x00 might be indicators of rootkits. We'll do some experiments about this
Just remember, love is life, and hate is living death.
Treat your life for what it's worth, and live for every breath
(Black Sabbath: A National Acrobat)
Excellent!
Keep up the good work,
Love you too
Hi Pepi,
My loop the same with that version.
Ah... catching up above .. yes the same 0x00.
Shalom,
Steven
Last edited by Steven Avery; 2009-04-10 at 06:53.
Added 1.6.2.15 some days ago and today 1.6.2.16 with 0x00 fixes
Downloads here
Just remember, love is life, and hate is living death.
Treat your life for what it's worth, and live for every breath
(Black Sabbath: A National Acrobat)
Just tried 1.6.2.16
Well... I can no longer see the <0x00> russian dolls but it still has a [+]cfg and I can't expand it.
When I click on the + it doesn't expand the cfg key.
And Search is still jamming on it
Last edited by YaffYaff; 2009-04-24 at 04:23.
RegAlyzer 1.6.2.16 crashes for me too. Virtual memory usage rises dangerously fast on Win XP Sp3
Similar issue post here:
http://forums.spybot.info/showthread.php?p=352990
Sigh... It's been over 2 years and many releases. I think the issue is in the bug list but it must have a very low priority. I really miss this RegAlyzer. I gaved up already an no longer use it.
I had a spark of hope when I got the email notification of your post.
Oh well. Would have been a nice xmas gift to see a resolution.