1. Regedit call ps1 vs. PowerShell 7.5
It seems the issue is related to the version of PowerShell you're using.

PowerShell 7.5 is a newer version of PowerShell, and it's possible that the improvements and bug fixes in this version have resolved the issue you're experiencing.

The "blue PowerShell" you're referring to is likely PowerShell 5.1, which is the default version of PowerShell on Windows 10 and Windows 11.

2. Difference between PowerShell 5.1 and 7.5
The issue may be related to a difference in behavior between the two versions of PowerShell. Here are some possibilities:

- The rules for processing paths may have changed between the two versions.
- Special characters or spaces in paths may be handled differently.
- PowerShell configuration settings may be different between the two versions.

3. Some PowerShell 5.1 Use Cases
If you need to use PowerShell 5.1 for some reason, you can try to find a workaround for the problem you're experiencing. Here are some suggestions:

- Try enclosing the path in double quotes ("") to see if that resolves the issue.
- Use the `-LiteralPath` parameter instead of `-Path` to see if that resolves the issue.
- Try replacing spaces in the path with backticks (`) to see if that resolves the issue.

If you don't need to use PowerShell 5.1 specifically, you can continue using PowerShell 7.5, which seems to be working fine for you.