WinPE 10 built specifically for AIO Boot comes with PEStartup tool which helps you to customize WinPE in your own way.

WinPE 10

What is WinPE 10? Windows Preinstallation Environment (also known as Windows PE and WinPE) is a lightweight version of Windows used for the deployment of PCs, workstations, and servers, or troubleshooting an operating system while it is offline. WinPE 10 is the WinPE version of Windows 10.

WinPE 10 is built from the Win10PESE tool. Includes both 64-bit and 32-bit versions that you can easily integrate into the AIO Boot.

WinPE 10 with PEStartup


At present, there are still many old and weak computers in use. That these machines can not use WinPE 10. To help you can rescue these computers easier, I have rebuilt a Mini Windows XP from Hiren’s BootCD.

WinPE XP with PEStartup


With PEStartup, you can customize WinPE 10 and XP like changing wallpaper, installing drivers, adding Shortcuts, Registry and Autorun.

You can boot into WinPE and open PEStartup to setup, or run AIOCreator.exe -> Tools -> PEStartup.

  • Drivers: automatically install drivers every time booting into WinPE.
    • Drivers can be downloaded from DriverPacks.
    • If you want to use your driver, compress it to a .zip file.
    • For XP, you need to rename the file and add “XP_” before the file name.
    • You should extract .7z files and compress them in ISO format. PEStartup will mount the ISO without having to extract them to install the driver. This saves time and disk space.
    • PEStartup will automatically install the drivers contained in the “\Drivers, \Drivers_x64, \Drivers_x86 and \Drivers_XP” folder in the root of your USB. You need to extract the files to this folder.
      • \Drivers: for ALL.
      • \Drivers_x64: for WinPE 64-bit.
      • \Drivers_x86: for WinPE 32-bit.
      • \Drivers_XP: for WinPE XP.
    • Double Driver is a good program for backing up your drivers. After backing up the drivers from Windows you are using, you can compress them or copy them to the appropriate folders above.
  • Shortcuts: add shortcut to desktop screen. This gives you quick access to the files.
  • AutoRun: automatically runs programs every time the system boots.
  • Registry: automatically import Registry files every time you boot into WinPE.



There are 6 files that you can download at Google Drive, Mega, Yandex Disk and Fshare. The files include:

  1. WinPE_10_x64_v1607_xxx.wim
  2. WinPE_10_x86_v1607_xxx.wim
  3. XP.wim
  4. WinPE_x64_Apps.iso
  5. WinPE_x86_Apps.iso
  6. WinPE_All_Apps.iso (this is a package that includes applications running on both 32-bit and 64-bit).

See Changelog.txt for changes.


You can integrate WinPE 10 through the following simple steps:

  1. First you need to download and install AIO Boot if you have not already.
  2. Run AIOCreator.exe, select “Integration“, select “Windows” and “WinPE 7/8.1/10“.
  3. Browse to the WinPE_10_x64_v1607_xxx.wim file for 64-bit and/or WinPE_10_x86_v1607_xxx.wim for 32-bit.
  4. Click OK.
  5. Copy the WinPE_x64_Apps.iso file for 64-bit and/or WinPE_x86_Apps.iso for 32-bit and WinPE_All_Apps.iso for both 32-bit and 64-bit to the \AIO\Files\WinPE\ folder on the AIO Boot drive. For .7z files, you need to extract these files to get the ISO files.
  6. Restart your computer and boot into WinPE.

If this version does not meet your needs, use WinPE 10 Sergei Strelec. Good luck!

WinPE and PEStartup tools can also be added to Easy2Boot. Read the author’s article for more details.

Join the Conversation


Your email address will not be published. Required fields are marked *

  1. Hi Team.
    How to do i customize the OS Installation.
    Like user creation, partion creation and all

  2. your application is very very good and even excellent, i do not know how to say thank you,, i used it as a technician many times to backup restore or even diagnostic dead operating systems, really thank you

  3. The WinPE_10_v1607 only has one WinPE_10_x86_v1607XXXX.wim file there is no x64 version. Could you help please?

    Thank you.

  4. Hi,
    I think I am confused on the PEstartup? Is this only if I am booting from a USB? Or can I use this if I am booting to an integrated WINPE in AIO?
    Because I would like to integrate WINPE into AIO, then boot to it over my network and then have it AUTOSTART HDClone? Because I cannot seem to get it to integrate HDClone either?
    Please help?

  5. Hi,
    I tried to integrate the WIN PE all files and it tells me invalid file? Can you fix this please?

    1. Hi Again,
      Is that Win PE all apps a FULL bootable WIN PE? Cause I opened it and its only the apps I think? Either way I cannot seem to get it to integrate?
      Please help

    2. What I would really LOVE to be able to do and I am willing to PAY you if you can help me get this working.
      I would like to be able to boot into HDClone and have it install an image over my network. I know it will install images over my network because I am already doing this, however I have to go through like 10 steps to make it do this including map my drive and then I must know the path to my images and its a pretty big hassle. However If I can make it boot into HDclone then it will work perfectly but when I try to integrate HDclone it says to contact the author for support and it wont integrate into AIO?
      Can you please help me with this?
      As I said I am willing to pay you to make this work?

  6. Tu,
    When I use the 1607 WIM files referenced in the Download section of the Add Win10 PE with PEStartup to AIO Boot page, the Desktop shortcuts function works when booting from the USB drive.
    However, when I build a Win10 PE SE build and integrate the ISO using the AIOBoot utility, add shortnamed folders and files to the USB drive and use PEStartup to add Desktop shortcuts. They don’t show up when I boot from the USB drive.
    What am I doing wrong?

  7. Is there any way in both Shortcuts and Autorun to specify use a drive letter (in the path) that might change depending on what partitions are on the PC that is having WinPe run upon it.
    The Environment variables (%CDDRIVE% as an example) would be set to ‘Y:’

    When I created shortcuts I *think* they had the prefix of ‘X:’ prefixed to the Target when I tried using such a variable.

    1. Hi,
      It only allows you to use the X: drive and the drive you are putting PEStartup on.
      It is possible that environmental variables will be supported in the future.

  8. Firstly, thanks for all your work on AIO Boot
    It would be nice for the original project ChrisR’s Win10PESE to have written acknowledgments for your WinPE 10 built.

      1. Hi, I saw that your WinPE 10 are based on my project.
        Is it possible to write the acknowledgments or to give a link to Win10PESE.
        I do it for free without any income. It is my only benefit in the work done.

          1. Thanks a lot Tứ,
            I am only an end user of pecmd. I do not know what your problem is, DEVI works fine here,
            Drivers must be integrated first by using driver integration plugin
            Also, I believe that some drivers need
               REGI HKLMSYSTEMSetupSystemSetupInProgress=#0
               DEVI %WinDir%infMyDrivers.inf)
               REGI HKLMSYSTEMSetupSystemSetupInProgress=#1

  9. I booted to just wim 10 file using Easy2Boot but I don’t see PEStartUp shortcut? Where does PEStartup come from?

      1. Thanks. I figured it out and got it working before you replied!
        The PEStartup app is really cool. They should include it into ChrisR’s Win10PESE WinBuilder project.
        Have you contacted them about it?

          1. Thank you. I added the link at the article footer, my users will know that they can also add WinPE to Easy2Boot.
            I want to include QEMU on AIO Boot. I see that RMPrepUSB has StartFromUSB.cmd and RunIso.cmd. It works fine, I want to use it, do you agree?

          2. To autorun a .bat file, I found you need to put START before the path to the file so that you can see the cmd shell.

            On another point:
            It is a bit of a pain to set it up for both 32-bit and 64-bit WinPEs. e.g. to add a new shortcut, you have to boot to 32-bit WinPE and add it in, then boot to a 64-bit WinPE and add it (or a 64-bit version) in. It would be better if there could be a checkbox for both 32-bit and 64-bit when an item is added. e.g. If I boot on a 64-bit WinPE, the 64-bit checkbox would be ticked when I go to add a new entry, but I could also tick the 32-bit box or untick the 64-bit box and tick the 32-bit box. In this way I don’t need to boot to two different WinPEs. Is this possible?

          3. Sorry, I do not understand ‘Why do not you boot into WinPE 64-bit to run and configure both 32-bit and 64-bit versions?’
            If I boot in WinPE 64-bit, configure PEStartup and then boot WinPE 32-bit, the changes are not remembered??? I have to also configure again in 32-bit PE?

            P.S. Help button in PEStartup does not mention –hide for autorun, .iso support for drivers or Drivers folder functions.

          4. Ah – OK, I understand – but you are assuming that WinPE 64-bit has Wow64 support – but many WinPEs do not have WoW64 components and will not run 32-bit programs.

  10. How can I integrate both WinPE 10 and Strelec WinPE. I added both menu under main.cfg but it didn’t show up when booting up.
    Only the one on the top of main.cfg show up in the boot up menu.

      1. Did you refer to this article? I must be blind or really dumb for not finding it anywhere in this article that mention about integrating both WinPE 10 and Strelec WinPE.
        Could you point me to the article that discuss the integration for Win10PE and Strelec PE?