Error between installable NVDA and portable NVDA

[Sergio Gómez]

Hello,

 

I've just discovered some strange behavior. 

When we go to the NVDA menu, under the Tools submenu, then to “Create portable copy,” we choose the destination, check or uncheck whether we want it to create a dedicated folder for the portable copy, check or uncheck “Copy user configuration,” and mark (this one definitely checked) “Launch portable copy after creation,” we can observe that—after the creation—only the current NVDA instance restarts and the portable copy does not launch.

 

I’ve noticed this since version 2025.1 and waited in case it was already reported, but since I’ve seen this behavior again, I’m reporting it here, as I don’t believe it should work this way. The portable copy should launch as indicated.

 

Thank you.

 

Best regards.

 

Sergio G. C.

 

[Noelia]

Hello, Sergio: I cannot reproduce this error. with NVDA 2025.2beta2, and Windows 11 24H2 (10.0.26100.4652) workstation AMD64.

I've created a portable copy and it's launched as expected after creation.

Hope someone can provide more info.

--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/001601dbf1c7%2448c61a90%24da524fb0%24%40gmail.com.

[Sergio Gómez]

Well… it’s possible that the error has been fixed in the betas—I’m on the stable 2025.1.2 version, and I’m experiencing this issue; I haven’t tried the betas.

 

Thanks for the info, maybe it’s been fixed and I’m only just finding out now.

 

Sergio G. C.

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAAtLpyfn711N3XHwXeuhCz-M3sA4iwF7ObLHrMp%2BL5ukUonhtw%40mail.gmail.com.

[Cyrille BOUGOT]

Hi Sergio

I have not tried to reproduce, but I'd recommend that you open a GitHub issue, so that we can have all the required information, from the template.

Please also indicate how you check which version is running (portable or installed).

Cheers,

Cyrille

[Cyrille BOUGOT]

(second attempt to answer)

Hi Sergio

I have not tested. But such issue deserves a GitHub issues to be opened. It will allow to gather all the needed information, from the template.

Could you open one?

Cheers,

Cyrille

Le jeudi 10 juillet 2025 à 22:12:09 UTC+2, Sergio Gómez a écrit :

[Cyrille BOUGOT]

It's a test, thanks.

(my two previous answers have been deleted)

Le jeudi 10 juillet 2025 à 22:12:09 UTC+2, Sergio Gómez a écrit :

[Noelia]

Publicly, thanks Cyrille.

Your messages were classified as possible spam, and I have approved them now.

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/cc88039f-e58d-478e-9c1b-cd7b7e8d1771n%40nvaccess.org.

[Sergio Gómez]

Hello,

 

I don’t know how to use GitHub. I have an account, but I’ve never used it because I find it confusing due to the fact that it’s not in my language—my language is Spanish.

 

Cheers.

 

Sergio G. C.

[Noelia]

I cannot reproduce the described problem.

But if you need help to create the issue, in case the bug is not fixed for you, if you have Dropbox or something to provide a link to your portable copy, I can try to see if I can reproduce the problem and create an issue on GitHub.

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/004001dbf24a%2406b02370%2414106a50%24%40gmail.com.

[NVDA Screen Reader Discussion]

Hello!
If necessary, I can also test.

Best regards,

Rui Fontes
NVDA portuguese team

[Cyrille BOUGOT]

Hi Sergio

I have performed tests.

On my end, the portable copy is launched, but with the configuration of the installed copy, or maybe the copy where it was created from.

That's probably what happens on your end too?

I'll provide a fix, or at least, open a GitHub issue.

Cheers,

Cyrille

[Sergio Gómez]

Hello again,

 

If you can't reproduce the issue but I am experiencing it, I think we won't publish it on GitHub for now—I'll wait for the next stable release, or maybe if I find some time, I'll report it using the new beta version of NVDA.

 

Thanks for your willingness, Noelia.

 

Best regards.

 

Sergio G. C.

 

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAAtLpyd0TE49s%3DSBMsq8B-S5re83%3DcVKv2taOgUN%2ByyNXHajGQ%40mail.gmail.com.

[Sergio Gómez]

Hi,

 

For now, don't worry — I'll see if the issue gets resolved by using the NVDA betas or the next stable release, and if the problem continues, I'll mention it here.

 

Thanks for your intention, Rui.

 

Best regards.

 

Sergio G. C.

 

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/a4ed1d39-7b05-46d6-8690-8aad791ae095n%40nvaccess.org.

[Cyrille BOUGOT]

Hi Sergio

I have opened an issue (#18442) and a PR to fix it (#18443).

Can you confirm that on your end, the portable actually starts, but uses the config of the installed version instead of its own configuration?

To identify if a portable or an installed version is running, you can use commands that only run on installed versions, e.g. audio ducking (NVDA+shift+D).

Cheers,

Cyrille