Skip to content

Updating installed NVDA: OSError: [WinError 8235] A referral was returned from the server. #18347

@josephsl

Description

@josephsl

Hi,

Looks like it began with alpha-36949 but managed to reproduce this on two computers with alpha-37017:

Steps to reproduce:

Prerequisite: NVDA alpha-36989 (2025.2.0.36989) is installed on a computer (not a portable copy):

  1. Check for NVDA updates.
  2. Go through the update process, including replying "yes" to UAC prompt (or provide admin credentials).
  3. If you can hear it, listen for the error sound at the end.

Actual behavior:

An error sound is heard at the end of updating the installed copy of NVDA, and NVDA does not restart after. The traceback ends with:
OSError: [WinError 8235] A referral was returned from the server.

Expected behavior:

No errors and NVDA restarts.

NVDA logs, crash dumps and other attachments:

ERROR - queueHandler.flushQueue (05:15:46.533) - MainThread (6796):
Error in func _doShutdown
Traceback (most recent call last):
File "queueHandler.pyc", line 67, in flushQueue
File "core.pyc", line 461, in _doShutdown
File "core.pyc", line 446, in _startNewInstance
File "shellapi.pyc", line 53, in ShellExecute
OSError: [WinError 8235] A referral was returned from the server.

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

alpha-37017,9dc93393 x86

Windows version:

Windows 11 24H2 beta (10.0.26120.4452)

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

None

Other information about your system:

Used as a development workstation iwth multiple portable NVDA versions present (for portable ocpies, update proceeds as usual)

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.

No issues with updating to alpha-36989,071247b0

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?

Yes

Note about the log

The log comes from a different computer running Windows Insider canary channel build (27881) but the traceback is the same.

Thanks.

alpha-37017update.log

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions