No longer starts up on user login.

[palladin9479]

None of the fan control v198 releases startup automatically when the user logs in. I have even put a link to the exe in the startup folder, made it run as admin, everything and it still will not start up. I revert back to v196 and startup works again. Not sure what was changed but likely a regression bug.

[tobbissimo]

same. Starts automatically when computer starts, but not when awaking from sleep.

[Rem0o]

Startup works by creating a scheduled task in the Windows Task Scheduler. Mind taking a look at the underlying task?

[maru801]

same. Starts automatically when computer starts, but not when awaking from sleep.

Same here. I can confirm that waking my PC from sleep makes fan control close. I need to reopen it every time I wake from sleep.

My PC is running Windows 10. I'm currently on V198 too, but noticed this has been happening with the last update as well.

[AnonymousWP]

Yes I can reproduce this; after sleep, FanControl has exited. When I start it, configuration is loaded again.

[BledaMundzuk]

Same here. Tried several work-arounds to no avail

[Rem0o]

Any crash dump in EventViewer ?

[AnonymousWP]

Any crash dump in EventViewer ?

Yep, here it is in XML format:

<System>
  <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> 
  <EventID>1000</EventID> 
  <Version>0</Version> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000000000000000</Keywords> 
  <TimeCreated SystemTime="2024-08-05T16:49:23.2100209Z" /> 
  <EventRecordID>18218</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="22564" ThreadID="22560" /> 
  <Channel>Application</Channel> 
  <Computer>Anonymoussaurus</Computer> 
  </System>
<EventData>
  <Data Name="AppName">FanControl.exe</Data> 
  <Data Name="AppVersion">198.0.0.0</Data> 
  <Data Name="AppTimeStamp">666b0000</Data> 
  <Data Name="ModuleName">atiadlxx.dll</Data> 
  <Data Name="ModuleVersion">31.0.24033.1003</Data> 
  <Data Name="ModuleTimeStamp">663c055a</Data> 
  <Data Name="ExceptionCode">c0000409</Data> 
  <Data Name="FaultingOffset">0000000000162bf1</Data> 
  <Data Name="ProcessId">0x4a00</Data> 
  <Data Name="ProcessCreationTime">0x1dae72feb1bc63f</Data> 
  <Data Name="AppPath">C:\Program Files (x86)\FanControl\FanControl.exe</Data> 
  <Data Name="ModulePath">C:\Windows\SYSTEM32\atiadlxx.dll</Data> 
  <Data Name="IntegratorReportId">7f4d5580-56e6-4192-9dcc-cfa68e2644c0</Data> 
  <Data Name="PackageFullName" /> 
  <Data Name="PackageRelativeAppId" /> 
  </EventData>
  </Event>

[Rem0o]

Are you guys all on AMD gpus? Which kind?

[AnonymousWP]

Are you guys all on AMD gpus? Which kind?

7800XT. Need any screenshots?

[Rem0o]

Driver version for Adrenaline/ADLX also would be appreciated.

[AnonymousWP]

Driver version for Adrenaline/ADLX also would be appreciated.

24.5.1. Where do I find the version of ADLX?

[maru801]

Are you guys all on AMD gpus? Which kind?

AMD 7900XT Adrenaline v24.5.1

[Rem0o]

Are you all staying on 24.5.1 because of bugs on games with the newer drivers? All my testing I've been doing lately on 24.7.1

[AnonymousWP]

Are you all staying on 24.5.1 because of bugs on games with the newer drivers? All my testing I've been doing lately on 24.7.1

That's right. 24.6.1 had stability issues according to some users on a forum and Reddit. 24.7.1 has a known issue regarding reduced performance on Battlefield 2042. That's why I'm staying on 24.5.1 for now.

[maru801]

Are you all staying on 24.5.1 because of bugs on games with the newer drivers? All my testing I've been doing lately on 24.7.1

I've just been lazy and haven't updated yet. I'll update later and see if it fixes the issue.

[BledaMundzuk]

Are you guys all on AMD gpus? Which kind?

Latest Nvidia driver here

[Asmod4n]

Startup works by creating a scheduled task in the Windows Task Scheduler. Mind taking a look at the underlying task?

that doesn't work with windows 11. you mustn't use UAC for it to work. the only solution is to write a windows service and give that system rights.

[maru801]

Updating my PC to the latest AMD Adrenaline version seems to have fixed the issue.

[GLWine]

The problem also persists on version 199, even inserting the program into the pinification utility does not change.