Winlicence error with Avast update

Home › Forums › Breakaway Audio Enhancer › Winlicence error with Avast update

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • February 14, 2017 at 11:39 am #3267
    spotty69
    Member

    I'm running Windows 10. My Avast (free version) has just updated itself to v17.2.2286 (build 17.1.3394.0), and now Breakaway Audio Enhancer will no longer load, giving a "Winlicence" error (see attached picture)

    If I disable Avast, it loads fine – so Avast is clearly the problem.

    Has anyone else ha this issue?

    Many thanks.

    Attachments:

    February 14, 2017 at 8:10 pm #5717
    Milky
    Keymaster

    Have you updated to the latest release as per this link? http://www.forumclaessonedwards.com/forum/index.php/topic,5308.0.html

    February 16, 2017 at 11:42 am #5718
    spotty69
    Member

    Yes – I actually only bought the software a couple of weeks ago and so I have the latest version.

    March 5, 2017 at 10:20 pm #5719
    spotty69
    Member

    Hi, no further replies, is there any update on this?

    I'm unable to run Breakaway with my chosen AV software. If there is no workaround I'll sadly have to ask for a refund as the software is non-functional.

    Many thanks,

    March 6, 2017 at 12:32 am #5720
    JesseG
    Member

    The makers of WinLicense have been notified and a new build that fixes it will be out shortly. In the mean time, you can disable Avast while starting Breakaway, and then re-enable it after Breakaway has started.

    That works for me in my testing. I also use Avast on my personal systems. The thing that triggers the WinLicense protection is the new "Behavior Shield" in Avast.

    Sorry for the inconvenience until the new build comes out.

    March 7, 2017 at 6:04 pm #5721
    spotty69
    Member

    Thanks Jesse. I actually found out in the meantime that adding the Breakaway EXE to Avast's exclusion list also works.

    Cheers!

  • Author
    Posts
Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.