Qt Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Unsolved

    Solved Avast alarm to Qt 5.10.1 static build

    General and Desktop
    3
    7
    914
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      nNullSpace last edited by

      (windows 8.1 pro + Qt 5.10.1 + windows-build-qt-static.ps1 in admin powershell)

      as the attached image.

      And Avast blocks some file extraction from "qt-everywhere-src-5.10.1.zip", such as "configure.bat".

      Is there any other people experience that?

      I tried "qt-everywhere-src-5.10.0.zip" at the same time, it works well.

      0_1526027338561_a1.jpg

      nNullSpace

      1 Reply Last reply Reply Quote 0
      • K
        koahnig last edited by

        Hi and welcome to devnet forum

        Your anti-virus application is just calling out that there is a new application which might be potentially dangerous.

        Yes, that happens to others also. It is a matter how nervous your AV-checker is. In a hyper-sensitive mode any AV checker will call out by anything trying to scan the disks and/or trying to communicate with the outside world.

        qmake is a central part required for using Qt libs. It has to scan the source files. If you do not allow it to do it, you cannot use Qt libs.

        Ultimately it is your decision on how to continue.

        Personally I have made the experience with my AV-checker that it is removing once in a while applications I just have generated as dangerous. It becomes weird when you start to debug. You check in one moment and all is there, but suddenly it is when trying to access. :(

        Vote the answer(s) that helped you to solve your issue(s)

        1 Reply Last reply Reply Quote 2
        • mrjj
          mrjj Lifetime Qt Champion last edited by mrjj

          Hi
          Its pretty normal for Avast
          I had to tweak it to ignore my build folder and
          not scan the exe every god damn time :)

          You might want to disable CyberCapture to let it build.

          1 Reply Last reply Reply Quote 1
          • N
            nNullSpace last edited by

            Hi, koahnig, thanks for your explanation.

            The funny point is that Avast doesn't bark at Qt 5.10.0.

            Maybe Qt can ask Avast put 5.10.1 into the white list or something?
            I am not pretty sure about how anti-virus software works, just a suggestion.

            nNullSpace

            1 Reply Last reply Reply Quote 0
            • N
              nNullSpace last edited by

              I have to correct what I said.
              5.10.0 also suffers from that. (CyberCapture is off)
              So, I pick the ultimate solution -- turn off Avast.

              Considering that had not happened weeks ago, I think the root cause is Avast.

              K 1 Reply Last reply Reply Quote 0
              • K
                koahnig @nNullSpace last edited by

                @nNullSpace

                You might want to rethink.

                I do not know Avast, but most when not all AV-checker have different modes from basic checks to paranoid. Often some high-level mode denying most of thinks are activated by default.

                With my AV checker BitDefender I had to exclude also folders for building. However, to search such settings is certainly a nuisance, but less of a problem than rebuilding of your OS after an AV attack.

                Vote the answer(s) that helped you to solve your issue(s)

                1 Reply Last reply Reply Quote 1
                • mrjj
                  mrjj Lifetime Qt Champion last edited by

                  Hi
                  Also try disable Hardened Mode to check if thats the reason.

                  1 Reply Last reply Reply Quote 2
                  • First post
                    Last post