Weird how it had an ACER slic table, which is zsmin loader default. Someone used a loader on your pc, without your knowledge. That's why it was an OEM SLP key
Wow, well I guess I have more to go looking into than I thought. How does a Volume License work? Can other people besides the owner access these keys? Or are you simply trying to say that there's no way this is a coincidence and that I'm SOL for trying to buy a VL key? What exactly is a loader?
THE vl key shown in the diag dump you provided was leaked last year, I am surprised it worked for you. According to the diag, you are genuine, at-least until that key gets blacklisted. You may never have a problem but you may want to read up on the repository so you atleast know what you are dealing with as far as activation.
A loader is something that sits on your computers bootsector and puts a SLIC table into memory before Windows loads Now you need to know what a SLIC table it: A slic table is how OEMs preactivate computers in a factory. THey put a SLIC table in the bios, and windows reads this, and when combined with the correct certificate and oem slp master key, it activates. A loader installer installs the loader, certificate, and master key so your computer thinks its an OEM activated machine. Someone has used a loader on your computer, but just didnt install the correct certificate. If you have an ACER slic, you need an ACER cert. Get it now?
Yes, thank you. I imagine what happened is that this business owner installed the loader and when I flashed my BIOS several weeks ago trying to troubleshoot memory problems it removed said loader thus invalidating Windows. Because Windows gives multiple chances for validation I sat in good status for a while before it finally invalidated. Guess I need to check twice before I go trusting a stranger with my PC.
Flashing your BIOS will not invalidate a loader. The loader dynamically inserts the SLIC every time you start the PC.
Bios flash will not remove the loader. The loader is still there because you can see the SLIC 2.1 from acer in the diagnostic report. The other possibility is that you flashed with a modded bios, where did you get the bios file from?
Or, someone goofed up and installed the wrong key and cert. Just download Daz's loader, and it will make a loader that matches your brand and everything, and is near impossible to detect
I downloaded the BIOS direct from ASUS. I'd prefer to be legit, just gotta get this guy to give me a refund for the fraud.
What I meant was, he told me he purchased a VL and that he goes down a list of keys. That's all I know. Not interested in anything illegal, if I were I certainly wouldn't have paid a business owner to do it for me. Now that would have made me a real tool. As of now I'm just an unwilling tool.
Oh, now I get it! He told you he'd installed a VL key, but used a crack instead. You my friend, have been scamed. This is very common thing for crook OEM builders/repairmen to do.
BTW, No such thing as a VL key technically. You can have some retail keys as set of a VL, or a single MAK key good for a lot of activations, but offline VL keys only existed in XP days.
I have a Gigabye mobo and modded it using the award tool to have a Dell SLIC 2.1. I then installed the Dell key and certificate. Windows has been listed as 'Genuine' for several months. But just today, I got notification that my copy was 'non-genuine'. I have auto-updates turned on, so I assume an update has caused this. I used Daz's loader and did a soft mod, again with the Dell SLIC, key and cert. Windows now reports it is genuine again. It seems Microsoft has been able to detect the modded bios and flag it is non-genuine. However the soft-mod was not detected.
Analysis of the MGADiag report I would like to clear something about the OEM Activation 2.0 Data in the report. First it checks whether the bios is ACPI complaint or not. If true, the results are Here you can see that since there is no SLIC table, so the 2nd and 3rd line are not available. In this result the SLIC table is present and the Marker version is shown as 0x20001. The last line checks for consistency of the OEMID and OEMTableID within the SLIC table and not with the other ACPI tables present in the BIOS. Code: BIOS Information: ACPI Table NameOEMID ValueOEMTableID Value APICACRSYS APIC0946 FACP ACRSYS ACRPRDCT HPET ACRSYS OEMHPET MCFG ACRSYS OEMMCFG SLIC _ASUS_ Notebook OEMB ACRSYS OEMB0946 ASF! AMD SB600ASF SSDT A M I POWERNOW The data presented below BIOS information is a dump of the ACPI tables present in the system along with their OEMID and OEMTableID.
i see it shows the date of the bios installed when it was made at least for mine by the manufacture i wonder if they will kill one's that were out say 2 years ago well before win7 was around?? this is what mine said for the results slic check does this look okay? OEM Activation 2.0 Data--> BIOS valid for OA 2.0: yes Windows marker version: 0x20001 OEMID and OEMTableID Consistent: yes BIOS Information: ACPI Table NameOEMID ValueOEMTableID Value APICDELL APIC1445 FACPA M I OEMFACP MCFGDELL OEMMCFG SLICDELL QA09 OEMBDELL OEMB1445 AAFT070809OEMAAFT GSCI070809GMCHSCI SSDTDpgPmmCpuPm so what happens say you used a toshiba toshinv00 to mode the bios but a different toshiba cert (still a 2.1 version though) installed in windows. would they still be okay both being toshiba? meaning is still says activated but would wat you think pick this up as a miss match or the mgadiag tool?
WAT will not check the BIOS date against anything, it only gathers the information along with other hardware details. It will not activate. You need matching cert for that slic.
Hazar, may I remember that you are a Supermod and you can't afford to use that language...... I'm watching this thread...I hope I don't have to close it. It seems this matter is not discussible... ..kindergarten.... HrOffline: 0x00000000 HrOnline: 0x00000000 offline? It's both zero....it's neither nor...lol.... wat server? How do you know?