@joseph-chircop_497308027822318
I can verify this Intel theory:
I have a desktop with two graphics drivers - Intel Arc (Iris) on the CPU side (1 monitor), and NVIDIA RTX 3070 (3 monitors).
If I disable the monitor that's driven by the Intel hardware in Windows' Display Settings, I can then open the Reolink client.
Even more curious is that I can then re-enable that monitor while the Reolink client is open, and it continues to work properly (even if I move it to the display driven by the Intel hardware).
If I close the app and try to open it again with all displays enabled, it won't open, which is the issue noted in this thread.
This therefore must be some bug or issue in the startup sequence of the Reolink app. It clearly isn't a problem once the app is actually launched, as noted above.
Please relay this information to your developers so they can resolve this issue in a (hopefully forthcoming) client version. I can provide more details if required.
P.S., if you have a beta version of the client that already fixes this issue, I'd love to give it some testing and provide feedback. I'm a professional application & game developer, so I know a thing or two about useful feedback.
