I'm preparing to retire after 35 years in IT and need to resolve one last issue for a client. The client has four HP desktops in a peer-to-peer network with no server or domain. Two machines were delivered with the same vendor image and SID, and they're having problems setting up a basic SMB share. I recommended reimaging one of the PCs with a generalized image to give it a unique SID. The reinstall completed, but Windows 11 will no longer activate. The edition matches the original installation, and I verified the OEM product key embedded in the HP firmware, but Windows reports that the key is invalid. The client only has the OEM licenses that came with the PCs and no volume licensing. What's the best way to restore activation before I hand the computer back?
3 Answers
First confirm that the reimage installed the exact edition the PC was licensed for, such as Windows 11 Pro versus Home. An OEM key embedded in the firmware should normally activate automatically when the matching edition is installed. If it does not, connect the machine to the internet, run the Activation troubleshooter, and check whether it detects a digital license. If that still fails, Microsoft support can verify the HP entitlement and help with activation.
Since these are individually licensed OEM PCs, a volume MAK or KMS key would not apply. I’d avoid unofficial activation scripts or inexpensive gray-market keys. Verify the product key and edition using the built-in licensing commands, reinstall the correct HP/OEM edition if necessary, and escalate to HP or Microsoft if the firmware key is being rejected.
For future deployments, use Sysprep with the Generalize option before capturing or duplicating an image. That creates a new machine identity and avoids cloning the same SID. It’s also worth noting that identical SIDs are not usually the only cause of Windows file-sharing problems; check duplicate computer names, network profiles, credentials, share permissions, and firewall settings as well.
There’s no volume licensing involved here—the client has only four standalone HP systems with their original OEM licenses, so I’ll focus on confirming the installed edition and having Microsoft or HP validate the embedded entitlement.