ID 604482 - Nuke becomes unresponsive when opening the Properties of a Viewer that has NDI Monitor Out enabled but doesn't currently have an open Window

Problem summary:
Nuke becomes unresponsive when opening the Properties of a Viewer that has NDI Monitor Out enabled but doesn't currently have an open Window 
 
This may also occur with other Monitor Out devices, but does not seem to affect the "Floating Window" option. 
 
Customer reported version:
Nuke 16.0v4
 
Customer reported platform:
Windows 10
 
Steps to reproduce:
1) Launch Nuke on a machine with NDI installed and open the Script Editor
2) Execute the following code to create a Viewer node without an open Window:

nuke.nodes.Viewer(monitorOutEnable=True, monitorOutDevice="NDI")

3) Double-click the Viewer2 node to open its Properties, and observe Nuke's performance
 
Expected behavior:
The Viewer's Properties and Window should open when double-clicking the node. 
 
Actual behavior:
If a Viewer does not currently have an open Window, like when it is created via Python or Copy/Pasted, Nuke will enter an unresponsive state if the Viewer's Enable Monitor Out knob is checked and the Monitor Out Device is set to NDI. 
 
The same problem occurs when minimizing the Nuke application and then maximizing it, as this attempts to open a Window for each Viewer in the script. 
 
Workaround:
Besides disabling Monitor Out via Python before attempting to open the Viewer's Properties, there is no known workaround at this time.
 
Reproduced by Support in:
Nuke 16.0v4 - Windows 11
Nuke 15.1v1 - Windows 11
Nuke 15.0v3 - Windows 11 -- Regression
 
Unable to reproduce bug in:
Nuke 16.0v4 - macOS 14 Sonoma
Nuke 15.1v1 - macOS 14 Sonoma
Nuke 15.0v3 - macOS 14 Sonoma
Nuke 15.0v2 - Windows 11
 
Rocky/Linux is untested as NDI is not available on that operating system
 
Earliest version tested:
Nuke 15.0v2 - This issue doesn't appear in this version and has regressed