Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: malfretup on October 28, 2020, 07:35:28 PM
-
Hello everybody
On two computers, one upgrading from Windows 10 2004 to Windows 10 20H2, and another from Windows 7 to Windows 10 20H2, the update failed
So, reguarding to Microsoft advices, I unistalled avast on both computers... and finally the update went perfect on both computers.
But, when I tried to resinstall Avast on both, at the end of the installation there is message, saying that an error occured and my computer will restart in 1 minute... and at each reboot, at the end of the login session, same message and reboot... The only way to be ok, is to go in safe mode and use avastclear to delete avast...
Can you please find a solution, I want to use Avast and no another Antivirus
I am using the latest offline version of Avast Free... and it was the same issues with Avast Online
Thanks
-
I guess that right now windows 10 and avast have a bit of a conflict on the latest windows 10 update. Well, it still could have been a co incidence but since both of your computers had the same issue I consider that to be unlikely.
Well, microsoft a lot of times says to disable third party antiviruses before updating since there can be a conflict but that still doesn't explain why is there a conflict.
-
I guess that right now windows 10 and avast have a bit of a conflict on the latest windows 10 update. Well, it still could have been a co incidence but since both of your computers had the same issue I consider that to be unlikely.
Well, microsoft a lot of times says to disable third party antiviruses before updating since there can be a conflict but that still doesn't explain why is there a conflict.
Just FYI, Had no issues at all installing 20H2 on 2 Win 10 64Bit OS's
No conflict with Avast on any Windows update and have made no adjustments to my Avast settings\
-
I had no problem on 3 others computers…
That is Strange… very strange
-
I didn't have a problem as well but the thing is why did it happen on both of the computers? That seems strange to me.
-
I think that maybe there is a registry problem on it…
or maybe that all those computers had Windows 10 from a Windows 7 system... that is maybe a clue...
-
I think that maybe there is a registry problem on it…
or maybe that all those computers had Windows 10 from a Windows 7 system... that is maybe a clue...
Was the update something you received via the normal update process or,
did you upgrade on your own?
-
Same problem here. Updating Windows 10 to 20H2 with installed Avast Antivirus Free fails. After deinstallation of Avast updating to 20H2 went through. But after installing Avast, Windows 10 20H2 permanently reboots.
Error message (translated) :
sihost.exe
In this application, the system has determined the overflow of a stack-based buffer. this overflow could allow a malicious user to take control of the application
and subsequentally:
Your pc will automatically restart in a minute.
Windows has to be restarted due to a problem
Luckily it's a VM with a snapshot before installation of Avast.
-
What version# of Avast Check About Avast for the information.
-
The latest one : 20.8.5684.0
-
Hi, I forwarded it to the devs...
-
Thanks :)
-
I didn't get that issue for now but the OP still didn't state if he upgraded on his own or if he got the update via windows update.
-
I just tried to update on my other machine and it worked with no problem.
-
I didn't get that issue for now but the OP still didn't state if he upgraded on his own or if he got the update via windows update.
The strange thing it is sitting there in my Optional updates waiting for me to download it. So it doesn't appear to be an Automatic Update as such, you have to initiate the download first before it will update.
I don't know if that is more to do with my settings on this Windows 10 laptop or not.
-
It's probably your settings. For me there are 2 options to update:
1. If I want to get the update without waiting for microsoft, then I download that tool called windows 10 update assistant and update through that but the best way is just to wait and then the update pops up on the main update screen, and not in the optional updates one, and there's just that download and install button.
-
The latest one : 20.8.5684.0
Follow instructions: https://support.avast.com/article/33/ and post the File-ID and/or name of the Support-File here afterwards.
-
It really seems as though this update has issues. I just went ahead and update and now it won't show in my updates history on windows update, and my build is still 2004, when it was actually looking like it's updating. And if I run the update assistant it says that there is windows 10 2009 new version available, but in settings of windows, it doesn't show anymore, like it has dis appeared.
-
It really seems as though this update has issues. I just went ahead and update and now it won't show in my updates history on windows update, and my build is still 2004, when it was actually looking like it's updating. And if I run the update assistant it says that there is windows 10 2009 new version available, but in settings of windows, it doesn't show anymore, like it has dis appeared.
Obviously it your version is 2004, yhou haven't received the latest version.
(https://d1ka0itfguscri.cloudfront.net/Lh/2020/10/30/14/41/cY6v2psk0D/preview.jpg)
-
See, here's the thing, and I'll explain it.
Today, a new quality update for 2004 showed up in my windows update.
I clicked download and install. Everything went fine, restarted, updated.
But the thing is, even this update doesn't show in my history, like there was no update at all, when actually there was, and I know for a fact this update was 2009 because otherwise it only shows in optional updates but not it was on the main screen of windows update, the area where you can also check for updates.
So I have no idea what's going on here but it is like when I updated the update is no where to be found.
And in the update assistant it shows me that there's a new version available so what the hell is going on here. This update really has issues.
-
I don't know what update 2009 is because the latest update would be the following,
(https://d1ka0itfguscri.cloudfront.net/Lh/2020/10/30/16/48/cY6vDJsply/preview.jpg)
-
My version is: Version 2004 (OS Build 19041.610
But the latest update is 20 h2, or as so called, 2009.
-
My version is: Version 2004 (OS Build 19041.610
But the latest update is 20 h2, or as so called, 2009.
You can't be running 20H2 if your version is 2004.
-
Just for interest, here's what showed up today for my OS's
-
I know but that doesn't explain how the hell is the update now gone and how was it installed then and then dis appeared from the history, i swear it installed just fine.
-
Hi all of you…
I made two new updates from Windows 7 to Windows 10 20H2 and installing avast on it after and it crashes…
I will try a new install of Windows 7 on a VM and after make the update to Windows 10 20H2 and after install avast and see what is happenning
-
Hi all of you…
I made two new updates from Windows 7 to Windows 10 20H2 and installing avast on it after and it crashes…
I will try a new install of Windows 7 on a VM and after make the update to Windows 10 20H2 and after install avast and see what is happenning
More information would be helpful. What other Security software is installed on that computer? What error message did you receive?
I'm on Windows 10 v 20H2 and Avast runs just fine.
-
Hi, I forwarded it to the devs...
Hi Asyn
So I did a fresh install of Windows 7, directly un update to Windows 10 20H2, and once it was finished, installed Avast… and the same problem is still coming up at the end of the installation…
So it seems to be a problem from maybe a registry key in Windows 7, still present in the updated system on Windows 10...
Hope the devs will try as I done and find a solution…
-
Hi, the devs would need some logs...
Follow instructions: https://support.avast.com/article/33/ and post the File-ID and/or name of the Support-File here afterwards.
-
Hi, the devs would need some logs...
Follow instructions: https://support.avast.com/article/33/ and post the File-ID and/or name of the Support-File here afterwards.
I think the devs could create themselve a VM with Windows 7 and then update to Windows 10 20H2 using the Mediacreation tool ! can't they ?
So because I am cool and I have some time to waste… here are two reports ID :
VH3NR (after I uninstalled avast using avast clear from safe mode and reboot the computer)
IM58P (the report has been made from safe mode because the computer is rebooting in loop)
I hope it will help
-
Hi, the devs would need some logs...
Follow instructions: https://support.avast.com/article/33/ and post the File-ID and/or name of the Support-File here afterwards.
I think the devs could create themselve a VM with Windows 7 and then update to Windows 10 20H2 using the Mediacreation tool ! can't they ?
<snip>
Whilst they probably could do that yes, but what they can't do is exactly replicate your system.
Hopefully your logs will help them with the problem.
-
Hi, the devs would need some logs...
Follow instructions: https://support.avast.com/article/33/ and post the File-ID and/or name of the Support-File here afterwards.
I think the devs could create themselve a VM with Windows 7 and then update to Windows 10 20H2 using the Mediacreation tool ! can't they ?
<snip>
Whilst they probably could do that yes, but what they can't do is exactly replicate your system.
Hopefully your logs will help them with the problem.
Because I had the problem on many computers updated from Windows 7 directly to Windows 10 20H2 or from Windows 7 to Windows 8, 8.1 10 and go to the latest and have the same problem, I supposed that the problem was Windows 7
So I made a Windows 7 VirtualBox VM, with Nothing else except Windows, directly make un update with the MediaCreationTool, and so go to Windows 10 20H2 and after, install avast… So with all those explanation, they can, for sure, replicate exactly the system :)
-
So because I am cool and I have some time to waste… here are two reports ID :
VH3NR (after I uninstalled avast using avast clear from safe mode and reboot the computer)
IM58P (the report has been made from safe mode because the computer is rebooting in loop)
I hope it will help
Thanks, the devs are informed.
-
Hi, the devs think it might be related to HVCI. Do you have HVCI/Core isolation/Memory integrity enabled..?
-
Hi, the devs think it might be related to HVCI. Do you have HVCI/Core isolation/Memory integrity enabled..?
Absolutely not
As I said, this problem appeared only on computers who were first on Windows 7 and upgraded from Windows 7 to Windows 10 20H2 not reguarding if there was other Windows between Windows 7 to Windows 10
-
OK, the devs are trying to reproduce it...
-
OK, the devs are trying to reproduce it...
They will easyly I think ;)
-
I can confirm the problem reported by malfretup:
My laptop was updated from Windows 7 to Windows 10 a year ago. The update from Version 2004 to 20H2 via MediaCreationTool failed when migrating applications. After uninstalling Avast Free (20.8.2432) with avastclear the update of Windows 10 was successful, but reinstalling Avast resulted in the described boot-loop.
Manually installing KB4562830 on the other hand worked fine. So the cause are most probably remnants of Avast in the Registry/WinSxS from its installation under Windows 7.
Albeit only few users would be affected this time, it should be fixed before the next Feature Update requires an inplace update.
-
I had absolutely no issues updating from 2004 (fully updated) to 20H2 using Windows Update, that was very quick and painless. I guess you are using the media creation tool because 20H2 was not yet shown as available for your machine.
-
OK, the devs are trying to reproduce it...
They will easyly I think ;)
Dev-Info: I can confirm we've reproduced the issue in VirtualBox and we're trying to figure out, what is the cause (and whether it might be caused by our AV or not). So far the issue only manifests on systems upgraded from Win7, not on clean installations.
-
Dev-Info: I can confirm we've probably found the cause - there seems to be an issue in SAM (security account manager) database (corruption), that manifests when lsass.exe (https://en.wikipedia.org/wiki/Local_Security_Authority_Subsystem_Service) tries to access it. The issue can be triggered not only by Avast installation, but also plainly by opening lusrmgr.msc (local users and groups manager), and clicking Groups directory. This tool also accesses the SAM via LRPC call to lsass.exe Warning: If the issue gets triggered, it may not be possible to log into the system again and full recovery/re-installation might be needed.
This issue is therefore not caused by Avast, we just trigger it during installation. We will do our best to contact Microsoft and support them with artifacts from our investigation (we should be able to provide full memory dump) to resolve the issue, but we sadly cannot promise anything going from there.
-
Dev-Info: I can confirm we've probably found the cause - there seems to be an issue in SAM (security account manager) database (corruption), that manifests when lsass.exe (https://en.wikipedia.org/wiki/Local_Security_Authority_Subsystem_Service) tries to access it. The issue can be triggered not only by Avast installation, but also plainly by opening lusrmgr.msc (local users and groups manager), and clicking Groups directory. This tool also accesses the SAM via LRPC call to lsass.exe Warning: If the issue gets triggered, it may not be possible to log into the system again and full recovery/re-installation might be needed.
This issue is therefore not caused by Avast, we just trigger it during installation. We will do our best to contact Microsoft and support them with artifacts from our investigation (we should be able to provide full memory dump) to resolve the issue, but we sadly cannot promise anything going from there.
OK, it's great that the Devs found the bug using all the clues I provided :) and I was quite sure that the problem was one from Microsoft... I hope they will correct it quickly, so I could install back again avast on my upgraded computers :)
Actually, Avira is installed... and I prefer Avast lol :)
I keep an eye on this subject
-
Info from Microsoft: https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-20h2#1514msgdesc
-
Info from Microsoft: https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-20h2#1514msgdesc
Great news... Now we have to wait a little time before having an update :)
-
For me it seems that Windows 2020-11 Cumulative Update has solved the problem.
I was able to update a VM installation that has failed before on both ways:
- Installing the 2020-11 updates on Windows 10 Version 2004 and updating to Windows 20H2 with installed Avast Free Antivirus
- Removing Avast and updating to Windows 20H2, then installing the 2020-11 Cumulative Update and reinistalling Avast afterwards
Though I wouldn't go any risk and won't make the update without a reliable backup/restore path
-
I will try on one of my computers right now...
It worked perfectly... that is good news :) Avast is back with the november update :)
Thanks to all, thanks to the devs :)
-
I simply disabled the Avast shields till the next restart and had no problems updating 4 systems.
-
I will try on one of my computers right now...
It worked perfectly... that is good news :) Avast is back with the november update :)
Thanks to all, thanks to the devs :)
You're welcome and thanks for the feedback.
-
I will try on one of my computers right now...
It worked perfectly... that is good news :) Avast is back with the november update :)
Thanks to all, thanks to the devs :)
You're welcome and thanks for the feedback.
With many computers having the sames issues, it was important for me to share about it ;)
-
For me it seems that Windows 2020-11 Cumulative Update has solved the problem.
I was able to update a VM installation that has failed before on both ways:
- Installing the 2020-11 updates on Windows 10 Version 2004 and updating to Windows 20H2 with installed Avast Free Antivirus
- Removing Avast and updating to Windows 20H2, then installing the 2020-11 Cumulative Update and reinistalling Avast afterwards
Though I wouldn't go any risk and won't make the update without a reliable backup/restore path
This solution was perfect for me. I had to reinstall windows 2 times. After upgrading to windows version 20H2 I tried to install avast and it gave a fatal error and windows did not recover.
After seeing this comment I did the procedure of installing windows 20H2, installing "Windows 2020-11 Cumulative Update" and then avast. Worked perfectly. There should be a warning on the avast website or something regarding the need for this update.
Thanks for sharing this info.
-
I simply disabled the Avast shields till the next restart and had no problems updating 4 systems.
I didn't even disable the shields and the Windows 10 20H2 update went without a hitch.
Now if Avast was working before Windows 10 20H2 update and there was no change in Avast I don't know how Avast can be responsible. Or I would imaging there would be many, many more such topics in the forums.
-
I simply disabled the Avast shields till the next restart and had no problems updating 4 systems.
I didn't even disable the shields and the Windows 10 20H2 update went without a hitch.
Now if Avast was working before Windows 10 20H2 update and there was no change in Avast I don't know how Avast can be responsible. Or I would imaging there would be many, many more such topics in the forums.
I personally have never disabled Avast for any Windows Updates (including Feature Updates) and have not experienced any issues. ???
-
I simply disabled the Avast shields till the next restart and had no problems updating 4 systems.
I didn't even disable the shields and the Windows 10 20H2 update went without a hitch.
Now if Avast was working before Windows 10 20H2 update and there was no change in Avast I don't know how Avast can be responsible. Or I would imaging there would be many, many more such topics in the forums.
I personally have never disabled Avast for any Windows Updates (including Feature Updates) and have not experienced any issues. ???
It may not cause a problem but it certainly effects the speed of the update (upgrade)
-
I simply disabled the Avast shields till the next restart and had no problems updating 4 systems.
I didn't even disable the shields and the Windows 10 20H2 update went without a hitch.
Now if Avast was working before Windows 10 20H2 update and there was no change in Avast I don't know how Avast can be responsible. Or I would imaging there would be many, many more such topics in the forums.
I personally have never disabled Avast for any Windows Updates (including Feature Updates) and have not experienced any issues. ???
It may not cause a problem but it certainly effects the speed of the update (upgrade)
The problem was only on computers wich has been updated to Windows 10 from Windows 7 !!!
-
I simply disabled the Avast shields till the next restart and had no problems updating 4 systems.
I didn't even disable the shields and the Windows 10 20H2 update went without a hitch.
Now if Avast was working before Windows 10 20H2 update and there was no change in Avast I don't know how Avast can be responsible. Or I would imaging there would be many, many more such topics in the forums.
I personally have never disabled Avast for any Windows Updates (including Feature Updates) and have not experienced any issues. ???
Me neither.
Update issues are related to updating from ( much ) older Windows versions, it seems.
Greetz, Red.