System performs fine after a boot up that is twice as long as normal. I took a trace with windows performance recorder and took a look at it but I am not skilled at reading this. Looks like there might be a code integrity issue with aswAMSI.dll. If anyone has suggestions on analyzing the trace or recording traces and what to record, they are welcome. Image attached showing what I am looking at.
Another image showing a bunch of errors related to the file i mentioned above.
And this warning message about the slow boot process is logged intermittently. I have seen the time get as high as 2 minutes:
Log Name: Application
Source: Microsoft-Windows-Winlogon
Date: 4/5/2020 12:42:15 PM
Event ID: 6006
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: Jim-ASUSPC
Description:
The winlogon notification subscriber took 64 second(s) to handle the notification event (Logon).
Event Xml:
6006
0
3
0
0
0x80000000000000
125209
Application
Jim-ASUSPC
Profiles
64
Logon
00000000
If there is something I can do to fix this issue let me know. Thanks.
BTW this is all happening with version 20.2.2401 (build 20.2.5130.565)
OS version is 1909 build 18363.752
Another intermittent error that is happening:
Log Name: Application
Source: Microsoft-Windows-User Profiles Service
Date: 4/5/2020 11:30:21 AM
Event ID: 1552
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: Jim-ASUSPC
Description:
User hive is loaded by another process (Registry Lock) Process name: C:\Program Files\Avast Software\Avast\AvastSvc.exe, PID: 3588, ProfSvc PID: 1952.
Event Xml:
1552
0
2
0
0
0x8000000000000000
125155
Application
Jim-ASUSPC
C:\Program Files\Avast Software\Avast\AvastSvc.exe
3588
1952
Same issue in Windows 7 ever since the update. It is intermittent. I would say it does it about 2/3rds the time I boot.
It happens after I enter my log in password but before the main page desktop loads. It used to take 10-20 seconds, now it takes over 120 seconds.
Hello Jimbo93, these error messages are (kind of) normal for 3rd part AVs using AMSI dll(s) and they should not be anyhow connected to the slow boot. As for the slow boot, could you please ZIP and upload the logs from performance recorder to our FTP server:
https://support.avast.com/en-us/article/160
And if you have a bit more time, it would be nice to have both logs from boot with and without avast, so we can compare the differences. Thank you very much.
Ok, thanks. I just need a couple days to reproduce some of that/ confirm I can reproduce it, cause I uninstalled avast to give it one last go.
Thank you in advance for you time and help.
Quick info on how I resolved various errors and slow boot problems. Note that this is a 9 year old ASUS laptop that was win7 and I upgraded to win 10 late last year. After the upgrade to win 10 there have been issues like performance counters broken which I believe happened because either driver issues or missing original software. I had repaired the driver and related issues and it seemed like avast was the only thing not working right. But what appears to have happened is I caused a couple issues myself by rebuilding wmi with a poorly designed tool, and also by moving the system partition at one point and not making sure I aligned it ( starting sector wasn’t right ). It was a tip in Sisoft Sandra that the alignment was off that pointed me to that. I aligned it with Mini-Tool Partition wizard, then removed all Volume shadow copies and this seemed to make a big difference. I also had removed some software including Visual Studio and some windows features I wasn’t using to eliminate any Other conflicts. At this point avast 20.3 is working beautifully and I have booted it over 10 times since I installed it. So ask me anything. 
Forgot to mention one other repair I did which could have been at issue. The windows defender platform, I found how to reset it which causes it to reinstall. It’s MpCmdRun.exe -resetplatform , if I remember correctly. The platform updates had failed at one point and I am pretty sure it needed this.
Thank you for the update, I am glad you were able to fix the perf. issue and Avast works fine now.