[ BUG ] Import-FalconConfig failing on PowerShell Core with Key cannot be null error

[quantmn5]

Describe the bug
I'm still facing issues with build 2.2.2 while importing a previously exported falcon-config.
Importing host-groups, prevention policy and response policies are all failing.
I try to import a config-export for a freshly provisioned Customer ID (no config set besides default prevention policies).

Not sure if i'm doing anything wrong here.. it all worked fine in the second last version. PSFalcon 2.2.1 did not work, neither is the current version.

To Reproduce
Simply using the import-FalconConfig with or without -assignexisting /-modifyexisting / -modifydefault flags results in the errors you can find in the attached screenshot.

Expected behavior
I expect the config to be imported properly.

Environment (please complete the following information):

• OS: Windows11
• PowerShell: 7.2.6
• PSFalcon: 2.2.2

Additional context

Transcript content
Invoke-FalconPreventionPolicyAction: C:\Users\username\Documents\Powershell\Modules\PSFalcon\2.2.2\Public\psf.config.ps1:340

$PolicyID | & "Invoke-Falcon$($Type)Action" -Name $Action
Cannot validate argument on parameter 'Id'. The argument " " does not match the "^[a-fA-F0-9]${32}$" pattern.
Supply an argument that matches "^[a-fA-F0-9]${32}$" and try again.

[bk-cs]

I was able to narrow down the error (which only occurs when using PowerShell Core) to the Confirm-Parameter private function. Through some testing, I believe I have an updated version of Confirm-Parameter that will fix this problem.

Can you replace the contents of the Private\Private.ps1 file in your local PSFalcon module with the contents of the file below?

https://raw.githubusercontent.com/CrowdStrike/psfalcon/2.2.3/Private/Private.ps1

Once complete, you'll need to reload PowerShell, re-import PSFalcon and retry Import-FalconConfig.

[quantmn5]

Works perfectly fine with the new Private.ps1 file. Thanks for your support!

[bk-cs]

Leaving open in case others run into this issue before the 2.2.3 release.

[bk-cs]

Resolved in v2.2.3 release.