microsoft / microsoft/winget-pkgs
Non-Admin Users Can't Launch After Machine Scope Installation: Adobe.Acrobat.Reader.64-bit
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
Adobe Acrobat Reader 64-bit installed via winget with machine scope works for administrators but fails to launch for non-admin users with errors "Attempt to call a method that has not been implemented" and "Raise without Handler!" I originally posted the issue here (with screenshots):
https://superuser.com/questions/1895632/
This link above reveals that the issue is only a recent problem. Prior to version 25.001.20474 (of Adobe.Acrobat.Reader.64-bit), machine scoped installs worked for all users.
Steps to reproduce
- Install Adobe Acrobat Reader with:
winget install --id Adobe.Acrobat.Reader.64-bit --scope machine --source winget - Log in as administrator - application works correctly
- Log in as non-administrator user
- Launch Adobe Acrobat Reader
- Observe error dialogs: "Attempt to call a method that has not been implemented" followed by "Raise without Handler!"
Actual behavior
The installation works correctly for administrator accounts but fails for non-admin users with two specific error messages:
- "Attempt to call a method that has not been implemented" appears first
- Upon clicking OK, a second error "Raise without Handler!" appears
This makes the application completely unusable for non-administrator users despite being installed with machine scope.
Expected behavior
When installing Adobe Acrobat Reader 64-bit with --scope machine parameter, the application should be properly installed for all users on the system, both administrators and standard users.
Environment
[Environment Information]
Windows Package Manager v1.10.390
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.26100.3775
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.25.390.0
[System Information]
OS Name: Microsoft Windows 11 Pro
OS Version: 10.0.26100 N/A Build 26100
OS Manufacturer: Microsoft Corporation
System Type: x64-based PC
Screenshots and Logs
The error dialog screenshots were provided in the original SuperUser question and can be found at:
- First error: https://i.sstatic.net/Ape9WT8J.png
- Second error: https://i.sstatic.net/mLceBsyD.png
I've tried the following troubleshooting steps:
- Uninstalled Adobe Acrobat Reader completely through Windows Settings
- Deleted all Adobe AppData folders for a clean installation
- Reinstalled with the same winget command
- Rebooted the system
The issue occurs after machine-wide installations via the --scope machine argument.
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 the failure with winget install --id Adobe.Acrobat.Reader.64-bit --scope machine --source winget, then compare launches under administrator and standard accounts on the reported Windows environment. Trace the Adobe.Acrobat.Reader.64-bit package and its machine-scope installation behavior; the issue is done when standard users can launch the installed application without either reported error.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100