User Rights

[Lisandro]

Use Auslogics Registry Defrag (http://www.auslogics.com/en/software/registry-defrag) and see what you get. If it is not enough, we can use a registry cleaner to reduce its size.

[alanrf]

David,

just an oversight I think:

As you can see the system one in my image is 256 a quarter of my RAM, but it will compact down quite nicely to 48KB,

That is actually the security folder and it was just 256Kb not 256Mb.  The real SYSTEM file is the third one down in your image and it does not compact much at all.  Hopefully the original poster will get a much better compaction level.  I am wondering if the SYSTEM file size was the one posted since in my case, as in yours, the really large file is the SOFTWARE one.

 

[ymryan]

So, I can't use Avast?

[ymryan]

I did the registry cleanup, and and still can't download Avast :

17.04.2008 06:02:18 general: Started: 17.04.2008, 06:02:18
17.04.2008 06:02:18 general: Running setup_av_pro-491 (1169)
17.04.2008 06:02:18 system: Operating system: WindowsXP ver 5.1, build 2600, sp 2.0 [Service Pack 2]
17.04.2008 06:02:18 system: Memory: 72% load. Phys:64032/228708K free, Page:299740/559692K free, Virt:2069600/2097024K free
17.04.2008 06:02:18 system: Computer WinName: YVONNE
17.04.2008 06:02:18 system: Windows Net User: YVONNE\YRyan
17.04.2008 06:02:18 general: Cmdline: /sfx /sfxstorage "C:\DOCUME~1\YRyan\LOCALS~1\Temp\_av_sfx.tm~a02312"  /srcpath "C:\DOCUME~1\YRyan\LOCALS~1\TEMPOR~1\Content.IE5\A17ST03E"
17.04.2008 06:02:18 general: DldSrc set to sfx
17.04.2008 06:02:18 general: Old version: ffffffff (-1)
17.04.2008 06:02:18 general: Install check: SetupVersion does NOT exist
17.04.2008 06:02:18 general: SGW32P::CheckIfInstalled set m_bAlreadyInstalled to 0
17.04.2008 06:02:18 registry: ERROR!:Cannot access registry HKLM\SYSTEM\CurrentControlSet\Services\avastTestService, error code: 0x000005AA
17.04.2008 06:02:18 general: Err:Not enough user rights to continue

[Lisandro]

So, I can't use Avast?

Did you try what I've posted before?

Use Auslogics Registry Defrag (http://www.auslogics.com/en/software/registry-defrag) and see what you get. If it is not enough, we can use a registry cleaner to reduce its size.

[DavidR]

David,

just an oversight I think:

As you can see the system one in my image is 256 a quarter of my RAM, but it will compact down quite nicely to 48KB,

That is actually the security folder and it was just 256Kb not 256Mb. 
<snip>

Thanks Alan, I wasn't paying much attention, just trying to show the effects the tool can have.

[ymryan]

Yes I ran Auslogics Registry Defrag and reboot

[Lisandro]

Yes I ran Auslogics Registry Defrag and reboot

Which is the size, after defragmenting, of that registry file?
Maybe Igor's theory is not applicable here...
Can't you install avast (yet)?

[ymryan]

stil 57,344 KB in can't install. yikes!

[alanrf]

Let's try a slightly different tack.

In Windows can you please go:

Start > Run > type "regedit.exe" (without the quotes) > OK

Then in the regedit display can you please use the left panel to navigate down as shown in the image attached here.

Does the right panel look the same as the one in the image? 

Do not change anything - please just let us know.

[ymryan]

Yes, it looks just like that

[alanrf]

I assume that you followed the advice from Tech on the defragment tool.

I am most puzzled as I assume that simply using that tool would indicate that you have enough rights over the registry.

The Microsoft documentation I read states pretty clearly that registry size issues were eliminated with Windows XP.

avast team - how about providing a quick registry update file for that key (and a removal of it) for the user to try?  It should produce the same error the avast update is reporting - if not then well ... different story.

[igor]

Well, what if you try to create a new key manually (= from regedit)
Maybe the same as avast! installer was trying to create - HKLM\SYSTEM\CurrentControlSet\Services\avastTestService

[alanrf]

Igor,

good point but I was thinking the user might be more comfortable with something coming from avast. 

As I mentioned earlier though I assumed that running the utility recommended by Tech would have demonstrated whether there were enough rights.  Any thoughts? 

Could there be another protection tool in use blocking avast performing a registry update? 

[psw]

alanrf
But the playing with registry in the abovementioned state is rather dangerous operation. Obtaining 0x5AA error is not bad variant. BSOD during load examples when SYSTEM hive size exceeding 200M can be found in inet. Are sure that this risk is required?
Probably the only reasonable way is to try find registry key with extra size and delete it with subsequent hive compact.