Avast users using latest version 18.4.2388 and 18.3.2333 on Windows 10 1803 are getting ‘UI failed to load and AV service is not responding‘ error. If visiting Windows services console and setting ‘Remote Desktop Services’ service startup type to automatic and status to running, and repairing or reinstalling Avast hasn’t helped, then wait for the hot fix to be released by Avast or follow the below instructions to see the issue gets resolved on your end.
Update: Avast has already delivered the fix to 18.2 and 18.3 versions via microupdate. The company as promised, pushed the hotfix to Avast 18.4.2338 build as well, you need to restart to apply the fix.
To confirm fix is applied to your Avast version, navigate to below key in registry and look for the no 356=?
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\AVAST Software\Avast\micropupdates
Avast’s UI failed to load error on Windows 10 1803
When a major update for Windows 10 releases, software runs on it sometimes breaks, causes issues. Same the case with Avast, in the past, on Windows 10 1607, Avast has caused BSOD and later, the antivirus company fixed the issue. Avast UI failing to load issue seems to fall in that category with Windows 10 1803.
Coming 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.
“Yes the problem is that auto-recovery when service isn’t running doesn’t work on latest Windows 10. We plan to release hotfix for version 18.4 today, and next week also fix for version 18.3”.
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’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.
Ensuring Windows 10 1803 you’re using with latest cumulative Update and other updates installed also minimizes the issue.
Other issues with Avast 18.4
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. Avast is aware of this and confirms to fix the issue with June Update.
Selecting Registration information right click menu item of Avast tray icon opens the Avast interface, it’s a bug, no answer from Avast on this.
Uh no, they haven’t. Between May 16 and May 20, 2018, I upgraded five Windows 10 (1803) builds from Avast 2333 to 2338 and every one of them began displaying the “GUI failed …” error message within a day or so. The button to restart had no effect; computer restart had no effect.
The only way I could get around this was to uninstall 2338 and reinstall 2333.
Upon reinstalling 2333, I had to quickly select “manual update” for the program. On one computer, even doing that (confirmed) Avast upgraded 2333 to 2338 anyway. On that computer I’m now running built-in Windows Defender until such time as this problem has really been fixed, but I’m seriously considering abandoning Avast because of this. I’ve been an Avast user since version 4, but enough is enough. There are equally competent AV programs out there besides Avast.
No problem though, third-party antiviruses really causing lot of problems. Recently Windows 10 upgrade to 1803 with Avast installed caused problems to some users. Better to stay with Windows Defender, you can often perform scans manually with Malwarebytes and also run adwcleaner. That will be enough.
It is not a good idea to recommend Windows Defender. It has regularly failed certification as an anti virus and no, it will not be enough if you want decent anti virus performance. Secondly, it isn’t third party software causing a problem with Windows 10 but the other way around.