Avast doesn't lauch at start, and interface is just a white rectangle

system · 2017-05-13T14:58:55.000Z

Hi, I have a W10 64b PC, and Avast 17.4.2294 is acting weirdly since I don’t know when: First I noticed it wouldn’t launch at startup, then after I launch it manually the UI just displays a white rectangle. The notification icon works normally and says my system is protected. I already tried to reinstall it, is it a common issue?

Asyn · 2017-05-13T15:25:34.000Z

Which Avast…? (Free/Pro/IS/Premier)
Other security related software installed…?

system · 2017-05-13T15:38:59.000Z

Avast free, no other active antivirus tool.

Asyn · 2017-05-13T15:43:17.000Z

Download Avast Free Antivirus: https://files.avast.com/iavs9x/avast_free_antivirus_setup_offline.exe
Follow instructions: https://www.avast.com/uninstall-utility (Run this tool for all prior installed Avast versions…!!)
Reinstall Avast with the downloaded installer from point 1.
Reboot.

system · 2017-05-13T19:28:49.000Z

I reinstalled it this way and the UI still shows a white screen. I can still bring up the parameters for updates as usual.

Eddy · 2017-05-13T19:31:46.000Z

Check if the Terminal services are running.

system · 2017-05-13T19:59:28.000Z

apparently it’s not… how is that important?

Eddy · 2017-05-13T20:52:54.000Z

Because avast needs them to run to work.

system · 2017-05-13T21:02:50.000Z

It doesn’t even seem to be installed… am I good for a Windows reinstall?

DavidR · 2017-05-13T21:26:13.000Z

What doesn’t seem to be installed ?

Terminal Services is a windows service not an avast one, but it uses it.
Allows multiple users to be connected interactively to a machine as well as the display of desktops and applications to remote computers. The underpinning of Remote Desktop (including RD for Administrators), Fast User Switching, Remote Assistance, and Terminal Server.

Terminal services isn’t in every OS:
It is in XP and mine is set to Manual and it is running, presumably avast made a call for it and it is running.

I don’t see Terminal Services in services.msc for Windows 7 Starter SP1 32bit or Windows 10 Home 64bit.
However, there is a service DComLaunch in those and DComLaunch is what is being started by The Terminal Services in Win XP.

system · 2017-05-13T22:22:09.000Z

I don’t see a term* service in services.msc, however the plug and play service is running is has the same launch path.

DavidR · 2017-05-13T22:37:20.000Z

As I said Terminal Services isn’t in windows 10 or win 7, it is only in win XP.

Check services.msc in windows 10 and see if the DCOM Server Process Launcher (DComLaunch) service is running. Mine is set to Automatic and is running.

system · 2017-05-13T22:46:26.000Z

Found the french name, and it’s automatic and running too. I’ll update to creator and see if it fixes anything…

system · 2017-05-14T13:59:11.000Z

I had this problem tonight after reinstalling Avast Free, but after a while the normal stuff appeared.

system · 2017-05-14T19:40:44.000Z

I just uninstalled it, I’d rather rely on Windows Defender than risk to forget launching it one day.

Announcements