A Microsoft platform for building and publishing apps for Windows devices.
I am currently working the issue and will provide an update soon. Thank you for your patience.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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
wmic csproduct get UUID consistently returns the correct value.Win32_ComputerSystemProduct.UUID via PowerShell also works normally.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
A Microsoft platform for building and publishing apps for Windows devices.
I am currently working the issue and will provide an update soon. Thank you for your patience.
HI @Xie Steven ,
ASHWID does not have a fixed length. Its components and ordering may change depending on the hardware detected at the time of the call.
I recommend not relying on the BIOS component alone. If a stable device identifier is required, please consider using SystemIdentification.GetSystemIdForPublisher(). If ASHWID must be used, each component should be parsed separately and the application should tolerate hardware drift.