Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: ymryan on April 15, 2008, 12:16:04 PM
-
I get following log when trying to update: 15.04.2008 06:12:39 general: Started: 15.04.2008, 06:12:39
15.04.2008 06:12:39 general: Running setup_av_pro-44a (1098)
15.04.2008 06:12:39 system: Operating system: WindowsXP ver 5.1, build 2600, sp 2.0 [Service Pack 2]
15.04.2008 06:12:39 system: Memory: 86% load. Phys:31332/228708K free, Page:300196/559692K free, Virt:2069620/2097024K free
15.04.2008 06:12:39 system: Computer WinName: YVONNE
15.04.2008 06:12:39 system: Windows Net User: YVONNE\YRyan
15.04.2008 06:12:39 general: Cmdline: /downloadpkgs /noreboot /silent /progress
15.04.2008 06:12:39 general: DldSrc set to inet
15.04.2008 06:12:39 general: Operation set to INST_OP_UPDATE_GET_PACKAGES
15.04.2008 06:12:39 general: Old version: 44a (1098)
15.04.2008 06:12:39 system: Using temp: C:\DOCUME~1\YRyan\LOCALS~1\Temp\_av_proI.tm~a02760 (6509M free)
15.04.2008 06:12:40 general: SGW32P::CheckIfInstalled set m_bAlreadyInstalled to 1
15.04.2008 06:12:40 internet: SYNCER: Agent=Syncer/4.70 (av_pro-1098;p)
15.04.2008 06:12:40 system: Computer DnsName: yvonne
15.04.2008 06:12:40 system: Computer Ip Addr: 74.65.11.113
15.04.2008 06:12:40 system: Installed in: C:\Program Files\Alwil Software\Avast4 (6509M free)
15.04.2008 06:12:40 internet: SYNCER: Type: use IE settings
15.04.2008 06:12:40 internet: SYNCER: Auth: another authentication, use WinInet
15.04.2008 06:12:40 package: Part prg_av_pro-44a is installed
15.04.2008 06:12:40 package: Part vps-8041500 is installed
15.04.2008 06:12:40 package: Part news-4b is installed
15.04.2008 06:12:40 package: Part setup_av_pro-44a is installed
15.04.2008 06:12:40 package: Part jrog-10 is installed
15.04.2008 06:12:40 general: Old version: 44a (1098)
15.04.2008 06:12:40 registry: ERROR!:Cannot access registry HKLM\SYSTEM\CurrentControlSet\Services\avastTestService, error code: 0x000005AA
15.04.2008 06:12:40 general: Err:Not enough user rights to continue
-
Are you logged as an administrator? Or just a common user?
Maybe your avast installation got somehow corrupt, then I suggest an installation from the scratch:
1. Uninstall avast from Control Panel first.
2. Boot.
3. Download the latest version of Avast Uninstall (http://www.avast.com/eng/avast-uninstall-utility.html) and use it for complete uninstallation.
4. Boot.
5. Install again the latest avast! (http://www.avast.com/eng/programs.html) version.
6. Boot.
7. Check and post the results.
-
When I try to uninstall from control panel, I get the "not enough user rights" message also (following. I am the administrator.
16.04.2008 07:16:40 general: Started: 16.04.2008, 07:16:40
16.04.2008 07:16:40 general: Running setup_av_pro-44a (1098)
16.04.2008 07:16:40 system: Operating system: WindowsXP ver 5.1, build 2600, sp 2.0 [Service Pack 2]
16.04.2008 07:16:40 system: Memory: 85% load. Phys:32476/228708K free, Page:214492/559692K free, Virt:2069620/2097024K free
16.04.2008 07:16:40 system: Computer WinName: YVONNE
16.04.2008 07:16:40 system: Windows Net User: YVONNE\YRyan
16.04.2008 07:16:40 general: Cmdline: /uninstwiz
16.04.2008 07:16:40 general: Old version: 44a (1098)
16.04.2008 07:16:40 system: Using temp: C:\DOCUME~1\YRyan\LOCALS~1\Temp\_av_proI.tm~a03840 (6434M free)
16.04.2008 07:16:40 general: SGW32P::CheckIfInstalled set m_bAlreadyInstalled to 1
16.04.2008 07:16:40 general: DldSrc set to inet
16.04.2008 07:16:40 internet: SYNCER: Agent=Syncer/4.70 (av_pro-1098;p)
16.04.2008 07:16:41 system: Computer DnsName: yvonne
16.04.2008 07:16:41 system: Computer Ip Addr: 74.65.11.113
16.04.2008 07:16:41 system: Installed in: C:\Program Files\Alwil Software\Avast4 (6434M free)
16.04.2008 07:16:41 internet: SYNCER: Type: use IE settings
16.04.2008 07:16:41 internet: SYNCER: Auth: another authentication, use WinInet
16.04.2008 07:16:41 package: Part prg_av_pro-44a is installed
16.04.2008 07:16:41 package: Part vps-8041500 is installed
16.04.2008 07:16:41 package: Part news-4b is installed
16.04.2008 07:16:41 package: Part setup_av_pro-44a is installed
16.04.2008 07:16:41 package: Part jrog-10 is installed
16.04.2008 07:16:41 general: Old version: 44a (1098)
16.04.2008 07:16:41 registry: ERROR!:Cannot access registry HKLM\SYSTEM\CurrentControlSet\Services\avastTestService, error code: 0x000005AA
16.04.2008 07:16:41 general: Err:Not enough user rights to continue
-
But what is 'avastTestService'?? Is this service should be really present on 4.7?
Can you see this service in regedit? If so who has rights for this service?
-
But what is 'avastTestService'?? Is this service should be really present on 4.7?
Can you see this service in regedit? If so who has rights for this service?
It's a test registry key created during installation to check the user rights access to Windows registry. It is deleted afterwards when the user has the enough rights to install.
-
I uninstalled from the website, reboot and tried to reinstal and got this message: 16.04.2008 12:49:43 general: Started: 16.04.2008, 12:49:43
16.04.2008 12:49:43 general: Running setup_av_pro-491 (1169)
16.04.2008 12:49:43 system: Operating system: WindowsXP ver 5.1, build 2600, sp 2.0 [Service Pack 2]
16.04.2008 12:49:43 system: Memory: 63% load. Phys:82888/228708K free, Page:359584/559692K free, Virt:2069600/2097024K free
16.04.2008 12:49:43 system: Computer WinName: YVONNE
16.04.2008 12:49:43 system: Windows Net User: YVONNE\YRyan
16.04.2008 12:49:43 general: Cmdline: /sfx /sfxstorage "C:\DOCUME~1\YRyan\LOCALS~1\Temp\_av_sfx.tm~a03436" /srcpath "C:\DOCUME~1\YRyan\LOCALS~1\TEMPOR~1\Content.IE5\A17ST03E"
16.04.2008 12:49:43 general: DldSrc set to sfx
16.04.2008 12:49:43 general: Old version: ffffffff (-1)
16.04.2008 12:49:44 general: Install check: SetupVersion does NOT exist
16.04.2008 12:49:44 general: SGW32P::CheckIfInstalled set m_bAlreadyInstalled to 0
16.04.2008 12:49:44 registry: ERROR!:Cannot access registry HKLM\SYSTEM\CurrentControlSet\Services\avastTestService, error code: 0x000005AA
16.04.2008 12:49:44 general: Err:Not enough user rights to continue
-
HKLM\SYSTEM\CurrentControlSet\Services\avastTestService, error code: 0x000005AA
16.04.2008 12:49:44 general: Err:Not enough user rights to continue
Can you check if you have this Registry key and then try to delete it before installing?
-
I'm not sure where to look for it
-
Strange error code...
Please check your registry hive (Windows\System32\Config\System) - how big is that file?
-
I'm not sure where to look for it
Regedit.exe from C:\Windows folder.
But if you've never work with the registry, it will be safer no managing it...
-
Registry Hive = 57,344 KB
-
Well, it's quite a lot... I've found a statement than XP registry hive limit is 1/4 of physical memory (or 200MB, whichever is smaller).
Your physical memory is 228708KB (256MB with a part used by graphics adapter?) - which, divided by 4, gives 57177KB...
So, maybe your SYSTEM hive is simply too big and new keys can't be created. Now, I'm not sure how to shrink it, however... maybe somebody else knows some tools?
-
But officially RSL was dropped in XP (http://support.microsoft.com/kb/292726).
There is reference to registry compactor NTRegOpt (http://www.snapfiles.com/publishers/lars-hederer/index.html)
Reported cases when this utility made decrease system hive on 70-80%. Obviously in the case of bloated system hive, but the size 57M looks like hive is bloaded.
-
Well, could be, it's just that:
- the statement comes from a book by M. Russinovich - whom I'd trust at least the same as MS KB article ;D
- this error 5AA (ERROR_NO_SYSTEM_RESOURCES) is weird; it indicates that some kind of internal limit has been reached
- there was a similar case (http://forum.avast.com/index.php?topic=12427.0) here some time ago - and the user's hive was slightly over 200MB...
MS docs say that the error may also be returned when a key is opened more than 65534 times simultaneously... might be some leak, don't know how likely it is. Maybe it could be checked by Process Explorer - looking for "\Services" handle...
-
I use a little tool to compact the registry hives, RegCompact.net, see image.
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, so I need to compact some of the Hives on my system. Not all the Hives see that much activiy so don't need compacting very often, the system hive is the one that gets some hammer.
How It Works
RegCompact.NET will enhance your system's performance by optimizing the way your system's registry hives are stored on disk. During the normal operation of a Windows system, registry data is constantly being written to and removed from the registry. Over time this data becomes scattered within the registry file and when information is deleted from the registry holes are left which fragment the data within the registry. Due to this, accessing a few related pieces of information from the registry during program startup could become very slow as the system needs to traverse a very large file to find the data.
RegCompact.NET solves the problem of registry fragmentation and large size by rewriting the registry hives into new files which are completely optimised and often much smaller. Your computer is restarted after the registry hives are compacted and during system startup the old, fragmented files are replaced with the newly generated and optimized ones.
I have used this for some years without any adverse effect, however, like in life no guarantees. This program has now gone to RegCompactPro for about $12 I don't know if you will be able to find a copy of RegCompact.net version 1.8 or another tool that does the same.
-
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.
-
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.
-
So, I can't use Avast?
-
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
-
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.
-
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.
-
Yes I ran Auslogics Registry Defrag and reboot
-
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)?
-
stil 57,344 KB in can't install. yikes!
-
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.
-
Yes, it looks just like that
-
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.
-
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
-
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?
-
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.
-
The registry is subject to additions and deletions all the time this person is running.
This is 56M not 200M. I would also ask the original poster to confirm that this is the size of the SYSTEM file and not the SOFTWARE file.
-
Microsoft Windows Internals, Fourth Edition
In some cases, hive sizes are limited. For example, Windows places a limit on the size of the HKLM\SYSTEM hive. It does so because Ntldr reads the entire HKLM\SYSTEM hive into physical memory near the start of the boot process when virtual memory paging is not enabled. Ntldr also loads Ntoskrnl and boot device drivers into physical memory, so it must constrain the amount of physical memory assigned to HKLM\SYSTEM. (See Chapter 6 for more information on the role Ntldr plays during the startup process.) On Windows 2000, Ntldr places a fixed upper limit on its size of 12 MB, but on Windows XP and Windows Server 2003 it is more flexible, allowing the hive to be up to 200 MB or one fourth the amount of physical memory on the system, whichever is lower.
-
Then I think you may have cracked it.
If her SYSTEM file really is 56M then it just exceeds the capacity of one quarter of the system memory (reported by avast as 223.34M - a rather odd number).
So finding the space hog in that hive appears to be essential.
-
That's what I was saying here: :-)
http://forum.avast.com/index.php?topic=34759.msg292141#msg292141
I don't think the inability to create the key can be caused by other protection tools... I mean, it could be, but I'd expect a different error (ACCESS_DENIED, maybe SHARING_VIOLATION... but not NO_SYSTEM_RECOURCES, it's weird).
MS docs also mentions this:
A single registry key can be opened only 65534 times. When attempting the 65535th open operation, this function [RegCreateKeyEx] fails with ERROR_NO_SYSTEM_RESOURCES.
As I wrote in other post too, it might be possible to check by Process Explorer (looking for handles to Services key) - but I don't think this is the problem, I think it's more likely to be related to the hive size.
-
You are right Igor, it was foolish of me to expect MS documentation to be consistent ... "we have removed registry size limits in XP" .. well apart from these important limitations in the very small print.
-
So, what is my next step?
Thanks for all your help!
-
Hi There, I am now getting bombarded with JUNK! Do I really have no resolution to this?
Yvonne
-
If the registry key cannot be created in the Services tree (btw, you didn't write if you're able to create it manually from regedit or not) - and if the registry compacting didn't help (=shrink the hive size), then I really don't know what to suggest (except for reinstalling the OS).
You may try to export the registry (HKEY_LOCAL_MACHINE\System) to a .reg file and then try to find what uses so much space there... but if the hive is corrupted internally, it doesn't have to be included in the exported file. And, even if you find a big subtree and even if it could be deleted - there's no guarantee than the hive could be compacted later. :(
Btw, I don't think this problem affects avast! only - I'd expect other programs couldn't be installed as well (at least those installing some services).