Win10XPE - Build Your Own Rescue Media


  1. Posts : 90
    Windows 11 Pro
       #2681

    Rahulkmr said:
    These are 4-5 Aomie dll's files only... not system files.
    I agree now mostly people uses 64 bit system but i have few old 32 bit system so sometimes need to repair...

    I am surprised that you have old 32 bit hardware to repair. Manufacturers have only been building 64 bit machines for almost 2 decades I think. 32 bit operating system may be loaded on them but the hardware itself is 64 bit. As long as the hardware is 64 bit, then 64 bit Win10XPE will work on it for all repair purposes even if the machine's operating system is 32 bit. If it is a true 32 bit machine then Win10XPE will not even load on it. Also, I found that hardware that old may not have the specific system requirements, notably cpu requirements, for Win10 to run.
      My Computer


  2. Posts : 4,131
    Windows 3.1 to Windows 11
    Thread Starter
       #2682

    I think I solved - EaseUsPM - please test for me.. I tested loading in x64
    Also if someone has newest x86 Source ISO please test ABU - for list of missing program files
      My Computer


  3. Posts : 64
    Windows 10 64bit
       #2683

    ffrags said:
    I am surprised that you have old 32 bit hardware to repair. Manufacturers have only been building 64 bit machines for almost 2 decades I think. 32 bit operating system may be loaded on them but the hardware itself is 64 bit. As long as the hardware is 64 bit, then 64 bit Win10XPE will work on it for all repair purposes even if the machine's operating system is 32 bit. If it is a true 32 bit machine then Win10XPE will not even load on it. Also, I found that hardware that old may not have the specific system requirements, notably cpu requirements, for Win10 to run.
    My hardware 64 bit, but os 32 bit... i hv core i3, 256gb ssd, 4gb ram, i prefer 32bit os on 4gb ram, on 8gb i prefer 64 bit os.. and windows 10 works good..
      My Computer


  4. Posts : 4,131
    Windows 3.1 to Windows 11
    Thread Starter
       #2684

    Your Host OS does not matter when booted into XPE... So yes you can use x64 Source Media, as long as you have enough system memory for loading XPE into memory ( X: ) - also updated Notepad ++ (Post #2) > use Update ( "U" button) and test again

    Also ABU was updated a few months back - you may need to download or update existing project scripts
    As I do not see where a program file is missing in x86 file extraction - although I can not test as I do not have x86 source media
      My Computer


  5. Posts : 90
    Windows 11 Pro
       #2685

    Kyhi said:
    RE: Update Release 2020.12.17
    After efforts to try to support 20H2. There is no need to go further
    The result is not really reliable, depending on the components or applications used...

    In Windows 10 version 2009 - 20H2 ISOs, update packages were not added to winre.wim, as it is normally done!
    And so, the Versions between winre.wim and Install.wim do not match and that is the source of incompatibilities and problems.
    In addition to the C:\ drive in the registry instead of X:\ (already fixed)
    TechBench ISOs and Media Creation Tool ISOs are concerned, ISOs created via UUP files look good.

    Except for UUP ISOs, It is preferable to use Windows 10 version 2004 - 20H1 and forget Windows 10 version 2009 - 20H2

    In case the versions do not match, I have added a message to inform and ask to continue construction or not (No by default).

    About 4 days ago I decided to update as many apps as I could find that needed updating since the last time I built my Win10XPE project back at the end of January. With the help of this forum, Kyhi, APT, and other resources that job was rather quickly accomplished and painless.

    However, my build was still using an old Win10 20H2 source from UUP from either Dec 2020 or early Jan 2021. Even though both ChrisR and Kyhi have stated compatibility problems, as noted above, with 20H2 due to Microsoft doing things differently, they did have Win10XPE project sources of 12/17/20 and especially 01/16/21 that have worked well and stable with the early 20H2 source from UUP that I was using. No problems all these months. Everything working as expected.

    So after taking care of the apps that needed updating I decided to try and update the Win10 source. That took a good part of the last 4 days. I downloaded and tested the following source ISO's from UUP and one from TechBench.

    20H1 19041.928 -->from UUP
    20H1 19041.1052 -->from UUP

    20H2 19042.928 -->from UUP
    20H2 19042.1052 -->from UUP

    21H1 19043.906 -->from UUP
    21H1 19043.928 -->from TechBench
    21H1 19043.985 -->from UUP
    21H1 19043.1052 -->from UUP

    None of the above Win10 source ISO's yielded a working Win10XPE build. Sure the build process completed without errors but the resultant Win10XPE flash drive would not boot thru to the desktop. During boot, the white progress bar would move right along as expected then the screen with the blue microsoft window and circling dots would appear as expected then the numlock light would turn on and then just when you expect the Win10XPE desktop to appear the whole thing just hung at a blank dark screen.

    The only source iso's that would work were early 2004 - 20H1, as stated above, and 20H2 19042.906 from UUP. So for now I decided to stick with the 20H2 19042.906 source which was only an incremental update from what I had been using these several months.

    I thought I'd present my results here and see if anyone else has tried and found the same to be true. New Win10XPE project builders may need to make sure that they don't download a later 20H1 or 20H2 or 21H1 source ISO which tend to appear at the top of either UUP or TechBench sites.

    These more current source ISO, I assume, contain the latest security and bug fixes and enhancements but how important is that in a PE environment? Additionally, with each Win10 feature update getting only about 18 months of Microsoft support what might happen to Win10XPE next year when the 2004-20H1 source is no longer supported?
      My Computer


  6. Posts : 4,131
    Windows 3.1 to Windows 11
    Thread Starter
       #2686

    I currently test with Preview Release -
    Win10XPE - Build Your Own Rescue Media-image211.jpg

    Just tested Techbench 21H1
    Win10XPE - Build Your Own Rescue Media-image212.jpg

    XPE sees it as
    Win10XPE - Build Your Own Rescue Media-image213.jpg

    Builder displays a mis-match error - as expected...
    Win Version in PE is 19041.1

    So basically the same issue from 20H2
    A Basic Build of 21H1 - did result in a bootable ISO
    Last edited by Kyhi; 12 Jun 2021 at 22:01.
      My Computer


  7. Posts : 4,511
    several
       #2687

    Aomei Backupper 6.5.1 x86 .Running on x64 boot media with wow support.

    Code:
    \Uprograms\AomeiBackupper\
    
    \driver\
    LoadDrv_Win32.exe
    LoadDrv_x64.exe
    
    \driver\amd64\
    ambakdrv.sys
    ammntdrv.sys
    amwrtdrv.sys
    amwrtdrv10.sys
    msahci.sys
    
    \driver\i386\
    ambakdrv.sys
    ammntdrv.sys
    amwrtdrv.sys
    amwrtdrv10.sys
    msahci.sys
    
    \lang\
    ar.txt
    de.txt
    en.txt
    es.txt
    fr.txt
    hu.txt
    it.txt
    jp.txt
    nl.txt
    nl-be.txt
    pl.txt
    pt.txt
    ru.txt
    tr.txt
    zh-CN.txt
    zh-TW.txt
    
    \log\
    
    
    2Gpt_BCD
    2Mbr_BCD
    AmCore.dll
    Amnet.dll
    awsSns.dll
    Backup.dll
    Backupper.exe
    BackupRecovery.ini
    BrFat.dll
    BRFunction.ini
    BrLog.dll
    BrNtfs.dll
    BrVol.dll
    Clone.dll
    Color.xml
    Comn.dll
    CompleteSettings.ini
    Compress.dll
    Config.dat
    CurTaskState.ini
    DayTime.ini
    Dev.dat
    Device.dll
    DeviceMgr.dll
    DiskMgr.dll
    Encrypt.dll
    EnumFolder.dll
    EraseDisk.exe
    ExFatStd.dll
    FileDialog.dll
    FlBackup.dll
    FuncLogic.dll
    Global.ini
    GptBcd.dll
    ImgFile.dll
    Ldm.dll
    libamcbconsole.dll
    libamct.dll
    libcrypto-1_1.dll
    libcurl.dll
    libeay32.dll
    libssl-1_1.dll
    LoadDrv.exe
    Microsoft.VC80.CRT.manifest
    Microsoft.VC80.MFC.manifest
    Microsoft.VC80.OpenMP.manifest
    Microsoft.VC90.CRT.manifest
    NTHelp.dll
    NTLog.dll
    NTSQLite.dll
    other.ini
    partitionbackup_task_name.txt
    PeLoadDrv.exe
    QtCore4.dll
    QtGui4.dll
    QtNetwork4.dll
    QtWebKit4.dll
    QtXml4.dll
    sqlite3.dll
    ssleay32.dll
    Sync.dll
    UiLogic.dll
    UsbDetect.dll
    vcomp.dll
    Version.ini
    wimgapi.dll
      My Computer


  8. Posts : 90
    Windows 11 Pro
       #2688

    Kyhi said:
    I currently test with Preview Release -
    Win10XPE - Build Your Own Rescue Media-image211.jpg

    Just tested Techbench 21H1
    Win10XPE - Build Your Own Rescue Media-image212.jpg

    XPE sees it as
    Win10XPE - Build Your Own Rescue Media-image213.jpg

    Builder displays a mis-match error - as expected...
    Win Version in PE is 19041.1

    So basically the same issue from 20H2
    A Basic Build of 21H1 - did result in a bootable ISO

    Hi Kyhi,

    How are you? I haven't had any issues with Win10XPE lately where I needed to resolve them with your help. So it's good to hear from you today. I have to say your post has me puzzled. The TechBench ISO that you show is one of the one's I tried. The builder does display the mis-match error but DID NOT result in an ISO that would boot thru to the desktop. I totally forgot about doing a basic build. So I just created a basic build of 21H1 as you did and it worked. It booted all the way through to the desktop. Does this mean that my Win10XPE using the same source is choking on one of my many apps? Still doesn't explain why my normal build works using 20H2 19042.906. I will need to start my testing again on Monday eliminating apps during a normal build, I guess. Thanks for the basic build hint.
      My Computer


  9. Posts : 3,453
       #2689

    Kyhi said:
    1) I have not found a difference between in the ability between the "System" & "Admin" accounts... The reason "Admin" is required by certain Applications is because the "System" account is not a valid windows user account, where as the "Admin" account is...

    2) The Host OS Architecture does not matter when it come to creating XPE - as it is the Architecture of the "Source Media" the matters.

    3)Notepad ++ - has New Version - will have to look for difference in Application Files - thank you for reporting

    4)EaseUS PM 15.2 - now uses a different installer - thank you for reporting

    5)with UltraISO be sure to hit 'Enter" after inputting your Name & Serial (or leave values blank)

    6) I have not seen PowerISO

    Matthew - there is no need to be sarcastic - to somebody asking a question and not really sure of the correct answer...

    Superfly - Yes some applications are created by OEM to be used in PE (by XPE) but the OEM process requires a registered product...

    Tyler - I no longer host completed ISO files - as the download demand was to high on my cloud storage accounts.. Yet, once you create a new ISO with the Applications you mostly use - your good to go - just with that ISO - no need to rebuild again - unless you looking to update it..
    OK cool thanx.

    Thanx to all who replied especially Matthew (LOL!)
      My Computer


  10. Posts : 7,606
    Windows 10 Home 20H2
       #2690

    You are most welcome!
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 01:43.
Find Us




Windows 10 Forums