@cracking-skulls I'm having this same issue. Were you able to resolve it?

I did some digging and it appears bootType is being incorrectly detected as legacy, so the script is formatting the drive as MBR. $env:firmware_type contains the correct value, EFI. I found that the boot type is determined using Confirm-SecureBootUEFI, interpreting a failure to run as legacy boot. This system does not support secure boot, causing Confirm-SecureBootUEFI to crash, although it does use UEFI. Is there a reason Confirm-SecureBootUEFI is used instead of $env:firmware_type for the boot type?

@chavi Thank you Chavi for your reply.
I successfully installed my config on my new server.
The problem was the mysql export.

@tmowdy Yes, I've confirmed the information is correct. I think the cause of this is the image file was too large. Switching to SMB resolves this for me.

1.5.7, no tentative release date yet though.

@mardedude

Same issue hier.
I have also post it at the forum.
link forum post

@theopenem_admin Problem Resolved Thank you. AT least this is here now for others to see if needed!

Okay, I figured it out by reading the manual for another, unrelated module. For those who struggle with the same problem:

Create a script module with the content

if (! (Get-Process X)) { Exit -1 }

where "X" is the name of the process. You can use * as a wildcard, e.g. X* will match any process whose name starts with "X". Set the "Success Codes" value to "-1" and toggle "Use As Condition". Save the module with some name you can remember, e.g. "Check if X is running"

Now, when creating a policy, you can use this module as a condition in the "Conditions" tab and it will only run if the process is not running.