Created attachment 1957937 [details] Debug logs of the operator (wmco) Description of problem: When checking for services on a remote windows host (installed from another base language than en-us), the Windows Machine Config Opertaor (WMCO) crashes and restarts the bootstrapping process again (indefinitely). In my case, the machine has been created from a french installed windows 2022 template. As you might see in the log attached, because the "out" key value does not match what the controller wants, the golang process crashes and a stack trace is written to stdout. It would be great to support multiple languages by having to rely only on error codes instead of parsing errors. Version-Release number of selected component (if applicable): OpenShift 4.12.8 and WMCO 7.0.1 How reproducible: Every time Steps to Reproduce: 1. Create a golden image from the french 2022 server ISO 2. Add the machineset as you would normally with WMCO 3. Add a machine Actual results: The machine is never bootstrapped and added to the cluster. Expected results: Have the windows host added to the OpenShift Cluster, wether it is in french or not. Additional info: It may be an issue that there is no error catch going on. Because the WMCO loops on failure, it will never provision the other machines in queue to be bootstrapped. As it might fail for any other reason than language it would also be great to have error cactches.