Zoom is installed in C:\Windows\System32\config\systemprofile\AppData\Roaming\Zoom

[SamaelAmbrona]

Brief description of your issue

The package Zoom.Zoom is installed in the above mentioned path, which makes it unavailable for the users. It also doesn't create a registry neither is it listed with a Winget list.

Steps to reproduce

The software, like many other packages, is installed from MDM, using a script that uses Winget.exe install -e --id Zoom.Zoom
As it is installed in this folder, it is not accessible for users, neither appears in the Winget list, in the list of apps installed or in the windows registry.

Expected behavior

To be installed in some folder accessible for the users

Actual behavior

It is being installed in the above mentioned folder and cannot be used by users.
WinGet-2022-10-20-06-47-40.413.log

Environment

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

Windows: Windows.Desktop v10.0.19043.2130
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.18.2691.0

[Trenly]

This looks like it's an error with the Zoom installer itself being called in a system context from MDM, as winget just calls the installer. It does seem like in your context that it is writing to the registry keys, but since the user scope was selected, those registry changes would only show for the MDM user.

2022-10-20 06:47:42.623 [CLI ] Starting installer selection.
2022-10-20 06:47:42.623 [CLI ] Installer [X86,exe,User,] is current best choice
2022-10-20 06:47:42.623 [CLI ] Installer [X86,exe,User,] is better than [X86,msi,Machine,] due to: Scope
2022-10-20 06:47:42.623 [CLI ] Installer [X64,exe,User,] is better than [X86,exe,User,] due to: Machine Architecture
2022-10-20 06:47:42.623 [CLI ] Installer [X64,exe,User,] is current best choice
2022-10-20 06:47:42.623 [CLI ] Installer [X64,exe,User,] is better than [X64,msi,Machine,] due to: Scope
2022-10-20 06:47:42.623 [CLI ] Installer [Arm64,exe,User,] not applicable: Machine is not compatible with Arm64
2022-10-20 06:47:42.623 [CLI ] Installer [Arm64,msi,Machine,] not applicable: Machine is not compatible with Arm64
2022-10-20 06:47:42.623 [CLI ] Completed installer selection.
2022-10-20 06:47:42.623 [CLI ] Selected installer Architecture: 2
2022-10-20 06:47:42.624 [CLI ] Selected installer URL: https://cdn.zoom.us/prod/5.12.2.9281/x64/ZoomInstallerFull.exe
2022-10-20 06:47:42.624 [CLI ] Selected installer InstallerType: exe
2022-10-20 06:47:42.624 [CLI ] Selected installer Scope: User
2022-10-20 06:47:42.624 [CLI ] Selected installer Language: 
2022-10-20 06:47:42.630 [CLI ] Generated temp download path: C:\Windows\TEMP\WinGet\defaultState\Zoom.Zoom.5.12.9281\f7cba2e790a7d41658ea0f430ac775f08d9872add59168fd72f12262bc9f9786
2022-10-20 06:47:42.630 [CORE] Downloading to path: C:\Windows\TEMP\WinGet\defaultState\Zoom.Zoom.5.12.9281\f7cba2e790a7d41658ea0f430ac775f08d9872add59168fd72f12262bc9f9786
2022-10-20 06:47:42.631 [CORE] DeliveryOptimization downloading from url: https://cdn.zoom.us/prod/5.12.2.9281/x64/ZoomInstallerFull.exe
|
2022-10-20 06:47:47.754 [CLI ] Starting: 'C:\Windows\TEMP\WinGet\defaultState\Zoom.Zoom.5.12.9281\ZoomInstallerFull.exe' with arguments '/silent'
|
2022-10-20 06:49:19.522 [CLI ] During package install, 1 changes to ARP were observed, 1 matches were found for the package, and 1 packages were in both
2022-10-20 06:49:19.522 [CLI ] The entry determined to be associated with the package is 'Zoom', with publisher 'Zoom Video Communications, Inc.'

[fernandog]

SamaelAmbrona did you try run with:

--scope=machine

You can read more here:
microsoft/winget-cli#1772

https://learn.microsoft.com/en-us/windows/package-manager/winget/settings#scope

[fernandog]

you can read in the log:
2022-10-20 06:47:42.624 [CLI ] Selected installer Scope: User

[SamaelAmbrona]

SamaelAmbrona did you try run with:

--scope=machine

You can read more here: microsoft/winget-cli#1772

https://learn.microsoft.com/en-us/windows/package-manager/winget/settings#scope

Hello #fernandog

No, I haven't tried that. I will thank you very much.

Does it make sense then, to deploy to each computer (User) a JSON file to replace the Winget settings for the one we would prefer? For instance, to always use the Scope machine ...

Best regards

[DeusMaximus]

SamaelAmbrona That's a terrible idea, because now you're relying on the existence of a JSON file which may or may not exist when you go to install an application that requires the --scope=machine parameter to work correctly, and results in a nightmare to troubleshoot for users and technicians alike.

Why can't you just use the --scope parameter with your script? Or change the MDM scope for your Zoom package to run in the user scope? If you're using Romain (@Romanitho) 's winget-install.ps1 script, you can just do:

powershell.exe -Executionpolicy Bypass -File winget-install.ps1 -AppIDs "Zoom.Zoom --scope=machine"

[SamaelAmbrona]

DeusMaximus Thanks for the answer. I can perfectly add the --scope in the script that I am using. I was wondering if the use of a config file (like I read in some posts) would make sense or not, sorry if it is stupid of me to ask.

Best regards