Active Directory Login Issues Since Upgrade to 17.2.2517

[REDACTED]

Micro-update is being tested. ETA for go-public is 8 to 12 hours. We are in final testing phase. In urgency please contact our support they will provide you with the file and instructions.

Thanks @misak

Can you confirm if micro-updates are still deployed if Automatic Program Updates have been disabled in the cloud console?

[Manley]

misak - what is the new version number we should be looking for?

[PetrP]

Hello,

today we released a micro update for the self defense which should also fix the issue with roaming profiles.

Just give it some time to download or you can force it by a reboot or by executing AvastEmUpdate.exe. But when the update is applied a reboot is needed to take effect.

Thanks

Petr

[REDACTED]

I am currently showing Program Version 17.2.2517 (build 17.2.3419.0).

Is this the new build version that contains the fix?

[PetrP]

I am currently showing Program Version 17.2.2517 (build 17.2.3419.0).

Is this the new build version that contains the fix?

It's not a new program update, just a micro update for current version.

Petr

[Manley]

If version number doesn't change, how do we know if reboot is needed? Will it pop-up a reboot window prompt on each computer?

I am currently showing Program Version 17.2.2517 (build 17.2.3419.0).

Is this the new build version that contains the fix?

It's not a new program update, just a micro update for current version.

Petr

[REDACTED]

Thank you!  Yes, this is exactly why I was asking.  I realize the Program Version will remain the same, but wouldn't the build number change?

If version number doesn't change, how do we know if reboot is needed? Will it pop-up a reboot window prompt on each computer?

I am currently showing Program Version 17.2.2517 (build 17.2.3419.0).

Is this the new build version that contains the fix?

It's not a new program update, just a micro update for current version.

Petr

[REDACTED]

After micro-update and PC restart my avast! Business version is: 17.2.2517 (build 17.2.3419.59)

Thanks for the update!

[REDACTED]

Awesome!  Thanks for the follow up info.

[Manley]

@misak - is there another micro-update released recently? I had a client with a higher number than the .59

[Manley]

Now there is another micro-update that ends in .64. Any ideas on what this stuff is fixing?

[REDACTED]

Today is Monday. All faculty booting computers and getting a BSOD. New client 17.2.2517 has been installed on close to 2000
computers. for my school district. computers getting this all over the District. I have disconnected my 2 bench test computers running Windows 7. Boot into safe mode and removed Avast Business Client 17.2.2517.

Restarted computers 6 times, with no error's. Looks like big bug in version 17.2.2517. Please help how am I going to fix close to 2000 computers.

[REDACTED]

Same here mine are Dell's with the micro update .64

[REDACTED]

I performed a clean install of the latest version which is the .64 on 2 test computers. Restarted 6 times, no BSOD.

[Asyn]

Today is Monday. All faculty booting computers and getting a BSOD. New client 17.2.2517 has been installed on close to 2000
computers. for my school district. computers getting this all over the District. I have disconnected my 2 bench test computers running Windows 7. Boot into safe mode and removed Avast Business Client 17.2.2517.

Restarted computers 6 times, with no error's. Looks like big bug in version 17.2.2517. Please help how am I going to fix close to 2000 computers.

Hi, see: https://forum.avast.com/index.php?topic=199156.msg1379196#msg1379196