Author Topic: OCT 2016 - New ENdpoint Client release 10/27/2016  (Read 7664 times)

0 Members and 1 Guest are viewing this topic.

Offline Jeff.S

  • Moderator
  • Jr. Member
  • *
  • Posts: 77
OCT 2016 - New ENdpoint Client release 10/27/2016
« on: October 27, 2016, 04:56:12 PM »
Hi Guys,

There was a new release to the Endpoint clients today, Find the info below.
You can push a program update task or manually update the clients on the local devices, maintenance>update
This update does require a reboot.


Released 27 Oct 2016
Endpoint Protection (all EP/EPP/EPS/EPSP) version 8.0.1609


Changelog:
New logo in Endpoint Protection   
Fixed BSOD on latest Skylake CPU / Windows RS1


Thanks!
« Last Edit: October 27, 2016, 05:11:10 PM by Jeff.S »

Offline IT-KAV

  • Newbie
  • *
  • Posts: 17
Re: OCT 2016 - New ENdpoint Client release 10/27/2016
« Reply #1 on: October 31, 2016, 02:33:11 PM »
In version 8.0.1606 we had this: v 8.0.1606 and Security center error https://forum.avast.com/index.php?topic=180431.msg1276414#msg1276414

After update to this version, we have this (see attachment).
Defender is turned off by group policy and Avast don't registered itself in system again.
Is this some kind of sick joke that you are repeatedly running in your releases? We didn't get rid of your 8.0.1606 error comletely and it is here again...

Offline Bassmaster

  • Jr. Member
  • **
  • Posts: 75
Re: OCT 2016 - New ENdpoint Client release 10/27/2016
« Reply #2 on: October 31, 2016, 05:35:47 PM »
Is this update only for the client side or does the Enterprise Console have an update as well?

Offline Jürg2

  • Newbie
  • *
  • Posts: 4
Re: OCT 2016 - New ENdpoint Client release 10/27/2016
« Reply #3 on: November 02, 2016, 02:09:50 AM »
The same problem we had and discussed with 8.0.1606 update and I observe it with 8.0.1609 now again (not observed with 8.0.1607 and 8.0.1608).
After the installation of 8.0.1609 the maintenance centers of all 5 Windows 7 pro 64 bit computers show the same warning: No virus- and no spyware protection available and recommend to activate Window Defender - although Avast EPS seems to work properly.
Last time (8.0.1606) uninstalling and new installing Avast EPS on all 5 client machines did solve this particular problem only.
I don't intend to do the same again because it was really time consuming.
Therefore I kindly ask Avast to serve us a patch-file to eliminate this error.
« Last Edit: November 02, 2016, 02:11:58 AM by Jürg2 »

Offline K.J.

  • Newbie
  • *
  • Posts: 5
Re: OCT 2016 - New ENdpoint Client release 10/27/2016
« Reply #4 on: November 04, 2016, 02:41:50 PM »
Same here, just updated several Win7 x64 machines and got the same "no antivirus detected" on each and ever one of them so far... Tried "modifying" installation hoping it fixes itself, tried a complete repair installation too, neither helped. Also tried this, it was consistent but did the /salvage too, did not help either. And I'm not gonna uninstall and reinstall the whole thing on every machine (and maybe it won't work either). So fix it ASAP.

Offline Avosec-UK

  • Avosec Technical Support
  • Avast reseller
  • Sr. Member
  • *
  • Posts: 289
    • Avosec
Re: OCT 2016 - New ENdpoint Client release 10/27/2016
« Reply #5 on: November 04, 2016, 05:23:03 PM »
Here is a workaround for AEA Managed Endpoints:

1. Open Avast Enterprise Administration.
2. Right-click on the "Computer catalog" folder and select "Properties"
3. Navigate to "Policies: avast! Antivirus" > "Custom Ini Settings"
4. Add the following INI entry:
Code: [Select]
[AAVM]
WscRegistered_v6=0
5. Save the settings.
6. Wait couple of reboots
7. Remove the "Custom Ini" setting.

Offline studio_two

  • Full Member
  • ***
  • Posts: 109
    • Practical SBS
Re: OCT 2016 - New ENdpoint Client release 10/27/2016
« Reply #6 on: November 10, 2016, 10:45:16 AM »
Do you have a workaround for those of using SOA Console?

As noted above, this was an issue within 8.0.1606.

Kind Regards, Stephen

Update: As an experiment, I have manually edited "C:\ProgramData\AVAST Software\Avast\avast5.ini" on a couple of workstations (setting "wscregistered_v6=0"), and this seems to supress the error. It is quicker than a manual re-install, but still requires me to visit each client.
« Last Edit: November 10, 2016, 12:21:03 PM by studio_two »

Offline rami.mhk

  • Newbie
  • *
  • Posts: 1
Re: OCT 2016 - New ENdpoint Client release 10/27/2016
« Reply #7 on: November 29, 2016, 10:07:29 AM »
Same problem for me I tried all cmd commands but not solved???

Offline ap382

  • Newbie
  • *
  • Posts: 4
Re: OCT 2016 - New ENdpoint Client release 10/27/2016
« Reply #8 on: March 19, 2017, 10:22:19 PM »
No one answers since November 2016 ?!!!!  Is this product dead or alive???

Offline systemsadminAS

  • Newbie
  • *
  • Posts: 8
Re: OCT 2016 - New ENdpoint Client release 10/27/2016
« Reply #9 on: July 21, 2017, 02:54:02 PM »
We've had mixed results with build 1609 across the build iterations of Windows 10 since RTM, but generally the clients seem OK since the anniversary update.  I have been running it on Windows Server 2012 R2 Hyper-V VMs as well as on the Hypervisor, but on a box that we've recently been upgrading (both Hypervisor and VMs) to Server 2016, while the VMs appear to be ok, the system seems to crash if a scan is run on the Hypervisor - I'm guessing I need to specifically exclude more than just the .VHD VM hard disk files (there seems to be no option in SOA / build 1609 of the client to address virtual machines currently).  Any guidance on that?