![]() Avast is aware of this and confirms to fix the issue with June Update. If Avast has all shields disabled in the first place after installation, restart may fix the issue, but that may result in Shields Control to show wrong ‘Enable all shields (1 disabled)’ error. We’ve installed Avast with Minimal Protection Install option and not faced such error (update: damn! the error surfaced after one day, we’ve uninstalled Avast) you can try the same.Įnsuring Windyou’re using with latest cumulative Update and other updates installed also minimizes the issue. If you’ve upgraded from previous version, we request you to uninstall and reinstall the latest version to see it doesn’t trigger the issue. We plan to release hotfix for version 18.4 today, and next week also fix for version 18.3”. ![]() ![]() “Yes the problem is that auto-recovery when service isn’t running doesn’t work on latest Windows 10. Avast UI failing to load issue seems to fall in that category with Windows 10 1803.Ĭoming to the current issue, Avast forum now is flooded with user questions on this topic and Avast software has promised to release a fix soon. Same the case with Avast, in the past, on Windows 10 1607, Avast has caused BSOD and later, the antivirus company fixed the issue. When a major update for Windows 10 releases, software runs on it sometimes breaks, causes issues. Avast’s UI failed to load error on Windows 10 1803
0 Comments
Leave a Reply. |