FIX FOR: Your PC does not have sufficient unique identifiers available. , Get Win UUID failed. , Get M/B info failed.

Aug 14, 2018
3
7
1
34
Gamertag
Fragger321
#1
Hi everyone! I had this exact problem and I figured out a solution! It actually wasn't as hard as you may think. I'm a server/system admin and do freelance web design and stuff. I'm used to messing with stuff and figuring out fixes for things.

THIS ALSO FIXED THE ISSUE WHERE MY NVIDIA GEFORCE NOW WOULDN'T LAUNCH. IF YOU HAVE ISSUES WITH NVIDIA GEFORCE NOW THIS IS A FIX FOR IT AS WELL.


Step 1:

For whatever problem you get. Go here first:

"C:\Games\Halo 2 Project Cartographer\h2onscreendebug.log"

If you are getting any of these errors:

Could not connect to ROOT\CIMV2. Error code = 0x80070422
Get Win UUID failed.

Could not connect to ROOT\WMI. Error code = 0x80070422
Get M/B info failed.

Insufficient PC Identification! - Your PC does not have sufficient unique identifiers available. Please contact an admin about linking this PC with another that you own that does have sufficient info. This is to ensure fair online play.

This means that your computer cannot serialize a number (your motherboard's GUID/UUID and convert it/parse it to a string or an array of bytes so the game can authenticate/handshake your machine). Windows does this the same to stop pirating and hacking and what not. Lots of other companies are doing this as a way to ensure bans even if you change your IP.

If you have any of the errors above, please continue to step 2.




Step 2:

Check if these 2 services posted below are running in windows first before doing anything else.

To get here do these steps: Start->run->services.exe->right click and run as administrator

2.png




Step 3:

Make sure that this is the response back you get in an elevated command prompt window which is posted below.

To get here do these steps: Start->run->cmd.exe->right click and run as administrator


1.png

https://docs.microsoft.com/en-us/windows/desktop/wmisdk/winmgmt

Go here and make sure to salvage your repository then verify it after doing Step 2 if you do not see the same responses above.



Step 4:

Go back to step 3 until it looks like this screen and restart. Your game should work now!
 
Dec 16, 2024
3
1
3
25
Gamertag
Esemes16
#6
This article was a great help! Though the one issue I did have is that my log file was not in the same place, after a full scan of my system I found it in the C:\Users\*server or user username*\AppData\Local\Microsoft\Halo 2\logs\... and since I am running a server it was in the H2Server\instance# subdirectory.

Edit: fixed missing directory
 
Last edited:
Dec 16, 2024
3
1
3
25
Gamertag
Esemes16
#7
The problem I had is that the KVM hypervisor doesn't natively passthrough the SMBIOS attributes required. The fix I found on a fourm post from 10 years ago, was to run the dmidecode (use the -t1 and -t2 modifiers to filter for just the type 1 and 2 attributes) command on my hypervisor, grab the DMITYPE 1 and 2 attributes and put them in the XML configuration file on the hypervisor. I am using KVM through Fedora Server Cockpit, so the file was located in /etc/libvirt/qemu/ServerName.XML

However the way to add the data to the VM is through the following commands, after you have shutdown the VM and rebooted the hypervisor:
sudo qemu-system-x86_64 -smbios type=1,serial=YourSerialNumber,manufacturer=YourManufacturer,version=YourVersion
sudo qemu-system-x86_64 -smbios type=2,manufacturer=YourManufacturer,version=YourVersion,serial=YourSerialNumber,product=YourProductID

Edit:
Though if this doesnt work the third link below includes how to add the values into the configuration file manually.

Edit 2:
I've been fighting with this for a week and finally found the solution, before installing/creating/initializing the VM, ensure the firmware is set to UEFI and not BIOS, since its more compatible with newer technologies... like standardized formatting and transfer of SMBIOS data.

Sources:
https://forum.proxmox.com/threads/smbios-kvm-feature.2912/
https://gist.github.com/smoser/290f74c256c89cb3f3bd434a27b9f64c (though some of the Linux paths are incorrect and it uses the Windows paths, eg: sys_vendor is actually manufacturer)
https://libvirt.org/formatdomain.html#smbios-system-information
 
Last edited:
Likes: Berthalamew