Sensitive Data Shield Button Language is wrong

Philip128 · 2017-09-05T08:03:38.000Z

New Version Privacy Feature 17.6.2310 build 17.6.3625.0
The buttons are now in the wrong language for me . Instead of English I get
QUET NGAY

Eddy · 2017-09-05T08:07:44.000Z

Please post a screenshot

Philip128 · 2017-09-05T08:24:45.000Z

Now thats where the fun might also start. The machine has been at 98% for an hour now. I have a screen shot from one of my other machines. Have also discovered that if you stop the process on 5 machines all windows 10 so far listing the apps to be protected doesn’t seem to work. I sits there 30 mins or so on Loading with nothing happening

Philip128 · 2017-09-05T08:31:42.000Z

Once I am out there is another screen

Asyn · 2017-09-05T08:39:33.000Z

Repair Avast:

Control Panel → Add/Remove programs → Avast
Click on ‘Repair’.
Follow instructions.
Reboot.

Philip128 · 2017-09-05T10:40:40.000Z

No that didn’t work. All the other buttons are in English except the buttons for the new Sensitive Data Shield which are in this other language.

So repairing failed. So did removal and re-installation.

QUET NGAY is still there in the Sensitive Data Shield Menu on the button - the other button see screenshot is in English

Its probably not going to matter much. since this app finds sensitive files - some of which are good and some are not sensitive and others which are are not included and there is no apparent way of adding or removing from the list - just looking at what Avast selects.

Asyn · 2017-09-05T10:48:35.000Z

Hi, as I use the German version, I can’t further comment on it.

bob3160 · 2017-09-05T17:00:27.000Z

https://support.avast.com/support/tickets/new?form=3

PetefromAvast · 2017-09-05T19:33:31.000Z

Do you have any alternate languages installed, such as Vietnamese? (which is what the Scan Now button appears to be appearing in) This has been reported to the developers also, thank you for the report.

Alikhan · 2017-09-05T21:10:04.000Z

Mines is fine here.

Rednose · 2017-09-06T08:09:39.000Z

This is a known issue, and already fixed in an internal build.

Greetz, Red.

Announcements