High CPU utilization from AWSCLI runtime on Windows Server 2022 EC2 instance

### Describe the bug

We have observed sustained high CPU utilization caused by the AWS CLI Python runtime on our Windows Server 2022 Datacenter instance.

Issue Details:

Duration: 5.5+ hours of elevated CPU consumption
Process: Python runtime from C:\Program Files\Amazon\AWSCLI\runtime
CPU Impact: 59.3% sustained usage
Instance Type: r6id.4xlarge (should have sufficient resources)

Environment:

OS: Windows Server 2022 Datacenter
AWS CLI Version: aws-cli/1.37.15
Python Version: 3.12.6
Botocore Version: botocore/1.36.15
Exec Environment: EC2

Related AWS Case:
AWS Support case ID: 178882204600949 (opened for investigation)

Additional Context:
This is not typical behavior for our environment. We have not previously observed AWS CLI consuming this level of CPU resources. Task Manager screenshot attached showing the Python process and its child processes (Background Intelligent Transfer Service, WMI Performance Adapter, etc.).

Request:
Please investigate whether this is a known issue with aws-cli/1.37.15 on Windows Server 2022, or if there's a configuration/bug causing excessive processing.

### Regression Issue

- [ ] Select this option if this issue appears to be a regression.

### Expected Behavior

AWSCLI runtime CPU usage should have been very low, not even 1%.
It shouldn't be flat lining the CPU for 5.5 hours.

### Current Behavior

CPU came back to normal automatically after the case was raised with AWS

### Reproduction Steps

I haven't seen this issue before

### Possible Solution

_No response_

### Additional Information/Context

_No response_

### CLI version used

1.37.15

### Environment details (OS name and version, etc.)

Windows 2022 Server Datacenter

The report names no repository file, test, or reproducible command; begin by correlating AWS CLI 1.37.15 activity with Windows Server 2022 process and system logs. Done means identifying a reproducible cause or confirmed known issue and documenting a targeted fix or diagnostic, but the report alone does not define a code-level completion test.

Written by the indexing model from the issue text.