Rem0o / FanControl.Releases

This is the release repository for Fan Control, a highly customizable fan controlling software for Windows.
Other
13.99k stars 442 forks source link

Fan Control update v183 unable to detect sensors #2361

Open Etrinque opened 6 months ago

Etrinque commented 6 months ago

Describe the bug updated fan control portable to v183. prior version was working fine. update flagged error failure to load sensors 29 found /30 expected no sensors matched with fans that were matched prior. reload config. same result. no matched fans. automatic paring option fails with a no sensors detected error.

reload also fails in the same fashion.

system. Windows 11 amd 7700x amd 7900xt deep cool aio Gigabyte aorus elite mAtx wifi mobo 750watt gold A psu

Etrinque commented 6 months ago

logs mention nothing. 3/1/2024 8:06:39 AM: System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure. at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult) at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar) --- End of inner exception stack trace --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at FanControl.Domain.UpdaterService.d__24.MoveNext() 3/1/2024 8:06:39 AM: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure. at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult) at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar) 3/1/2024 8:06:39 AM: System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure. at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult) at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)

removed and installed prior version. unfortunately lost my config in the process. reinstalled new version. was able to auto assign and auto config but setings did not persist through pc sleep cycle.

will update further

Etrinque commented 6 months ago

Screenshot 2024-03-14 145808 Screenshot 2024-03-14 150036

ECHOSUD commented 6 months ago

With v183 this is my error log (I exited and reopened multiple times)

Log
15/03/2024 10:17:53 AM: System.Exception: Initialization was called twice.
   at FanControl.Domain.ComputerAccessLayer.Initialize()
   at FanControl.Domain.ComputerAccessLayer.Refresh()
   at System.Windows.Threading.DispatcherOperation`1.InvokeDelegateCore()
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at FanControl.Domain.ApplicationContext.d__13`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at FanControl.ViewModels.MainWindowViewModel.<>c__DisplayClass140_0.<b__10>d.MoveNext()
15/03/2024 10:19:32 AM: System.Exception: Initialization was called twice.
   at FanControl.Domain.ComputerAccessLayer.Initialize()
   at FanControl.Domain.ComputerAccessLayer.<>c__DisplayClass11_0.<b__0>d.MoveNext()
15/03/2024 10:19:32 AM: Initialization failed.
15/03/2024 10:22:05 AM: System.Exception: Initialization was called twice.
   at FanControl.Domain.ComputerAccessLayer.Initialize()
   at FanControl.Domain.ComputerAccessLayer.<>c__DisplayClass11_0.<b__0>d.MoveNext()
15/03/2024 10:22:05 AM: Initialization failed.
Rem0o commented 6 months ago

@Etrinque can you send the json file of your prior config? Might be in the backup folder within the configuration folder.

RoyaIFlush commented 6 months ago

I'm having the same issue, "no speed sensors". Reinstalling and reloading old configs and older versions (181 etc) do not fix the issue. Now it won't even recognize my fans at all. I'm attaching my old userconfig file. userConfig.json

WantStuff commented 6 months ago

Same issue for me (see #2366, not fixed)

WantStuff commented 6 months ago

I may have found the solution (at least for me). I did not have the dotnet 8 runtime installed, only 7. I have now installed the latest runtime and updated to v184, and the Controls are now all showing correctly and seem to be working - albeit with a "No Calibration" label at the bottom of the card; I will run the calibration later. Without the dotnet 8 runtime, I was seeing the exact same as shown above in the screenshots.

Not sure why the app did not complain about the missing runtime as I understood that the check was built into dotnet itself. @Rem0o maybe this could be an extra check you should add to the installer?

If anyone needs to know how to check the runtime version, you can open a CMD prompt and type dotnet --info. You should expect to see "Microsoft.WindowsDesktop.App 8.0.3" in the list of versions returned

AndyNewy commented 6 months ago

Same problem for me....On a windows 11 based machine. But on a windows 10 machine the V183 update worked just fine..... There was another update yesterday (I think) but didn't cure the issue. Should I delete and reinstall Fan Control????