microsoft / microsoft/winget-pkgs

[Package Issue]: Oracle.MySQLWorkbench version 26.7.0 needs to be a new package not an update.

Open
#435,200 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

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

https://github.com/microsoft/winget-pkgs/pull/434685

multiple problems in the same package:

problem 1: with Administrator Protection GPO enabled and running winget upgrade Oracle.MySQLWorkbench in an administrator console this ends up installing Workbench only in USER SCOPE for the non-accessible %USERPROFILE% folder that is usable only for the elevated account mode.

The normal, non-elevated %USERPROFILE% of the same account remains with the non-updated Workbench version 8.0.47 (from the machine scope installation).

problem 2:
When upgrading with machine scope explicitly requested from command line, this also ends up installed in USER scope - basically winget ignores the --scope parameter even if Workbench 8.0.47 is already installed in machine scope.

Steps to reproduce
  1. start an elevated terminal, run winget upgrade Oracle.MySQLWorkbench

Actual behavior
> winget upgrade
Name                       Id                             Version       Available    Source
-------------------------------------------------------------------------------------------
MySQL Workbench 8.0 CE     Oracle.MySQLWorkbench          8.0.47        26.7.0       winget

this will end up in the elevated admin-only %USERPROFILE%
in my case C:\Users\ADMIN_HomeUser\AppData\Local\Programs\MySQL

> winget upgrade Oracle.MySQLWorkbench
Found MySQL Workbench 8.0 CE [Oracle.MySQLWorkbench] Version 26.7.0
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
This package requires the following dependencies:
  - Packages
      Microsoft.VCRedist.2015+.x64
Downloading https://cdn.mysql.com/Downloads/MySQLGUITools/mysql-workbench-26.7.0-winx64.msi
  ██████████████████████████████   261 MB /  261 MB
Successfully verified installer hash
Starting package install...
Successfully installed

> winget upgrade  Oracle.MySQLWorkbench --scope machine
Found MySQL Workbench 8.0 CE [Oracle.MySQLWorkbench] Version 26.7.0
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
This package requires the following dependencies:
  - Packages
      Microsoft.VCRedist.2015+.x64
Downloading https://cdn.mysql.com/Downloads/MySQLGUITools/mysql-workbench-26.7.0-winx64.msi
  ██████████████████████████████   261 MB /  261 MB
Successfully verified installer hash
Starting package install...
Successfully installed

and... the machine scope Workbench still remains at version 8.0.47...

Image

The MSI installer also has a DisplayName issue: downloading and installing the new Workbench manually, in machine scope, for all users, ends up with a similar double installation alongside the old 8.0.47 Workbench.

Image Image
Expected behavior

expected:

  1. since Workbench 8.0.47 is already installed in machine scope then the upgrade should also be installed in machine scope, not user scope

  2. if installing in user scope at least use the correct non-elevated user profile path, not the %USERPROFILE% that is accessible exclusively when elevated.

Environment
environment: Windows 11 Pro 25H2 with 2026-09 cumulative updates and Administrator Protection GPO enabled.

> winget --info
Windows Package Manager v1.29.290
© 2026 Microsoft. All rights reserved.

Windows: Windows.Desktop v10.0.26200.9457
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.29.290.0

WinGet Directories
-------------------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads
Configuration Modules              %LOCALAPPDATA%\Microsoft\WinGet\Configuration\Modules

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled
ProxyCommandLineOptions                   Disabled
ConfigurationProcessorPath                Disabled
DefaultProxy                              Disabled
Screenshots and Logs

screenshots: see above

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

Start by reviewing pull request 434685 and reproduce the reported upgrade commands on Windows with MySQL Workbench 8.0.47 installed in machine scope. Compare the resulting user- and machine-scope installations and the MSI display names. Done means the upgrade honors the requested or existing machine scope, uses the correct user profile when applicable, and does not create duplicate installations.

Written by the indexing model from the issue text.

Assessment

Domain
cli, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.