Fiery

Thank you for the feedback.

Thank you for the feedback. And yes, feel free to send us an email with your questions.

We've issued an update to the AIDA64 UWP app in the Windows Store, and it's already available for download. It includes the mentioned workaround to avoid the crash on the Windows page.

We've issued an update to the AIDA64 UWP app in the Windows Store, and it's already available for download. It includes the mentioned workaround to avoid the crash on the Windows page, and also the necessary tweakings about your Xiaomi device.

Have you tried to restart Windows and reinstall RTSS? I don't know of other software that could output AIDA64 readings to a full-screen OSD.

Thank you, we'll update the ETA reading to show the ETA string in the next AIDA64 beta update due next week.

Do you mean how to use AIDA64 for network monitoring and network management? If yes, then it would be best if you could go through the following documents: http://www.aida64.co.uk/sites/default/files/public/download/documents/en/aida64business-setupguide.pdf http://www.aida64.co.uk/sites/default/files/public/download/documents/en/aida64business-manual.pdf Also there's the Domain Network Installer: http://www.aida64.co.uk/domain-installer Regards, Fiery

Yes, you can import all your old settings and your entered license key by backing up and restoring the AIDA64.INI and PKEY.TXT files. But, you can also just take the new beta ZIP package and extract it to your existing AIDA64 installation folder. Let it overwrite any existing files. It will retain your existing settings and license.

We've now tested it with 3 different devices, and as I've suspected, it's a platform issue. It comes up only on certain devices -- and not all devices --, because the Windows 10 Mobile Insider Preview upgrade wasn't performed properly. If you upgrade from WP8.1 or another Win10 Preview, and you don't perform a device reset (Settings / System / About / Reset your phone), then all kinds of weird things may happen. Now we've done the improper upgrade flow on 3 devices, and all 3 devices crash on the Windows page of AIDA64. While previously, when we performed the "Reset your phone" step after every preview build upgrade, no such crash happened on the same devices of ours. I of course understand that it's not easy to perform such reset operations on a device in use, but if you skip that step, Win10 preview builds will not function 100%. We will try to come up with a workaround in the next AIDA64 app update.

Thank you for the info. We've now tested it with 3 different devices, and as I've suspected, it's a platform issue. It comes up only on certain devices -- and not all devices --, because the Windows 10 Mobile Insider Preview upgrade wasn't performed properly. If you upgrade from WP8.1 or another Win10 Preview, and you don't perform a device reset (Settings / System / About / Reset your phone), then all kinds of weird things may happen. Now we've done the improper upgrade flow on 3 devices, and all 3 devices crash on the Windows page of AIDA64. While previously, when we performed the "Reset your phone" step after every preview build upgrade, no such crash happened on the same devices of ours. I of course understand that it's not easy to perform such reset operations on a device in use, but if you skip that step, Win10 preview builds will not function 100%. We will try to come up with a workaround in the next AIDA64 app update.

BTW, on your Lumia 920 did you perform a device reset after upgrading to Windows Mobile Preview Build 10581?

We'll try digging deeper to find where the problem might be. It's not easy, since we don't do anything special on the Windows page, and it works under 10581 on our test devices (Lumia 535, Lumia 930, and various PCs as well). And since another user reported similar crash on the Windows page, with a Lumia 930 running Windows 10 Mobile Preview, and since with a similar device and similar Windows build it's working fine for us, I'm leaning towards putting the blame on Windows 10 Mobile Preview. BTW, did you perform a device reset after upgrading to Windows Mobile Preview Build 10581 on all 3 devices? Thanks, Fiery

Thank you

Yes, we can switch from the current ETA seconds to the new ETA string. But make sure to properly specify the string type. Is it Ansi string or Unicode or UTF-8? It would also be great to improve the accuracy of the shared memory fields description by specifying whether they are signed or unsigned values, and also their endianness.

Thank you for the feedback. I'm afraid custom formatting for hardware monitor values is not possible.

You can download the mentioned new AIDA64 Extreme beta update from: http://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.

You can download the mentioned new AIDA64 Extreme beta update from: http://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.

You can download the mentioned new AIDA64 Extreme beta update from: http://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.

You can download the mentioned new AIDA64 Extreme beta update from: http://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.

Thank you, we've implemented the requested new hardware monitor items in the latest beta version of AIDA64 Extreme available at: http://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.

Thank you, got that, and already applied the necessary tweakings. I thought it was you, but wanted to confirm Thanks for the info, we'll try digging deeper to find where the problem might be. It's not easy, since we don't do anything special on the Windows page, and it works under 10581 on our test devices (Lumia 535, Lumia 930, and various PCs as well). BTW, since another user reported similar crash on the Windows page, with a Lumia 930 running Windows 10 Mobile Preview, and since with a similar device and similar Windows it's working fine for us, I'm leaning towards putting the blame on Windows 10 Mobile Preview. No, we don't, but I'm happy to explain the inner workings of our app, up to a certain degree.

Please note that on Windows Phone and Windows 10 Mobile it's not possible to detect CPU directly due to the strict sandboxing that is enforced by those operating systems. So both the legacy AIDA64 Windows Phone 8.1 app and the new AIDA64 UWP (Universal Windows Platform) app have to rely heavily on their built-in hardware databases. Which in your case doesn't seem to include the device in question. Please submit a report from the About page, and we will add your device to the hardware database of the AIDA64 app, and also fine-tune the CPU detection module to provide more information on your SoC. If you need further clarification on how the AIDA64 apps work, please feel free to ask either here in the public forum, or in private message. As for the Lumia 920 issue, please let me know what operating system does it have installed. Thanks, Fiery

Thank you for your feedback. We do have plans about localizing the Windows 10 Universal AIDA64 app in the future. We do not have plans to further improve the legacy Windows Phone 8.1 AIDA64 app though. We've recently ported the AIDA64 app to the new Windows 10 UWP (Universal Windows Platform), and we continue improving the new app; while providing only bug fixes and small improvements for the legacy Windows Phone 8.1 app. Regards, Fiery

As far as we're aware of, mobile platforms do not support such interrogation, so it's not possible to make an app for it. Regards, Fiery

The requested information will be implemented in the next AIDA64 beta update due in a few days from now.