Communication Studio application freezes on Disconnect

A customer reports that Communication Studio stops responding when Disconnect is triggered while the Network Scan has not yet finished. The UI becomes unresponsive and, according to the video evidence, cannot be used again without  killing/restarting the application.

Actual behavior:
After Disconnect is invoked, no dialog appears and no further UI response is visible; the application stays frozen until it is terminated manually.

Expected behavior:
While the "add device" of the network-scan operation is running, a progress dialog must be displayed for the entire duration of that operation, so the user can see the application is still working. Once the operation finishes, the dialog closes and Disconnect is processed normally.

Reproduction steps:

1. Open a project with DeviceNet Master
2. Start a Network Scan.
3. Trigger Disconnect while the scan is still in progress.