Instance is unresponsive after "cloning" it from the good working instance

I have the instance 'i-01' in us-west2. This is a Windows Server 2016 one. It works fine for years. I can access it via RDP, via Connect in AWS Console. It has SSM and Cloud Watch Agent services installed and running.

I created AMI ami-01 from it and launched a new instance i-02 in the same region from this ami-01. But:

1. One of the 2 Status Checks is Instance reachability check failed
2. I can't RDP to it
3. I can't connect via Session Manager in AWS Console
4. I can't connect via EC2 Serial Console. It gives me Still waiting for meta-data accessibility...

What I tried to do:

1. Reboot i-02
2. Reboot the initial i-01 to verify it will be accessible after rebooting. And it is.
3. Remove i-02 and create a new instance from ami-01. The same result - inaccessible.
4. Copy ami-01 to us-east1 region and create the instance there. The same result - inaccessible.
5. Run CLI command aws describe-instances and compare JSONs for both i-01 and i-02. No significant changes other than IP addresses and IDs.

The question is: How can I understand what is going on inside this instance and why it's inaccessible?