Fiery

What screen do you have?

Where do you get that error message? On a certain page of AIDA64? At AIDA64 startup?

AIDA64 doesn't have administrator privileges on your configuration right now. It means it cannot use most of its low-level hardware access functions. Try to check why that's the case. E.g. your Windows user lacks admin privileges. Or AIDA64 wasn't properly installed and certain files required to activate admin privileges are missing.

Thank you for your feedback!

Have you tried it with the latest AIDA64 release of v6.60 too?

Thank you! Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.

We've fixed the SanDisk Plus SSD entries in our SSD hardware database by making it less specific, in order to cover all versions of this very peculiar SSD https://www.aida64.com/downloads/latesta64xebeta

Are you using Win10 or Win11?

Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery

AIDA64 doesn't support aggregating network speeds from multiple computers.

Yes, the latest version of AIDA64 v6.60 supports all Alder Lake variants.

It's quite a tough one since many things could go south in the very complex sensor module of AIDA64 Please try to disable GPU sensor support on the Stability page as well. If it doesn't help, then we will need to disable some more to find the culprit. Thank you for your patience about this issue.

What motherboard do you have? I assume it's a desktop video card. Please let me know if by any chance it's the mobile (laptop) version of RTX 3080 Ti.

Try to disable the option DIMM thermal sensor support in AIDA64 / main menu / File / Preferences / Stability. Let me know if it helps.

Make sure to tick (enable) "Show sensor icons" on the top of the Sensor Icons page of Preferences too

What motherboard and CPU do you have?

The download link in the opening post should still work.

Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Also right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

Memory information is shown on the Motherboard / Memory page in AIDA64.

We don't know that display and we're not affiliated with the guy or company who's selling it on Amazon. Try to ask him for guidelines on how to set it up.

I suppose the SensorPanel Manager opens on another, currently inactive monitor or some other part of the Windows Desktop that's not visible. Try to open Registry Editor (run REGEDIT.EXE), navigate to: HKEY_CURRENT_USER\Software\FinalWire\AIDA64 And remove the following entries: SensorPanelMgrPosX SensorPanelMgrPosY SensorPanelMgrWindowSizeX SensorPanelMgrWindowSizeY That should reset the SensorPanel Manager window position and dimensions and should make you see it and use it again.

This is due to a new sandboxing/virtualization feature of Win11 called Memory Integrity. You need to disable that feature to make the BCLK and CPU core clock measurement of AIDA64 indicate the right values. We're working on a workaround for this issue.

Try it without the backslash after $HOSTNAME, also by putting it between " and ", so like this: /R "\\FILESERVER\install\TEMP\audit 2018\aida\$DATE\$HOSTNAME" /CSV /AUDIT /SAFE /DELAY 30 The space character in audit 2018 may have mixed it up