With version 4.8.4.5 x64 we are getting an error when trying to export settings: Error exporting registry key: 1314.
Does anybody have a clue what could be the issue?
Error exporting settings
Re: Error exporting settings
Did this problem exist prior to Blue Iris version 4.8.4.5? If not, then I would recommend updating to the latest/last version of Blue Iris 4, which is 4.8.6.3 x64. If you are unable to check for new updates within Blue Iris 4 application then download the update from https://blueirissoftware.com/40/update64.exe and run it. It will update your version from 4.8.4.5 x64 to 4.8.6.3 x64.
Blue Iris v5.3.9.10 | Win10 x64 version 22H2 | Dahua IPC-HFW2100, Amcrest IP2M-841W, Hikvision MINI PT DS-2CD2F52F-IS, Edimax IC-3030iWn | Intel i5-2500 CPU, 8GB Ram, Samsung 860 EVO 512GB SSD, WD Black 1TB HD.
Re: Error exporting settings
I will try that. Thanks.reddawg wrote: ↑Sun Aug 11, 2019 8:44 amDid this problem exist prior to Blue Iris version 4.8.4.5? If not, then I would recommend updating to the latest/last version of Blue Iris 4, which is 4.8.6.3 x64. If you are unable to check for new updates within Blue Iris 4 application then download the update from https://blueirissoftware.com/40/update64.exe and run it. It will update your version from 4.8.4.5 x64 to 4.8.6.3 x64.
Re: Error exporting settings
After upgrading unfortunately the error persists.tombone wrote: ↑Thu Aug 15, 2019 4:54 amI will try that. Thanks.reddawg wrote: ↑Sun Aug 11, 2019 8:44 amDid this problem exist prior to Blue Iris version 4.8.4.5? If not, then I would recommend updating to the latest/last version of Blue Iris 4, which is 4.8.6.3 x64. If you are unable to check for new updates within Blue Iris 4 application then download the update from https://blueirissoftware.com/40/update64.exe and run it. It will update your version from 4.8.4.5 x64 to 4.8.6.3 x64.
Re: Error exporting settings
Not that it helps...
Maybe export the Windows BI regestry, then, load it back to see it it complains. Maybe that will 'clear' something that's not valid.
You could examine the windows BI regestry to see if it looks strange.https://support.symantec.com/us/en/arti ... 12638.html
1314, 0x00000522, A required privilege is not held by the client.
Maybe export the Windows BI regestry, then, load it back to see it it complains. Maybe that will 'clear' something that's not valid.