Issue reported on this thread of NVDA users mailing list.

Steps to reproduce:

• Start your normal installed copy of NVDA
• NVDA menu -> Tools ->
• Ensure "Start the new portable copy after creation" is checked
• For more obvious result, uncheck "Copy current user configuration"
• Define path and other parameters as you want
• Press OK

Actual behavior:

The new portable copy start using the config folder of the installed copy.

Expected behavior:

The new portable copy should start using its own config folder.

NVDA logs, crash dumps and other attachments:

N/A

System configuration

NVDA installed/portable/running from source:

Both

NVDA version:

2025.2beta2

Windows version:

Windows 10 22H2 (AMD64) build 19045.5965

Name and version of other software in use when reproducing the issue:

N/A

Other information about your system:

N/A

Other questions

Does the issue still occur after restarting your computer?

Yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

I have not.
But acccording to this thread, the issue is present since 2025.1.

If NVDA add-ons are disabled, is your problem still occurring?

Yes

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

N/A