After a second installation of an incompatible add-on, this one is disabled after restarting NVDA.

[paulber19]

Steps to reproduce:

install an incompatible add-on for the first time from its installation file.

• restart NVDA.
• check that the add-on is activated.
• install this add-on again without uninstalling it.
• restart NVDA.

The add-on is then deactivated.

Actual behavior:

Expected behavior:

The add-on should be activated as when it was first installed.

NVDA logs, crash dumps and other attachments:

System configuration

NVDA installed/portable/running from source:

NVDA portable

NVDA version:

2023.3Beta4 and alpha

Windows version:

Windows 10 22H2 (10.0.19045) workstation x86

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

Other information about your system:

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.

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

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

Yes

[lukaszgo1]

Could you please fully fill the issue template?

[paulber19]

That's what I think I did, but the copy and paste didn't turn out well. here is the complement: - install an add-on for the first time from its installation file. - restart NVDA. - check that the add-on is activated. - re-install this add-on again without uninstalling it. - restart NVDA. The add-on is not activated after restarting NVDA. Le 05/10/2023 12:55, Łukasz Golonka a écrit :

…

Could you please fully fill the issue template? — Reply to this email directly, view it on GitHub <#15584 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADZLFFB6A2COIERY5AOXA5DX52G3DAVCNFSM6AAAAAA5T4EXBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBYGY2TGNZYGM>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[lukaszgo1]

There is still a lot of important info (which was asked in the template) missing:

• With what add-on you have tested exactly
• Has this worked in NVDA 2023.2

[paulber19]

Sorry, I didn't see this request in the template. It doesn't depend on the add-on. It just needs to be incompatible. I haven't tested with 2023.2, but I think the problem is occurring. Le 05/10/2023 14:36, Łukasz Golonka a écrit :

…

There is still a lot of important info (which was asked in the template) missing: * With what add-on you have tested exactly * Has this worked in NVDA 2023.2 — Reply to this email directly, view it on GitHub <#15584 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADZLFFGXPB3HG5PAQDXITW3X52SVBAVCNFSM6AAAAAA5T4EXBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBYHAYTEOBSHA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[paulber19]

In response to the second question: The problem also occurs with NVDA 2023.2. Le 05/10/2023 14:36, Łukasz Golonka a écrit :

…

There is still a lot of important info (which was asked in the template) missing: * With what add-on you have tested exactly * Has this worked in NVDA 2023.2 — Reply to this email directly, view it on GitHub <#15584 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADZLFFGXPB3HG5PAQDXITW3X52SVBAVCNFSM6AAAAAA5T4EXBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBYHAYTEOBSHA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[CyrilleB79]

Confirmed on my side on NVDA 2023.3beta4.