You'll have to disable the cluster services from the Host server(s). The cluster configuration is set up on the hosts and guest VMs don't have direct access to this. https://docs.microsoft.com/en-us/powershell/module/failoverclusters/stop-cluster?view=win10-ps
stop-cluster is the powershell command you'll need to use to stop services for all hosts in the cluster and stop the clustered applications.

Thanks Leon
So it may be happening in my environment, as I explained at the time of configuring in possible owners where I only leave a single node as a possible owner the rest deactivates them, at the moment that the node restarts or shuts down, they move to another node
and that It should not happen, the strange thing is that they move in off mode and once the proprietary node starts they move to their origin in on mode.

I was reading and I found this

"For Possible Owners, absolutely, positively not come online on a node that is not a possible owner.If
no possible owner nodes are up, then the groups will still failover to a node that’s not a possible owner, but it will not come online."

The hyper-v specialist is also posting here. So, tell me one additional thing, If he needs to uncheck possible owner. All the preferred Owners have to remain checked, don't you? or what does it depend on?