I found some time to play around with this a bit more. It turns out the
initial installer spawns multiple processes and doesn't actually wait until
it is finished. This causes the parent WinRM process to close it's shell
which has the side affect of killing any children it spawns.
It's weird
Ansible is a very popular project by any metric. Our delightful community
contributes numerous Pull Requests (PRs) every month. Unfortunately, the
volume of incoming PRs means contributors often have to wait days, weeks,
or months for PRs to be merged. Sometimes it takes that long for a
Thank you Jordan! I just tried the suggestion and it works great! I agree,
the installer is terrible to begin with. I initially wanted to do a
chocolatey package but it was overwhelmingly even more complex too learn
for this type of installer. I really appreciate your help and test
On Thu, Feb
