All Activity

Enter the CyberCurrent with “Voltaris Nexyra | D-6”! Where energy finds form, and precision becomes art. Size: 1920x480 Need a custom fit? Your panel, your way - tailored dimensions on request: 3840x1100 | 1280x800 | 1024x768 | 1920x720 | 1920x1080 & more! Precision > Futuristic: Temperature: CPU · GPU · RAM · VRAM: 100 State Utilization: CPU · GPU · RAM · VRAM: 100 States Clock: CPU · GPU: 60 States Note: Requires AIDA64 v7.70.7500 or Beta v7.99.7829 or above. Please click here to send me a PM to claim your exclusive Sensor Panel. Rise Beyond Limits - Where your system speaks in light, motion, and soul. Explore more on my webpage: Surjeet Skins From Reading Data to Experiencing It.

@MoonTime622 @Movingon007 @slipkidOG Check this out!

Here you can see the Watcher in action:

By looking for a solution for anyone still having issues with the SensorPanel moving, changing size, or restarting when using a secondary display with a different scale or resolution on Windows (as me, running latest AIDA64 8.25 version), and coming from this: I would like to introduce y'all: AIDA64 SensorPanel Watcher AIDA64 SensorPanel Watcher is a light script in refinement phase (but actually working) that checks if the AIDA .ini configuration file has changed and automatically readjust the position and size of the SensorPanel if they have changed as well. Note: The full script has been shared, but the Position and Size of the SensorPanel have to be changed according to users' preference.

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 Create a folder to store your reference .ini file. Example: C:\Path\To\Master\aida64.ini 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 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" 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 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 Save as AIDA64_Fixed_SensorPanel_Hidden.vbs. Note: Replace batPath with the path to your batch file. Step 4: Create the PowerShell Watcher Script 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 } 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 Open Task Scheduler (Win + S → Task Scheduler) Click Create Task… General Tab: Name: AIDA64 Sensor Panel Watcher Check Run only when user is logged on Check Run with highest privileges Configure for: Windows 10 Triggers Tab: New → Begin task: At log on → OK 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" 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) 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.

After rebooting and launching AIDA64 again, the Sensor Panel froze after about 5 hours. I opened AIDA64 from the system tray and successfully closed the Sensor Panel. When I clicked End Task in the task bar, AIDA64 appeared to close, but it still showed as a background process in the task manager Processes tab. Attempting to End Task there did nothing. Attempting to End Task in the Details tab got a message that the operation could not be completed. I relaunched AIDA64, and the Sensor Panel seems to be working.

@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 EDIT 2: Watcher launched (working but still in refinement process). See below

Greetings, I previously mentioned experiencing BSODs after updating to version 5.99. However, the administration was helpless in resolving this issue. Today, I submitted both versions 5.99 and 8.25 of the "kerneld-x64.sys" file, which is causing the problem, to the "claude.ai" website. The site found the problem, and I kindly request that you fix it. Respectfully.

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) Close AIDA64 entirely. Open Notepad as Administrator. Locate your AIDA64.ini file: %localappdata%\FinalWire\AIDA64\AIDA64.ini or in your installation folder. Find the [SensorPanel] section or add it at the end if it doesn’t exist. 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. Open Notepad. 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. Save as AIDA64_Startup.bat (type: All Files, not .txt). Create a shortcut to this .bat and place it in the Startup folder: Win + R → type shell:startup → paste shortcut. 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

Have you tried it with the latest AIDA64 beta update? https://www.aida64.com/downloads/latesta64xebeta

They should be there as Temperature #1 and Temperature #2 in your case.

It means you will need to wait for Asus to fix the issue on their end too. They're a bit slower than us though.

Windows reboot seems to fix them not showing to me. But those two temperatures do not show up in external application list.

So i also have the same problem, and yes I see your response and fix, but for some unknown reason the aida64 that come with the board will not update, and if I install it, it asks for a key.

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

As in the previous screenshot, they'll be labeled "Power Monitor #1 - #6". There are also entries for Total Power, Total Current and Power by Pin using the same nomenclature. I had to unplug and reseat the device before they were detected in Aida.

I apologize for double-posting. When posting elsewhere I am used to generally receiving a reply either within a day or two never. When I didn't get a reply within a few days, I thought I must have posted in the wrong category, that it belonged in Bug Reports. I won't do it again. I disabled GPU monitoring, closed AIDA64 by selecting End Task in the task manager Processes tab (where it appeared only as a background process), and restarted AIDA64. The Sensor Panel froze about half an hour later. When I selected End Task in the task manager Processes tab, the Sensor Panel closed and the AIDA64 icon disappeared from the system tray, but the Processes tab still shows AIDA64 running as a background process, and selecting End Task in the Details tab wouldn't work. Based on other attempts to close AIDA64, it seems possible that I didn't really restart it after disabling GPU monitoring. I'm about to reboot and try again and will report the results.

I wanted to create something that wasn’t techno-aggressive. An image from the internet + ChatGPT, and the new dashboard 1024x600 is ready.

Apologies, error on my side. I had to reseat the device before the current values were detected. Although I'm able to see the sensors and add them to my panel, I do notice that when I open the Aida app from the taskbar or even after a few minutes, the sensors disappear. Refreshing sensors and restarting both Wireview and Aida doesn't fix it, nor does closing Wireview so that Aida is the only app running. A reboot seems to be the only way to restore them.

Please avoid opening multiple topics for a single issue. I've replied in your other topic. This topic is closed.

In order to narrow this down, first please disable GPU monitoring in AIDA64 / Preferences / Stability / GPU sensor support, and let us know if it makes a difference. Make sure to restart AIDA64 after altering that option.

Can you see the voltage and current readings similarly labelled on the Computer / Sensor page of AIDA64?

Where did you find these? I dont even see them and no setting for wireview.

Could you share it, friend?

I attempted to modify my panel tonight and it appears that just the power values for the device are being captured (see screenshot). What I, and I think others that are interested in seeing, are the current values per pin. It could be that the device isn't detected perhaps? Is there anything that has to be enabled to see these values? If the device is indeed detected, is there a way to enable a view of the current for each pin?