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.

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

Strict script could be a little bit too strict (breaks genuine developer tools) #504

Open
lyndsay9968 opened this issue Feb 6, 2025 · 2 comments

Comments

@lyndsay9968
Copy link

I'm not sure this is expected behavior but executing strict script prevents the installation of certain development tools.
You can't install, for example, WebView2 (used by certain programs) or WSL2 (which also prevents Docker installation).
I understand that the strict option may break some things, but this seems a bit too extreme. Breaking down junk like the contacts app is perfectly understandable, but breaking down useful tools rather not.

Reproduction steps

  1. Install fresh Windows 10
  2. Install latest privacy.sexy (0.13.7)
  3. Run strict script
  4. Restart computer
  5. Try to install WebView2 or WSL2 or Docker

Proposed solution
The strict script should not break legit useful tools. Such actions should be in a separate extreme mode or remain as now in the all option.

Alternative solution
Introduce an additional developer-friendly switch that unchecks harmful for them scripts regardless of the selected mode.

@lyndsay9968
Copy link
Author

WSL2 installation error
A error was encountered during installation, but installation may continue. Component: 'Ubuntu' Error Code: 0x80072ee7

contrary to what it claims, the installation cannot continue

@lyndsay9968 lyndsay9968 changed the title Strict script could be a little bit too strict Strict script could be a little bit too strict (breaks genuine developer tools) Feb 6, 2025
@lyndsay9968
Copy link
Author

Additional details: After executing the standard script, you can install WebView2 so the problem is in the strict script.

I have to perform more tests because it turns out that even on a fresh system the installation of WSL2 ends up with the same error (the compilation number meets the requirements, but still does not work)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant