Make Plugin more robust against HWiNFO64 restarts

[hgross]

FanControl.HWInfo usually starts up successfully and is able to read my HWiNFO64 exports but whenever I have to restart HWiNFO the Plugin just stops by throwing an exception and never recovers:

19.12.2024 16:15:02: Update - System.Exception: HWInfo was closed during operation.
   at FanControl.HWInfo.HWInfoPlugin.Update() in C:\projects\fancontrol-hwinfo\HWInfoPlugin.cs:line 83
   at FanControl.Domain.BackendProviders.Plugin.PluginBackendProvider.Update()
   at FanControl.Domain.ComputerAccessLayer.Update()

Unfortunately I have to restart HWiNFO64 regularly since I use this plugin on my Streamdeck which regularly doesn't initialize correctly.

Can we get a more robust "reconnect/reactivate" mechanism in those cases?

[321MBT]

I second this request, and I have wanted to see it implemented for a while. I bet anyone who uses this plugin and relies on HWiNFO64 sensor readings for FC operation agrees it's a necessary improvement.

Here are other cases where FC will enter a never-ending loop when HWiNFO64 is killed while FC is running, forcing a hard kill of FC:

1. When HWiNFO64 updates, this is especially bothersome when one uses the beta channel with the Pro version with in-app updating, which occurs at least a few times per month, if not nearly weekly. For now, I have to kill FC, update HW, and then restart FC. And in case that happens while I'm doing intensive workloads, I set my BIOS fan control to very high speeds, which take over when I kill FC and is annoying due to the decibels. Overall, it's a very messy situation.
2. When something in FC (LHMLib in this case) breaks some HWiNFO64 sensors, which, in turn, breaks some of FC's controls when FC relies on HWiNFO64 for sensor readings.
3. Misconfiguration of FC, so that it starts before HWiNFO64.