Gary,
Several discussions on this forum address this same issue. Microsoft has released a patch in a recent Windows update that should automatically fix it.
Specifically, Update KB5050411 (Windows Recovery Environment update for Windows 10, versions 21H2 and 22H2), released on January 14, 2025, may resolve the problem.
Please check for and install any available Windows updates to see if this resolves the issue for you.
Here's the reference thread:
https://answers.microsoft.com/thread/a6123462-2...
Let me know if you still need more help.