Hi

I have created a working PE using WAIK under Windows 10

If I boot the ISO file in VirtualBox it boots really quickly and works fine

If I burn the ISO to CD/DVD and boot it on a real machine I get the blue logo, but it then sits for absolute ages before the spinning circle appears and it starts to boot - it does eventually go in, but can take several minutes

If I create USB using (MakeWinPEMedia /UFD D:\PE_TEMP G:) then it creates fine, but when trying to boot I get blue screen error with "winload.efi error 0xc0000225"

Any thoughts please

Hi all,

I want to create bootable live Windows PE on usb stick. I want to create it from Windows 10 installation i have.

I wonder, how can i achive that? Any instructions?

Thanks,

Rami

Hello!

I am developing an app for WinPE. And I want to run WinPE  10.0.16299.15 on older PC. But always when I run it on an old PC I always get an error about Physical Address Extension. I am using x86 WinPE and Pentium 4 with 512MB ram. How can I disable it in DISM?

Thank you for help!

PS: Sorry for my bad English.

The PEBakery Team are proud to present the ChrisPE project. Use this project to create WinPE from a range of 32-bit and 64-bit Windows sources, including -

Windows 7

Windows 7 (SP1)

Windows Server 2008 R2 SP1

Windows 8

Windows 8.1

Windows 8.1 Update

Windows 10

Windows RTM source files are recommended. The sources in the above list have been tested, other source files may also work.

This project has been internally tested and developed over the past two months and is now ready for a public beta release. The PEBakery Team anticipate ongoing development and the ChrisPE project is likely to continue to evolve. This may result in changes to some of the core features such as the menu system and supported shells.

Some of the current features include -

No caching of Windows source files - resulting in reduced storage space requirements on the Host OS used to build the project.

.wim support using internal PEBakery commands - the wimlib library is used for managed wim support. The full contents of the the Windows source and WinPE .wim files are not applied (extracted) to a local directory - resulting in significant time savings.

Support for a range of shells including bblean, CMD, LaunchBar and WinXShell.

WoW64 support.

This project has been developed as a base from which to add additional features.

Please note that it's been developed for use with the PEBakery builder and will not work in winbuilder as a number of commands are not supported.

Please download from the ChrisPE github repository - https://github.com/pebakery/chrispe

Instructions are included - please check the documentation in the download (readme.htm).

If you are not familiar with github - use the Clone or download button and select the Download ZIP option to download the project.

Feedback is welcome.

Please have fun.

The PEBakery Team (ied206, alacran, Atari800XL, homes32 and Misty)

Screenshot of ChrisPE with WinXShell -

EDIT: Not all the programs are in the basic download, there is a complementary pakage of scripts, I have it almost ready for upload and will be available for download very soon, new scripts are finished and working now, but under test to prevent any malfuntion, the pakage contains 25 new scripts.

alacran

Hi friends,

Is it possible to automatically run a bat script after the winpe environment has been created? Im trying to do this to automatically kickoff of the windows 7 installation from windows pe environment.

Following are the commands i wish to execute:

> net use z: \\172.16.255.254\win7 jet-123 /user:student

>z:\setup.exe

Please Please help!

Thanks

Hello

Since I upgraded to WinPe 3.0 I have not been able to successfully use startnet.cmd to call a batch file on boot up to identify my drive letter. The small DOS like box comes up as usual and you see it runs my batch file and then it immediately reboots WinPe. This process worked fine under WinPE 2.0 and 2.1. Below are variations I have tried in my Startnet.cmd file

startnet.cmd (1)

wpeinit

call mstart.bat

startnet.cmd (2)

wpeinit

mstart.bat

startnet.cmd (3)

wpeinit

@echo off

cls

Goto Begin

:Begin

ECHO FINDING BOOTABLE DRIVE

FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\WinPE_Boot_Media.txt SET DRIVE=%%i:

%DRIVE%\menu.bat

goto END

:END

Does anyone know why or what is causing WinPe to reboot after I call a batch file or running a script from Startnet.cmd. I am completely stumped ?!?!?!?!?!?!

Thank you

Hi All,

I have a huge problem with WINPE booting in UEFI (x64) mode and the auto DPI scaling it performs.

I've tried setting up an Unattend.xml with the DPI settings but with the DPI element included, the whole XML is ignored. As soon as I remove the DPI setting the XML works fine.

Another approach I've tried is using the startnet.cmd to set the registry for FontDPI to 96 but that doesn't fix it either.

Does anybody know how to fix this or disable the DPI scaling altogether for WINPE? To be clear this is in WINPE not OOBE.

Booting the WINPE in x86 BIOS mode does not trigger the auto DPI scale.

Thank you very much.

I'm building a WinPE (3.0 from Windows 7, or 10.0 from Windows 10; it doesn't matter to me) image and need smart card compatibility.
I tried to follow the steps mentioned in the following link:

but unfortunately, it didn't work for me; the service scardsvr is not running, and when I tried to start it - I got this error message "The executable program that this service is configured to run in does not implement the service."

So, does someone know what I should do to make it work properly?

Thanks a lot!

Was fiddling with the registry and broke my Win 7 installation (Lenovo y460p).  Now I'd like to recover some files before I go back to factory default.  I've created a Windows PE bootable USB stick with AOMEI Windows PE Builder and it sees the HDD but doesn't see the SSD.

The BIOS says it's a Samsung MMCRE32GEDXP-MVBL1.  I've tried to find drivers but the only download I can find is from doubledriver and when I download it the drivers are called doubledriver.exe.  That sounds a bit fishy to me.  In the past I've collected all drivers for this laptop from the Lenovo site but they don't seem to have any SSD drivers.

Does anybody have any advise which drivers I could use?  Perhaps some generic drivers?  I would very much like to recover a few files from the SSD. 

Thank you very much.

For those that are looking at working with Windows PE 3.0 and have not had the time to research them you can check out the updated commands at OS Attack. I copied these commands from the post there.

http://www.osattack.com/windows/commands-f...-windows-pe-30/

Create winpe_x86 directory in C:\PE (this WILL delete it if the directory already exists):

rd /s/q C:\PE\winpe_x86

cd “c:\Program files\windows aik\tools\petools”

call copype.cmd x86 C:\PE\winpe_x86

Mount the WIM image:

cd “C:\Program Files\Windows AIK\Tools\x86\Servicing”

DISM.exe /Mount-Wim /WimFile:C:\PE\winpe_x86\ISO\sources\boot.wim /index:1 /MountDir:C:\PE\winpe_x86\mount

UnMount the WIM image commiting changes:

cd “C:\Program Files\Windows AIK\Tools\x86\Servicing”

DISM.exe /unmount-Wim /MountDir:C:\PE\winpe_x86\mount /Commit

Add packages into your WIM, this can be edited to only add in what you need to reduce the size of the WIM:

cd “C:\Program Files\Windows AIK\Tools\x86\Servicing\”

dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe.cab”

dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe-wmi.cab”

dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe-hta.cab”

dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe-legacysetup.cab”

dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe-mdac.cab”

dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe-scripting.cab”

dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe-setup.cab”

dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe-wds-tools.cab”

Check what packages are installed:

cd “C:\Program Files\Windows AIK\Tools\x86\Servicing\”

dism /image:c:\PE\winpe_x86\mount\ /Get-Packages

UnMount the WIM image discarding changes:

cd “C:\Program Files\Windows AIK\Tools\x86\Servicing”

DISM.exe /unmount-Wim /MountDir:C:\PE\winpe_x86\mount /discard

Create Windows PE ISO:

cd “C:\Program Files\Windows AIK\Tools\x86″

oscdimg -n -bc:\PE\winpe_x86\etfsboot.com c:\PE\winpe_x86\ISO c:\PE\winpe_x86\winpe_x86.iso

Hello all,

how can i get the PCI BUSNUMBER X, Device X, Function X of networkcards

automatic to write the unattend.txt dynamicly, if I have two or more network cards?

Is there a way to do it with wmi (vbscript) or the devcon.exe utility or other reskit utility from microsoft?

I only found it in registry

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_1039&DEV_0900&SUBSYS_0A141019&REV_90\3&61aaa01&0&18

in LocationInformation = PCI bus 0, device 3, function 0

There must be a simple way to do it?

I tried it with the following wmi class Win32_PnPSignedDriver.

bye

Buddy

->Need to retrieve PC name and later change back to the original name

Boot to Win PE (for Win 10 v1809 32bit)

Need a script that will run in WinPE and do the following:

Load the registry hive of the computer into WinPE

Get the computer name from the registry (probably HKLM\System\CurrentControlSet\Control\ComputerName\ComputerName)

Save the computer name to a temporary folder on the USB

Partion & format the drive then install the image (my process).

After Windows setup is complete, a new PC name will be generated, so  need an additional script to:

change the computer name back to the original name.

NOTES:

An underline will be used in the original name, so a warning about non-standard characters will be likely and a restart required for the name to change. 

When manually changing the name, the older process (like Win7) from Control Panel / System / Advanced System Settings / Computer Name tab / [Change] button works... but the simplified Windows 10 way (Setting / System / About / [Rename this PC]) does not allow the use of the underline in the PC name.

hello forum.

i've allready made 'my' w10pe sometime ago only for dism capture purposes.
now, i need to add cleanmgr 'DiskCleanUp' to wpe.
like other apps, i've copied the .exe, .mui and the .mun to their respective folders.
i've Add-Package WinPE_OCs\WinPE-WMI.cab to the wpe.
but can't get cleanmgr 'Clean Manager / Disk Cleanup' to work.

any help please?
thank you.
best regards, l.a.

Hello, I'm not sure that this is the right place to ask this kind of questions, and if its not, im sorry.

Im using winpe for a project of mine, and im having some troubles with virtual adapters drivers.

Im using mini windows 10 v19.10, and i manage to get some drivers to work at boot, placing them in the system\drivers folder.

the only drivers that do not work after reboot are the openvpn tap adapter drivers, im using a portable version of ovpn and it requires me to install the drivers every time i reboot the device(OpenVPN TAP NDIS 6 Driver 9.21.1) .

can anyone explain me what am i missing here? 

Im also trying to permanently change the pagefile.sys and swapfile.sys sizes without success (dont bother answering if you dont know, cause it is not very important)

I have managed to edit the pagefile.sys, and i have exported the regedit log to the system\regist folder, but the os does not use the values I had set, as it shows 0mb of total paging size for all drivers.

EDIT;

"I have tried to edit the winpeshl and add the line Wpeutil CreatePageFile /path=C:\pagefile.sys /size=128 to it, but it does nothing

theres a line on that file already (/Windows/System32/Winkey.exe) that may be messing thigs up "

Also, would be nice to password protect the winpe usb stick (dont bother answering if you dont know, cause it is not very important)

Thanks in advance, and sorry for the bad english.

Hello. I have successfully created two WinPE ISO images with Win10PESE, one x86 version and one x64 version.

These two images were tested with VMWare Player and they worked fine.

I would like to have one single combined ISO image out of these two, such that:

1. Only booting from UEFI needs to be supported.
2. When booted on PC with x86 (32-bit) UEFI firmware, the x86 version of boot.wim is booted.
3. When booted on PC with x64 (64-bit) UEFI firmware, the x64 version of boot.wim is booted.

Is it even possible to archieve this? Any pointers are welcome.

While unknown as to what version this issue started with, the problem is replicated in WinPE v10.0.17763.1 but is not replicated in v10.0.14393.0. After much testing it appears that current WinPE detects an NVMe in an m.2 socket as a different type of disk (as expected) but then gives priority to other interfaces when it comes to disk numbering. The issue has been seen on 5 different boards so far, two different chipset manufacturers and 3 different board manufacturers.

Using a fixed driver set, WinPE v10.0.14393.0, booting via USB with a board where the only disk installed is in an M.2 socket, either SATA SSD or NVME, WinPE will give the M.2 device Disk 0 and the USB key Disk 1.

Using the same driver set, and WinPE v10.0.17763.1, booting via USB with a board where the M.2 socket has a SATA SSD, the M.2 device is Disk 0 and the USB key is Disk 1. If the device in the M.2 socket is an NVMe, the M.2 Device is Disk 1 and the USB key is Disk 0.

That is the problem. I have collected information relating to how the devices are detected on v10.0.17763.1, using a NUC10i3FNK with M.2 SATA and M.2 NVMe. In each scenario the USB key is removed prior to running the diskpart or wmic commands.

---------
NUC10i3FNK with Crucial MX500 M.2 SATA SSD
---------
Microsoft DiskPart version 10.0.17763.1

Copyright (C) Microsoft Corporation.
On computer: MININT-U8KOB3F

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          232 GB      0 B        *

DISKPART> sel disk 0

Disk 0 is now the selected disk.

DISKPART> detail disk

CT250MX500SSD4
Disk ID: {A5BFEC98-EA08-4F09-9568-043A4150E9C2}
Type   : SATA
Status : Online
Path   : 1
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(1700)#ATA(C01T00L00)
Current Read-only State : No
Read-only  : No
Boot Disk  : No
Pagefile Disk  : No
Hibernation File Disk  : No
Crashdump Disk  : No
Clustered Disk  : No

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     N   Windows      NTFS   Partition    232 GB  Healthy
  Volume 1         SYSTEM       FAT32  Partition    260 MB  Healthy    Hidden

X:\windows\system32>wmic /namespace:\\root\microsoft\windows\storage path msft_disk get Model,BusType
BusType  Model
11       CT250MX500SSD4

---------
NUC10i3FNK with Samsung 950 PRO M.2 NVMe
---------

X:\windows\system32>diskpart

Microsoft DiskPart version 10.0.17763.1

Copyright (C) Microsoft Corporation.
On computer: MININT-A7B045E

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 1    Online          476 GB      0 B        *

DISKPART> sel disk 1

Disk 1 is now the selected disk.

DISKPART> detail disk

AMD-RAID Samsung SSD 950 SCSI Disk Device
Disk ID: {6D23D8C0-4EA4-4923-9E0E-8988913D7006}
Type   : RAID
Status : Online
Path   : 8
Target : 2
LUN ID : 0
Location Path : UNAVAILABLE
Current Read-only State : No
Read-only  : No
Boot Disk  : No
Pagefile Disk  : No
Hibernation File Disk  : No
Crashdump Disk  : No
Clustered Disk  : No

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     D   Windows      NTFS   Partition    476 GB  Healthy
  Volume 1         Recovery     NTFS   Partition    500 MB  Healthy
  Volume 2         SYSTEM       FAT32  Partition    260 MB  Healthy    Hidden

DISKPART> exit

Leaving DiskPart...

X:\windows\system32>wmic /namespace:\\root\microsoft\windows\storage path msft_disk get Model,BusType
BusType  Model
8        Samsung SSD 950

The NUC10i3FNK is set to AHCI and RAID is not an option. Yet the WinPE will detect the NVMe as BusType 8 aka RAID and have no location path. There is only one M.2 socket in the system and no settings were changed in between testing the SSD vs NVMe except for obviously removing one and installing the other.

Normal WinPE is not able to run the WMIC command listed above. It requires WinPE-WMI,  WinPE-NetFX, WinPE-Scripting, WinPE-PowerShell and WinPE-StorageWMI WinPE_OCs .cab files, installing the StorageWMI last.

WinPE component reference:
https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/winpe-add-packages--optional-components-reference

WMI MSFT\_Disk class:
https://docs.microsoft.com/en-us/previous-versions/windows/desktop/stormgmt/msft-disk

Hello and hoping you are all doing well and staying healthy.  

I am relatively new to using WinPE, I am currently using .wim files to image a multiple partitioned HP ProLiant DL380 Gen 10 server with Server 2016.  I have created and wrote to all the partitions with no errors.  When I attempt to write the boot files to the 100MB boot partition using:  "C:\Windows\System32\bcdboot" "C:\Windows" /s "B:" the return is "Boot files successfully created" when I attempt to boot into the OS, I get the Windows logo then an error saying can't find boot files?  In WinPE when I change to the B: drive and provide the command dir /a it shows two files created in B:  bootmgr and BOOTNXT and the Boot directory which has multiple files in it.  Now the strange thing is, when I do the same thing on a HP ProLiant DL380 Gen 5 server everything works fine.  I have been beating my head against the wall on this one for weeks so finally decided to create a post.  My apologies as I don't have the experience many of you have.  I am an installer by trade but forced to perform System Engineer work due to loosing my SE.

Thank all of you that read and respond ahead of time.

All the best,

Anyone have anything that can build something like Make PE but for Windows 10?

One observable so far is that WinPE 10 builds do not automatically assign a drive letter to the OS volume of a disk that has Windows 11 or Server 2022 installed onto it. This does not effect imaging but does effect capturing images. You can find the volume with the OS and assign a drive letter to it in order to capture it as an image. So only automated capturing would be an issue if using the WinPE made from ADK 10.

I have not made a WinPE from ADK 11 yet to know if the issue also exists there or not.

Hello everyone! 

I am new-ish to winpe 10 and i don't understand a lot but i have tried a huge lot of things before finally giving up and coming to this website and writing this very message. I have been trying to complete a project of command line winpe 10 with wifi and custom commands for over a year now and i just cannot for the love of god able to connect winpe 10 to wifi. I totally give up now i have followed about 30 tutorials on how to connect winpe 10 to wifi  which all of them failed. This is a last  ditch effort for me can someone please give me a vanilla winpe 10 with just wireless  and Ethernet drivers already in it? whoever you are will help me a lot and god may bless your soul. trust me when i say i have searched and searched for over a year now and cannot find a premade vanilla winpe with just wireless drivers always this other junk included with it. it may feel like I'm just here to get the easy way out and being lazy but honestly I'm exhausted. 

Thanks alot and hope you have a blessed day