Hi Chon Yut,
Based on the symptoms, it is possible that the recovery partition was moved, had its GPT partition type or attributes changed, or that the Windows Recovery Environment (WinRE) configuration no longer points to the correct recovery location after the partition resizing operation.
I recommend starting by comparing the current disk layout, partition offsets, GPT type GUIDs, and partition attributes using DiskPart, PowerShell storage cmdlets, and reagentc /info to verify whether the recovery partition is still correctly identified by Windows. It is also important to inspect the recovery partition itself to determine whether the WinRE image and related files remain intact or whether metadata corruption occurred during the resize operation. Reviewing the output of reagentc /info alongside the physical partition layout can help identify mismatches between the configured recovery path and the actual partition location. Before making any corrective changes, I strongly recommend ensuring that a full backup of the system is available, as modifications to partition structures or recovery configurations can increase the risk of data loss if performed incorrectly. By correlating the partition configuration, WinRE registration status, and recovery partition contents, you can usually determine whether the issue is related to configuration drift, partition metadata changes, or damage to the recovery environment itself.
I hope the response provided some helpful insight. If you find this answer useful, please hit “accept answer” so I know it addressed your concern.
Jason