@abline_300510094090438 OK. Here is a full proof workaround. The Reolink userSettings file can be found on the C drive using File Explorer (as long as you have set it to show hidden directories).

It is at C:\user\<yourusername>\AppData\Roaming\reolink and it is called userSettings which you can edit with Notepad,

Scroll down to find this key:

{"key":"hardware-acceleration","type":"boolean","value":true,"_id":"SC7vYAO3Jz5CRFqs"}

(Note: I'm not sure if the id at the end might be different for you, but don't change it)

Just change the word true to false, save the file, and that then works next time you go in. I hope that helps. It's been a frustrating bug.

@hjwedemark_272067637797095 I had a problem where 8.8.5 closed immediately after opening. I found out that it was because I had 2 graphics boards (GPUs) in my laptop - one for Intel Discrete Graphics and one for NVidia GPU. When I changed my Settings in the NVidia Control Panel from 'Automatic' to 'NVidia GPU Only' it started working fine. Interestingly when I subsequently switched it back to 'Automatic' it still continued to work, so it must have been a 'first time run' issue.

@abline_300510094090438 OK. Here is a full proof workaround. The Reolink userSettings file can be found on the C drive using File Explorer (as long as you have set it to show hidden directories).

It is at C:\user\<yourusername>\AppData\Roaming\reolink and it is called userSettings which you can edit with Notepad,

Scroll down to find this key:

{"key":"hardware-acceleration","type":"boolean","value":true,"_id":"SC7vYAO3Jz5CRFqs"}

(Note: I'm not sure if the id at the end might be different for you, but don't change it)

Just change the word true to false, save the file, and that then works next time you go in. I hope that helps. It's been a frustrating bug.

I have just upgrade to Windows 11 PC and I have the same problem. The client software fires up for about a half a second then goes grey/black. This is hopeless ans seems to have been going on a while. Surely REOLink must employ capable support programmers to fix and test this? Perhaps not!!