microsoft / microsoft/winget-pkgs

[Package Issue]: BlenderFoundation.Blender

Open
#95,653 1 comment 13 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

Blender installs every medium version (e.g. 3.3., 3.4., etc.) in a separate folder, which results in loss of previously installed plugins and configured preferences between medium updates and disk space cluttering.

Steps to reproduce
  1. winget install BlenderFoundation.Blender --version 3.3.1
  2. winget update BlenderFoundation.Blender
  3. winget list --id BlenderFoundation.Blender
Actual behavior
  1. For each installed update, a new folder is created (e.g. C:\Program Files\Blender Foundation\Blender 3.3\, C:\Program Files\Blender Foundation\Blender 3.4\)
  2. These folders contain redundant files (blender.exe, blender-launcher.exe) and already contain version-specific directories (Blender 3.3\3.3\, Blender 3.4\3.4\)
  3. winget doesn't detect an update and suggests to update an app again (e.g. to install Blender 3.4 when it is already installed, but winget only detects previously installed Blender 3.3)
Expected behavior
  1. All Blender versions to be installed in the same root directory, e.g. C:\Program Files\Blender Foundation\Blender.
  2. Blender updates to be installed over previous versions in the same folder as it is already installed.
  3. Blender updates to be detected as installed after being applied.

Possible solution: use MSI Public Properties when calling blender-$version-$platform-$architecture.msi, for example:

.\blender-3.4.1-windows-x64.msi INSTALL_ROOT=`"C:\Program Files\Blender Foundation\Blender\`"

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

Windows: Windows.Desktop v10.0.19044.2486
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

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
Screenshots and Logs

No response

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 reproducing the issue with the provided winget install, update, and list commands, then inspect how the Blender MSI is invoked and how installed versions are detected. Done means successive medium-version updates use one root directory, preserve the expected installation state, and are recognized by winget without repeated update suggestions.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.