Printable View
Not sure if this has been reported.
Regalyzer search hangs on numerous keys in my WINXP registry.
The attachement is an export from regedit of a key Regalyzer can't digest.
I'm having this problem since 1.5 and it is still present in 1.6.
Any kind of help is more then welcome
Hmmm... I imported it (after editing the file to point to different location, replaced HKLM\SYSTEM\ with HKCU\RegAlyzerTest\), and did variouses searches, all run just fine.
A few questions, e.g. regarding the search dialog settings:
- By 1.6, do you refer to 1.6.0.11 or 1.6.0.12?
- Which search style did you define?
- Search focus (all checked probably)?
- Data types (all checked probably)?
- Any Misc options set?
Maybe you could also check permissions on these entries (Security information tab in RegAlyzer, right-click option in regedit)- are they different from other services?
> By 1.6, do you refer to 1.6.0.11 or 1.6.0.12?
1.6.0.12
> Which search style did you define?
Where do I set style?
>Search focus (all checked probably)?
I tried all, then unchecked only one (for all), then unchecked all
That's where I got really puzzled.
> Data types (all checked probably)?
Same as above
> Any Misc options set?
Same as above
> Maybe you could also check permissions on these entries (Security information tab in RegAlyzer, right-click option in regedit)- are they different from other services?
Yes! The keys causing problems seams to all have more restrictive permissions. But I can't read them in RegAlyzer, I need to use RegEdit to see the difference.
Even RegEdit doesn't shows all the sub keys. RegEdit EXPORT dump more information then what is shown by RegEdit gui.
Another strange thing I noticed is RegAlyser presents the key as an infinite Russian Dull. ie almost like there was a loop to itself. I can't get to the bottom of it. (See attachment). The "infinite loop" does not occure in RegEdit. But as I said, RegEdit does not show all the "hidden" keys.
I replied to your question. Let me know if you want me to run more tests.
The problem seams to be access rights related.
Heeeeelp :crazy: