[SOLVED] BIOS modded and activated: Today, "Windows is not genuine" pops up

Discussion in 'Windows 7' started by riahc3, Nov 2, 2010.

  1. riahc3

    riahc3 MDL Addicted

    Jul 29, 2009
    547
    34
    30
    But here is the thing: Before using the Dell cert (I copy them on my C:\ and run the commands) there was indeed a Asus cert there which I used to activate it when I installed it the first time this summer.

    Something really WTF is going on...
     
  2. riahc3

    riahc3 MDL Addicted

    Jul 29, 2009
    547
    34
    30
    And, while I think the topic on WHY this happened of of a sudden and the Asus cert/Dell SLIC is important, Im not sure if any want to talk about it.
     
  3. NoJuan999

    NoJuan999 Experienced SLIC Tool Operator

    Jul 31, 2009
    9,918
    1,935
    300
    #63 NoJuan999, Nov 2, 2010
    Last edited: Nov 3, 2010
    The Only thing I can think of is that you first Flashed a Bios Mod with ASUS SLIC 2.1
    and later Flashed an Updated Bios Mod with Dell SLIC 2.1.
    What MB do you have ?
    An ASUS P5B Deluxe or P5B Deluxe/Wifi-AP ???
     
  4. Phazor

    Phazor MDL Expert

    Sep 1, 2009
    1,144
    518
    60
    What i wonder is, what computer is this?

    Make? Model?

    All the BIOS tables seem to be DELL, so wouldnt that suggest that it is a DELL machine?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. NoJuan999

    NoJuan999 Experienced SLIC Tool Operator

    Jul 31, 2009
    9,918
    1,935
    300
    His MGADiag Reports shows:
    <BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>1238</Version>
    And the Only Bios I see with that Version Number is for the MBs I listed above.
     
  6. riahc3

    riahc3 MDL Addicted

    Jul 29, 2009
    547
    34
    30
    A Asus P5B Deluxe.
     
  7. s7ven

    s7ven MDL Novice

    Mar 12, 2010
    2
    0
    0
    A friend had the same issue. He used WATfix and followed the steps from post 18 and the OS was validated again.
     
  8. WeAreNotAlone

    WeAreNotAlone MDL Member

    Aug 31, 2007
    114
    13
    10
    #68 WeAreNotAlone, Nov 28, 2010
    Last edited: Nov 28, 2010


    RE: 6-pages...

    I noticed the thread title says "Solved"...

    I also noticed the opening post has not been edited to reflect how the issue was solved, nor does the OP state what MB is being used (till the end of the thread-post #66)

    Just a suggestion- In this thread it took till page 6 to find out MB ID.

    About about a rule that the opening post:

    A: Contains MB model ID /PC model ID info (In body of text of opening post, so problem, and fix are *permanently* tied to that ID string)
    B: Is edited with the "fix" info once a working solution is confirmed.

    I think the above would save everyone alot of time, help those searching also.

    ***********
    Regarding "A" with system info in BODY of opening post..

    Besides greatly reducing confusion, and providing much needed info for those trying to help, and helping those searching via ID strings.... It does away with problems created on some boards in which the thread is greatly devalued in worth when the OP relies upon their signature to convey system info- when sig is changed. (EG: Net result is "fixes" no longer match up with hardware being talked about)
    .
     
  9. Gradius

    Gradius MDL Member

    Jul 30, 2009
    198
    10
    10
    #71 Gradius, Jan 4, 2011
    Last edited: Jan 4, 2011
    Guys, I have the same problem with Asus, the cert (asus.XRM-MS) is wrong, I'm trying to find the correct one, so far, no luck!

    Bad one is (desktop?):
    File: ASUS.XRM-MS
    CRC-32: 4e12df85
    MD4: db063e011ce1df31942e76573870b854
    MD5: 1554e3a58b4d344db7f864d8612ec385
    SHA-1: c26597bfa66605b28ccf13638530c185cd52ff93

    Bin used:
    File: ASUS.BIN <- notebook!
    CRC-32: af40cf7a
    MD4: 0fe7126111aac14c8e79cb525a509c07
    MD5: 4d2ff85772164180814cf1a46a7ec906
    SHA-1: 1540c211aea9b66e338e37d75c75cb52d002a4a1

    Edit: Solved!

    I managed to find the correct cert (notebook):
    File: ASUS-_ASUS_-2.1.XRM-MS
    CRC-32: e1948081
    MD4: 3e2deb87b934ad7d230efea50f186e81
    MD5: 195ba525f938bd06ce2f4844a16ddced
    SHA-1: 5d3ae3e7f3d8a705678cb1c5830c55e995db332b