- Please see screenshot below for boot options
[ended with "The parameter is incorrect"]
Here's mine. Notice that same Boolean that has been questionable previously in this thread is present in the USB Drive "Firmware Application"
PS>bcdedit --% /enum {fwbootmgr}
Firmware Boot Manager
identifier {fwbootmgr}
displayorder {bootmgr}
{b4ba2f05-6bb4-11e5-836c-806e6f6e6963}
timeout 2
PS>bcdedit --% /enum {b4ba2f05-6bb4-11e5-836c-806e6f6e6963}
Firmware Application (101fffff)
identifier {b4ba2f05-6bb4-11e5-836c-806e6f6e6963}
description USB Drive
badmemoryaccess Yes
So, perhaps you could try listing each entry too? Ah. I see we already have that and badmemoryaccess is only referenced in {memdiag}. But you do have {badmemory} in your GlobalSettings. So what if you removed that item from there; perhaps there is a test to verify that badmemoryaccess is used (one way or another) if badmemory is referenced?
BTW while researching this I found out that the value I have (e.g. Yes) means the "bad memory" can be used! So, why would I need to change it? ; )