EKS, Windows node. networkPlugin cni failed, Failed to create pod sandbox

Hi Team, I am new in EKS and launching self-managed Windows nodes but my pod is stuck into “ContainerCreating” status while creating POD on windows node.
I am following below steps to create it.
1) Managed nodes – Linux - Step 1 to Step 4 to create cluster with Linux (https://docs.aws.amazon.com/eks/latest/userguide/getting-started-console.html)
2) Deployed Linux workload to test (https://docs.aws.amazon.com/eks/latest/userguide/sample-deployment.html). The Linux node is working properly.
3) Enabling windows Support (To enable Windows support for your cluster with a Windows client) (https://docs.aws.amazon.com/eks/latest/userguide/windows-support.html#enable-windows-support)
4) Launching self-managed Windows nodes (AWS Management Console) (https://docs.aws.amazon.com/eks/latest/userguide/launch-windows-workers.html)
5) Deploy a Windows sample application(https://docs.aws.amazon.com/eks/latest/userguide/windows-support.html#windows-sample-application)
While investigating (describing POD) I am getting below error.
Warning FailedCreatePodSandBox pod/windows-server-iis- Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container network for pod "windows-server-iis- ": networkPlugin cni failed to set up pod "windows-server-iis- _default" network: failed to parse Kubernetes args: pod does not have label vpc.amazonaws.com/PrivateIPv4Address
Some more input.
1) I am using Freetier account.
2) I am using t3.Micro for Managed Node for Linus (along with Cluster) with 2 nodes – Step 4 in point 1
3) I am using 2.micro for Self self-managed Windows nodes with 2 instance node – in point 4 above.
4) Not creating any addition VPC/Security Group/ Role/ServiceAccount or IAM Policy other then given in above steps.
5) I can see POD with
Limits: vpc.amazonaws.com/PrivateIPv4Address: 1
Requests: vpc.amazonaws.com/PrivateIPv4Address: 1

Start with the linked EKS Windows support and self-managed Windows node documentation, then reproduce the deployment and inspect the FailedCreatePodSandBox event for the missing vpc.amazonaws.com/PrivateIPv4Address label. Done means identifying whether the documented setup is incomplete or the Windows networking integration is failing, and recording a confirmed resolution or documentation change.

Written by the indexing model from the issue text.