cant enter url or website

[bri]

when i go to settings-browser data-enter website url or popular website and click add it does nothing,doesnt enter the website.
This worked on previous version but not with this version 23.3 build 15144

[DavidR]

I'm somewhat confused (easily done).

Where are you trying to do this, given you have posted in the Avast Cleanup sub-forum  ?
Now I don't use Avast Cleanup, but I don't know how it would go about cleaning up a URL or what Add is meant to do.

If you are trying to clear browsing data, surely that would be done in your browser settings - Avast Secure Browser or whatever browser you use.

[bri]

its in the settings in avast cleanup.

[DavidR]

OK I understand now.

I think I saw something in the forums fairly recently which may be related (not directly).

It had something to do with exceptions not being honoured and there was a response by Avast in the topic.  It was something to do with other Avast Components, exceptions not honoured by the Antivirus Exceptions.  This was/is meant to be/been resolved in a recent or upcoming program update.

Though I haven't been able to find that specific topic.

[bri]

Thanks for replying DavidR,the title i have is not great but wasnt sure how to word it.Its something with this version of cleanup that came out yesterday as the version b4 worked.Maybe someone from avast cleanup or someone who uses this program can reproduce this issue or maybe its just me?

[DavidR]

No problem.

I'm not sure if this issue, the non integration of exclusions/exceptions with the main antivirus exclusions/exceptions was related to CleanUp or another additional Avast paid product.  Might be worth a trawl through this sub-forum.

[Stellarman]

Hello everyone,

thank you for reporting the issue, we've also discovered the same proble internally and it was already fixed and in the latest version (23.3.15198) the problem does not occur again.

[DavidR]

Hello everyone,

thank you for reporting the issue, we've also discovered the same problem internally and it was already fixed and in the latest version (23.3.15198) the problem does not occur again.

Thanks for the clarification.

[bri]

Thanks for the update and it is now working in latest build