Hi. Upgraded Windows 10 build tonight. Significant problems with Avast Free. The service wouldn’t load or stop easily. Tried uninstalling and reinstalling a couple of times. Caused major sluggishness when installed.
Install wouldn’t seem to complete - and the Avast installer and the remediation never seemed to finish their jobs.
Avast is working perfectly for me in that build. In fact, it is working so well that it started blocking my entire internet connection to the outside world! It seems the change in how Windows 10 handles services on systems with a certain amount of RAM could be behind this monstrosity, although I’m not qualified enough to say for sure.
I have had major problems with Avast on build 14942. It broke Windows update, neither Edge, IE11 or firefox would load up sites properly. Any sites, such as YouTube, would not play videos as they simply failed to load. Many sites would just not load at all or would load once and then never again. Could not login to Gmail in FF at all, as it hung at the loading screen. I even had problems extracting files from ZIP archvies in Windows explorer. I tried doing an in place upgrade as well a clean install from an ISO to a formatted SSD and all seemed well up until I re-installed Avast on the newly built freshly formatted machine and all the same problems came straight back. I have now reverted back to a build 14936 from a previous system image backup and temporarily moved to the insider Slow ring. I have nver had to do that before.
Maybe due to weekend period, it would be good to be a little patient until Monday.
Until there, maybe logs and technical information about the errors would be useful.
Replying to confirm.
Symptoms experienced: System 95% unresponsive, Solid 38-40% Avast Service CPU always. Eventual system lock - mouse moves but cannot open anything - no apps or right-clicks. No internet access at all.
Event sequence:
Windows Update completed update to 14942 overnight. Logging in fine. System extremely unresponsive - took minutes to load Task Manager which showed ‘Avast Service’ at a constant 38-40% solid. Managed to load Avast - nothing appeared running, no updates or auto-scans. All features of Avast uninstalled - strictily anti-virus file/web shield and Network security - other features uninstalled (so at least it wasn’t an advanced feature doing this). Opened Avast, attempted ‘Reinstall’ which was needed long ago on Windows - seemed to cycle through reinstalling with progress bar - no change.
Rebooted… System now totally unresponsive. Unable to open anything, systray icons not loading. Avast still at 38%. Unable to load Programs and Features to uninstall. Ctrl-Alt-Del unresponsive - unable to reboot safely - hard reset. System was too unresponsive to consider reinstalling and based on past problems - (where Avast reinstall and a reboot had worked), researched this and decided to uninstall and wait.
Next boot quickly launched and uninstalled Avast successfully. shortly after - locked again. Hard reset - system back to normal functionality after uninstall. Trying another free AV while I await a solution - don’t like it, look forward to the next build of Avast or Windows - whoever finds and fixes it first…
@mnswiftone,
Why didn’t you simply go back to the previous build ??? It is one of the options.
I’m back on build 14936 and have changed my Insider update preference to slow.
Yes - but since Microsoft is Microsoft it is generally incumbent on the 3rd party software providers to solve the problem created by a change in the OS. The change may be faulty work at Microsoft or it may be due to a purposeful planned change to how the operating system works.
Since the vendor don’t even seem interested in acknowlging the problem, which is also present in build 14946 by the way, let alone fixing it, I am off to find another one now. Sorry but a bit of common courtesy would not have hone amiss. Apapretly it is too much to ask.
http://screencast-o-matic.com/screenshots/u/Lh/1476558809500-35483.png
No problem with this build.
There is a problem with the next build. I’ve changed over to slow updates instead of fast.
Hopefully that gives Microsoft a chance to fix their problem when something other that Defender is used to
protect your computer.