Topic: Win10XPE Project (Read 141367 times)

« **Reply #500 on:** February 18, 2019, 03:08:41 PM »

Sure - it is very odd as it works fine for full winre.wim build every time. I have disabled my AV too and still 100% repeatable!
I get this error in dialogue box:
---------------------------
Error
---------------------------
Cannot create file "H:\Win10XPE\Temp\WimSmallUpdate". The process cannot access the file because it is being used by another process: TXTDelLine,%w%,"delete '#1\#9' --force --recursive"
---------------------------
OK
---------------------------
The file is 0 bytes in size when examined afterwards.
I copied whole \Win10XPE folder to a spinning (old fashioned) disk drive and winbuild gives same error as I thought maybe it was timing issue.
I also tried extracting the Source ISO contents to a spinny drive (instead of using ImDisk to mount it) with same results.
Any ideas?

« **Reply #501 on:** February 18, 2019, 03:21:50 PM »

I also thought about a timing issue but since the process is the same in both cases, unfortunately I don't see, no idea

My Edit on my previous post, in case you hadn't seen
Maybe Tries to grant full administrator rights on the WIn10XPE base folder
And try again with the latest version, just published Win10XPE_2019-02-18 update
See you, I have to go...

« **Reply #502 on:** February 18, 2019, 03:44:47 PM »

Just did a Build with "Full Winre.wim with light WinSxs" (Always My Default Build Selection)
And with "Use Architecture for Target and ISO" (Usually I do not use Multi-Arch Folders)
Without An Issue...

I would test a few things..
manually delete Target and Temp Folders
Empty Recycle Bin
Reboot PC

And Test by
Deselecting Use Architecture

« **Reply #503 on:** February 18, 2019, 05:18:53 PM »

Quote from: Steve6375 on February 18, 2019, 03:08:41 PM

Sure - it is very odd as it works fine for full winre.wim build every time. I have disabled my AV too and still 100% repeatable!
I get this error in dialogue box:
---------------------------
Error
---------------------------
Cannot create file "H:\Win10XPE\Temp\WimSmallUpdate". The process cannot access the file because it is being used by another process: TXTDelLine,%w%,"delete '#1\#9' --force --recursive"
---------------------------
OK
---------------------------
The file is 0 bytes in size when examined afterwards.
I copied whole \Win10XPE folder to a spinning (old fashioned) disk drive and winbuild gives same error as I thought maybe it was timing issue.
I also tried extracting the Source ISO contents to a spinny drive (instead of using ImDisk to mount it) with same results.
Any ideas?

Perhaps try this tool. https://www.sordum.org/11263/streams-remover-v1-0/

« **Reply #504 on:** February 18, 2019, 05:30:45 PM »

@ChrisR
WOW, Just Noticed The Edits To The First Post Of This Project...
Very Nice With New Description and Project Pictures...

« **Reply #505 on:** February 18, 2019, 05:52:35 PM »

Thank you very much for the new version (today) @ChrisR.

I just tried it and commented on a problem I found. I have selected WoW64Basic in BuildCore, but when I try to run an x86 program in Win10XPE_x64 I get an error.
Does someone else have this?
Greetings.

« **Reply #506 on:** February 18, 2019, 05:57:55 PM »

Quote from: teik on February 18, 2019, 05:52:35 PM

Thank you very much for the new version (today) @ChrisR.

I just tried it and commented on a problem I found. I have selected WoW64Basic in BuildCore, but when I try to run an x86 program in Win10XPE_x64 I get an error.
Does someone else have this?
Greetings.

was your error something to do with corrupt side by side configuration? if so then yes I had it to when trying to run HDD low level format tool

« **Reply #507 on:** February 18, 2019, 06:15:02 PM »

Oups, My fault Sorry, an error indeed in WoW64 basic plugin

Code: [Select]

ExtractWimFile,\Windows\WinSxS\x86_microsoft.windows.c..-controls.resources_*_%Language%_*,WildCards
ExtractWimFile,\Windows\WinSxS\Manifests\x86_microsoft.windows.c..-controls.resources_*_%Language%_*.manifest,WildCards
==>
ExtractWimFile,\Windows\WinSxS\x86_microsoft.windows.c..-controls.resources_*_%Language%_*
ExtractWimFile,\Windows\WinSxS\Manifests\x86_microsoft.windows.c..-controls.resources_*_%Language%_*.manifest

I fix and update ~ 1h
Thanks for reporting

« **Reply #508 on:** February 18, 2019, 06:16:05 PM »

Quote from: ChrisR on February 18, 2019, 06:15:02 PM

Oups, My fault Sorry, an error indeed in WoW64 basic plugin
Code: [Select]
ExtractWimFile,\Windows\WinSxS\x86_microsoft.windows.c..-controls.resources_*_%Language%_*,WildCards
ExtractWimFile,\Windows\WinSxS\Manifests\x86_microsoft.windows.c..-controls.resources_*_%Language%_*.manifest,WildCards
==>
ExtractWimFile,\Windows\WinSxS\x86_microsoft.windows.c..-controls.resources_*_%Language%_*
ExtractWimFile,\Windows\WinSxS\Manifests\x86_microsoft.windows.c..-controls.resources_*_%Language%_*.manifest
I fix and update ~ 1h
Thanks for reporting

Thank you very much and sorry for not specifying more details of the problem, I was writing from the mobile.

- In Pecmd.iini it comes by default like this:

Code: [Select]

// LetterSwap
//EXEC =!%WinDir%\System32\LetterSwap.exe /auto /bootdrive Y:\CDUsb.y /Log %Temp%\LetterSwap.log
EXEC =!%WinDir%\System32\LetterSwap.exe /auto /bootdrive Y: /Log %Temp%\LetterSwap.log

But I had to add this as in the example discussed in the file.:

// LetterSwap
//EXEC =!%WinDir%\System32\LetterSwap.exe /auto /bootdrive Y:\CDUsb.y /Log %Temp%\LetterSwap.log
EXEC =!%WinDir%\System32\LetterSwap.exe /auto /bootdrive Y:\CDUsb.y /Log %Temp%\LetterSwap.log

Because otherwise it did, Win10XPE detected my letter C: (Personal installation of windows) like the Y:. It is for this reason that programs could not be loaded from USB.

« **Reply #509 on:** February 18, 2019, 08:06:59 PM »

The package Win10XPE_2019-02-18 update has been updated with only the above modification.
Well, I'll update it again for LetterSwap /bootdrive Y:\CDUsb.Y
I had the same problem before in my 1st test with C: remounted on Y:. It seems safer to keep CDUsb.Y marker file, for now.

« **Reply #510 on:** February 18, 2019, 09:00:20 PM »

Update done with the CDUsb.Y marker file and with the same dated package

It seems safer that way, for now.
Thank you teik for your feedback

« **Reply #511 on:** February 19, 2019, 12:15:08 AM »

Re. My Build error: Later version still has same issue.

[Success] TxtAddLine - Added line: [%BaseDir%\Temp\WimSmallUpdate] line: Value: delete '\Windows\Boot\PXE\zh-TW' --force --recursive Option: Append
Loop - Processing section: [WimSmallUpdateMui_Loop] From file: [%BaseDir%\Projects\Win10XPE\Core.script]
[Parameter] with parameters: [1],[2],[\Windows\Boot\PXE]
Iteration - Processing section: [WimSmallUpdateMui_Loop] in file: [%BaseDir%\Projects\Win10XPE\Core.script]
[Parameter] with parameters: [1] [\Windows\Boot\PXE]
[Success] StrFormat - converted [SPLIT(en-GB|en-US,|)] to variable: [#9] with result: [en-GB]
[Success] TXTDelLine - Deleted all corresponding lines in file: [%BaseDir%\Temp\WimSmallUpdate] string [delete '\Windows\Boot\PXE\en-GB' --force --recursive]
Iteration - Processed section [WimSmallUpdateMui_Loop] in file: [%BaseDir%\Projects\Win10XPE\Core.script]
Iteration - Processing section: [WimSmallUpdateMui_Loop] in file: [%BaseDir%\Projects\Win10XPE\Core.script]
[Parameter] with parameters: [2] [\Windows\Boot\PXE],[],[],[],[],[],[],[],[en-GB]
[Success] StrFormat - converted [SPLIT(en-GB|en-US,|)] to variable: [#9] with result: [en-US]
[Failed] Cannot create file "%BaseDir%\Temp\WimSmallUpdate". The process cannot access the file because it is being used by another process: [TXTDelLine,%w%,"delete '#1\#9' --force --recursive"]
[Warning] Halt
Iteration - Processed section [WimSmallUpdateMui_Loop] in file: [%BaseDir%\Projects\Win10XPE\Core.script]
Loop - Processed section [WimSmallUpdateMui_Loop] in file: [Loop,%ScriptFile%,WimSmallUpdateMui_Loop,1,%NbLang%,#1]
Run - Processed section [WimSmallUpdateMui] in file: [%BaseDir%\Projects\Win10XPE\Core.script]
Run - Processed section [WimSmallUpdate] in file: [%BaseDir%\Projects\Win10XPE\Core.script]
Run - Processed section [PrepareSmallWim] in file: [%BaseDir%\Projects\Win10XPE\Core.script]
[Clock] Script time: 17 seconds and 781 milliseconds

[Done] Finished processing script: Build Core

« **Reply #512 on:** February 19, 2019, 05:25:30 PM »

Quote from: ChrisR on February 18, 2019, 09:00:20 PM

Update done with the CDUsb.Y marker file and with the same dated package
It seems safer that way, for now.
Thank you teik for your feedback

I still have the same problem when opening x86 programs in the x64 version, it does not allow me to open them. I attached capture.. It's in Spanish but I hope you can understand it.
I tried it with SUMO which is a script made by James, but it also happens with all the executables that are x86.

« **Reply #513 on:** February 19, 2019, 07:14:40 PM »

Update Your 2019.02.18 Download
Win10XPE\Projects\Win10XPE\Features\WoW64.Script
Was Fixed and Just tested as working x86 Apps on x64 build

« **Reply #514 on:** February 19, 2019, 08:11:46 PM »

Quote from: James on February 19, 2019, 07:14:40 PM

Update Your 2019.02.18 Download
Win10XPE\Projects\Win10XPE\Features\WoW64.Script
Was Fixed and Just tested as working x86 Apps on x64 build

Right, I downloaded the new update today and I have tried it, but I still have that error that I mentioned before.
Now I keep doing more tests to be able to come up with a problem.

« **Reply #515 on:** February 19, 2019, 08:30:18 PM »

I just tried again right now from the latest downloaded package.
I have not encountered any problems with x86 Apps, they work normally here
Check that you have these folders and files:

Code: [Select]

; WinSxS Folders
\Windows\WinSxS\x86_microsoft.windows.c..-controls.resources_*_%Language%_*
\Windows\WinSxS\x86_microsoft.windows.common-controls*
\Windows\WinSxS\wow64_microsoft.windows.gdiplus.systemcopy_*
\Windows\WinSxS\x86_microsoft.windows.gdiplus_*\*.*
\Windows\WinSxS\x86_microsoft.windows.i..utomation.proxystub_*
\Windows\WinSxS\x86_microsoft.windows.isolationautomation_*
\Windows\WinSxS\x86_microsoft-windows-servicingstack_*
; manifest Files
\Windows\WinSxS\Manifests\x86_microsoft.windows.c..-controls.resources_*_%Language%_*.manifest
\Windows\WinSxS\Manifests\x86_microsoft.windows.common-controls_*.manifest
\Windows\WinSxS\Manifests\wow64_microsoft.windows.gdiplus.systemcopy_*.manifest
\Windows\WinSxS\Manifests\x86_microsoft.windows.gdiplus_*.manifest
\Windows\WinSxS\Manifests\x86_microsoft.windows.i..utomation.proxystub_*.manifest
\Windows\WinSxS\Manifests\x86_microsoft.windows.isolationautomation_*.manifest
\Windows\WinSxS\Manifests\x86_microsoft.windows.systemcompatible_*.manifest
\Windows\WinSxS\Manifests\x86_microsoft-windows-servicingstack_*.manifest

« **Reply #516 on:** February 19, 2019, 08:41:57 PM »

@Steeve
In your Log extract, the 1st TXTDelLine works but not the 2nd, after the failure of DirMake,...
These are very basic WB functions! I've never seen this in user feedback.
It's not a question of project or choice between Full or Light Winre.wim but clearly a problem with your configuration but I don't know more

« **Reply #517 on:** February 19, 2019, 09:19:45 PM »

@Steve6375

2 ideas:

1)
you seem to have something else on your os that locks .script txt files ! and hence prevent access by builder.

maybe an antivirus that locks files during the scan !

such thing will cause most projects around here fail, have you test with other projects,
I am sure they will also produce similar log failures....

2)
a similar failure also exists if you have a connection to drive that connection is not continuous or fast enough or .. unknown..
Here I have 3TB usb harddisk which I can not use to build or for source cd because ...... !
(also I can not use same 3TB usb harddisk for virtual machines because ...... )
The same disk is fine to archive all my files.

« **Reply #518 on:** February 19, 2019, 10:27:28 PM »

Quote from: ChrisR on February 19, 2019, 08:30:18 PM

I just tried again right now from the latest downloaded package.
I have not encountered any problems with x86 Apps, they work normally here
Check that you have these folders and files:

Code: [Select]
; WinSxS Folders
\Windows\WinSxS\x86_microsoft.windows.c..-controls.resources_*_%Language%_*
\Windows\WinSxS\x86_microsoft.windows.common-controls*
\Windows\WinSxS\wow64_microsoft.windows.gdiplus.systemcopy_*
\Windows\WinSxS\x86_microsoft.windows.gdiplus_*\*.*
\Windows\WinSxS\x86_microsoft.windows.i..utomation.proxystub_*
\Windows\WinSxS\x86_microsoft.windows.isolationautomation_*
\Windows\WinSxS\x86_microsoft-windows-servicingstack_*
; manifest Files
\Windows\WinSxS\Manifests\x86_microsoft.windows.c..-controls.resources_*_%Language%_*.manifest
\Windows\WinSxS\Manifests\x86_microsoft.windows.common-controls_*.manifest
\Windows\WinSxS\Manifests\wow64_microsoft.windows.gdiplus.systemcopy_*.manifest
\Windows\WinSxS\Manifests\x86_microsoft.windows.gdiplus_*.manifest
\Windows\WinSxS\Manifests\x86_microsoft.windows.i..utomation.proxystub_*.manifest
\Windows\WinSxS\Manifests\x86_microsoft.windows.isolationautomation_*.manifest
\Windows\WinSxS\Manifests\x86_microsoft.windows.systemcompatible_*.manifest
\Windows\WinSxS\Manifests\x86_microsoft-windows-servicingstack_*.manifest

I have made a new test, using all the files of this new version less (WoW64_AddFiles.txt and WoW64.Script I used it Win10XPE_2019-02-12 update). Results: with the two files of the previous version, x86 executables work correctly.

I go back to erase everything and use the original files of this update to find if those files that you have commented are found.

« **Reply #519 on:** February 19, 2019, 10:34:45 PM »

Update all the project with also script.project and macro.script

And before rebuilding, save the Target folder.
By comparing them, you should have the same files, without orphan files.