0x800700b7 : Cannot create a file when that file already exists

[rogerstewart]

Brief description of your issue

I am encountering the same issue as described in the previously closed #1433. However, I am using the latest version described in Environment below.

I have tried reinstalling and downgrading Microsoft.DesktopAppInstaller. The 0x800700b7 still persists.

Log entry:

2023-07-27 09:03:12.947 [FAIL] D:\a\_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Microsoft\Schema\1_0\Interface_1_0.cpp(190)\WindowsPackageManager.dll!00007FFAA973A05D: (caller: 00007FFAA973FEF9) Exception(1) tid(22f0) 800700B7 Cannot create a file when that file already exists.

Steps to reproduce

winget list
winget upgrade

Expected behavior

Commands should execute without error.

Actual behavior

Failed to open the predefined source; please report to winget maintainers.
An unexpected error occurred while executing the command:
0x800700b7 : Cannot create a file when that file already exists.

Environment

Windows Package Manager v1.5.1881
Windows: Windows.Desktop v10.0.22621.1992
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.20.1881.0

PowerShell 7.3.6
Windows Terminal 1.17.11461.0
Windows 11 Enterprise 22H2

[trolleyboy]

Seeing the same issue since last week
Environment:

Windows Package Manager v1.5.2201
Windows: Windows.Desktop v10.0.22621.2134
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.20.2201.0

PowerShell 7.2.13
Windows Terminal 1.17.11461.0
Windows 11 Enterprise 22H2

[trolleyboy]

Update - ran winget upgrade --verbose-logs, then ran winget --logs-open.
Opened the most recent verbose log file and saw lots of SQL related lines. Skipped to the end of the file and noted that each time the error occurred, it mentioned Dropbox among the SQL results.
Uninstalled Dropbox (v180.something if I recall) and Winget now working successfully.

[ElectricErger]

I'm dealing with the same issue

Windows Package Manager v1.6.2631
Windows: Windows.Desktop v10.0.19045.3448
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.21.2631.0

I fixed it by using the powershell installer stated in the 1.6.2291 preview Install-Module -Name Microsoft.WinGet.Client.

Unfortunately, I could not tell you how this fixed the problem. The only difference I'm seeing in the logs is that the command line seems to use an absolute path to winget.exe instead of just "winget". Still showing all of the errors when Interface_1_0.cpp\WindowsPackageManager.dll hits error 800700B7 Cannot create a file when that file already exists.

Perhaps it's something with the Windows Store? It could also just be a matter of the sources doing some kind of funky upgrade that breaks some version's compatibility.

[dxman]

I've been experiencing the same issue for quite a while now, including the latest version.

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

Windows: Windows.Desktop v10.0.19045.3930
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.21.3482.0

winget upgrade --verbose-logs results in 29 such errors, all of which appear to be located in close proximity to queries relating to various Microsoft and .NET runtimes. At a glance, the version numbers being queried do not appear to match those of the installed versions of these runtimes.

For example, starting at line 80772 of the attached log file, it appears to be querying for v12.0.21005.1 of the Microsoft Visual C++ 2013 Redistributable, which directly precedes the error message at line 80836. But according to the Programs and Features window, the installed version is 12.0.40664.0 (see attached screenshot).

Not sure if that matters, but thought I'd point it out since leads on diagnosing the problem seem to be thin.

WinGet-2024-01-13-20-33-24.136.log