-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix EnableWindowsPackageManagerCommandLineInterfaces
Policy Behavior
#4293
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer that we not throw an exception as control flow, but I can live with it.
Hello @Madhusudhan-MSFT , @ryfu-msft could you please advise when this fix will be released, and will it require an update to the Intune management engine ? |
Deploying Intune Store Apps still failing with error "blocked by policy", if EnableWindowsPackageManagerCommandLineInterfaces policy is set. Tested with v1.7.11261 and also with v1.8.1133 in preview. Any news regarding this still existing issue @JohnMcPMS @ryfu-msft? |
Intune distributes a copy of winget binaries with their client release. The fix will be available in Intune client 2406 release (to be released end of June). |
Credit to @JohnMcPMS for initial implementation and guidance.
There is an issue where if the
EnableWindowsPackageManagerCommandLineInterfaces
policy is disabled, all COM calls would be blocked. This PR fixes that behavior by moving the CLI policy check toCoreMain
in the CLICore project so that it only performs the check if being executed from the command line and unblocks COM calls.Verified manually using the updated SampleUWPCaller. Also added E2E tests to check this behavior.
Microsoft Reviewers: Open in CodeFlow