How to Creat your own Windows 10 fr _business_editions SVF repository

Discussion in 'Windows 10' started by dubwa, Jun 3, 2018.

  1. dubwa

    dubwa MDL Novice

    Mar 11, 2014
    8
    2
    0
    Hi everybody i'm just a starter here ..i want to creat my own svf repo for

    fr_windows_10_business_editions_version_1803_updated_march_2018_x64_dvd_12064240.iso

    i just want eany tutorial or trick to start wiith it

    and i have some questions :

    1/
    does if i want to make ''fr business.iso''==> i must merge en_business.iso+ fr svf wich is extracted from client consummer i will get fr business.iso ??


    en_business.iso + Svf from fr-client consummer iso =====fr_business.iso true or false ?

    but the problem is Svf from fr-client consummer iso are deffirent from Svf from fr-client business iso


    2/ i saw different svf repo uploaded by @Enthousiast & @GezoeSloog ....the first uploaded by @Enthousiast (fr_windows_10_business_editions 12064240.svf) have 330.89 Mo and the same file posted by GezoeSloog ( cloud.mail...............ru........./public/723S/F8s1RXPWz/) have just 139Mo

    What does that mean !!! ? and how ?
    ???
     
  2. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    16,848
    21,177
    340
    #2 Enthousiast, Jun 3, 2018
    Last edited: Jun 3, 2018
    A svf repo means a collection of svf files.

    It needs smartversion. a source iso and target isos's.

    Gezoesloog uses this route:

    Code:
    EN>XX > XX Consumer > XX Business
    I go this route:

    Code:
    EN Consumer > XX Consumer
    EN Business > XX Business
    So, to create the french business iso using @GezoeSloog svf patches you need these SVF patches from his Repo:
    Code:
    en_windows_10_consumer_editions_version_1803_updated_march_2018_x64_dvd_12063379.iso
    >
    fr_windows_10_consumer_editions_version_1803_updated_march_2018_x64_dvd_12064260.svf
    =
    fr_windows_10_consumer_editions_version_1803_updated_march_2018_x64_dvd_12064260.iso
    >
    fr_windows_10_business_editions_version_1803_updated_march_2018_x64_dvd_12064240.svf
    =
    fr_windows_10_business_editions_version_1803_updated_march_2018_x64_dvd_12064240.iso
    Using my SVF(/SFX) patches it should be (patches from my SVF repo):
    Code:
    en_windows_10_business_editions_version_1803_updated_march_2018_x64_dvd_12063333.iso
    >
    fr_windows_10_business_editions_version_1803_updated_march_2018_x64_dvd_12064240.svf
    =
    fr_windows_10_business_editions_version_1803_updated_march_2018_x64_dvd_12064240.iso
     
  3. dubwa

    dubwa MDL Novice

    Mar 11, 2014
    8
    2
    0
    i'm really thankful for you Mr Enthousiast but i saw some comment of you ..that you are saying that you used evaluation version as source iso ..does evaluation version and official version have the same files and size i mean maybe the evalution version have not all the packages and feautures which obligate customers to buy the official one ....and using it as source maybe is a risq

    same as @GezoeSloog : XX Consumer to XX Business ...

    which better you see ..the first roote or your roote ?
     
  4. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    16,848
    21,177
    340
    I made source packages:
    Enterprise EVAL > EN Consumer
    Enterprise EVAL > EN Business

    The resulting en-US consumer and business iso's are the source packages for the EN Consumer > XX Consumer and the EN Business > XX Business patches.
     
  5. dubwa

    dubwa MDL Novice

    Mar 11, 2014
    8
    2
    0
    aaah i understand now the procedure ..just final question for exemple :

    you have enterprise eval and enterprise official : the only different betwween them the eval one cant be activated after 90 day ...

    does both of them have the same size and features i mean nothing missing in files or features or files ?
     
  6. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    16,848
    21,177
    340
    The install will be the same but the eval can't be activated beyond it's timelimit.

    Never install EVAL editions when you desire to keep it running for longer then 90 days.

    As i've explained, the EVAL > Consumer and Business patches only exist to create the en-US source iso's.
    If you already have the needed en-US source iso's you don't need the EVAL>Consumer and Business patches at all.
     
  7. dubwa

    dubwa MDL Novice

    Mar 11, 2014
    8
    2
    0
    thank you very very very much that's a huge favor i was searching in web for 4 hours for that ...
     
  8. dubwa

    dubwa MDL Novice

    Mar 11, 2014
    8
    2
    0
    a Conclusion : to creat Svf repo for all business iso for all language i must have all MSDN business iso ? and that's how you did ?