microsoft / microsoft/winget-pkgs
[Package Issue]: Microsoft.Office Architecture
Nobody has claimed this yet.
- 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 installing the Microsoft Office package via Winget, the installation ignores the --architecture flag and installs the 32-bit version of Office. The 32-bit version of Office also gets installed if the --architecture flag is not included in the command.
Steps to reproduce
- Command - winget install Microsoft.Office --architecture x64
- Open Word, or other Office programs, and complete or ignore the initial setup.
3a. Open Task Manager and check program architecture
3b. Open program shortcut properties and check target location.
Actual behavior
The Office install is installing the 32-bit version of the software regardless of the --architecture flag or the architecture of the machine that it is running on.
Expected behavior
I am expecting Office to install to correct architecture version of Office as passed by the command.
Environment
Windows Package Manager v1.2.10271
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.19044.1645
Package: Microsoft.DesktopAppInstaller v1.17.10271.0
Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
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
Also running this command on a machine with Windows 64 bit.
Screenshots and Logs
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing winget install Microsoft.Office --architecture x64 on the stated 64-bit Windows environment, then inspect the linked diagnostic log and verify the installed program in Task Manager or its shortcut target. Done means the command installs the x64 Office version rather than the 32-bit version, and the behavior is consistent with the requested architecture.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100
