If it doesn't work and if you are sure that you used the OEMBIOSCHANGER correctly, then your last resort is antiwpa3 (included in the extracted OEMBIOSCHANGER folder in C drive). It will validate your windows. But, the only defect in it, is antivirus flag it as a virus, while it is not, it is a false positive, so, don't worry about it, just exclude it from antivirus scanning... FYI, the OEMBIOSCHANGER is the most powerful method, so, be sure to make it right. Use option number 1 when you open OEMBIOSCHANGER tool and check what what is the Slip string and CRC value and copy the appropriate bios files (uncompressed or compressed) and run OEMBIOSCHANGER tool and check again.
No. The tool will sometimes change the serial without changing the oembios files. The non genuine will go away after you validate with the correct OEMBIOS fileset, OEM serial, and OEM text string in bios. Not "permanent".
medic, I'm running windows 7 and VMware with windows xp professional. I wanted to use oem_bios_changer on my VMware (with windows xp professional) and I got the same way here as our friend, Parry... Is it right to use oem_bios_changer in a VMware? If yes, I checked and found that there's no SLP string in my MB. So, how do I insert it? (I don't want to flash) Information: - I have a Dell Optiplex 745 desktop pc. - I run windows 7 professional. - I run VMware and have windows XP professional on it. Thank you in advance...
I cant see the pics..upload them or add them larger. If it says legit then thats it. If yo have a gigabyte string and you use the tool correctly, you will be genuine...period. There is no reason to use the antiwpa if you have the slp strings added top your vmware bios. There is no flash necessary to add the strings to your board bios either..please note that the vmware has its own bios unless you use the passthrough feature. There is no WGA for xp 64 bit.
Seems like bad file host, a blank page is returned whenever I try to download the changer. Hope a new host can be found!