That statement may be correct...run Setup.exe one from the Sources folder
I do not use "Setup.exe" - Nor Do I Run any form of MS Setup
I use DISM to apply the Image Index to the OS Partition
Last edited by Kyhi; 17 Sep 2019 at 12:55.
Win10XPE Only Supports Windows 10 - Basically Windows 10 and Windows 10 Drivers are already being used to boot the PC on that PC's hardware..
My external USB HDD, My Passport, already has a small Ext4 partition containing an installed OS—Linux Mint.
In the attached screenshot, when I click on "My Passport (F:)", nothing happens. "Safely Remove Hardware" does not work on Win10XPE.
On Linux, the command "sudo hdparm -y /dev/sdx" = "Safely Remove Drive".
On Windows, is there an equivalent command?
Last edited by Matthew Wai; 18 Sep 2019 at 03:04.
@Matthew Wai :What will be the consequences if I run "setup.exe" in the root? I intend to clean install Windows using Win10XPE.
1. I think you should launch Setup.exe from the Sources folder because :
if you execute it from the root of the Mounted folder, it should try to overwrite the current XPE Boot & its boot partition. Actually, its like performing an In-place Upgrade or Repair Install.
When I want a second OS / multiboot on another partition on the same internal hard disk, I run Setup.exe from the Sources folder from within the current OS & you are planning almost a same thing : booted into one OS : XPE Boot & from there planning install on a different partition i.e. an Internal HDD Partition.
Just to Mention :
If you run a process which needs a lot of space in Temp folder, you may have problems because by default the Temp folder is put on B: RamDisk ( 1.40 GB ) . It is put on the system RAM for a good pace but the space is limited to 1.4 GB.
By default options, You can increase it up to 2 GB by unchecking ImDisk ( RAM) box & increase WinPE Cache to 2048 mb in the Build Core options. Then your Temp folder would be again put on X: Boot ( RAM ) but in 2GB of your system Ram.
Or the other thing boot into the XPE & manually transfer Temp folder to the biggest & fastest drive or partition.
Or let the IMDisk integrate into the build. After boot, launch the IMDisk App & allocate more ram to B: RamDisk.
While allocating more Ram to RamDisk , take care of your system Ram capacity!
Luckily it happened for me using NTLite. It prompted me that it needs 10 GB space in Temp folder & offered me to change Temp folder for the NTLite app's Temp directory. I located it on a big & empty partition of Internal Hard disk & It was all well. Not all apps would prompt like NTLite!
Thanks & Regards. ...
Last edited by Vineet Garg; 18 Sep 2019 at 05:50.
I can't say anything surely about it, Its my limitation, That's why I put that into 'Just To Mention'!Will I have problems if I run “/sources/setup.exe” to clean install Windows onto my internal HDD without changing RamDisk (1.40 GB)?
When I did that, I did not make notice of what happens to the Temp folder. But as a warning, Its clear : if the process requires more space in the Temp folder ( As the case was with NTLite), It may be troublesome.
To say honestly : If I am supposed to perform that task, I would like to use WinNTSetup3 which is included in the Win10XPE ISO by default. I have many recommendations for that program though I never used it personally.
Thanks & Regards. ...
Win10XPE_2019-09-18 Update - See First Post
WinXShell: Update rc4.2beta2. Added support for Microsoft Managment Control (MMC)
StartIsBack++: Update v2.8.9
Rufus: Update v3.7
PinUtil: (New) v1.2.1 Pin To Taskbar and StartMenu Utility. pecmd.ini and AddPin macro have been updated accordingly
Jrepl.bat: (New) v8.4 Perform global regular expression, text, bin, search and replace operation
Autorun.cmd: Remove Google Chrome.lnk no longer required with latest versions
Explorer,IME Common...: Additional dependencies for Windows 20h1 Insider Preview. Successfully tested with Build 18980
Build Core: ComputerName with Wildcards ?,+ accepted. --> The ComputerName environment variable is broadcasted in PeNetwork_AfterStartup.cmd
* New option to Patch Controller.dll to Get the Credentials Window
* Additional choice for the WinPE Cache Size 3072,4092
Explorer: Add "Volatile" Environment variable HomePath, HomeDrive and LocalAppData
Internet Explorer 11: Added Registry, Files, Search Engine Icon and Set the UserChoice
Config: Explorer and WinXShell use the same registry now. Also Associate .cfg,.inf,.ini,.log,.scp,.script,.txt,.wtx (txtfile) for Full Software
NET Framework: The plugin can now be called from another App and write Registry Settings without the need for the Full Software
Switch to Admin: Hidden option to Pre-Create Admin Profile before switching, if needed.
Create ISO: Patch DrvInst.exe and Controller.dll to Get the Credentials Window, if enabled in Build Core
Remote Desktop: Patch Controller.dll to Get the Credentials Window is moved in Build Core and Create ISO. It is Used for Remote Desktop but Also for Mapping a Network Drive,...
Note: NLA Support Requires the Admin account. It is Not Available with the System Account, even with Files and Registry from Switch To Admin plugin
PowerShell Core-6: Link updated to v6.2.3
Q-Dir: Update v7.8.2
Acronis TrueImage 2020: (New) current build 20770. In place of ATI 2019
AOMEI Backupper: Link updated to v5.2.0
AOMEI Partition Assistant: Link updated to v8.4.0
Macrium Reflect Free: Update v7.2.4440
CPU-Z: Update v1.90
HWinfo: Update v6.10
MPC-BE: Link updated to auto select one of the available mirrors
VLC Media Player: Program Version (Link) updated to 3.0.8
AnyDesk: Update v5.3.2
Google Chrome: Update v76.0.3809.100. Revised Registry and add USER DATA Import Process
Mozilla Firefox Quantum ESR: (New) current version downloaded v68.1.0.7177
NETFx3 Add-Feature: (New) Utility. Enables/Disables .NET Framework 2.0-3.5 Support in XPE
Plugin Creator: NoExitOnError if script warning message
XPE Microsoft Edge x64(x86) Plugin Creator: (New) Utility. Will Create a X64(x86) XPE Plugin From The Actual Edge Setup File
Win10XPE - How To Quick Start Guide.PDF: Updated with larger (less Blurry) Pictures
Google Chrome: Updated to latest version 77.0.3865.75
Note: If you have a customized Pecmd.ini in Custom\Pecmdini --> it must be deleted, renamed...
To be in agreement with the included Pecmd.ini which use the new PinUtil tool and to be able to pin your Apps.
