Windows software Window closing after adding node V0.1.74 (2020-07-03)

[PITP2]

Hi,
I have an issue with the V0.1.74 (2020-07-03) of the windows software.
When I add a new node the application close automatically ....
OS : Windows 10

[idlezombie]

Just started doing a fresh setup first time using OZW. Experiencing the same crash as described above. First 8 nodes added without issue (all Aeotec ZW089 and ZW112). First crash happened on node ID 10 which also happened to be the first ZW100 I added. Experienced exact same crash on adding every subsequent ZW100 and then also on a ZW122. Still going through my devices so will post more if I notice any other patterns.

I am also on Windows 10, no third party AV. Running OZW in docker on a Pi4 with Aeotec Z-Stick Gen5 (the broken one, using a USB hub to work around while waiting for delivery of the revised model).

[idlezombie]

Oh and also same error log in Event Viewer on every crash, different offset each time etc. but always same dll:

Faulting application name: ozwadmin.exe, version: 0.1.75.0, time stamp: 0x5fa0fa79
Faulting module name: Qt5Core.dll, version: 5.12.8.0, time stamp: 0x5e82d0d9
Exception code: 0xc00000fd
Fault offset: 0x00074ca7
Faulting process ID: 0x27b4
Faulting application start time: 0x01d6bb3445097564
Faulting application path: C:\Program Files (x86)\OpenZwave Admin\ozwadmin.exe
Faulting module path: C:\Program Files (x86)\OpenZwave Admin\Qt5Core.dll
Report ID: f3eb80f4-0a10-443e-955c-2036833e38a6
Faulting package full name:
Faulting package-relative application ID:

[idlezombie]

Further update, has continued to crash after adding nodes of ZW096, ZWA008, ZW132, ZW111. However interestingly did NOT crash after adding secure nodes ZW062 and ZW117. I think it also did not crash when adding a Yale YRD446 in secure mode but I wasn't fully paying attention that time.

I had added those nodes in no particular order so might have been secure, unsecure, secure etc. and it would crash on the unsecure so definitely related to that.

I did not have the security key set until adding these nodes this morning so I am assuming the first 8 nodes that I reported not crashing were not added in secure mode though those door sensors do like to go secure. So not sure if that means much or is just a red herring.

Forgot one other detail yesterday I'm using admin version 1.75 not 1.74 as per the OP.

[idlezombie]

Just observed another detail in relation to this, it's not just when adding nodes it also happens when the controller is starting up. So if I open the admin program and connect to the daemon while the network is still starting up I will see the list of nodes and all the details being pulled still. It will stay open until the point where the z-wave plus logo is added to all the nodes in the list which seems to be the last step in the startup process. At that stage the app will crash.

It seems that is the same stage it crashes after adding a node as well so its not so much anything to do with adding a node that is crashing it but whatever action it is doing last in checking/adding that zwave plus logo to the node.