setup : Throws an exception error when used to gather custom facts for Windows targets. about ansible.windows

[briantist]

As @jborean93 mentioned in your original issue:

For this particular problem we changed the behaviour of PowerShell modules always running with $ErrorActionPreference = 'Stop' whereas before some were set to Continue and errors were just being ignored. The problem you have here really should be fixed in your custom facts script to properly handle errors that it raises and either ignores them or continues to error if you want the end user to see that error and somehow fix it.

The error is popping up from a script in that directory. It seems that before 2.8 the script there would still have been broken, it just would have been ignored.

I recommend you try putting one script at a time in there to see which one is failing, and then if possible post that script.

If you can't post it, maybe try executing it yourself like this:

powershell.exe -NonInteractive myscript.ps1

And see if you can get a better error message with line number.
You might have something in the script that prompts for user input.