OEM Recovery Partition Creator for Windows

Discussion in 'MDL Projects and Applications' started by AnarethoS, Sep 11, 2010.

  1. tcntad

    tcntad MDL Guru

    Oct 26, 2009
    4,324
    1,414
    150
    it may have been the in earlier versions but i believe there is no general need for it
     
  2. Chibi ANUBIS

    Chibi ANUBIS MDL Chibi Developer

    Apr 28, 2014
    1,156
    833
    60
    Please ignore the ei.cfg is not very important
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. AnarethoS

    AnarethoS MDL Expert

    Jul 31, 2009
    1,229
    1,472
    60
    Oups, my bad. Probably moved the file rather than copying it.

    The EI.CFG is manly to "unlock" other version of Windows 10/11 when you have a registered key in the BIOS and when you don't whant to use the autounattend.xml method.

    So 99% (random number lol) of the time you won't need it.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. AnarethoS

    AnarethoS MDL Expert

    Jul 31, 2009
    1,229
    1,472
    60
    I have repackaged 5.0.4 to add back the Ei.cfg example file.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. sneakychrono

    sneakychrono MDL Novice

    Jan 2, 2013
    12
    1
    0
    Hi Everyone, and thank you AnarethoS for all the work you have put into this. I just ran into this issue and wanted to know if someone can help me.

    In section 12.5 in the PDF when I executed "Install-Windows 1X.cmd" I got an error saying the scanstate.exe or config_appsandsettings.xml was missing.

    Both the x86 and amd64 folder only had their respective scanstate.exe only because originally those folders were empty.

    So I went and created a blank file named Config_AppsAndSettings.xml. After that, I was able to execute "Install-Windows 1X.cmd" with no errors.

    Now when I execute "Sysprep.cmd" from C:\Recovery\OEM, I am able to make all the choices and at the end, after I choose choice 1 to confirm, I get a scanstate.exe - system error.

    it says "The code execution cannot proceed because unbcl.dll was not found" after clicking the OK button I get the same error prompt but instead of unbcl it says migcore.dll was not found.


    I am using Windows 11 to do this. I got the scanstate from the user state migration tool from the Microsoft website from the ADK tools.

    Any help will be appreciated.

    Thank you.
     

    Attached Files:

  6. mhussain

    mhussain MDL Member

    Oct 1, 2012
    249
    84
    10
    hi, what is the password for the 2 files?
    cheers.
     
  7. tcntad

    tcntad MDL Guru

    Oct 26, 2009
    4,324
    1,414
    150
    On the first "page" of the install
     
  8. Raksith N

    Raksith N MDL Novice

    Dec 22, 2021
    23
    8
    0
    Hello there, it's been long time. I have a big problem, I am using push button reset to create oem image. When i create and shutdown, take an image using paragon hard disk manager and then restore it to another device which hardware is exactly same as the once i used for creating image. But unfortunately it is not working because after cloning the bcd store is getting changed and cannot boot to recovery partition. Any sugestions? I am stuck here
     
  9. Raksith N

    Raksith N MDL Novice

    Dec 22, 2021
    23
    8
    0
    I tried backing up and restoring bcd store from windows command, but no use not working.
     
  10. Raksith N

    Raksith N MDL Novice

    Dec 22, 2021
    23
    8
    0
    #3550 Raksith N, Jun 16, 2022
    Last edited: Jun 16, 2022
    Any update guys? waiting for your reply thanks in advance
     
  11. Flipp3r

    Flipp3r MDL Expert

    Feb 11, 2009
    1,834
    828
    60
    There must be an issue with your cloning. There's no other reason for it to fail.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. Raksith N

    Raksith N MDL Novice

    Dec 22, 2021
    23
    8
    0
    Ohh ok yeah you are correct when i create it on one machine it works fine but when i clone it to other one this issue is coming, any idea how to fix this? Earlier it was working but not fails every time. Already tested 20 times now :sad:
     
  13. Raksith N

    Raksith N MDL Novice

    Dec 22, 2021
    23
    8
    0
    In bcdedit /enum all it is showing unkown value for some of the items.
     
  14. Raksith N

    Raksith N MDL Novice

    Dec 22, 2021
    23
    8
    0
    Here is the output of bcdedit /enum all

    Firmware Boot Manager
    ---------------------
    identifier {fwbootmgr}
    displayorder {bootmgr}
    {1543b147-ecfb-11ec-987c-d83e2d3d2c60}
    timeout 1

    Windows Boot Manager
    --------------------
    identifier {bootmgr}
    device partition=\Device\HarddiskVolume2
    path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
    description Windows Boot Manager
    locale en-US
    inherit {globalsettings}
    default {current}
    resumeobject {1543b149-ecfb-11ec-987c-d83e2d3d2c60}
    displayorder {current}
    toolsdisplayorder {memdiag}
    timeout 30

    Firmware Application (101fffff)
    -------------------------------
    identifier {1543b147-ecfb-11ec-987c-d83e2d3d2c60}
    description Hard Drive

    Windows Boot Loader
    -------------------
    identifier {current}
    device partition=C:
    path \Windows\system32\winload.efi
    description Windows 10
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {1543b14b-ecfb-11ec-987c-d83e2d3d2c60}
    displaymessageoverride Recovery
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice partition=C:
    systemroot \Windows
    resumeobject {1543b149-ecfb-11ec-987c-d83e2d3d2c60}
    nx OptIn
    bootmenupolicy Standard

    Windows Boot Loader
    -------------------
    identifier {1543b14b-ecfb-11ec-987c-d83e2d3d2c60}
    device ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{1543b14c-ecfb-11ec-987c-d83e2d3d2c60}
    path \windows\system32\winload.efi
    description Windows Recovery Environment
    locale en-us
    inherit {bootloadersettings}
    displaymessage Recovery
    osdevice ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{1543b14c-ecfb-11ec-987c-d83e2d3d2c60}
    systemroot \windows
    nx OptIn
    bootmenupolicy Standard
    winpe Yes

    Resume from Hibernate
    ---------------------
    identifier {1543b149-ecfb-11ec-987c-d83e2d3d2c60}
    device partition=C:
    path \Windows\system32\winresume.efi
    description Windows Resume Application
    locale en-US
    inherit {resumeloadersettings}
    recoverysequence {1543b14b-ecfb-11ec-987c-d83e2d3d2c60}
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    filedevice partition=C:
    filepath \hiberfil.sys
    bootmenupolicy Standard
    debugoptionenabled No

    Windows Memory Tester
    ---------------------
    identifier {memdiag}
    device partition=\Device\HarddiskVolume2
    path \EFI\Microsoft\Boot\memtest.efi
    description Windows Memory Diagnostic
    locale en-US
    inherit {globalsettings}
    badmemoryaccess Yes

    EMS Settings
    ------------
    identifier {emssettings}
    bootems No

    Debugger Settings
    -----------------
    identifier {dbgsettings}
    debugtype Local

    RAM Defects
    -----------
    identifier {badmemory}

    Global Settings
    ---------------
    identifier {globalsettings}
    inherit {dbgsettings}
    {emssettings}
    {badmemory}

    Boot Loader Settings
    --------------------
    identifier {bootloadersettings}
    inherit {globalsettings}
    {hypervisorsettings}

    Hypervisor Settings
    -------------------
    identifier {hypervisorsettings}
    hypervisordebugtype Serial
    hypervisordebugport 1
    hypervisorbaudrate 115200

    Resume Loader Settings
    ----------------------
    identifier {resumeloadersettings}
    inherit {globalsettings}

    Device options
    --------------
    identifier {1543b14c-ecfb-11ec-987c-d83e2d3d2c60}
    description Windows Recovery
    ramdisksdidevice unknown
    ramdisksdipath \Recovery\WindowsRE\boot.sdi
     
  15. Flipp3r

    Flipp3r MDL Expert

    Feb 11, 2009
    1,834
    828
    60
    Why don't you use this feature provided by the recovery package?
    -USB recovery media creator in Windows 7/8/10
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. Raksith N

    Raksith N MDL Novice

    Dec 22, 2021
    23
    8
    0
    Yeah sure but i need to create sysprep image to another device just like OEM setup, to use USB recovery media creator i need to finish OOBE process, i need before it.
     
  17. Raksith N

    Raksith N MDL Novice

    Dec 22, 2021
    23
    8
    0
    Can i use in sysprep mode or from any Winpe? Just like cloning?
     
  18. Raksith N

    Raksith N MDL Novice

    Dec 22, 2021
    23
    8
    0
    All right my problem is solved using another solution to clone, just working fine. Sorry for late reply.
     
  19. Raksith N

    Raksith N MDL Novice

    Dec 22, 2021
    23
    8
    0
    #3559 Raksith N, Jun 22, 2022 at 11:00
    Last edited: Jun 22, 2022 at 11:49
    I have another problem, if anybody can help me it would be very helpful. My first boot from Hi to All done takes exactly 10 mins i have ran timer for more than 30 times all same. I have checked logs in windows event viewer one or the other service is waiting for 10 mins like wsvsc, wmi, license activation, windows hello etc i have solved all but it keeps coming every time different errors, when i run the same sysprep from direct windows 10 all working fine. How can i reduce it back to 2-3 mins?
     
  20. tcntad

    tcntad MDL Guru

    Oct 26, 2009
    4,324
    1,414
    150
    But the sysprepped image is already on the machine, that one will be copied to USB, not the live install..