1 Windows 8.1 Pro Product Key Windows 8.1 Activated Keys 2022 (Updated).If ((byteArray = 1 || byteArray = 2 || byteArray = 3 || byteArray = 9) & byteArray = 0)ĭeviceSerial += byteArray.
CPU ID of the processor || Size of the memory || Serial number of the disk device || BIOS we filter the hardware modules that are unlikely to be changed, and aggregate them to a string. Var byteArray = .copyToByteArray(hardwareToken.id) Var hardwareToken = .getPackageSpecificToken(null) the code is based on a code from this thread // get the hardware Profile id and convert it to byte Array Here is a code example in JavaScript that filters form ASHWID the hardware modules that are unlikely to be changed (CPU id, size of memory, serial number of the disk device and bios) and convert it to string. If this is an issue and if you can't address this properly (for example using a network check) I would suggest you don't support them at all (just quit if you detect a VM). In theory an user can create multiple copies of the same VM with exactly the same hardare and software configuration. If you have to target VMs too then things become more complicated.
If they install a new OS then they have to update your license too (but I would use it combined with something else to be sure they won't use the same OS copy on multiple computers or virtual machines). In this case a good compromise could be the OS serial number (not the MachineGuid).
Again a combination of multiple IDs (chosen carefully) can help you to minimize customers effort when they change their hw/sw setup. You can still use them but you have to put extra care (and code) to manage that situation. In the past MAC address was vastly used for this but mobile devices changed these rules (because it's easy to turn off a NIC). As for an unique identifier for the device you can't be sure nothing will change. I would use a combination of many (stable) IDs.
If you're sure you're targeting a portable device like a phone or a tablet then disk serial number (or CPU ID, if available, or MB or BIOS) may be appropriate too (because it's pretty uncommon they'll change). In this case I would suggest to use the MachineGuid, unless they reinstall the OS they wouldn't have to worry (but do them a favor and provide a way to read back that GUID somewhere).
If with a small hardware change your users won't be able to read their previous files well, they'll be unhappy. In this case you have to think when data may be unrecoverable. You can get this informations through WMI or (if you're targeting WinRT) through specific bytes of the ASHWID structure.
You may even use the S/N of the primary disk (with portable devices it's pretty stable and you may even use it in combination with other serial numbers to build your own ID). This won't help you if he/she completely renew its hardware but it should be stable enough (but you have to define what is enough in your case). If you have to identify a particular device (regardless to the user) you have many options, what I'd prefer to do is to generate an ID using only stable data (S/N from motherboard and BIOS, for example). Identify the user? Check for license? Encrypt data? Each of these has a different "best practice" for ID. What's the proper solution.well it depends on what you have to do with that ID. If you can identify a component you're pretty sure that won't change (motherboard for example) you may use a simple WMI query to get its serial number but you should always provide a fallback because many many MBs returns a fake S/N (and virtual machines may returns always the same one). You can find such ID in HKLM/Software/Microsoft/Cryptography, it's a string named MachineGuid. In the registry there is an unique ID generated during Windows installation and it won't change until you reinstall Windows. If you can't rely on hardware because it's easy to add memory, change disks, add another network card (for example turning on/off bluetooth or wi-fi) then you have to rely on a "software" ID. Yes, there is such ID (but it may not be applicable in your case). No, there is not such ID because (in theory) you can change ANY hardware component so you may get a completely different ID (that's why Microsoft suggest to calculate a score based on ASHWID).