Windows node with powershell as default fails to add to the cluster

Issues observed while adding windows node to the cluster.
Below are the scenarios that were tested:
1. scale up windows node with default set as powershell
2. scale up windows node with default set as cmd - with antivirus enabled
3. scale up windows node with default set as cmd - without antivirus enabled.

Observations:
Scenario 1:Default as powershell.

As the node boots up it immediately goes into deletion and machine gets deleted from backend.

Scenario 2: scale up windows node with default set as cmd - with antivirus enabled

This node booted up and marked "provisioned as a node" in machines output.
However the node never come up a ready state.
This VM is running and doesn't have the issue with the deletion from vSpehre and OCP. 

Scenario 3: scale up windows node with default set as cmd - without antivirus enabled
 
This node booted up and marked "provisioned as a node" in machines output.
However the node never come up a ready state.
This VM is running and doesn't have the issue with the deletion from vSphere and OCP.
With this Node we were able to collect logs directly from it, because Powershell as the default shell was not set.

**IMP: As soon as we set Powershell as the default shell, the node was deleted from vSphere and from OCP too.**   

100%    

    1. add WMCO operator with cluster proxy enabled
    2. use golden image for windows node and configure it to use powershell as default
    3. scale up the machine set
    

 Node never gets added to the cluster   

Node should get added to the cluster