You should be able to load Windows directly ... if that is what you are asking about.
If you cannot see where/how to do this, please boot the DBG version and share the log it produces.
This will be in the same ESP you ran RefindPlus from.

Got it. I was a bit loose with my words when I said you can load Windows directly, as no, you currently cannot in the way you meant.
That is, RefindPlus always loads the Windows Boot Manager on the ESP for UEFI Windows and does not try to run files from within Windows.

The log shows RefindPlus is working as expected. I cannot offer anything on why the Windows Boot Manager is not doing what it is meant to.
Perhaps try disconnecting one of the Windows instances each to see if there is any difference in the outcome.

ok...what i don't understand: the first time the windows bootmanager is entered by refind it shows the selection menu. the second time it boots directly into the windows partition selected before.....so is't it possible to call the windows boot manager for example with a parameter to tell it to boot directly a specified partition (as done the second time its entered)?

When you say "refind", do you mean RefindPlus or rEFInd?
Best to spell precisely to eliminate confusion.

In terms of params, yes it is possible to pass params to items being called but RefindPlus does not pass any params to UEFI Windows.
That is, any difference in behavior is not down to parameters being passed:

000-Snip1
000-Snip2

This is unless you meant rEFInd but I don't think that passes any params either

That is, any difference in behavior is not down to parameters being passed

Well, on thinking about things a bit, while RefindPlus is not passing any params, it does not mean there no params in play as you summised.

What may be happening is that the Boot Manager could be looking for a Boot#### nvRAM variable, then setting this and returning to whatever started it if absent, and then, if run again, picking this up and using it.

RefindPlus could set this for the first boot if what it is is known. You can try the following to check:

• Load RefindPlus and load uEFI shell
• Run dh -d -v > dh_d_v_before.txt
• Exit shell and load UEFI Windows
• When you are returned to Refindplus, load the shell again and run dh -d -v > dh_d_v_after.txt
• Exit the shell and continue

Share the files to see what, if anything, changed between the two runs.

NB: You probably need to enter FS0: before running those shell commands
The RefindPlus package may contain a UEFI shell file but I forget.
If it does not, you can get one here: https://github.com/tianocore/edk2/tree/UDK2018/ShellBinPkg/UefiShell/X64.
See here for HowTo: #105 (comment)

Hi again,
to be more precisely - yes i'm talking about "refind PLUS". sorry for not being clear enough.
Have implemented shell and executed the commands suggested by you....there are some differences, but i'm not able to interpret if they are relevent or not.
Files are attached.
dh_d_v_after.txt
dh_d_v_before.txt

Thanks but sorry, I gave you a command for different output.

Please use these instead:

• dmpstore > nvram_dump_before.txt
• dmpstore > nvram_dump_after.txt

I will still look that the ones from earlier (they show what images are loaded)

PS: Correct spelling is RefindPlus for this and for the upstream project, rEFInd

hmm, not so good news - both file are identical. So it seems that Windows Boot Manager handles this "internally"

I see. Well, it was just a wild idea to potentially work around what seems to be a broken/misconfigured setup.

The Windows boot manager should not be loading something else on selecting a Windows instance it presents. You need to look into how and why this is so and fix it. Best bet is on a Windows support channel.

Good luck!

The site's sugested fix makes sense. Technically though, it is fixing a "misconfiguration" from the Windows boot manager's perpective.

Before you make the changes suggested there, try to save copies of the BCD file before and after to see whether this is how the "Params" are being passed (I suspect it is). It might be possible to add something to RefindPlus to read/amend the BCD as needed if so.

mentioned method works well :-)) WindowsBootManager starts windows directly, when there is only one posibility available ...and have hidden the original MicrosoftBootManager.
if you're interested in - BCDs are attached (had to rename them to *.zip as upload without extensions was not possible)
BCD_both.zip
BCD_gaming.zip
BCD_working.zip

Thanks. Nice.

What I was actually thinking might be useful was to go through a version of the steps I outlined for the nvram dump but with the orignal BCD instead. The boot manager must be amending this as the BCD is effectively an extension of the nvRAM. Can then try to figure out what is changed.

• Load RefindPlus, unhide the orignal windows entry and load uEFI shell
• Run cp /Path/To/Orignal/BCD /Path/To/Orignal/BCD_BEFORE
• Exit shell and start load UEFI Windows with the previously hidden instance
• Select same Windows instance that triggered the previous behaviour
• When you are returned to Refindplus, load the shell again and run cp /Path/To/Orignal/BCD /Path/To/Orignal/BCD_AFTER
• Exit shell and continue

Basically trying to see what gets changed.
Can perhaps then, at some point, look at modifying RefindPlus to make similar changes before trying to load the boot manager.