[QUESTION] - Windows 10 ISOs created with svf-patch do not match?

Discussion in 'Windows 10' started by Lexar, Dec 29, 2016.

  1. Lexar

    Lexar MDL Novice

    Nov 17, 2013
    16
    1
    0
    Hallo experts,

    I have created some Windows and Office ISOs with svf-patches. (Thanks for the patches).
    The sha1-hash matches with the value on msdn.
    But when I verify the ISOs with "Windows and Office Genuine ISO Verifier" or "MSDN File Verfier by Inge" I get the information, that the file does not match (both programs show the correct hash).
    Can someone explain it, please?
     
  2. l33tissw00t

    l33tissw00t MDL Addicted

    Dec 6, 2012
    699
    423
    30
    Maybe it's also checking filename? Can you post a screenshot?
     
  3. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    17,295
    22,010
    340
    At least give us the info about what exactly you try to verify. When the sha-1 matches with the ones on MSDN then it is the correct one.

    Filename is not part of the checksum, that shouldn't matter.
     
  4. Lexar

    Lexar MDL Novice

    Nov 17, 2013
    16
    1
    0
    Here are screenshots from two files.
    w**65.zippyshare.com/v/Pulf5OOg/file.html

    I have just seen that only files from VLSC are affected. That explains why "MSDN File Verfier by Inge" does not show matching files. It can only handle with MSDN.
    But "Windows and Office Genuine ISO Verifier" works with both, MSDN and VLSC files.
     
  5. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    17,295
    22,010
    340
    Why post screenshots on zippy...?

    Do you have the downloadlink for that iso verifier?
     
  6. Lexar

    Lexar MDL Novice

    Nov 17, 2013
    16
    1
    0
    Windows and Office Genuine ISO Verifier => h**p://genuineisoverifier.weebly.com/
     
  7. LostED

    LostED SVF Patch Lover

    Jul 30, 2009
    4,794
    11,425
    150
    then you are OK


    maybe those need to update with the latest checksums
     
  8. Lexar

    Lexar MDL Novice

    Nov 17, 2013
    16
    1
    0
    #10 Lexar, Dec 30, 2016
    Last edited: Dec 30, 2016
    (OP)
    Now I have studied the "Windows and Office Genuine ISO Verifier" with an editor and I could find that it doesn't contain all of the VLSC hashes, so it reports a mismatch for some ISOs.
    Thanks to GezoeSloog for the hint.