Share your Sensorpanels

[MaxMS]

I wanted to create something that wasn’t techno-aggressive.

An image from the internet + ChatGPT, and the new dashboard 1024x600 is ready.

[ZifnabHydre]

1280 * 480 - For Star Wars fans and supporters of the Galactic Empire. Long Live the Emperor.

StarWars-Empire-1280x480.spzip

[1 PC Tip a day]

I’d like to share a detailed solution for anyone struggling with the Sensor Panel moving, resizing, or resetting when using a secondary display with different scaling or resolution. This is a common pain point discussed by users like scotts, supes, WeakLaugh, and Atila on the official AIDA64 forums, where many report that the panel resizes itself or jumps between monitors after rebooting or reconnecting displays. (https://forums.aida64.com/topic/7580-sensor-panel-resized-itself-after-connecting-new-monitor-now-i-cant-fix-it/)

---

Goal

Lock your Sensor Panel on a secondary monitor with fixed size/position and make it launch reliably with Windows — even if monitors disconnect/reconnect or have different DPI scaling.

---

1) Edit the AIDA64 configuration file (AIDA64.ini)

1. Close AIDA64 entirely.
2. Open Notepad as Administrator.
3. Locate your AIDA64.ini file:

%localappdata%\FinalWire\AIDA64\AIDA64.ini

or in your installation folder.

4. Find the [SensorPanel] section or add it at the end if it doesn’t exist.
5. Replace or set the following values according to your monitor setup:

[SensorPanel]
Active=1
FixedSize=1
Width=1280
Height=400
PositionX=-1600
PositionY=1040
LoadLayout=1
LayoutFile=C:\AIDA64\SensorPanel_Fixed.spzip

[Display]
AutoAdjustDPI=0
AutoAdjustResolution=0

What to change for your setup:

• Width / Height → set these to the exact resolution of your Sensor Panel window. This locks the panel size.
• PositionX / PositionY → coordinates of the panel on your screen:
  • PositionX = horizontal offset relative to the primary monitor; multiply by the primary monitor’s DPI scaling if it differs from 100%.
  • PositionY = vertical offset from the top of the virtual desktop; usually PrimaryMonitorHeight - SecondaryPanelHeight if the panel sits at the bottom.
• LayoutFile → point to the .spzip or .a64sp layout you saved. Use the full path, without quotes.
• [Display] section prevents AIDA64 from automatically adjusting DPI or resolution when monitors reconnect.

---

2) Create an automatic startup script (.bat)

This ensures AIDA64 opens after Windows has initialized monitors, preventing resizing or jumping.

1. Open Notepad.
2. Paste:

@echo off
REM Close AIDA64 if already running
taskkill /f /im aida64.exe >nul 2>&1

REM Wait 8 seconds for Windows to arrange displays (adjust if your monitors need more time)
timeout /t 8 /nobreak >nul

REM Start AIDA64
start "" "C:\Program Files (x86)\AIDA64 Extreme\aida64.exe"

What to change for your setup:

• timeout /t 8 → increase if your secondary display takes longer to initialize.
• Path to aida64.exe → replace with the actual path where AIDA64 is installed on your PC.

3. Save as AIDA64_Startup.bat (type: All Files, not .txt).
4. Create a shortcut to this .bat and place it in the Startup folder:
   • Win + R → type shell:startup → paste shortcut.
5. Optional: In the shortcut properties → Run: Minimized, so the console window doesn’t appear.

---

What This Fix Solves

• Locks Sensor Panel size & position on your secondary monitor
• Prevents Windows DPI scaling from resizing it unexpectedly
• Ensures AIDA64 launches after monitors are ready
• Stops AIDA64 from jumping to the primary display on reboot or after connecting virtual monitors

---

Why This Is Needed

Many users report that the Sensor Panel keeps resizing or moving after disconnects, restarts, or when DPI scaling differs between monitors — even with “Lock panel size/position” enabled in preferences. (https://forums.aida64.com/topic/7580-sensor-panel-resized-itself-after-connecting-new-monitor-now-i-cant-fix-it/)

---

Credits & References

Thanks to users across the AIDA64 community (e.g., scotts, supes, WeakLaugh, Atila) for identifying that the core issue relates to panel resizing on monitor changes and scaling, which inspired this workflow. (https://forums.aida64.com/topic/7580-sensor-panel-resized-itself-after-connecting-new-monitor-now-i-cant-fix-it/)

---

Disclaimer

Text created using ChatGPT, as English is not my native language. It is strongly recommended to make a backup of your .ini file before editing anything. No responsibility is assumed for unexpected malfunctions; use at your own risk.

 

EDIT: Tested and working with version 8.25.8200 of the program

Edited 16 hours ago by 1 PC Tip a day

[1 PC Tip a day]

@Mice007 I’m trying to understand which lines in the AIDA64 ini file actually define the size and position of the Sensor Panel. I’ve noticed that some settings like enabling the context menu are saved, but the width, height, and position don’t seem to be applied from the ini. The reason I ask is that I’ve created a script acting as a ‘watcher’ to always copy a master ini to the installation folder if it detects changes. If I can determine which ini parameters control the size, it would allow me to partially fix the panel misalignment...

 

EDIT: Nevermind, I am programming a basic "Watcher" that checks the size and position of the SensorPanel every 5 seconds, and adjusts it if there have been changes

5 hours ago, 1 PC Tip a day said:

I’d like to share a detailed solution for anyone struggling with the Sensor Panel moving, resizing, or resetting when using a secondary display with different scaling or resolution. This is a common pain point discussed by users like scotts, supes, WeakLaugh, and Atila on the official AIDA64 forums, where many report that the panel resizes itself or jumps between monitors after rebooting or reconnecting displays. (https://forums.aida64.com/topic/7580-sensor-panel-resized-itself-after-connecting-new-monitor-now-i-cant-fix-it/)

---

Goal

Lock your Sensor Panel on a secondary monitor with fixed size/position and make it launch reliably with Windows — even if monitors disconnect/reconnect or have different DPI scaling.

---

1) Edit the AIDA64 configuration file (AIDA64.ini)

1. Close AIDA64 entirely.
2. Open Notepad as Administrator.
3. Locate your AIDA64.ini file:

%localappdata%\FinalWire\AIDA64\AIDA64.ini

or in your installation folder.

4. Find the [SensorPanel] section or add it at the end if it doesn’t exist.
5. Replace or set the following values according to your monitor setup:

[SensorPanel]
Active=1
FixedSize=1
Width=1280
Height=400
PositionX=-1600
PositionY=1040
LoadLayout=1
LayoutFile=C:\AIDA64\SensorPanel_Fixed.spzip

[Display]
AutoAdjustDPI=0
AutoAdjustResolution=0

What to change for your setup:

• Width / Height → set these to the exact resolution of your Sensor Panel window. This locks the panel size.
• PositionX / PositionY → coordinates of the panel on your screen:
  • PositionX = horizontal offset relative to the primary monitor; multiply by the primary monitor’s DPI scaling if it differs from 100%.
  • PositionY = vertical offset from the top of the virtual desktop; usually PrimaryMonitorHeight - SecondaryPanelHeight if the panel sits at the bottom.
• LayoutFile → point to the .spzip or .a64sp layout you saved. Use the full path, without quotes.
• [Display] section prevents AIDA64 from automatically adjusting DPI or resolution when monitors reconnect.

---

2) Create an automatic startup script (.bat)

This ensures AIDA64 opens after Windows has initialized monitors, preventing resizing or jumping.

1. Open Notepad.
2. Paste:

@echo off
REM Close AIDA64 if already running
taskkill /f /im aida64.exe >nul 2>&1

REM Wait 8 seconds for Windows to arrange displays (adjust if your monitors need more time)
timeout /t 8 /nobreak >nul

REM Start AIDA64
start "" "C:\Program Files (x86)\AIDA64 Extreme\aida64.exe"

What to change for your setup:

• timeout /t 8 → increase if your secondary display takes longer to initialize.
• Path to aida64.exe → replace with the actual path where AIDA64 is installed on your PC.

3. Save as AIDA64_Startup.bat (type: All Files, not .txt).
4. Create a shortcut to this .bat and place it in the Startup folder:
   • Win + R → type shell:startup → paste shortcut.
5. Optional: In the shortcut properties → Run: Minimized, so the console window doesn’t appear.

---

What This Fix Solves

• Locks Sensor Panel size & position on your secondary monitor
• Prevents Windows DPI scaling from resizing it unexpectedly
• Ensures AIDA64 launches after monitors are ready
• Stops AIDA64 from jumping to the primary display on reboot or after connecting virtual monitors

---

Why This Is Needed

Many users report that the Sensor Panel keeps resizing or moving after disconnects, restarts, or when DPI scaling differs between monitors — even with “Lock panel size/position” enabled in preferences. (https://forums.aida64.com/topic/7580-sensor-panel-resized-itself-after-connecting-new-monitor-now-i-cant-fix-it/)

---

Credits & References

Thanks to users across the AIDA64 community (e.g., scotts, supes, WeakLaugh, Atila) for identifying that the core issue relates to panel resizing on monitor changes and scaling, which inspired this workflow. (https://forums.aida64.com/topic/7580-sensor-panel-resized-itself-after-connecting-new-monitor-now-i-cant-fix-it/)

---

Disclaimer

Text created using ChatGPT, as English is not my native language. It is strongly recommended to make a backup of your .ini file before editing anything. No responsibility is assumed for unexpected malfunctions; use at your own risk.

 

EDIT: Tested and working with version 8.25.8200 of the program

Edited 10 hours ago by 1 PC Tip a day

[1 PC Tip a day]

AIDA64 SensorPanel Watcher – Complete Guide

Introduction

The AIDA64 SensorPanel can sometimes open in the wrong position or size, especially on multi-monitor setups. This Watcher system ensures the panel always opens in the correct location and size, using a master .ini file as reference.

Features:

• Automatically runs when Windows starts
• Monitors the AIDA64 .ini file every few seconds
• Fixes the SensorPanel window position and size
• Runs silently in the background

The system uses:

• Master .ini file – your reference configuration
• PowerShell Watcher script – monitors the .ini file and fixes the window
• Hidden VBS launcher – runs the batch silently with admin rights
• Optional batch file – copies the master .ini file and restarts AIDA64

---

Step 1: Prepare the Master .ini File

1. Create a folder to store your reference .ini file. Example:

C:\Path\To\Master\aida64.ini

2. Copy your desired AIDA64 .ini file into this folder. This is the file the watcher will use as a reference.

---

Step 2: Create the Batch File

1. Open Notepad and paste:

@echo off
taskkill /f /im aida64.exe >nul 2>&1
timeout /t 5 /nobreak >nul
copy /y "C:\Path\To\Master\aida64.ini" "C:\Program Files\FinalWire\AIDA64 Extreme\aida64.ini" >nul
start "" "C:\Program Files\FinalWire\AIDA64 Extreme\aida64.exe"

2. Save as AIDA64_Fixed_SensorPanel.bat.

Note: Replace the paths with your master .ini file path and AIDA64 installation folder.

---

Step 3: Create the Hidden VBS Launcher

1. Open Notepad and paste:

Set objShell = CreateObject("Shell.Application")
If WScript.Arguments.Length = 0 Then
    objShell.ShellExecute "wscript.exe", """" & WScript.ScriptFullName & """ runas", "", "runas", 1
    WScript.Quit
End If
batPath = "C:\Path\To\Watcher\AIDA64_Fixed_SensorPanel.bat"
Set WshShell = CreateObject("WScript.Shell")
WshShell.Run """" & batPath & """", 0, False

2. Save as AIDA64_Fixed_SensorPanel_Hidden.vbs.

Note: Replace batPath with the path to your batch file.

---

Step 4: Create the PowerShell Watcher Script

1. Open Notepad and paste:

$master = "C:\Path\To\Master\aida64.ini"
$install = "C:\Program Files\FinalWire\AIDA64 Extreme\aida64.ini"
$vbs = "C:\Path\To\Watcher\AIDA64_Fixed_SensorPanel_Hidden.vbs"
$SensorPanelClass = "TForm_HWMonitoringSensorPanel"

if (-not ("WinAPI" -as [type])) {
Add-Type @"
using System;
using System.Runtime.InteropServices;
using System.Text;
public class WinAPI {
    public delegate bool EnumWindowsProc(IntPtr hWnd, IntPtr lParam);
    [DllImport("user32.dll")]
    public static extern bool EnumWindows(EnumWindowsProc lpEnumFunc, IntPtr lParam);
    [DllImport("user32.dll", SetLastError=true)]
    public static extern int GetClassName(IntPtr hWnd, StringBuilder lpClassName, int nMaxCount);
    [DllImport("user32.dll")]
    public static extern bool IsWindowVisible(IntPtr hWnd);
    [DllImport("user32.dll")]
    public static extern bool MoveWindow(IntPtr hWnd, int X, int Y, int nWidth, int nHeight, bool bRepaint);
}
"@
}

$global:foundHandles = @()

function Get-FileHashMD5($file) {
    if (Test-Path $file) { return (Get-FileHash $file -Algorithm MD5).Hash } else { return "" }
}

function Fix-SensorPanel {
    $global:foundHandles = @()
    $callback = {
        param($hWnd, $lParam)
        if ([WinAPI]::IsWindowVisible($hWnd)) {
            $classSb = New-Object System.Text.StringBuilder 256
            [WinAPI]::GetClassName($hWnd, $classSb, $classSb.Capacity) | Out-Null
            if ($classSb.ToString() -eq $SensorPanelClass) { $global:foundHandles += $hWnd }
        }
        return $true
    }
    $delegate = [WinAPI+EnumWindowsProc]$callback
    [WinAPI]::EnumWindows($delegate, [IntPtr]::Zero) | Out-Null
    foreach ($hWnd in $global:foundHandles) {
        for ($i=0; $i -lt 10; $i++) {
            [WinAPI]::MoveWindow($hWnd, -1280, 1040, 1280, 400, $true)
            Start-Sleep -Milliseconds 200
        }
    }
}

while ($true) {
    if (Get-FileHashMD5($master) -ne Get-FileHashMD5($install)) {
        Start-Process "wscript.exe" -ArgumentList ('"' + $vbs + '"') -Verb RunAs
    }
    Fix-SensorPanel
    Start-Sleep -Seconds 5
}

2. Save as AIDA64_Watcher.ps1.

Note: Update paths to your master .ini file, installation folder, and VBS file.

---

Step 5: Create a Hidden Scheduled Task

1. Open Task Scheduler (Win + S → Task Scheduler)
2. Click Create Task…
3. General Tab:
   • Name: AIDA64 Sensor Panel Watcher
   • Check Run only when user is logged on
   • Check Run with highest privileges
   • Configure for: Windows 10
4. Triggers Tab:
   • New → Begin task: At log on → OK
5. Actions Tab:
   • New → Action: Start a program
   • Program/script: powershell.exe
   • Add arguments:

-WindowStyle Hidden -ExecutionPolicy Bypass -File "C:\Path\To\Watcher\AIDA64_Watcher.ps1"

6. Settings Tab:
   • Allow task to run on demand
   • Run task as soon as possible after a missed start
   • Restart task if it fails (1 min interval, 3 attempts)
7. Click OK → Enter password if requested

---

How it Works

• The Watcher checks the installed .ini file against the master .ini file
• If differences are detected, it runs the batch file silently to update AIDA64
• The PowerShell script searches for the Sensor Panel window by class name
• Moves it to the correct monitor and resizes it
• Runs invisible in the background with very low resource usage

---

Resource Usage:

• The Watcher uses minimal CPU and memory (typically <5 MB RAM, negligible CPU).

---

Disclaimer

Text created using ChatGPT, as English is not my native language. It is strongly recommended to create a Windows system restore point before editing anything. No responsibility is assumed for unexpected malfunctions; use at your own risk.