Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. Qt maintenance tool crashes with unhandled win32 exception [37360]
Forum Updated to NodeBB v4.3 + New Features

Qt maintenance tool crashes with unhandled win32 exception [37360]

Scheduled Pinned Locked Moved Unsolved Installation and Deployment
3 Posts 2 Posters 306 Views 1 Watching
  • 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.
  • C Offline
    C Offline
    cdwijs
    wrote on last edited by
    #1

    Qt maintenance tool crashes with unhandled win32 exception [37360]

    Steps to reproduce:

    1. Start Qt Maintenance Tool
    2. Click next, and skip
    3. Choose "Update Components". Now it's retrieving meta information.
      At the "Select Components" window, the following updates are checked:
      Qt Creator 4.10.0 (installed 4.7.2)
      Qt Creator 4.10 CDB Debugger Support (installed 4.7.2)
      Python ... License version 2 (installed 1.0.0)
    4. Click next, and then click Update. Now the text "Updating components of Qt" and a progress bar is drawn. One second later, I see "MaintenanceTool.exe has stoppen working" with a debug and close program option.
    5. Choose Debug. Now "Visual Studio just in time debugger" is opened, with the message "An unhandled win32 exception occurred in Maintenancetool.exe [37360]"
    6. Choose "yes", so visual studio 2010 is started, then the message "invalid license data". comes up. Click close, and choose "no" at the question if you want to use another debugger. Now the maintenance tool is closed.

    Versions:
    Qt Maintenance Tool: Digital Signature signing time: "‎dinsdag ‎14 ‎mei ‎2019 13:08:26" Date modified 03-06-2019 8:46
    Windows 7 enterprise SP1 64 bit
    Qt: 5.11.1 mingw53_32

    How to get around this?

    jsulmJ 1 Reply Last reply
    0
    • C cdwijs

      Qt maintenance tool crashes with unhandled win32 exception [37360]

      Steps to reproduce:

      1. Start Qt Maintenance Tool
      2. Click next, and skip
      3. Choose "Update Components". Now it's retrieving meta information.
        At the "Select Components" window, the following updates are checked:
        Qt Creator 4.10.0 (installed 4.7.2)
        Qt Creator 4.10 CDB Debugger Support (installed 4.7.2)
        Python ... License version 2 (installed 1.0.0)
      4. Click next, and then click Update. Now the text "Updating components of Qt" and a progress bar is drawn. One second later, I see "MaintenanceTool.exe has stoppen working" with a debug and close program option.
      5. Choose Debug. Now "Visual Studio just in time debugger" is opened, with the message "An unhandled win32 exception occurred in Maintenancetool.exe [37360]"
      6. Choose "yes", so visual studio 2010 is started, then the message "invalid license data". comes up. Click close, and choose "no" at the question if you want to use another debugger. Now the maintenance tool is closed.

      Versions:
      Qt Maintenance Tool: Digital Signature signing time: "‎dinsdag ‎14 ‎mei ‎2019 13:08:26" Date modified 03-06-2019 8:46
      Windows 7 enterprise SP1 64 bit
      Qt: 5.11.1 mingw53_32

      How to get around this?

      jsulmJ Offline
      jsulmJ Offline
      jsulm
      Lifetime Qt Champion
      wrote on last edited by
      #2

      @cdwijs Any anti-virus software running?
      Also, you can file a bug report in Qt bug tracker.

      https://forum.qt.io/topic/113070/qt-code-of-conduct

      C 1 Reply Last reply
      0
      • jsulmJ jsulm

        @cdwijs Any anti-virus software running?
        Also, you can file a bug report in Qt bug tracker.

        C Offline
        C Offline
        cdwijs
        wrote on last edited by
        #3

        @jsulm
        Yes, we have the antivirus software "Symantec Endpoint Protection" running. I can't disable that.
        I think this problem started a few weeks ago after I had successfully updated Qt, and then tried to install the next update a week later.

        I have created the bugreport here:
        https://bugreports.qt.io/browse/QTCREATORBUG-22973

        1 Reply Last reply
        0

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved