Avast WEBforum

Business Products => Avast Business => Topic started by: Tom610 on March 30, 2023, 09:34:14 AM

Title: bug: planed patch installation is executed 2h later
Post by: Tom610 on March 30, 2023, 09:34:14 AM
Anyone else that has this problem? It must have come with one of the last Hub updates.

We use mainly global policies, set to patch installation at 12.00 o clock and they will be executed/planed for 14.00...  ???
Title: Re: bug: planed patch installation is executed 2h later
Post by: Infratech Solutions on March 30, 2023, 11:03:59 AM
Yes, we have a similar problem.

We have the policy to scan for new patches everday at 10:00 and install patches inmediattely, but patches are configurated to be installed at 11:00 of next day.

AVAST says: "please note that devices will show Scheduled status of patches before the installation, even if the policy is configured to install the patches immediately, this is as per design. We will investigate internally if this can be optimized in any way."  :o
Title: Re: bug: planed patch installation is executed 2h later
Post by: Tom610 on March 31, 2023, 04:53:27 PM
I guess what support meant is that when patch installation is skipped and executed manually the hub will then change installation time to this: as soon as the device is available...
But this is not what I'm talking about.

Scheduled patch installation has always been reflected the way it is configured within the policies. I see no logical reason for showing a diffrent time as configured within the policies...
Title: Re: bug: planed patch installation is executed 2h later
Post by: Tom610 on April 18, 2023, 10:57:20 AM
Update: Case is created, still no current reply on this. I requested an update.

So far it could also be the case that this is just a display error... I wasn't able to confirm for sure....
Title: Re: bug: planed patch installation is executed 2h later
Post by: Tom610 on April 21, 2023, 09:28:40 AM
Update on this: Today I figured out, that this 2h was reported from my side to Avast support on feburary 28th. In this case the 2h also have effect on antivirus report and antivirus detections...

Where the Antivirus report says the detection occured at 8.39 the hub GUI of the related client says it was detected at 10.39.

It is obvious that both problems have the same cause...