elie/PhoenixPE
1
0
Fork 0
mirror of https://github.com/PhoenixPE/PhoenixPE.git synced 2025-09-17 18:48:04 +02:00
Code Issues Packages Projects Releases Wiki Activity

Updated FAQ (mediawiki)

Jonathan Holmgren
2022-06-12 12:17:31 -05:00
parent d3b52571d0
commit affbb5f64a
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
FAQ.mediawiki

@@ -20,8 +20,14 @@ PhoenixPE on the other hand targets advanced users and developers that what more
'''TL;DR: No. It's an alternative. The developers of both projects are part of a vibrate community that works together and shares their knowledge and experience. Use the one that best meets your needs. You can't go wrong.'''
= Win11 Support =
== Building from a Win11 source with explorer shell causing blackscreen on boot.
Due to changes to Explorer.exe with Win11 to support the redesigned start menu and taskbar, the Win11 explorer.exe desktop crashes in WinPE. You can work around this issue by using explorer.exe from a Win10 source or HostOS. Due to Microsoft's EULA we cannot distribute explorer.exe with PhoenixPE, however the Explorer shell script will allow you to provide explorer.exe from either your Win10 Host or another source. If you have made progress getting the Win11 explorer to work in WinPE please post your findings in the development forums.
= Common Issues =
== Bluescreen/Issues testing with VMWare/VirtualBox ==
It's important to remember when testing with VMWare/VirtualBox you need to take into account the memory and CPU requirements of the PE you will be testing. WinPE is RAM intensive. Remember that just because you configure a VM with 2 CPU's and 4GB RAM, it doesn't mean that it's available to the VM. These resources are shared with the host, and must be free in order to be used by the VM. Errors such as a bluescreen "System Thread Exception Not Found", or hang on PreShell Configuration are almost always caused by too little RAM or not enough CPU resources. Try increasing the resources and/or closing CPU/RAM intensive applications (Web Browsers, games, video streaming, etc.) on the host. WinPE built on Win11 require at least 4GB RAM, where with Win10 you could sometimes get away with 2GB. Ramdisk size and the size of your boot.wim file all need to be taken into account when determining memory requirements.
It's important to remember when testing with VMWare/VirtualBox you need to take into account the memory and CPU requirements of the PE you will be testing. WinPE is RAM intensive. Remember that just because you configure a VM with 2 CPU's and 4GB RAM, it doesn't mean that it's available to the VM. These resources are shared with the host, and must be free in order to be used by the VM. Errors such as a bluescreen "System Thread Exception Not Found", or hang on PreShell Configuration are almost always caused by too little RAM or not enough CPU resources. Try increasing the resources and/or closing CPU/RAM intensive applications (Web Browsers, games, video streaming, etc.) on the host. Ramdisk size and the size of your boot.wim file all need to be taken into account when determining memory requirements.