Avast WEBforum
Business Products => Archive (Legacy) => Avast Business => Avast Endpoint Protection => Topic started by: KDibble on September 09, 2015, 05:26:08 PM
-
Using Endpoint Protection 8.0.1603 on a Windows XP Pro SP3 box with VPS 150903-0. System/license is controlled by SOA 1.3.3.35 on a Windows 7 machine. Program updates are disabled in the SOA. NO firewalls are in use.
I see that this is not the current VPS. The SOA shows a green checkmark for this machine and says the last update was on September 3, and that all shields are running.
Every couple of hours for the past 2 days on this machine I have gotten an Avast pop-up claiming that Avast is unable to update successfully. However, the client says everything is up to date ("latest update received" today just a few minutes ago, even though the VPS is not current) and working fine. The last time the pop-up appeared, I clicked the "update now" link on it. Avast attempted to update but halted with a message saying something like "insufficient storage space to complete the operation".
The XP box has 420 GB free space; the Win 7 SOA box has nearly 1 TB of free space. Obviously this error is bogus.
I know: XP is old, etc. etc. etc. However, Avast claims to still support XP, and has issued no statements to the contrary.
Probably if I uninstall and reinstall the client I'll get an updated VPS.
However, I wanted to ask if anyone has seen this.
Thanks.
-
Unfortunately, there's not much you can do about it. If you update your VPS regularly, there is less chance for hitting this bug. You can use VPSUpd (https://www.avast.com/en-us/download-update) manually to fix it (for some time).
-
Thank you.
I'm not sure what you mean about updating VPS regularly.
The SOA requests VPS updates from Avast every four hours. However, there is no pre-defined or custom "job" in the SOA that can force-push VPS updates from the SOA to the clients. The only job options relating to updates concern downloading updates from Avast's corporate servers to the machine that hosts the SOA. As a practical reality, then, workstations have to pull updates, and they only do that when they reboot.
If I have to have a special program to cause my managed Win XP client to update its VPS, I might as well just uninstall and reinstall the client.
-
Hi, I have got the same problem with many XP workstations. When I reinstall the client everithing is ok to the next Monday. Yes on Monday the problem appears again. What can I do? Please give some solution. We paid some money about it and Avast says "XP is supported OS"
-
I am having the same issue with some XP workstations. Uninstalling/reinstalling works for a couple of days and then they're no longer able to update.
-
I have heard that this update is to be released this month, and we have exactly 2 weeks left in this month!
-
I like to add we're seeing the same problems on a random subset of our equipment. The "storage" referred to is RAM, not disk space.
This is a snippet out of the Setup.log files of an effected PC:
17.09.2015 16:00:52.000 1442520052 (null) GetFileWithRetry: vps_32-1140-113f.vpx downloaded and verified
17.09.2015 16:00:52.000 1442520052 (null) DldPackage: C:\Program Files\AVAST Software\Avast Business\Setup\vps_32-1140-113f.vpx, returned 0x00000000
17.09.2015 16:00:54.000 1442520054 (null) PerformPkgDiff: pPkgDiffStorage->m_pbtBufNew allocated 255477305
17.09.2015 16:00:58.000 1442520058 (null) PerformDiff: Ok
17.09.2015 16:00:58.000 1442520058 (null) HttpGetWinsock(http://192.168.250.14:16135/vps_32-1141-1140.vpx)
17.09.2015 16:00:58.000 1442520058 (null) Used server: http://192.168.250.14:16135
17.09.2015 16:00:58.000 1442520058 (null) GetFileWithRetry: vps_32-1141-1140.vpx downloaded and verified
17.09.2015 16:00:58.000 1442520058 (null) DldPackage: C:\Program Files\AVAST Software\Avast Business\Setup\vps_32-1141-1140.vpx, returned 0x00000000
17.09.2015 16:00:58.000 1442520058 (null) PerformPkgDiff: pPkgDiffStorage->m_pbtBufNew allocated 255563766
17.09.2015 16:00:58.000 1442520058 (null) ERROR PerformPkgDiff: pPkgDiffStorage->m_pbtBufNew == NULL
17.09.2015 16:00:58.000 1442520058 (null) PerformDiff: vps_32-1141-1140.vpx Bad, error code 0x00000008
17.09.2015 16:00:58.000 1442520058 (null) Vpu: C:\Program Files\AVAST Software\Avast Business\Setup\vps_32-1141-1140.vpx, size: 710682. md5: E583217B43A653AB5B3F51E45551D2EB, computemd5 returned 0x00000000, sig: 010F1232F13BBBE6D25C889C81DBB8ED82096E16421DA8687762A28C2E437A49C6CFABA4A2149374 returned 0x00000000
17.09.2015 16:00:58.000 1442520058 (null) PerformDiff( vps_32, 1140, 1141 ) failed 0x00000008
17.09.2015 16:00:58.000 1442520058 (null) Error:Not enough storage is available to process this command.
If I read this correctly, the problem appears to be that the updater tries to allocate two ~256 MB blocks of RAM and gets denied by the OS on the second block. This particular box has 3GB installed of which 1.5 GB was free at the time. The failure could be due to memory fragmentation, but even after a reboot, the update still fails.
(I guess it is time to update the stated "only 128MB RAM needed" in the minimum system requirements...)
-
My XP box has 4 GB of RAM, so that's not likely to be a factor in my case.
-
I am also suffering from this issue, I do hope it will be fixed soon?
-
Getting this on PC's at several of my clients :-\
I've tried re-installing but after a few days updates stop happening with the usual insuffient storage error.
Other PC's are updating fine from the same SOA/Server.
-
Hi Guys,
Just wanted to let you know that we are aware of the issue with XP devices getting this error. At this time you can update manually by downloading the updates from here:
https://www.avast.com/en-us/download-update
I have seen reports that this works for some and others it works for a few days then the error returns. We are working on a new release for the endpoint product line and should be ready this week or next from the last work I had.
Will try to keep you posted as more updates become available.
Thanks!
Jeff
-
Hi, the manual update method doesn't work for me. It runs, but says it's already up to date. When I check afterwards it still has the old definitions :-\
-
I've been working on this issue since September 4th with Avast! Technical Support (most recently Che Johnson).
During the process of attempting to resolve this issue, it has been established that if an automatic or streaming virus definition update attempt occurs (and fails) prior to running running VPSUPD.EXE, the VPSUPD.EXE process will fail to install the updated virus definitions.
In order for VPSUPD.EXE to succeed, both automatic and streaming virus definition updates need to be disabled.
Here's a configuration that has worked for my organization:- Configure a Computer Group in the Enterprise Administration Console* with the following settings (NOTE: only those settings I changed from our standard settings are listed):
Policies: avast! Antivirus / Updates
- Update from: Second-level mirror: {any server name or IP address that is NOT a mirror}
- VPS Update: Auto (prevents warnings in the Avast! GUI that Automatic Updates are disabled)
- Program Update: Manual
- UNCHECK "If mirror is unreachable, update from the Internet"
Policies: avast! Antivirus / Updates Details
Update Options:
- UNCHECK "Show notification box after automatic update"
- UNCHECK "Show notification box if an error occurs"
Auto-update Interval:
- Auto-update every: 30000 minutes
Policies: avast! Antivirus / Cloud services
Streaming Updates:
- UNCHECK "Enable streaming updates"
These settings prevent Avast! from automatically updating from local or Internet update sources.
Policies: avast! Antivirus / Password
Protected Areas:
This setting prevents end-users from manually clicking "Update engine and virus definitions" (NOTE: This will only work if your configuration is set as password-protected to begin with!)
- Place your affected XP systems in this new Computer Group
- REBOOT all of the affected systems
Since the affected systems have probably already tried to update automatically, they'll be in a "failed" state and will not update even if VPSUPD.EXE is manually run; a reboot ensures that the updates do not automatically take place.
- Apply VPSUPD.EXE either manually or via automated scripting/deployment system
Since it's an executable, you might have to get creative in scripting the update if your deployment system doesn't handle executables well.
- Verify via EAC* that the updates are being applied.
In my experience, there have been several systems that refused to update even after taking all of these steps; usually, the systems that have failed manual VPSUPD.EXE updates all show multiple "YYMMDD##_stream" folders in %ProgramFiles%\AVAST Software\Avast\defs. The only fix for those systems is a reinstall with an up-to-date installation package.
*: I have no idea if SOA contains these same features; modify as necessary to apply these settings via SOA.
YMMV.
--
Troy
Systems Administrator
Episcopal Community Services of San Francisco
-
Thanks for those detailed instructions, I'll give them a try tomorrow 8)
-
Thanks for those detailed instructions, I'll give them a try tomorrow 8)
Any luck with your configuration?
--
Troy
-
I've made the changes in SOA but haven't added the VPSUPD.exe to the login script.
Will try it manually with one PC and see if it works first.
-
I've made the changes in SOA but haven't added the VPSUPD.exe to the login script.
Will try it manually with one PC and see if it works first.
Good luck with it.
A couple of things to keep in mind:
- If you have a number of YYMMDD##_stream folders extant in %ProgramFiles%\AVAST Software\Avast Business\defs, the VPSUPD.EXE may fail; I'd recommend you try to find a test machine that is clear of these folders; and
- If SOA doesn't show a version upgrade following a successful VPSUPD.EXE run, you may be able to "force" a SOA update by restarting the "client" service that Avast uses for communication (with EAC, it's "avast! Enterprise Client Service").
-
Unfortunately the PC's I looked at had the _stream folders and even after deleting them it still came up with the "VPD database is already up to date" message :(
-
Unfortunately the PC's I looked at had the _stream folders and even after deleting them it still came up with the "VPD database is already up to date" message :(
Yeah; I had that on a number of systems as well.
According to the history on my Avast! support ticket, there is no way (short of uninstall/reinstall) to clear those _stream folders out.
My experimentation with trying to clear the _stream folders out manually wound up breaking the Avast! install on a test system (had to uninstall/reinstall); after that, I didn't risk it further, and just began the practice of moving the machine(s) to the "no updates" group, uninstalling and reinstalling.
Hope you're not dealing with too many machines (I had about 10 out of 50 that needed a full uninstall/reinstall).
--
Troy
-
This was supposedly to be fixed by the end of September. Today is October 1. What is the status on this bug, please.
Thank you.
-
This was supposedly to be fixed by the end of September. Today is October 1. What is the status on this bug, please.
From a recent ticket update, it appears they've still got the updated program in beta:
It's possible there will be a delay of about a week. The developers are still making some small changes prior to releasing the beta but I will know more Friday morning in which case I will let you know but its probably looking more like next week unfortunately but I will confirm once I hear back from QA.
I could be misinterpreting the statement.
So, program update Real Soon Now. ???
--
Troy
-
So, program update Real Soon Now. ???
Let's hope so ::)
-
Let's hope so ::)
What, not satisfied with the update schedule for the 20-month-old software that you bought and paid for, while the folks who are installing it on their home systems (or violating the license by installing it on their work systems) get the latest-and-greatest for free? Quelle horreur! :o
(Yeah, I know...smart-a**ery. Last refuge and all that. :P )
--
Troy
-
I've managed to update a couple of PC's by manually running VPSUPD.exe. I think the trick is to turn off all the auto updating and then wait until a new update is released and then run VPSUPD.exe. This gets around the "you are already up to date" error as the last update it tried to install automatically is older than the one contained in VPSUPD.exe.
-
After trying any kind of solution available regarding this particular error 0x8 (in windows xp), nothing was able to solve this error. Namely,
IRPStackSize registry entry modification (https://support.microsoft.com/en-us/kb/106167) (Still same Error)
PoolUsageMaximum and PagedPoolSize registry entries modification (https://support.microsoft.com/en-us/kb/304101) (Still same Error)
I also added Ram to several clients (Still Same error).
Moreover in several cases the VPSUPD.exe cannot be executed successfully generating a “You are already up to date” popup box (yet, you have very old defs)
In either case, the problem reappears every 1-2 days, making it very difficult to manage the updated VPSUPD.exe distribution and installation on the clients.
From my point of view, the error occurs while incremental update of vps_32-XXXX.vpx definitions file is executed; using the small frequent updates vps_32-XXXX-XXXX.vpx.
For some reason the “old definitions file” (vps_32-XXXX.vpx), which is already huge ~250MB, cannot be updated/appending the latest definitions.
After many attempts, I use the following solutions is the following,
- 1) Before proceeding, using the AEA console, I disable the Self-Defense module of my XP Computers Group (Located in the Troubleshooting Tab)
2) I create a script that deletes the old VPS_32-XXXX.vpx file located in the %programfiles%\AVAST Software\Avast Business\Setup\
This script can be executed either on your clients using a logon script or a Registry entry, or on the server using the administrative shares of the clients \\Client\c$\%programfiles%\AVAST Software\Avast Business\Setup\
3) After deleting, every client will be forced to download the fresh-full VPS_32-XXXX.vpx file through mirror and update AVAST with the latest definitions.
4) Last, I check that every client has the latest definition and re-enable the defense module of my Computer Group.
I know that the above mentioned procedure is a waste of bandwidth and might not worth for a small Lan, but in case of several remote sites or large Lan, it is very simple and quick for daily usage.
Hope to have an AVAST program update very soon.
-
It seems to be getting worse, I have more machines affected by it this week than I did last :(
-
It seems to be getting worse, I have more machines affected by it this week than I did last :(
The only workaround I've found so far that consistently works for our deployment is to place ALL XP machines into a separate EAC/SOA computer group with automatic updating disabled per previous posts, and go through the process of manually updating these machines (or scripting an update at startup, use the command line "{path\to\}VPSUPD.EXE /silent" if you don't want users to receive feedback on the process).
I've scripted an update process that is slightly more complex (as I have several remote sites where XP machines are failing auto-update, and the VPSUPD.EXE executable is really too large to be running on multiple systems across a multi-site WAN); the scripts I wrote for our deployment download the current VPSUPD.EXE from Avast to machine-local storage and install it on a 4-hour cycle (leveraging machine-local Scheduled Tasks).
I can't do it today, but possibly tomorrow (as we may not receive an update until next week, according to latest ticket notes) I'll be able to clean them up and post them here for general use.
--
Troy
-
I've managed to get them to update by using WGET to download the latest VPSUPD.exe and then running that from the login script.
Doesn't look good to the customers though, a couple of which have just renewed for 2 years :o
-
The problem still exists: using Avast endpoint 8.0.1603 and the error message is "Last encountered error: Not enough storage is avaliable to process this command" when trying to update the avast virus defs.
wait for the official solution.
Hi Guys,
Just wanted to let you know that we are aware of the issue with XP devices getting this error. At this time you can update manually by downloading the updates from here:
https://www.avast.com/en-us/download-update
I have seen reports that this works for some and others it works for a few days then the error returns. We are working on a new release for the endpoint product line and should be ready this week or next from the last work I had.
Will try to keep you posted as more updates become available.
Thanks!
Jeff
-
I've scripted an update process that is slightly more complex (as I have several remote sites where XP machines are failing auto-update, and the VPSUPD.EXE executable is really too large to be running on multiple systems across a multi-site WAN); the scripts I wrote for our deployment download the current VPSUPD.EXE from Avast to machine-local storage and install it on a 4-hour cycle (leveraging machine-local Scheduled Tasks).
I can't do it today, but possibly tomorrow (as we may not receive an update until next week, according to latest ticket notes) I'll be able to clean them up and post them here for general use.
Well, a day late, but here it is.
Two files:
- VPSUPD.CMD.TXT
--- RENAME TO VPSUPD.CMD ---
Primary script file for downloading and executing VPSUPD.EXE on an XP-based system with EPS/EPS+ installed
May be run as a Computer Startup Script (from Active Directory) or manually as Administrator (or a user with administrative privileges)
May be installed locally or on network share
Syntax:
{path\to\}VPSUPD.CMD {debug} {delay {#} | remove | override}
Parameters:
- debug
Ordinarily, the script defaults to "silent" mode; this parameter provides console output and VPSUPD.EXE feedback. May be used with other parameters
- delay {#}
Allows creation of machine-local Scheduled Task to run every 4 hours, with #-minute delay (default 10); this allows the Computer Startup Script to specify the Scheduled Task without causing resource contention at machine startup. Cannot be used with override or remove parameters
- remove
Deletes previously-created Scheduled Task with no further action. Cannot be used with override or delay parameters
NOTE: creating a file called "VPSUPD.REMOVE" in the same folder as VPSUPD.CMD will also remove the previously-created Scheduled Task with no further action; this allows for "zero-touch" configuration of large numbers of systems in an AD domain (when run from a server share)
- override
The script checks for a file called "VPSUPD.NOACTION" in the same folder as VPSUPD.CMD; if the file exists, the script will not perform any actions. This allows "zero-touch" global disable of the script for debugging or testing purposes.
Specifying the "override" parameter ignores the existence of the file and allows the script to be run anyway. Cannot be used with "delay" or "remove" parameters
Requires VPSUPD.VBS, below
The script is internally documented as to the various functions it performs.
- VPSUPD.VBS.TXT
--- RENAME TO VPSUPD.VBS ---
Visual Basic script that performs the actual download of VPSUPD.EXE
Used in conjunction with VPSUPD.CMD
The script is internally documented as to the various functions it performs.
The scripts do not require any third-party tools (WGET, similar) in order to function.
*** PLEASE NOTE ***
The scripts download VPSUPD.EXE from the Avast download servers to a local directory on the target machine (the directory location can be modified by modifying VPSUPD.CMD).
You must create a Global Exception in Avast! for the directory location where VPSUPD.EXE is downloaded in order for the update to run successfully!
Questions welcome; however; I reserve the right to treat you like an idiot if reading the contents of either file would have answered your question.
--
Troy
-
Update from my trouble ticket with Avast (as of 10/12):
I still don't have a "date" at which we're going to see the updated installation files; however, I have been told the following:
When the update is available you will be prompted to do so via the client and console so you will know when the update is available immediately without need of any email communication.
I've asked if this applies in situations where automatic updates have been disabled (such as for all of the XP systems we still have active here), and I'll post again when I know the answer to that question.
However, it doesn't appear that Avast intends to provide any general notification (email, forum post, etc.) when the update is available.
--
Troy
-
I've asked if this applies in situations where automatic updates have been disabled (such as for all of the XP systems we still have active here), and I'll post again when I know the answer to that question.
And, as of 10/15, I've received the following update to my Avast! trouble ticket:
You will be notified on the server which will be the only way you can push the update, the clients will be prompted in their VPS a new program update is available but it can only be distributed through the console if it's a managed client.
So, as near as I can tell, the only notification any of us will receive at this point is when either the Avast! Enterprise (or SOA) Console shows a "notification" that there is a newer version of the program, or when the individual client systems receive such a notification (presuming, of course, that the configuration has not been modified to either automatically update the program itself or to prevent program updating).
And so, we wait...and wait...and wait.
--
Troy
-
Status update from avast! Technical Support as of this morning:
The release for the new program will be available at the end of this month hopefully. When the program update is available you will be prompted on the client that a new program update is available and will then need to first update the console, then push the new client installation.
So, we ask that you continue to be patient.
So, for the third time, I've been told, "Update Real Soon Now." >:(
--
Troy
-
Thank you, Troy, for taking the time to share with us what information you have concerning this issue.
I will wait a little while longer for the up and coming update. And if all else fails, I will follow your instructions for your workaround.
Let's hope the update will be here soon. :)
~~ Angie
-
Sad to say, but IMHO the current version of Avast can no longer be considered suitable for enterprise use. v7 + AES was a considerable step backwards compared to v4 + ADNM. The shortcomings are all over these fora but the pleas have fallen on deaf ears for over two years. And now this. The manual daily update "workaround" is a kludge that does not scale so this bug effectively renders the product useless.
As our subscription was about to expire, we were monitoring this situation before committing the money for another year. As there is not even light at the end of the tunnel, we will not be coming back.
One last thing for others contemplating the same: give yourself plenty of leeway to replace Avast as the thing simply stops working at the end of the subscription. You do not even get to use the last signature updates you paid for despite the claim of a lifetime license on the scan engine.
-
Update to my trouble ticket received today at 2:27am Pacific:
Unfortunately I have been told that due to the delay of the upcoming consumer product release then the Endpoint program update will be delayed. I know your about as upset as I to hear about this delay and if we can push out a beta sooner then I will let you know directly as I just wanted to give you the heads up as you've been extremely patient with us thus far.
Very sorry.
And there you have it, folks.
scoenye: I can't blame you for jumping ship; at this point, I will not be able to recommend to my organization's directors that we continue with avast! beyond the end of our subscription.
--
Troy
-
So they are saying working on a new consumer product gets priorty over fixing a business product that people have paid a lot of money for >:(
I can see them loosing a lot of business customers over this ::)
-
So they are saying working on a new consumer product gets priorty over fixing a business product that people have paid a lot of money for >:(
I can see them loosing a lot of business customers over this ::)
Yes! Our 3 years subscription is about to expire and we have more than 100 clients....
I hope the bug will be fixed soon!!!
-
The problem still exists: using Avast endpoint 8.0.1603 and the error message is still the same "Last encountered error: Not enough storage is avaliable to process this command" when trying to update the Avast VPS. If I use the manual VPS update that works seemingly but I manage 20+ client so I don't have time and patience to every day update all manually....!!!
Unfortunately, we are in the middle of a 2 year subscription so my boss not wants to hear any new subscription or change! He said " we are paying enough to Avast to solve this problem " .....
SO WE ARE STILL wait for the official solution!!!! >:( >:(
not to mention that so far I recommend Avast to all my friend, customer and family member... but nowadays my trust begins to waver....
(to every native speaker: sorry for my engrish...) ;)
So they are saying working on a new consumer product gets priorty over fixing a business product that people have paid a lot of money for >:(
I can see them loosing a lot of business customers over this ::)
Yes! Our 3 years subscription is about to expire and we have more than 100 clients....
I hope the bug will be fixed soon!!!
-
If I use the manual VPS update that works seemingly but I manage 20+ client so I don't have time and patience to every day update all manually....!!!
You might try this: https://forum.avast.com/index.php?topic=176210.msg1254186#msg1254186 and this: https://forum.avast.com/index.php?topic=176210.msg1257983#msg1257983
The first post is the configuration in Enterprise Administration Console for the group to disable automatic updates (per a support case I opened in September with Avast! technical support).
The second post is a pair of scripts (Windows Command Script and VBScript) I threw together to create an "automated" update when it became clear that Avast! was not going to rapidly resolve this issue back in September...and now that it's November, and we still have no resolution on the issue, it seems to be even more fortuitous.
The total package has been working well for my installation (200+ clients at 13 sites, plus laptop users).
Unfortunately, we are in the middle of a 2 year subscription so my boss not wants to hear any new subscription or change! He said " we are paying enough to Avast to solve this problem " .....
You might want to let your boss know that the money you've already paid seems to be going to support the development of a new "free" product, rather than being invested in improving (or at least maintaining) the enterprise product...and any potential improvements to the "enterprise" product will only be implemented AFTER the "free" and one-shot paying customers are well taken care of.
Avast! seems to assign a higher priority to their "consumer" user base, given that we're now 22 months without a single update to the Avast! core program (while the "consumer" product has been updated routinely); the most recent update from Avast! to my trouble ticket makes it entirely clear that, for Avast!, the "consumer" (read: free package) takes total precedence over the "enterprise" package (bought and paid for, usually at thousands of US Dollars):
Update to my trouble ticket received today October 26, 2015 at 2:27am Pacific:
Unfortunately I have been told that due to the delay of the upcoming consumer product release then the Endpoint program update will be delayed. I know your about as upset as I to hear about this delay and if we can push out a beta sooner then I will let you know directly as I just wanted to give you the heads up as you've been extremely patient with us thus far.
Very sorry.
And there you have it, folks.
not to mention that so far I recommend Avast to all my friend, customer and family member... but nowadays my trust begins to waver....
Not surprised; I know I won't be renewing my organization's 250-user license of Avast! when it expires in August 2016.
I'm still using (at home) and recommending the Avast! free product; after all, they're actually improving it regularly.
However, I intend to find an enterprise anti-malware solution where the company puts their enterprise customers that actually put thousands of dollars each into their revenue stream above their one-shot "consumer" customers and their "free" customers.
Good luck!
--
Troy
-
thanks ECS Systems Manager but i want to use an official solution (an update) for this problem not a "half a loaf is better than no bread" method.... >:(
Your post other half is true and good picture it what I also think about this situation.... And that is a big shame on you AVAST! Inc.
I encourage and support a "free software for everyone" approach but not against the paying customers.... So think this again and do something...
-
Hi everybody,
I've found a temporary solution that keeps winxp pattern up to date: I've luckily stored on a network share the original installation package for clients, generated before the last program release. So it has been simple uninstall Avast from Win Xp machines and reinstall it by the old package. For me is working good both versions 7.x and 8.0.1490 tested on different customers. Obviously I hope Avast Support will solve this issue as soon as possible. I would like to know how to disable "warning" notification on taskbar about program not up to date.
Thanks, Fabio.
-
Yesterday I sent a ticket into the support system...
Ticket ID: 26523
Subject: "Update Failed" Messages on Win XP SP3
Today I get the following e-mail...:
Hello,
We have recently implemented some changes on our ticketing system. Could you please use the following form and resend your query to the Business support team, I am afraid they use a different system to ourselves so I am unable to transfer this request over to them.
https://www.avast.com/contact-us.php?subject=BUSINESS-SUPPORT
so far this is not FUNNY.... :P BUT I sent them also, so I wait they answer...
-
I have been having this same issue since the beginning of September on both Win XP and Win 7 computers. I'd say probably about 35% of our computers have this issue - messages when updating are either "Virus Definitions are up to date" or "Not enough storage". I have performed the work around's mentioned in this thread and other threads. They have worked on some computers but not others, and on the computers the work around worked on, a high percentage of them start having the same issues again after about a week.
-
Shocking customer service from Avast! We have 120 user license with 24 months left to run. Our Windows XP and Windows 10 stations are unprotected. Support department repeatedly fob us off with broken promises. If you're considering purchasing Avast! for your corporate environment, take my advice and DON'T BUY IT. Rubbish.
-
On 16. November I get the following message from AVAST:
Hello,
On the troubled machines please download the vpsupd.exe on those machines and it should fix the issue for the short term and later this month the new Program update for Endpoint will be released which will resolve the issue for all machines along with fixing some other small minor bus.
You can download the file below. **Please be sure to disconnect those XP machines from the default group so they do not receive any automatic updates which will undo the fix. We should have this issue resolved with the upcoming program update.
I hope this provides some solution for the meantime.
http://files.avast.com/iavs5x/vpsupd.exe
The reason for this tool is to delete all previous VPS files from avast and it enables the client to download new ones so it should remove the problem with not enough space.
Unfortunately you will need to run this manual update each day until the new program update is released. However, if you like you can migrate to our new Business Security product.
In all honesty it provides more flexibility in the management of different operating systems, lighter on resources not needing a localized database and cloud managed along with all the most up to date consumer features as well as business grade solutions.
It's a free cloud managed security product supporting PC's, Mac's and Windows File Servers (Exchange Servers Optional). This product has many advantages. One, its cloud managed requiring no dedicated equipment or servers for you to managed it which allows you to manage the clients regardless if on a Domain or Workgroup environment and will continue working regardless if your on your network or not. Two, it's very easy to use - you'll be able to signup and install your first account in five minutes or less.
You can sign up online and get instant access. http://www.avast.com/business
Keep in mind that any existing security software will have to be removed before installing Avast for Business. I recommend removing via your console's uninstall task or if you have stand alone machines to use the following tool below which is our uninstall tool.
https://www.avast.com/en-us/uninstall-utility unless you used a GPO or other management software to un-install.
In hoping that you do like the new business product we would honor the remaining coverage on your license and migrate the credit to use for the Premium product until your credit runs out in which case you can pay a monthly fee for the Premier usage or continue to use the Free version. As this product is licenseless you can install the client on as many seats as you choose, there is no limitation.
To move from Endpoint to Avast for Business please log into the cloud portal below and setup the account.
1. Log into your cloud portal. https://id.avast.com/en-us/login?target=https%3A%2F%2Fbusiness.avast.com%3A443%2F
2. Add a device then at the top right hand side of page click 'Try Premium' to activate the 14 day trial.
3. Please enter a valid credit card. (You will not be billed)
4. Then activate Premium on your devices. The workstations will have to be rebooted to confirm subscription change.
5. Just contact us at absfeedback@avast.com for any further questions about migrating current subscription to Free for Business for the remaining time on your license and we will transfer the credits from your Endpoint account to the Avast for Business.
OR
Just wait until later the Endpoint update to it's new release month of November.
Again, we apologize and more than understand the inconvenience as we are working as fast as possible to update the client which even I agree is over due.
Very Sorry,
Kind Regards,
Che'Johnson
So, everyone may deduct the conclusion.... i think we see a soft compel here to migrate our EPP to their new cloud based software.....because the promised update is still not here...... :( :-\
-
See: https://forum.avast.com/index.php?topic=179623.0
-
This may be off-topic but related anyway.
I now have exactly the described problems with my WinXP pc's. On my Win7 pc's, I don't use Avast, so no clue about that.
The difference from the other posts here, is that my XP's are standalone pc's with Avast free v7.0.1474.
The definition updating stopped working on the 11. october 2015, and afterwards the symptoms are exactly as described earlier in this thread.
The reason for writing this, is that I think the problem is in the definition signatures, since my program has not been updated.
I checked the ashupd.exe, and it is dated 30oct2012. The other files are also old, so the problem is not related to updated program files.
Of course I don't expect Avast to care about definition update bugs introduced to version 7.0.1474, so this post is only made in the hope that it may help
the IT-admins, who now suffer from this major bug, to find a solution.
And to the Evangelists: Yes, I know that WinXP and Avast 7 are are extremely dangerous, and should be updated ;)
-
...so this post is only made in the hope that it may help the IT-admins, who now suffer from this major bug, to find a solution.
The solution is to update to the latest Beta, follow the link in Reply #46.
-
See: https://forum.avast.com/index.php?topic=179623.0
Thanks Asyn, I see Avast posted a "Beta" update today, and this is nice, but two little things bothers me still:
Nr. 1: We encourage you to begin testing as soon as possible to help us identify any potential bugs or issues before our official release date, which is set to 9th of December.
Nr. 2: **There is no restriction on this public beta however please note that this should be used in testing environments as this is not a final release and you may experience unexpected results.
I know that I'm ungrateful and twitchy but why WE do the testing phase with "unexpected results" in our business related environment where every wasted minutes has a price... ???
Sorry but I still waiting the final relase which now **officially** dated 9th of December.... (exactly 3 months!! after the first error report) :P
-
You're welcome.
-
**There is no restriction on this public beta however please note that this should be used in testing environments as this is not a final release and you may experience unexpected results.
Some weeks ago, some resellers had a first private beta to test before this new public beta. AVAST Software is working in this upgrade for some time.
We encourage you to begin testing as soon as possible to help us identify any potential bugs or issues before our official release date, which is set to 9th of December.
It's not mandatory to test this beta version, but it can be good for small environments to resolve, temporally, XP and Windows 10 problems. As I mentioned before, a previous private version has been tested, but every customer is different, every network is different, every machine is different... so when more people test the beta in their different environments, more easy to detect bugs, better for all.
-
So after several months of waiting we finally get an updated version and it's had zero effect on the problem, still getting an error updating on XP PC's ::)
Maybe in another 3 months we'll get another beta which actually fixes the issue :P
-
@MavenIT: The nice part about being a pessimist is that you are constantly being either proven right or pleasantly surprised. I hope to prove you wrong, give it few more days, all right?
-
Are we going to have the XP issue fixed on December 9th with the final release? We only have to wait 3 days.
-
Are we going to have the XP issue fixed on December 9th with the final release? We only have to wait 3 days.
Unless something goes awry, yes.
-
@MavenIT: The nice part about being a pessimist is that you are constantly being either proven right or pleasantly surprised. I hope to prove you wrong, give it few more days, all right?
Your comment shows that you don't appreciate how serious this problem is.
If I was a home user using the free version and there was a major problem that still wasn't fixed after 3 months then I wouldn't be too upset, after all it hadn't cost me anything. This is an issue with a product that businesses have paid a lot of money for which they rely on to keep their PC's secure. Having spent that money they expect a high level of support.
I run a PC support company and advise my customers on what products to use. It doesn't reflect well on me when they've just bought a 2 year license for something and shortly afterwards a major fault is found. I then have to keep telling them don't worry Avast will have a fix for it soon.
How many of those do you think will want to renew their licenses when the time comes?
How can I recommend to other customers they switch to Avast when I can't be sure that any issues they have will be dealt with swiftly?
-
I appreciate the seriousness of this issue but I am a developer in quite a big company nowadays. I cannot (positively) influence release scheduling, product support or public relations. I cannot answer your rhetorical questions but I could talk extensively about this particular problem.
Unfortunately, there is no simple fix or workaround I could offer for legacy systems (Windows XP/2003 x86). You need to wait for new release which incorporates several independent fixes for this problem with public beta containing first set of them. It just wasn't enough (though it fixed those two computers running Windows XP x64).
-
Official Update is out... : https://forum.avast.com/index.php?topic=180249.0 (https://forum.avast.com/index.php?topic=180249.0)
-
...and now the VPS mirror not function the last good is version 9.12.2015 - 151209-0
:( :( :(
no errors, no updates, last VPS 10.12.2015 - 151210-0
avast!Enterprise 8.0.378 updated today morning
avast 8.0.1606
Mirror status from today:
=========================================
avast! Mirror
=========================================
Mirror folder: C:\Program Files\AVAST Software\Enterprise Administration\Mirror\mirror
Mirroring products: abp,ais
Current versions in mirror:
avast! Endpoint Protection: 8.0.1606 (Dec 09, 2015)
Virus database: 151209-0 (Dec 09, 2015)
and mirror log from today:
11.12.2015 09:20:25.000 1449822025 (null) Started: 11.12.2015, 09:20:25
11.12.2015 09:20:25.000 1449822025 (null) Running mirror_w32-0 (0)
11.12.2015 09:20:25.000 1449822025 (null) Operating system: Windows 7 ver 6.1, build 7601, sp 1.0 [Service Pack 1] SERVER
11.12.2015 09:20:25.000 1449822025 (null) Memory: 22% load. Phys:3234976/4193848K free, Page:4194303/4194303K free, Virt:2049400/2097024K free
11.12.2015 09:20:25.000 1449822025 (null) Computer WinName: VMWAVAST
11.12.2015 09:20:25.000 1449822025 (null) Windows Net User: SYSTEM
11.12.2015 09:20:25.000 1449822025 (null) Operation set to INST_OP_MIRROR_MIRROR
11.12.2015 09:20:25.000 1449822025 (null) Using temp: C:\Windows\TEMP\_av_mirrI.tm~a01928 (10040M free)
11.12.2015 09:20:25.000 1449822025 (null) Computer DnsName: VMWAVAST
11.12.2015 09:20:25.000 1449822025 (null) Computer Ip Addr: 192.168.222.17
11.12.2015 09:20:25.000 1449822025 (null) scr: mirror begin...
11.12.2015 09:20:25.000 1449822025 (null) SYNCER: Type: no proxy
11.12.2015 09:20:25.000 1449822025 (null) SYNCER: Auth: no authentication
11.12.2015 09:20:25.000 1449822025 (null) GUID: 42faab2d-92ee-457f-818e-e7419cdf94ed
11.12.2015 09:20:25.000 1449822025 (null) scr: Mirroring...
11.12.2015 09:20:25.000 1449822025 (null) Server definition(s) loaded for 'main': 29 (maintenance:0)
11.12.2015 09:20:25.000 1449822025 (null) SelectCurrent: selected server 'Download t5085699 AVAST5 Server' from 'main'
11.12.2015 09:20:25.000 1449822025 (null) scr: Using server: http://t5085699.iavs5x.u.avast.com/iavs5x
11.12.2015 09:20:25.000 1449822025 (null) HttpGetWinsock(http://t5085699.iavs5x.u.avast.com/iavs5x/servers.def)
11.12.2015 09:20:26.000 1449822026 (null) GetFileWithRetry: servers.def downloaded .
11.12.2015 09:20:26.000 1449822026 (null) servers.def not changed, 1444204600
11.12.2015 09:20:26.000 1449822026 (null) Server definition(s) loaded for 'main': 29 (maintenance:0)
11.12.2015 09:20:26.000 1449822026 (null) SelectCurrent: selected server 'Download x4263354 AVAST5 Server' from 'main'
11.12.2015 09:20:26.000 1449822026 (null) scr: Using server: http://x4263354.iavs5x.u.avast.com/iavs5x
11.12.2015 09:20:26.000 1449822026 (null) HttpGetWinsock(http://x4263354.iavs5x.u.avast.com/iavs5x/jollyroger.vpx)
11.12.2015 09:20:26.000 1449822026 (null) GetFileWithRetry: jollyroger.vpx downloaded .
11.12.2015 09:20:26.000 1449822026 (null) jollyroger.vpx not changed, 1449664957
11.12.2015 09:20:26.000 1449822026 (null) HttpGetWinsock(http://x4263354.iavs5x.u.avast.com/iavs5x/mirror.def)
11.12.2015 09:20:26.000 1449822026 (null) GetFileWithRetry: mirror.def downloaded .
11.12.2015 09:20:26.000 1449822026 (null) mirror.def not changed, 1449669113
11.12.2015 09:20:27.000 1449822027 (null) scr: Setting product 'abp' files (652 of 657 set)
11.12.2015 09:20:31.000 1449822031 (null) scr: Resetting existing files (reset 652 files, leaving 0 files).
11.12.2015 09:20:31.000 1449822031 (null) Server definition(s) loaded for 'main': 29 (maintenance:0)
11.12.2015 09:20:31.000 1449822031 (null) SelectCurrent: selected server 'Download x4263354 AVAST5 Server' from 'main'
11.12.2015 09:20:31.000 1449822031 (null) scr: Using server: http://x4263354.iavs5x.u.avast.com/iavs5x
11.12.2015 09:20:31.000 1449822031 (null) scr: mirroring 'abp' - nothing to do.
11.12.2015 09:20:31.000 1449822031 (null) scr: Setting product 'ais' files (4 of 657 set)
11.12.2015 09:20:31.000 1449822031 (null) scr: Resetting existing files (reset 4 files, leaving 0 files).
11.12.2015 09:20:31.000 1449822031 (null) Server definition(s) loaded for 'main': 29 (maintenance:0)
11.12.2015 09:20:31.000 1449822031 (null) SelectCurrent: selected server 'Download g0512802 AVAST5 Server' from 'main'
11.12.2015 09:20:31.000 1449822031 (null) scr: Using server: http://g0512802.iavs5x.u.avast.com/iavs5x
11.12.2015 09:20:31.000 1449822031 (null) scr: mirroring 'ais' - nothing to do.
11.12.2015 09:20:31.000 1449822031 (null) scr: Mirroring done.
11.12.2015 09:20:31.000 1449822031 (null) Direct delete of file: C:\Windows\TEMP\_av_mirrI.tm~a01928\onefile
11.12.2015 09:20:32.000 1449822032 (null) scr: Sumarizing...
11.12.2015 09:20:33.000 1449822033 (null) scr: Setting product 'abp' files (652 of 657 set)
11.12.2015 09:20:33.000 1449822033 (null) scr: Setting product 'ais' files (653 of 657 set)
11.12.2015 09:20:33.000 1449822033 (null) Return code: 0x20000001 [Nothing done]
11.12.2015 09:20:33.000 1449822033 (null) Stopped: 11.12.2015, 09:20:33
11.12.2015 09:50:25.000 1449823825 (null) Started: 11.12.2015, 09:50:25
11.12.2015 09:50:25.000 1449823825 (null) Running mirror_w32-0 (0)
11.12.2015 09:50:25.000 1449823825 (null) Operating system: Windows 7 ver 6.1, build 7601, sp 1.0 [Service Pack 1] SERVER
11.12.2015 09:50:25.000 1449823825 (null) Memory: 23% load. Phys:3203888/4193848K free, Page:4194303/4194303K free, Virt:2049400/2097024K free
11.12.2015 09:50:25.000 1449823825 (null) Computer WinName: VMWAVAST
11.12.2015 09:50:25.000 1449823825 (null) Windows Net User: SYSTEM
11.12.2015 09:50:26.000 1449823826 (null) Operation set to INST_OP_MIRROR_MIRROR
11.12.2015 09:50:26.000 1449823826 (null) Using temp: C:\Windows\TEMP\_av_mirrI.tm~a03028 (10039M free)
11.12.2015 09:50:26.000 1449823826 (null) Computer DnsName: VMWAVAST
11.12.2015 09:50:26.000 1449823826 (null) Computer Ip Addr: 192.168.222.17
11.12.2015 09:50:26.000 1449823826 (null) scr: mirror begin...
11.12.2015 09:50:26.000 1449823826 (null) SYNCER: Type: no proxy
11.12.2015 09:50:26.000 1449823826 (null) SYNCER: Auth: no authentication
11.12.2015 09:50:26.000 1449823826 (null) GUID: 42faab2d-92ee-457f-818e-e7419cdf94ed
11.12.2015 09:50:26.000 1449823826 (null) scr: Mirroring...
11.12.2015 09:50:26.000 1449823826 (null) Server definition(s) loaded for 'main': 29 (maintenance:0)
11.12.2015 09:50:26.000 1449823826 (null) SelectCurrent: selected server 'Download f6645934 AVAST5 Server' from 'main'
11.12.2015 09:50:26.000 1449823826 (null) scr: Using server: http://f6645934.iavs5x.u.avast.com/iavs5x
11.12.2015 09:50:26.000 1449823826 (null) HttpGetWinsock(http://f6645934.iavs5x.u.avast.com/iavs5x/servers.def)
11.12.2015 09:50:26.000 1449823826 (null) GetFileWithRetry: servers.def downloaded .
11.12.2015 09:50:26.000 1449823826 (null) servers.def not changed, 1444204600
11.12.2015 09:50:26.000 1449823826 (null) Server definition(s) loaded for 'main': 29 (maintenance:0)
11.12.2015 09:50:26.000 1449823826 (null) SelectCurrent: selected server 'Download j8529562 AVAST5 Server' from 'main'
11.12.2015 09:50:26.000 1449823826 (null) scr: Using server: http://j8529562.iavs5x.u.avast.com/iavs5x
11.12.2015 09:50:26.000 1449823826 (null) HttpGetWinsock(http://j8529562.iavs5x.u.avast.com/iavs5x/jollyroger.vpx)
11.12.2015 09:50:26.000 1449823826 (null) GetFileWithRetry: jollyroger.vpx downloaded .
11.12.2015 09:50:26.000 1449823826 (null) jollyroger.vpx not changed, 1449664957
11.12.2015 09:50:26.000 1449823826 (null) HttpGetWinsock(http://j8529562.iavs5x.u.avast.com/iavs5x/mirror.def)
11.12.2015 09:50:26.000 1449823826 (null) GetFileWithRetry: mirror.def downloaded .
11.12.2015 09:50:26.000 1449823826 (null) mirror.def not changed, 1449669113
11.12.2015 09:50:28.000 1449823828 (null) scr: Setting product 'abp' files (652 of 657 set)
11.12.2015 09:50:31.000 1449823831 (null) scr: Resetting existing files (reset 652 files, leaving 0 files).
11.12.2015 09:50:32.000 1449823832 (null) Server definition(s) loaded for 'main': 29 (maintenance:0)
11.12.2015 09:50:32.000 1449823832 (null) SelectCurrent: selected server 'Download f6645934 AVAST5 Server' from 'main'
11.12.2015 09:50:32.000 1449823832 (null) scr: Using server: http://f6645934.iavs5x.u.avast.com/iavs5x
11.12.2015 09:50:32.000 1449823832 (null) scr: mirroring 'abp' - nothing to do.
11.12.2015 09:50:32.000 1449823832 (null) scr: Setting product 'ais' files (4 of 657 set)
11.12.2015 09:50:32.000 1449823832 (null) scr: Resetting existing files (reset 4 files, leaving 0 files).
11.12.2015 09:50:32.000 1449823832 (null) Server definition(s) loaded for 'main': 29 (maintenance:0)
11.12.2015 09:50:32.000 1449823832 (null) SelectCurrent: selected server 'Download k0578934 AVAST5 Server' from 'main'
11.12.2015 09:50:32.000 1449823832 (null) scr: Using server: http://k0578934.iavs5x.u.avast.com/iavs5x
11.12.2015 09:50:32.000 1449823832 (null) scr: mirroring 'ais' - nothing to do.
11.12.2015 09:50:32.000 1449823832 (null) scr: Mirroring done.
11.12.2015 09:50:32.000 1449823832 (null) Direct delete of file: C:\Windows\TEMP\_av_mirrI.tm~a03028\onefile
11.12.2015 09:50:32.000 1449823832 (null) scr: Sumarizing...
11.12.2015 09:50:33.000 1449823833 (null) scr: Setting product 'abp' files (652 of 657 set)
11.12.2015 09:50:33.000 1449823833 (null) scr: Setting product 'ais' files (653 of 657 set)
11.12.2015 09:50:33.000 1449823833 (null) Return code: 0x20000001 [Nothing done]
11.12.2015 09:50:33.000 1449823833 (null) Stopped: 11.12.2015, 09:50:33
11.12.2015 10:20:25.000 1449825625 (null) Started: 11.12.2015, 10:20:25
11.12.2015 10:20:25.000 1449825625 (null) Running mirror_w32-0 (0)
11.12.2015 10:20:25.000 1449825625 (null) Operating system: Windows 7 ver 6.1, build 7601, sp 1.0 [Service Pack 1] SERVER
11.12.2015 10:20:25.000 1449825625 (null) Memory: 22% load. Phys:3231976/4193848K free, Page:4194303/4194303K free, Virt:2049400/2097024K free
11.12.2015 10:20:25.000 1449825625 (null) Computer WinName: VMWAVAST
11.12.2015 10:20:25.000 1449825625 (null) Windows Net User: SYSTEM
11.12.2015 10:20:25.000 1449825625 (null) Operation set to INST_OP_MIRROR_MIRROR
11.12.2015 10:20:25.000 1449825625 (null) Using temp: C:\Windows\TEMP\_av_mirrI.tm~a03964 (10039M free)
11.12.2015 10:20:25.000 1449825625 (null) Computer DnsName: VMWAVAST
11.12.2015 10:20:25.000 1449825625 (null) Computer Ip Addr: 192.168.222.17
11.12.2015 10:20:25.000 1449825625 (null) scr: mirror begin...
11.12.2015 10:20:25.000 1449825625 (null) SYNCER: Type: no proxy
11.12.2015 10:20:25.000 1449825625 (null) SYNCER: Auth: no authentication
11.12.2015 10:20:25.000 1449825625 (null) GUID: 42faab2d-92ee-457f-818e-e7419cdf94ed
11.12.2015 10:20:25.000 1449825625 (null) scr: Mirroring...
11.12.2015 10:20:25.000 1449825625 (null) Server definition(s) loaded for 'main': 29 (maintenance:0)
11.12.2015 10:20:25.000 1449825625 (null) SelectCurrent: selected server 'Download x0553502 AVAST5 Server' from 'main'
11.12.2015 10:20:25.000 1449825625 (null) scr: Using server: http://x0553502.iavs5x.u.avast.com/iavs5x
11.12.2015 10:20:25.000 1449825625 (null) HttpGetWinsock(http://x0553502.iavs5x.u.avast.com/iavs5x/servers.def)
11.12.2015 10:20:25.000 1449825625 (null) GetFileWithRetry: servers.def downloaded .
11.12.2015 10:20:25.000 1449825625 (null) servers.def not changed, 1444204600
11.12.2015 10:20:25.000 1449825625 (null) Server definition(s) loaded for 'main': 29 (maintenance:0)
11.12.2015 10:20:25.000 1449825625 (null) SelectCurrent: selected server 'Download x4181316 AVAST5 Server' from 'main'
11.12.2015 10:20:25.000 1449825625 (null) scr: Using server: http://x4181316.iavs5x.u.avast.com/iavs5x
11.12.2015 10:20:25.000 1449825625 (null) HttpGetWinsock(http://x4181316.iavs5x.u.avast.com/iavs5x/jollyroger.vpx)
11.12.2015 10:20:25.000 1449825625 (null) GetFileWithRetry: jollyroger.vpx downloaded .
11.12.2015 10:20:25.000 1449825625 (null) jollyroger.vpx not changed, 1449664957
11.12.2015 10:20:25.000 1449825625 (null) HttpGetWinsock(http://x4181316.iavs5x.u.avast.com/iavs5x/mirror.def)
11.12.2015 10:20:25.000 1449825625 (null) GetFileWithRetry: mirror.def downloaded .
11.12.2015 10:20:25.000 1449825625 (null) mirror.def not changed, 1449669113
11.12.2015 10:20:27.000 1449825627 (null) scr: Setting product 'abp' files (652 of 657 set)
11.12.2015 10:20:30.000 1449825630 (null) scr: Resetting existing files (reset 652 files, leaving 0 files).
11.12.2015 10:20:30.000 1449825630 (null) Server definition(s) loaded for 'main': 29 (maintenance:0)
11.12.2015 10:20:30.000 1449825630 (null) SelectCurrent: selected server 'Download g0512802 AVAST5 Server' from 'main'
11.12.2015 10:20:31.000 1449825631 (null) scr: Using server: http://g0512802.iavs5x.u.avast.com/iavs5x
11.12.2015 10:20:31.000 1449825631 (null) scr: mirroring 'abp' - nothing to do.
11.12.2015 10:20:31.000 1449825631 (null) scr: Setting product 'ais' files (4 of 657 set)
11.12.2015 10:20:31.000 1449825631 (null) scr: Resetting existing files (reset 4 files, leaving 0 files).
11.12.2015 10:20:31.000 1449825631 (null) Server definition(s) loaded for 'main': 29 (maintenance:0)
11.12.2015 10:20:31.000 1449825631 (null) SelectCurrent: selected server 'Download x4181316 AVAST5 Server' from 'main'
11.12.2015 10:20:31.000 1449825631 (null) scr: Using server: http://x4181316.iavs5x.u.avast.com/iavs5x
11.12.2015 10:20:31.000 1449825631 (null) scr: mirroring 'ais' - nothing to do.
11.12.2015 10:20:31.000 1449825631 (null) scr: Mirroring done.
11.12.2015 10:20:31.000 1449825631 (null) Direct delete of file: C:\Windows\TEMP\_av_mirrI.tm~a03964\onefile
11.12.2015 10:20:31.000 1449825631 (null) scr: Sumarizing...
11.12.2015 10:20:32.000 1449825632 (null) scr: Setting product 'abp' files (652 of 657 set)
11.12.2015 10:20:32.000 1449825632 (null) scr: Setting product 'ais' files (653 of 657 set)
11.12.2015 10:20:32.000 1449825632 (null) Return code: 0x20000001 [Nothing done]
11.12.2015 10:20:32.000 1449825632 (null) Stopped: 11.12.2015, 10:20:32
:(
-
...and now the VPS mirror not function the last good is version 9.12.2015 - 151209-0
Yep same here. SOA is reporting it's up to date but the defs are from the 9/12/2015 :-\
-
Is the latest VPS 12/9 or 12/10?
Since 12/11 has not been released as of yet for today.
-
Is the latest VPS 12/9 or 12/10?
The SOA is reporting 151209-0 which is the first release on 12/9.
I've checked a PC running Avast Business Security 2015 and that shows the current defs as 151211-0 i.e 12/11, so I would have expected the EPP defs to be updated at around the same time.
-
First of all, thanks for your patience!
151209-0 really is the latest available virus definition version for Endpoint Protection. We are working with the release engineering to smooth out the virus definition release process, as there were some changes in it after the release. The new virus definition update should be ready soon. We are going to keep you posted on this topic.
-
Ok, thanks for the reply 8)
After all the updating issues I guess I've become a bit nervous when the defs are more than a day old :o
-
As I see, my VDB in Endpoint updated this morning to new. 151211-5, but strange - that update is an yesterday release. Avast for bussiness now have only 1 update of virus base in 1 day?
What with cool words about hundreds updates in a day by cloud?
-
The most XP stations have VPS 151209-0 (8.0.1606)
but last is 151213-3
from log one XP station:
14.12.2015 6:50:30 Function setifaceUpdatePackages() has failed. Return code is 0x00000008, dwRes is 00000008.
:-(
-
Windows XP still have problem
from 75 stations is 55 not updated
"Error:Not enough storage is available to process this command."
:(
-
Is there any news regarding a solution?
-
https://forum.avast.com/index.php?topic=180249.0
-
Since I started this thread, I will add, for the record:
I had only one XP machine on my network.
With the arrival of Endpoint Protection 8.0.1606, when I moved the XP machine into my SOA group that gets program updates, the update was installed automatically and the problem stopped happening on that machine.
I did not have to update the SOA to get this result. I'm still running SOA 1.3.3.35 on a Win 7 Ultimate machine.
I am satisfied that this particular problem, as I reported it, is fixed.
Thanks to avast! staff.