microsoft / microsoft/winget-pkgs

[Package Issue]: Microsoft.VisualStudioCode reports error code 67 "the network name cannot be found" when upgrading

Open
#96,486 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Bug
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
376

Description

Please confirm these before moving forward
  • I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
  • I have not been informed if the issue is resolved in a preview version of the winget client.
Category of the issue

Installation issue.

Brief description of your issue

when updating visual studio code 1.75.0 to 1.75.1, the installer will download but will fail displaying the following error:

"ShellExecuteEx failed; code 67. The network name cannot be found."

Steps to reproduce

update visual studio code from version 1.75.0 to version 1.75.1.

Actual behavior

the installer will download and prompt for UAC credentials, after being supplied with these credentials, the installer will crash displaying the following error:

"ShellExecuteEx failed; code 67. The network name cannot be found."

Expected behavior

the update should be done successfully.

Environment
Windows Package Manager v1.4.10173
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19045.2546
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.19.10173.0

Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

User Settings: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
Screenshots and Logs

WinGet-2023-02-13-13-21-00.180.log
VSCodeSetup-x64-1 75 1 tmp_dIrkshtpjz

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file or test is named. Start by inspecting the attached WinGet log and reproducing the Microsoft.VisualStudioCode 1.75.0-to-1.75.1 upgrade; determine whether the failure belongs to package metadata, the installer, or the client. Done means identifying the responsible component and documenting or routing the fix accordingly.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
cli, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.