Win10XPE Project

Thank You For Your feedback..
There was a small registry typo effecting x86 build...

Beyond Compare-4 Fixed....

Thanks James, It works now.

Thanks
I updated the package with the fix for Beyond Compare-4

Win10XPE_2019-07-20 update

With a few small additions:
Pintool: Update powerpc's pintool v2.4.0.7
StartIsback++: Enable Taskbar JumpList by default
Network: Add Network and Sharing Center by default with Full Software hive. As a reminder, the Full Software is automatically used if Admin or DotNet are selected

In keeping with the Norm
Here is the Win10XPE Add-on Package for 2019.07.19
Although the Apps are posted and available separately > I've included them a single hosted download

Edit: Oops sorry for the date, James

Thank you soooo much for keeping this working.

Big thank you for the little tweaks for WIM only and AIO Boot.

New to this but I have been using the oven to 1703 few years back- so after a first attempt to use 1903 witch failed with bsod..I manage to successful build with 1809 but:

1. I want to get a random name instead of project name or custom name - * didn't worked :(
in the old and current Win10PE_SE is a component that specifically address this matter - basically I need to load this PE to multiple computers in the same time and execute some hta, vbs and cmd scripts and to avoid naming conflict in the network I just need to leave the default random name mininnt...
Please point me to the right direction witch ini xml where to look into

2. I didn't look closely enough is a check box or something to add support for vbs mshta components or could I use adk with add package...dism commands...

Thank you and sorry if I post on the wrong place

1) You will have to wait on ChrisR to address the issue of "a random name instead of project name or custom name"
2) is this what you looking for Common Components

winre.wim already has hta'vbs components. No need to add them with an check box. unless you want to remove them.


The build is based on the Winre.wim recovery environment which has the following default features:
Quote
... ,WinPE-Scripting, ..., WinPE-HTA, ...

1. I want to get a random name instead of project name or custom name - * didn't worked :(

We can wait for a fancy fix from ChrisR or you can try the following workaround.

1. Create a batch file GenPCName.cmd in the folder: Projects/Tools with content:

Code: [Select]

@echo off
@echo [ComputerName] > PCName.ini
@echo RDName=WINNT%RANDOM% >> PCName.ini

2. In file Projects/Win10XPE/Features/CoreOptions.Script, line 90: Replace

Code: [Select]

If,%ComputerName%-,Equal,-,Set,%ComputerName%,%ProjectName%

with

Code: [Select]

//If,%ComputerName%-,Equal,-,Set,%ComputerName%,%ProjectName%
If,%ComputerName%-,Equal,-,Begin
  ShellExecute,Hide,cmd.exe,"/C #$q%GTools%\GenPCName.cmd#$q"
  IniRead,%BaseDir%\PCName.ini,ComputerName,RDName,%ComputerName%
End

3. Go to Main interface>Build Core>Computer Name
leave the Custom Name empty

4. Test the result...

WinPE will auto set hostname.
remove the CALL of RegComputerName

We can wait for a fancy fix from ChrisR or you can try the following workaround.

1. Create a batch file GenPCName.cmd in the folder: Projects/Tools with content:

2. In file Projects/Win10XPE/Features/CoreOptions.Script, line 90: Replace

3. Go to Main interface>Build Core>Computer Name - leave the Custom Name empty

4. Test the result...

The result will be a random Name for that PE Build - thus if PE Build is deployed to multi-PC's  -- ALL will have the same random name ...

WinPE will auto set hostname.
remove the CALL of RegComputerName

 

The result will be a random Name for that PE Build - thus if PE Build is deployed to multi-PC's  -- ALL will have the same random name ...

Aha! This name must be set during the booting process.
I think the issue can be fixed if we modify the PENetwork.ini appropriately so that it can generate a random hostname each time WinPE boots up.
Just custom this ini file and it works as we wanted.

Note that PENetwork will set new host each time by using the information from the ini file. If we disable RegComputerName command, the hostname still be whatever PENetwork gives.

 PENetwork.ini (33.2 kB - downloaded 26 times.)

I believe was able to get MINWINPC
Although, You may have to Edit PENetwork.ini to remove existing parameters

attachments removed as ChrisR Responded

Here is WinPE's origin way to get random hostname or specify hostname on booting.
Put this file in System32,
https://github.com/slorelee/wimbuilder2/blob/master/Projects/WIN10XPE/_CustomFiles_/PEMaterial/unattend.xml

call TextReplace the Architecture="amd64" to x86, if you build x86 PE.
call TextReplace to config the ComputerName, EnableNetwork, EnableFirewall, ...

There are many Computer Name and WinPE Registry RegWrite's throughout the Build, which had to be removed...

Updated Acronis True Image 2020 to support retail release..
See index...

I believe was able to get MINWINPC
Although, You may have to Edit PENetwork.ini to remove existing parameters

My previous post might not be clear enough.
What I meant was: We do  not need to change the Computer Name or anything else, just only modify the PENetwork.ini by adding ??++. Then PENetwork will do the rest of the job. Meaning it will assign a new hostname (PENetwork does not care the predefined Computer name) everytime we boot PE.

These Are For TESTING ONLY
\Win10XPE\Projects\Win10XPE\ (Attachment Link)
\Win10XPE\Projects\Win10XPE\Features\ (Attachment Link)
Note: These attachments will be removed after a predefined number of downloads - Unless There Is Feedback With Testing Results

I will test your scripts today and give some more comments.

Here is WinPE's origin way to get random hostname or specify hostname on booting.
Put this file in System32,
https://github.com/slorelee/wimbuilder2/blob/master/Projects/WIN10XPE/_CustomFiles_/PEMaterial/unattend.xml

call TextReplace the Architecture="amd64" to x86, if you build x86 PE.
call TextReplace to config the ComputerName, EnableNetwork, EnableFirewall, ...

@slore: Are you using PENetwork as a network manager or the native Windows network manager in your PE build?

I just look at the interwoven design concept of XPE and its distribution or Release to the Mass General Public..

This is one user with one certain request to support a certain application...

Basically asking how to customize the Project to support his needs....

For which I feel is not Project Release Related...

Although 5 modifications have been suggested to support the request..

We can wait for a fancy fix from ChrisR

As that decision rests solely in his hands in regards to the Project Release

@slore: Are you using PENetwork as a network manager or the native Windows network manager in your PE build?

Both them can be the manager in My PE build. Use both, or use the one you like,
But for small size and more customization, I perfer 3rd part application, PENetwork is good.

Both them can be the manager in My PE build. Use both, or use the one you like,
But for small size and more customization, I perfer 3rd part application, PENetwork is good.

Thanks for your information. I also prefer PENetwork app.