Windows 7 x64 excessively slow to startup and shutdown with Avast free 21.4.2464

Avast free 21.4.2464 works fine with Windows 8.1 and 10 but I have needed to revert to Avast 21.3.2459 for Windows 7. Where can I find the procedure to pass relevant information to Avast? I am happy to remain with 21.3.2459 and will attempt to successfully update it to Avast 21.5 when it becomes available.

I have a hunch that a deadlock condition resulting from the use of Avast 21.4 exists in my Windows 7 x64 system. It certainly has not occurred with versions of Avast prior to 21.4 which I was using in combination with Windows 7 for a considerable time before 21 May 2021.

There IS an issue in Avast free 21.4 but if Avast isn’t sufficiently interested to check it out then that’s fine with me. I maintain an archive of at least the previous ten subdot release offline installers so am ready to row back if necessary. I just want to know how to feedback data to the devs.

Avast 21.3 is, as far as I am concerned, as valuable as 21.4. I diligently update at each new subdot release so that I can do my due diligence as a beta tester (the Free version is a beta, isn’t it?).

  1. Enable debug logging (Menu > Settings > General > Troubleshooting > Enable debug logging) and reproduce the issue.
  2. Follow instructions: https://support.avast.com/article/33/ and post the File-ID or name of the Support-File here afterwards.

I have uninstalled OSArmor 1.4.3 from the problem Windows 7 x64 system and the problem is not now apparent. There is no longer a problem with Avast 21.4. There was no problem between OSArmor and Avast 21.3 even though OSArmor’s settings were much more restrictive than when using its default settings.

In brief, my Windows 7 x64 system is presently running Avast free 21.4 but not now running OSARmor 1.4.3 and it is shutting down and starting up without any delays. I will not be reinstalling OSArmor.

It seems clear to me that Avast 21.4 is susceptible to interference from OSArmor 1.4.3 whereas Avast 21.3 and previous versions are not.

If you still wish me to supply debug information, I will reinstall OSArmor and go through the debug data gathering and reporting procedure as previously requested.

Thanks for the feedback, probably no need to dig deeper.

OSArmor, at least with version 1.4.3 or earlier, seems to pose a significant disruption risk. I have had a few experiences where uninstallation of OSArmor eliminates problems. I have no experience with the more recent paid-for versions of OSArmor. I had thought that because Windows 7 was receiving updates that it wuld be immune from OSArmor. Avast 21.4 showed otherwise. Avast goes deep under the skin of an OS and so becomes as susceptible to disruption by OSArmor as the OS.

I still employ OSArmor 1.4.3 on Windows XP but OSArmor post-dates all the software running on my incarnation of that OS.