Win10XPE - Build Your Own Rescue Media [2]

Xenithar · 16 Sep 2022

Not to sound rude, but I'm not running DOS. Why on earth would I extract to the root of any drive? I am in IT security and that's a massive no-no. Yes, I understand file-level permissions quite well and those aren't an issue. Does this have to do with the max path? In 9X it was 256 characters but I believe it's far higher now. There are no spaces in the path either.

So would you please explain why we need to use the root of a drive? I can understand why you wouldn't extract it to Program Files or the Windows paths, but why not my user folder, where I have full permissions?

Oh and to your response about Ventoy, I absolutely LOVE Ventoy. I have my official MS ISO images on a 32GB drive with Ventoy and my Linux ISOs on another 32GB drive. Ventoy is the best booting tool I have ever found.

Kyhi · 16 Sep 2022

"Not to sound rude" -
Well, you did..

Xenithar · 16 Sep 2022

Again, I wasn't trying to, but whenever one challenges another without being able to hear their voice or see their face it seems to come across badly. I was not trying to insult you, I simply want to know why a method that hasn't been used in 30yrs is recommended here. The only two reasons I could think of (permissions and/or max path length) I asked about and I was being genuine. If there is some other reason I want to know it, not only for making this build work, but because I could apply it in my day-to-day work. The thing is, Microsoft and most people who train/educate the IT/IS community recommend against this. I am simply asking why it is required here, especially considering that the program itself runs as admin and has full permissions to everything.

doudiii · 17 Sep 2022

Xenithar said:

... The only two reasons I could think of (permissions and/or max path length)....

remove the limitation
gpedit
Computer Configuration > Administrative Templates > System > Filesystem > Enable NTFS long paths.

tested
" C:\Users\cretino\Desktop\Win10XPE" all ok
"C:\360Down\Win10XPE-WIn10XPE_2022-01-07\Win10XPE-WIn10XPE_2022-01-07\Win10XPE_2022-01-07.7z\Win10XPE" ok
but "TorBrowser_x64" not ok ,i changed this to work under this path

Code:

//Run,%ScriptFile%,Extract
//--
If,ExistDir,%Target_Prog%\%ProgramFolder%,DirDeleteQ,%Target_Prog%\%ProgramFolder%
If,Not,ExistDir,%Target_Prog%,DirMake,%Target_Prog%
//DirCopy,%GTemp%\%ProgramFolder%,%Target_Prog%
ShellExecute,Hide,%GTools%\7z.exe,"x #$q%SetupFile%#$q -pWin10XPE -y -o#$q%Target_Prog%\%ProgramFolder%#$q"
//--

nb : remove the limitation = biggg security hole

personally,i do not recommended

@ JakubJ
as Kyhi said We use Ventoy as an ISO boot solution
here is ex with ventory mounted as Y:

Win10XPE - Build Your Own Rescue Media [2]-sshot-1.jpg

Kyhi · 17 Sep 2022

The "ROOT" is the first folder structure on a Drive ( Just like C:/Windows ) - what you are suggesting is everything should run from within "Microsoft" root folders... According to "Microsoft" maybe......

But to followup on that "WE" suggested using your Data Drive...

Win10XPE - Build Your Own Rescue Media [2]-image102.jpg

And if your TOR 64 is failing - please forward me the script you are actually using.....

Kyhi · 17 Sep 2022

Code:

ShellExecute,Hide,%GTools%\7z.exe,"x #$q%SetupFile%#$q -pWin10XPE -y -o#$q%GTemp%\%ProgramFolder%#$q"

"H:\Win10XPE\Temp\TorBrowser_x64\firefox.exe"

Code:

DirCopy,%GTemp%\%ProgramFolder%,%Target_Prog%

"H:\Win10XPE\Target\Program Files\TorBrowser_x64\firefox.exe"

And the reason we use the [ EXTRACT ] process is so that you can run TOR 64 on the Host PC via the "Launch" Button

Win10XPE - Build Your Own Rescue Media [2]-image103.jpg

And Yes, We try to avoid Long File Paths & using C:\ Drive...
What good is a Recovery Option if it is on the Drive you are trying to recover
I boot directly into Win10XPE from H:\ (Host Boot Option)

---------------------------------------------------------------------------------------------------

1) You will need to allow a Windows Defender "Exception" for Win10XPE (ie. Project-Directory-Folder)
I would suggest the same exception for any A/V software, in order to allow the Program Exe's to run
without being blocked by your Host System....

2) Download 7-ZIP 32-Bit x86 Installer or 7-ZIP 64-Bit x64 Installer to open the Project's File Archive

3) Download The Win10XPE*.7z Project File(s)

4) Extract The Archive File(s) To Your Data Drive ( D:\Win10XPE )

Xenithar · 17 Sep 2022

Fair enough, if it is for the long path issue I get it. Windows is still in 1985 in this aspect. I do run a Windows 10 VM exclusively for this process, so I can do it if I have to. Also, Defender is dead in the VM. Group Policy disabled it.

Again, I apologize for offending you previously. I respect you and the work you do, I just get taken aback when I see advice that goes against the grain and I know I can come across as gruff. My bad, and thank you both for your explanations.

Hans1 · 20 Sep 2022

Dear Kyhi,

to day the release of Windows 11 2H22 22621-382 started.
Can you tell when the support of XPE for 2H22 will be released ?

hans1

Kyhi · 20 Sep 2022

Not really.... Tested 22H2 Release

Win10XPE - Build Your Own Rescue Media [2]-screenshot00001.jpg

Hans1 · 21 Sep 2022

Hi Kyhi,

unfortunately it does not work for me with windows 11 pro 22621.

Can you maybe share your current XPE files or show us your settings in the "build core" and his "subpoints".

thank you