Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[BUG]: "Standard" profile limits Winget CLI Functionality #142

Closed
wgetgoose opened this issue Jun 7, 2022 · 2 comments
Closed

[BUG]: "Standard" profile limits Winget CLI Functionality #142

wgetgoose opened this issue Jun 7, 2022 · 2 comments
Labels
bug Something isn't working

Comments

@wgetgoose
Copy link

Description

When using the standard profile, the functionality for "winget" cli's repo is removed. This is possibly due to a blockage of the https://winget.azureedge.net/cache URL.

OS

Windows 11 Home- Build 22000.708

Reproduction steps

Use standard profile on privacy.sexy, and attempt to run winget upgrade --all or winget source reset --force. The repositories will not be able to be updated.

Scripts

On Hastebin: https://hastebin.skyra.pw/civuqupoti.bash

Screenshots

Additional information

What option would I need to disable to restore functionality? I assume it's a telemetry issue, but there are multiple options not specifying winget.
@wgetgoose wgetgoose added the bug Something isn't working label Jun 7, 2022
@Remyie
Copy link

Remyie commented Apr 7, 2023

I encountered the same problem. "Failed in attempting to update the source: winget"
Sometimes it also says "Installation failed: system failed to register the windows.firewall extension". Turns out Winget and it's repos require windows defender firewall to be enabled. I believe privacysexy doesn't disable windows defender by default anymore, but if you are not careful enough and decide to both tick "disable windows defender firewall" and "Disable OS components for Defender", it will break winget and several other stuff.

Here's how I fixed it:

  • Go to https://privacy.sexy/.
  • Privacy Over Security > Disable Windows Defender, click revert on "Disable Windows Defender Firewall" and "Disable OS Components For Defender".
  • Download the batch file and run it with admin privileges.
  • Restart your PC.
  • Open up Powershell and run "winget source reset --force".
  • Then run "winget source update".

It should be able to update now. If it still says it couldn't update try these:

  • Run command prompt as administrator and copy paste these commands:
    reg add HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\mpssvc\ /v Start /t Reg_DWORD /d 2 /f
    reg add HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\mpsdrv\ /v Start /t Reg_DWORD /d 3 /f
  • Restart pc.
  • Open up Powershell and run "winget source reset --force".
  • Then run "winget source update".

If it's still not working try changing your dns.

So in short, it's not a bug with privacysexy, just winget being annoying. Not telling why it's unable to update the repos.
To avoid people accidentally breaking winget, the names of these settings could be changed to include "(Breaks Winget)"

undergroundwires added a commit that referenced this issue Apr 10, 2024
@undergroundwires
win: improve firewall docs /w winget impact #142
ffd647d 
This commit enhances the documentation related to disabling the firewall
services in Windows, with a focus on the `winget` CLI's functionality,
resolving #142.

Changes:

- Expand documentation to include implications on `winget` CLI,
  addressing the issue #142.
- Add documentation for disabling `mpsdrv` service.
- Align documentation for disabling `mpssvc` service to match updates
  made for `mpsrv` to maintain consistency across documentation.
- Introduce documentation for parent categories affected by scripts
  that disable these services.
- Add documentation for parent categories for disabling these firewall
  services.

The documentation aims to provide users with a comprehensive
understanding of how these changes affect both system performance and
security posture.
@undergroundwires
Copy link
Owner

Hi @Remyie,

Thank you for all information, sorry for my late response, I missed this issue.

It's addressed since 0.13.2 🚀.

Actions taken:

  1. Winget is specifically mentioned as being broken in script titles:

image

  1. Winget behavior is documented in script/parent category documentation:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@undergroundwires @wgetgoose @Remyie