ASHWID Change

Question

Hi,

Based on my previous thread here, related to ASHWID (memory parameter change)

https://learn.microsoft.com/en-us/answers/questions/5559036/ashwid-%28fluctuation%29-issue-in-certain-windows-11-m?source=docs

The memory parameter is being changed when the laptop is switched from one Dell Docking station to another Docking station. How switching can cause this? This was working for a very long time. only recently we are getting this issue with some customers.

And the processor parameter in ASHWID can also change (Apart from replacing the procesor) ?

Answer 1

Hi @Raja Shanmugam ,

Thanks for reaching out.

From what you described, this behavior can be confusing at first, but it aligns with how Windows generates hardware identifiers like ASHWID. ASHWID doesn’t use fixed physical serial numbers - instead, Windows hashes hardware information that it reads from the system firmware (SMBIOS) and the operating system at runtime. Because of that, it’s sensitive to how the hardware is reported, not just whether the physical parts have changed. For context on how Windows reads hardware information from firmware, see the SMBIOS documentation here:

https://learn.microsoft.com/en-us/windows-hardware/drivers/bringup/smbios

and also this page about how Windows reads hardware information:

https://learn.microsoft.com/en-us/windows/win32/sysinfo/getting-hardware-information

When switching between different Dell docking stations, the system may re‑enumerate hardware and change the way memory information is reported by the firmware or drivers - even if the memory modules themselves are unchanged. Slight differences in what Windows reads can result in a different hash for the memory portion of the identifier.

Similarly, the processor portion of the identifier can change without replacing the CPU. Windows retrieves processor details such as architecture, processor ID, and other attributes via APIs like GetSystemInfo or the Win32_Processor class (which itself reads information from SMBIOS). For more information, see:

https://learn.microsoft.com/en-us/windows/win32/api/sysinfoapi/ns-sysinfoapi-system_info

https://learn.microsoft.com/en-us/windows/win32/cimwin32prov/win32-processor

If firmware/BIOS reports slightly different processor information, the resulting hash can change.

In short, ASHWID isn’t guaranteed to remain stable through all hardware state changes, especially with external hardware like docking stations involved. For scenarios requiring a stable machine identity, it’s recommended not to rely on ASHWID alone as an absolute identifier.

Hope this helps! If my answer was helpful - kindly follow the instructions here so others with the same problem can benefit as well.

Answer 2

The ASHWID (Application Software Hardware ID) can be influenced by various hardware changes, including switching docking stations. When a laptop is connected to different docking stations, it may detect changes in hardware configurations, such as memory parameters, which can lead to fluctuations in the ASHWID. This is because the docking stations may have different configurations or capabilities that the operating system recognizes, affecting how the hardware is reported.

Regarding the processor parameter in ASHWID, it is generally expected that this parameter would only change if the physical processor is replaced. However, certain system updates or changes in the operating environment could potentially lead to variations in how the processor is identified by the system, even without a physical replacement. This might include changes in BIOS settings or updates that modify how the system interacts with the hardware.

---

References:

• Resolved issues in Windows 11, version 24H2
• The %NUMBER_OF_PROCESSORS% environment variable may show incorrect values