Lehufrog

I looked it up and the default startup time for AIDA64 is 10 seconds after logon in the Windows Task Scheduler. Razer Synapse is in the Windows startup program so I'm not sure exactly when it starts.

It's not exact, but the AIDA64 icon appears first in the notification window.

No. I'm talking about the autorun feature of Razer synapse itself. When I turn off the autorun feature of Razer synapse, AIDA64 works fine. There is no function to run AIDA64 using Razer synapse. I don't know why this error occurs when there is no connection between the two software. Maybe the error occurs during the task scheduler stage when Windows boots up?

I figured out what the problem was. The Razer synapse software for the Razer headset was set to automatically start when Windows starts, and it seems to be conflicting with this. If I turn off the auto-start option for Razer synapse, the sensor panel is created in the normal position. How on earth do I fix this? I know the cause, but I can't find a solution.

Yes. That feature is turned on.

Sadly, upgrading to the beta version still has the same issue.

I use windows 11

It's the same symptom as the article posted in 2017. I am using dual monitors. One is for the sensor panel and the other is the main monitor. The sensor panel position only changes strangely when I restart my computer. If I quit AIDA64 while my computer is on and restart it, it goes back to its original position. (press the position reset button in the sensor panel settings, it will return to its original position.) However, even if I increase the delay time to around 10 minutes in Windows Task Scheduler, it still spawns on a monitor I haven't specified. I attach the image of monitor settings and registry value Main monitor : 3440x1440 SensorPanel monitor : 600x1024 (Vertical)