Win10XPE - Build Your Own Rescue Media [2]

Win10XPE does not work (no desktop) with last Fido source Windows 11 23H2 v2 (Build 22631.2861 2023.12)

Kyhi said:

Full WinRE > Missing Required Files
Full Hive > Missing Registry Entries

Also if Camera requires so much editing of existing MTP.Script -
then Camera_XPE.script should be stand alone

I'm doing that. As soon it is finish I'll post it.

Cipri said:

Win10XPE does not work (no desktop) with last Fido source Windows 11 23H2 v2 (Build 22631.2861 2023.12)

Can you please test with my missing files script (see link in the previous posts).

fgaifen said:

Can you please test with my missing files script (see link in the previous posts).

It does not work either, no difference, the problem seems to be StartAllBack.

Cipri said:

It does not work either, no difference, the problem seems to be StartAllBack.

Works with winxshell with my missing files script. After finish camera script i'll investigate that...

Cipri said:

Win10XPE does not work (no desktop) with last Fido source Windows 11 23H2 v2 (Build 22631.2861 2023.12)

Yes. I discovered the same also about a week ago. All will work normally with the v1 download from November but not with the v2 from December. I've seen this happen before. When it happens I usually just wait for the next release of source files or a new release of Win10XPE. Additionally, both Microsoft and Fido seem to offer only the latest non-working version of the source file. So if you don't already have the older working source then where do you get it.

Kyhi said:

Test this please >
MediaTransferProtocol_XPE.Script

Tested but same thing "unable to create video capture filter"

Kyhi said:

,,,,
then Camera_XPE.script should be stand alone

i agree with you, im stil using the old one ...

ffrags said:

Yes. I discovered the same also about a week ago. All will work normally with the v1 download from November but not with the v2 from December.....

its ok "2023-12-12 " 22631.2861

ffrags said:

Yes. I discovered the same also about a week ago. All will work normally with the v1 download from November but not with the v2 from December. I've seen this happen before. When it happens I usually just wait for the next release of source files or a new release of Win10XPE. Additionally, both Microsoft and Fido seem to offer only the latest non-working version of the source file. So if you don't already have the older working source then where do you get it.

Fido now offers only the latest version, it may work or not. To solve this problem I propose to replace in script.project line 139 latest Fido release URL with the 2 last known working Fido releases URLs, one for Win 10 and another for Win 11.

For Win 11 example:
//Set,%FidoURL%,"https://github.com/pbatard/Fido/releases/latest/download/Fido.ps1.lzma"
Set,%FidoURL%,"https://github.com/pbatard/Fido/releases/download/v1.53/Fido.ps1.lzma"

Cipri said:

Fido now offers only the latest version, it may work or not. To solve this problem I propose to replace in source.script line 139 latest Fido release URL with the 2 last known working Fido releases URLs, one for Win 10 and another for Win 11.

For Win 11 example:
//Set,%FidoURL%,"https://github.com/pbatard/Fido/releases/latest/download/Fido.ps1.lzma"
Set,%FidoURL%,"https://github.com/pbatard/Fido/releases/download/v1.53/Fido.ps1.lzma"

That should work. I just downloaded v1.53 from github and ran the powershell script. It actually started to download the source version we need. Doudii shows that v2 is working for him while it doesn't work for us which remains unexplained.

ffrags said:

.... Doudii shows that v2 is working for him while it doesn't work for us which remains unexplained.

the only thing i have added in my basic build is this key

Code:

//Enable Launch Folder Windows in a Separate Process
RegWrite,HKLM,0x4,Tmp_Default\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced,SeparateProcess,1

It allows me to test different shell without any problems ...