Apps on Y-?-Drive not present at UEFI -Boot

Hey Guys,

First: I am no programmer, I am No coding expert i am just a small enduser who would like use things only. I have no other intension.
Therefore please made instructions as easy as possible:)
To the problem:
I createt an winp se-.iso. It works so far. It seems that the apps i use are on an  y-Drive? wich is mountet at start? So it seems for me.
The Problem is now, that even on normal mbr-boot?, sometimes the y-drive with the apps is also not there.
If i try uefi/secure -boot then there are no y-drive and apps on it at all. I have only a few standard apps like it seemed, but no apps on y-drive...
How can i make now, that the y-drive and the apps on it are allways and exspecialy in uefi-boot are present?

regards
 

Hi enduser,

It seems that the apps i use are on an  y-Drive?

default yes

wich is mountet at start?

no or yes, up to condition ...

I have only a few standard apps like it seemed,

-->
Short answer:

on Build\"CdDrive - X: - Y:" Plugin
 Enable "Run All from Ram"

Let us know the result. 

Thanks a lot Lancelot for this hint!
If i do so, would this raise the amount of ram the target system needed to start the iso?
My goal is to have such low requirement as possible for running the project.
This brings me to another question: To reach this goal is it better to use x86 or 64bit build?
If an x86 build is is used on an x64 target system, has this somehow limitations?

Hi enduser,

Spend some time (few days) with the project and test yourself to see which options fit your goals. 

You will get better and faster answers with your tests instead of a reply on a topic during the learning period.

That is one of the reasons projects created with many options instead of a simple builder.

New PE end-users always have similar startup questions for 10 years TheOven.org created,
 after spending a short time they quickly figure out themselves. 

To reach this goal is it better to use x86 or 64bit build?
If an x86 build is is used on an x64 target system

At UEFI uses the same bitness to boot.
Almost all x64 machine uses a 64bit UEFI. Use a x64 PE then.

Hey,
thanks guys.

Sure i am on it with self tests, like the whole time.
I change things, create new ISOs. Test them and thats the way i learn a lots of things.
To speed up my learning curve and that i don t have to invent the wheel each time its neverthless
very helpfull to just answer some basic questions, wich might be easy to answer for the experts; )

So wich project needs more ram on the target system: an x86-build.iso, or an x64.build.iso?
And also again, will i have limitations if i boot an createt x86-winp-se.iso on an x84 target system - the questions is for mbr-boot and for uefi-boot.
To answer this questions help to make more specific goal-orientet tests: )

regards

x86 is usually smaller (File Size) and requires less system memory to load
x86 will not boot in UEFI Mode - except on systems with "ATOM" processors
x86 will boot x86 & x64 systems in Legacy (MBR/Bios) mode - if Legacy/CSM Support enabled in Bios
Keeps Options to a the minimum as possible to insure ability to Load WinPE into Low System Memory PC's

Thank you James!

Sorry, its quoting allways the whole text, but i want only quote several pasages.
So i must make this this way:

"x86 is usually smaller (File Size) and requires less system memory to load"

Exactly this i wantet to know. I already sugestet that this will be the case...

"x86 will not boot in UEFI Mode - except on systems with "ATOM" processors"

Interesting that expection here is with atom processors. But exactly this i have feared.
I also think on my lazy friends with creating the system. It should also rin on their machines, for diagnostic and recovery tasks.
An female friend for example bought this teribble surface and she don t listen to me to give this crap back. Its so beatiful and so light and the great display and stuff she answers. Girls are not thinking logical in the most case, you know: )
But she is exact the case, becouse my project should also boot on uefi -machines. If i have this correct in mind, it was not possible to disable uefi on this surface. Maybe it was also not even possible to disable secure boot.
I would never buy such a crap like microsoft-surface....Terrible syste, really horrible!

"x86 will boot x86 & x64 systems in Legacy (MBR/Bios) mode - if Legacy/CSM Support enabled in Bios"
Ok, then i have to create an lightweight x86-project and an lightweight x64 -project that i can work with all possible systems i will be confrontet in the field (my lacy friends computers:)

regards

Update1:

Problems occured. The x86-build gives me a bluescreen with the error "multiprocessor configuration is not supportet".
Can t be. Bad joke?: )
As you can not just use actual win10.iso images for build, i used the recomendet version: Win10_1809_German_x32.
I also know there is an project arin or similiar with wich you can  use atcual win10.IOs. But this leads to other problems. So i must use the spoken old ISOs of Windows10 for the project.
With the x64 Version of this old 1809 version: "Win10_1809Oct_v2_German_x64", build is working, no bluescreen with error.
Strange, isn t it?
The only thing i can try on this point is useing a still older 32bit Version of Windows10. I still have this Version: "10240.16384.150709-1700.TH1_CLIENTENTERPRISE_S_EVAL_X86FRE_DE-DE"
If its also not working, then i stuck on this point, till the problem wich leads to this multiprocessor-nonsens BSD is solved...

Update 2: Stranger things :)

The builded project with "10240.16384.150709-1700.TH1_CLIENTENTERPRISE_S_EVAL_X86FRE_DE-DE".iso, works.
No multiprocessor bluescreen like if i use "Win10_1809_German_x32".iso.
I don t understund that.
Strange, but so far so good. I got only a error on driver path/patch/inject -something, while building the project with ""10240.16384.150709-1700.TH1_CLIENTENTERPRISE_S_EVAL_X86FRE_DE-DE"".iso,
, but the buidling -process goes on to the end and the iso seems to work. At least i don t get the spoken BSOD; )

Win10_1809_German_x32.

I am downloading Win10_1809_German_x32.iso now

I also know there is an project azin or similiar with wich you can  use atcual win10.IOs. But this leads to other problems.

what are these "other problems" ?

Strange, isn t it?

not much, life 
 we can not test all projects with all languages and with all none-rtm sources,
  I mostly test with en-us source, till one day one report something with another source & lang
      (eg. now downloading Win10_1809_German_x32.iso  )

No multiprocessor bluescreen like if i use "Win10_1809_German_x32".iso.

just downloaded and tested, works fine with 1 processor 1 core, also 2 processor 2 cores (=4)  ......

Tip: You can enable \"Basic Project" Plugin to make Basic test builds (mostly to test different sources) which will be faster 

Win10_1809_German_x32.

I am downloading Win10_1809_German_x32.iso now

Sorry for make you work. That was not my intention, but thx a lot for your help.

I also know there is an project azin or similiar with wich you can  use atcual win10.IOs. But this leads to other problems.

what are these "other problems" ?

Had some error messages and building stops. From this point, i was goeing back to 1809.64bit wich was working.
Did no further investigation becouse becouse lack of knoweldge and used again the last working method. Typical enduser behaviour: )

Strange, isn t it?

not much, life 
 we can not test all projects with all languages and with all none-rtm sources,
  I mostly test with en-us source, till one day one report something with another source & lang
      (eg. now downloading Win10_1809_German_x32.iso  )


[/quote]

Oh, i should i also mention, that added to the scripts from win10p-se, scripts for tools wich i need for working.
I can t of course not exclude that perhaps some of this script is responsible for the spoken error.
It should not, but life...you never know what happens:)

Sorry for the quoting disaster above: )

"You can enable \"Basic Project" Plugin to make Basic test builds (mostly to test different sources) which will be faster  "

Sure, i also had a similar suspect. I test a build with basic scripts only.

Hi enduser,

I do not know which "Plugins" you add.
 We call them Plugins since they will only work projects that use Plugins
  (for today: Gena Azin-WimBuilder Azin-LiveSystemPro Win7PESE Win8PESE Win8.1SE Win10PESE)
    They will not work with other projects ...

Further write Plugin 

*
> Had some error messages and building stops. From this point, i was goeing back to 1809.64bit wich was working.
> Did no further investigation becouse becouse lack of knoweldge and used again the last working method. Typical enduser behaviour: )

Well I am trying to get things to work out of the box knowing Typical enduser behaviour,
 but if I do not have problem here I need some info from end user side  to figure out special condition at end-user side.

*
I do not know which Plugins you add, but you seem to drive fast and crash faster 

Take it easy.
 step by step. 

Hey Lancelot,

thx a lot for your work, your explanation and especialy for your patience; )

"I do not know which "Plugins" you add."

It was some plugins from my former win7pse -build.
But wich plugins it was exactly, i also don t know anymore, becouse i copied them just in the folders wich i think it belongs, for example filemanagers i copied to file-tasks and so on.
It gona get funy to try to find out wich plugins it were excatly.
I think i don t notice the problem with the bluescreen, becouse of multi processor configuration wich i get actual, becouse i used this older win10.32 -bit -entprise image wich works for some reasons wich i don t know.
With this 1809.x86 -image it is not working.
I also tried basic build. Also with this build i get this multiprocessor config -bluescreen.
This time, i made an foto from it and attached it.
If i understood you correct, basic-project, should override plugin -settings and useing only basic plugins. So this bluescreen shouldn t have appeard.
But i get this blurescreen. Very strange..


"Well I am trying to get things to work out of the box knowing Typical enduser behaviour,
 but if I do not have problem here I need some info from end user side  to figure out special condition at end-user side."

Comprehensible:) Thats all things wich can be done, after the major goal is reached.
My workflow is first to solve the task, then i make additional tests.
At the moment i have unfortunatly problems to finish the task becouse of this mentioned bluescreen.
I can go now back to use again the working enterprise x86.iso for bulding wich works, or find out why i have this strange not logical problem...
So, the best is step by step, you are right!

regards


Edit: qr-code from the foto removed becouse i don t know if it can contain sensitive informations, but propably i am only to paranoid; )

Hi enduser,

step by step, have a fresh start 

- Extract Win10PE_SE_2020-03-28.zip to an empty folder
- Start builder
- Use Utils\"Update Win10PESE (Exact and Secure)" Plugin --> Click "Update (Download + Copy)" Button

Make a working build and test with an emulator to see if it boots fine on virtual
we have
VirtualTest\"VirtualBox Virtualization" Plugin
VirtualTest\"VMware Virtualization" Plugin
to test easily
(After Build, use small green play button on Plugin UI)

After you can get Win10PESE boot with Virtual, you can dig more.

The above steps are written to ALL "Typical end-users" for years and work fine to figure out things.

*
Well there is no clear information on your reply about questions I ask,
 as written before,
  Take it easy,
     slowly with step by step 



Edit:
https://errortools.com/windows/how-to-fix-multiprocessor_configuration_not_supported-error-in-windows-10/
https://windowsreport.com/multiprocessor_configuration_not_supported-windows-10/

Back 2 basic but struggle with this BSOD continues; (

In the meantime, i did the most you recomendt.
I was goeing back to the original archive, extractet it again and statet to build with the 1809.x86.iso.

"- Use Utils\"Update Win10PESE (Exact and Secure)" Plugin --> Click "Update (Download + Copy)" Button"

This was the only thing wich i did not. I check do this yet, but i don t think that it will solve the problem.
The result is at the moment, i get again this spoken bluescreen.
The Image is working correctly in virtual box. I onlny get this bluescreen with real hardware....
Is maybe my 1809.x86 -iso defective? But i don t think so.

"Well there is no clear information on your reply about questions I as"

Maybe i over read it. What do you want to know? Sorry.

Hi enduser,

let's go step by step

*

"- Use Utils\"Update Win10PESE (Exact and Secure)" Plugin --> Click "Update (Download + Copy)" Button"

Good 

*

The Image is working correctly in virtual box.

Good news.

*

"Well there is no clear information on your reply about questions I as"

Maybe i over read it. What do you want to know? Sorry.

one of them:

I also know there is an project azin or similiar with wich you can  use atcual win10.IOs. But this leads to other problems.

what are these "other problems" ?

?????????????


*********
First Step:
since x86 fail, and following your bsod picture ... :

Enable "Basic Project" Plugin + "make sure Run All From Ram enabled" + Try with Win10_1809_German_x64 source

only 3 parameters with default project 

you can get rtm source from https://tb.rg-adguard.net/public.php
 (which I and most regular-users around %99.9 test with)

I do not know how you boot or prepare boot media,
 you can prepare your ufd (usb flash disk) with Virtual Test\"Copy to USB-Device" Plugin
   (after Build (BigBluePlay), use small green play button with \Virtual Test\"Copy to USB-Device" Plugin
    ufd will be formatted ...
    )
 
+ first make sure you boot fine on vbox
+ and let's see how it goes on your real hw test
+ and ????????????? 

-
fixed (edit) my previous reply
since you will be testing with Win10_1809_German_x64 source
better use Virtual Test\"Copy to USB-Device" Plugin