Author Topic: Installer partial yet fatal failure breaking functionality of Avast! [2262]  (Read 6212 times)

0 Members and 1 Guest are viewing this topic.

Offline Dwarden

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1789
  • Ideas, that's ocean without borders!
    • Bohemia Interactive
INSTALLER and post-install revalidation of deployed files is totally broken
it updated all the key components like drivers and such
and failed to update 90% of the binaries and librarires except the most used
so it looked like updated version but in reality was broken like hell
all because the installer just copied the *.tmp files into e.g. C:\Program Files\AVAST Software\Avast\ and subfolders
but actually failed to overwrite the existing files and did nothing else (e.g. warn it failed)
so end-user gets "success" info and has no idea his AV is totally messed and broken en random

Quote
ok I can clearly see the Avast! update from 2261 to 2262 failed partially

where
"Avast! System drivers" were updated properly

yet
"C:\Program Files\AVAST Software\Avast\*.*" files failed to be updated

I see tons of A*.tmp files which are new and actually are newer libraries inside

so serious flaw on the updater part (two+ restarts since btw.)

it seems like the installer/updater is missing 'final' part where it scans hashes of all Avast! libraries and executables

don't you have some binary which does this
to generate log with list/updates all missing/obsolete libraries / components ?


so, after tracking and replacing some hundred files the Avast ! updater/installer failed to rename/update

I must say that

1. avast! antivirus and other projects naming convention for filenames is terrible

sometime it's ash*
sometime it's aa*
sometime it's as*
sometime it's asw*
sometime it's avast*
sometime it's something .exe or .dll

2. terrific rules for 'Original FileName' description field
A. often not being the final name used
B. even funnier formats like this one or none
"VBoxRT.dll VBoxRT.dll VBoxRT.dll"

3. I really can't understood why there is no binary to check integrity of Avast!'s files

it will search C:\Program Files\AVAST Software\Avast\
same goes for \Common Files\Av\* w/e
then list all missing or corrupt / obsolete files (not matching latest version)
because it's simple matter of hash list

so one could easily run "AvastIntegrityCheck.exe"
it would toss out "All files are correct!" or "Problem detected, please see log 'AvastIntegrityCheck.log' for details !"

puzzling ...


« Last Edit: April 28, 2016, 02:24:15 PM by Dwarden »
https://twitter.com/FoltynD , Tech. Community, Online Services & Distribution manager of Bohemia Interactive

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 70585
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
I may mention it again, there's no beta ATM.
Build 2262 is a final release meanwhile...
Win 8.1 [x64] - Avast PremSec 21.5.6346.B5i [UI.645] - EEK - Firefox ESR 78.11 [NS/uBO/PB] - TB 78.11
Avast-Tools: Secure Browser 91.0 - Cleanup 21.1 - SecureLine 5.12 - Driver Updater 21.1 - CCleaner 5.81
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Offline Dwarden

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1789
  • Ideas, that's ocean without borders!
    • Bohemia Interactive
I may mention it again, there's no beta ATM.
Build 2262 is a final release meanwhile...

in that case it's even more disaster ;)
cause this 'stable' update totally broken the avast! on my system

some colleagues already uninstalled Avast! at home PC due to this (similar/same problems (mess after restart))
https://twitter.com/FoltynD , Tech. Community, Online Services & Distribution manager of Bohemia Interactive

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 70585
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Well, I can only speak for my systems.
Everything up and running here. :)
Win 8.1 [x64] - Avast PremSec 21.5.6346.B5i [UI.645] - EEK - Firefox ESR 78.11 [NS/uBO/PB] - TB 78.11
Avast-Tools: Secure Browser 91.0 - Cleanup 21.1 - SecureLine 5.12 - Driver Updater 21.1 - CCleaner 5.81
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 85075
  • No support PMs thanks
Well, I can only speak for my systems.
Everything up and running here. :)

I have left this system on the regular release version (I got tired with the permanent Beta branding on the UI)  and as yet I haven't been offered 11.2.2262 or whatever mixed up build number that is going to end up with.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 21.4.2464 (build 21.4.6266.561) UI 1.0.639/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline Dwarden

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1789
  • Ideas, that's ocean without borders!
    • Bohemia Interactive
so I went to https://forum.avast.com/index.php?topic=185928.msg1309651#msg1309651

and downloaded offline full installer (200+MB)

guess what, SAME result and same broken install ...

seriously HOW this can happen on stable public release ?

https://twitter.com/FoltynD , Tech. Community, Online Services & Distribution manager of Bohemia Interactive

Offline Avosec-UK

  • Avosec Technical Support
  • Avast Reseller
  • Sr. Member
  • *
  • Posts: 296
    • Avosec
The behaviour you describe happens  when a reboot is needed, after reboot the files should be replaced.

Do you know if the user was prompted with a Reboot message? The Setup.log file should be able to tell you that.

Offline Dwarden

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1789
  • Ideas, that's ocean without borders!
    • Bohemia Interactive
The behaviour you describe happens  when a reboot is needed, after reboot the files should be replaced.

Do you know if the user was prompted with a Reboot message? The Setup.log file should be able to tell you that.

when I was updating to 2262 avast asked me to reboot, I did
after reboot, avast asked me AGAIN to rebot, I did

then it was broken

same goes after trying to use offline 2262 installer

and I got similar reports after 2261 and 2262 from colleagues , partners and our customers
so w/e is happening it seems to be less than rare
https://twitter.com/FoltynD , Tech. Community, Online Services & Distribution manager of Bohemia Interactive

Offline Avosec-UK

  • Avosec Technical Support
  • Avast Reseller
  • Sr. Member
  • *
  • Posts: 296
    • Avosec
Can you copy the Setup.log and Update.log files from "C:\ProgramData\AVAST Software\Persistent Data\Avast\Logs", strip any private information and share them with us?


Offline Dwarden

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1789
  • Ideas, that's ocean without borders!
    • Bohemia Interactive
nvm, files found was in the other log folder ...
« Last Edit: April 28, 2016, 04:44:20 PM by Dwarden »
https://twitter.com/FoltynD , Tech. Community, Online Services & Distribution manager of Bohemia Interactive

Offline Dwarden

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1789
  • Ideas, that's ocean without borders!
    • Bohemia Interactive
logs sent to Petr.Chytil ... hopefully something of use there ...

also repeated retry with offline installer + another round of restarts finally fixed it !

so now the question is, what went wrong cause I feel sorry for avg end-user with such problem
https://twitter.com/FoltynD , Tech. Community, Online Services & Distribution manager of Bohemia Interactive

Offline essexboy

  • Malware removal instructor
  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 40627
  • Dragons by Sasha
    • Malware fixes
I have installed/reinstalled this version several times now with no problem at all..  I am using windows 10 build 14332

Offline drake127

  • Avast team
  • Sr. Member
  • *
  • Posts: 324
Hey,

while that's certainly valid point about integrity check, it's basically what Avast Repair does (is supposed to do). Unfortunately, in your case it seems that our installer/repair is unable to schedule those temporary files to be moved to their correct place. And that's rather odd and I would be glad to find out why. Can you check you Avast log files and/or PendingFileRenameOperations key before and after reboot? There must be something that is preventing us to write there.

Offline Dwarden

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1789
  • Ideas, that's ocean without borders!
    • Bohemia Interactive
well it's updated already ...

since I faced just some new BSOD (because of Avast! again (rofl)) {dumps for sale !!! ;) }

2262 still has the dreaded (already reported) Stuck threads bug https://forum.avast.com/index.php?topic=183875.0

https://twitter.com/FoltynD , Tech. Community, Online Services & Distribution manager of Bohemia Interactive

Offline drake127

  • Avast team
  • Sr. Member
  • *
  • Posts: 324