Our UWP app calls the Windows API ASHWID (Application Specific Hardware ID) to retrieve the device UUID for uniquely identifying the tablet. However, an anomaly occurs where this value cannot be fully or correctly retrieved under certain conditions:
After a device reboot, all hardware information can only be read for the first 2 to 3 minutes. After this timeout period, it becomes impossible to retrieve BIOS-related ID information.
Additional Troubleshooting Observations
- Executing the WMI command
wmic csproduct get UUID consistently returns the correct value.
- Querying
Win32_ComputerSystemProduct.UUID via PowerShell also works normally.
- The operating system itself is able to successfully read the device's BIOS UUID.
- Only the
ASHWID API fails to return the BIOS identifier after 2–3 minutes post-reboot. The issue is temporarily resolved by restarting the device.
Troubleshooting Tests Performed
- Changed the power plan to "Ultimate Performance" mode.
- Performed a clean boot.
- Performed a clean boot with all non-essential applications stopped (including OEM power management software).