-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
[BUG]: Ran the standard protection and now my Windows does not display notifications to apps like Instagram and Whatsapp #339
Labels
Comments
I probably got this on, but I didnt check it myself. |
Hi @hollowflowers, did @plantindesk's suggestion this resolve your issue? |
no, I reinstalled Windows. but I´m pretty sure I used some setting that broke it or uninstalled some sort of framework, idk.
…________________________________
De: undergroundwires ***@***.***>
Enviado: sábado, 27 de abril de 2024 11:49
Para: undergroundwires/privacy.sexy ***@***.***>
Cc: hollowflowers ***@***.***>; Mention ***@***.***>
Assunto: Re: [undergroundwires/privacy.sexy] [BUG]: Ran the standard protection and now my Windows does not display notifications to apps like Instagram and Whatsapp (Issue #339)
Hi @hollowflowers<https://github.com/hollowflowers>, did @plantindesk<https://github.com/plantindesk>'s suggestion this resolve your issue?
—
Reply to this email directly, view it on GitHub<#339 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BHU5JMDOPYVMEQ765UJMAZTY7OUHTAVCNFSM6AAAAABF3ODPD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBQG4YDMMZRGY>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
undergroundwires
added
the
blocked/need-repro
Needs a test case to reproduce the bug
label
Apr 28, 2024
undergroundwires
added a commit
that referenced
this issue
May 21, 2024
This commit improves disabling app access by correcting minor issues, adding missing access control configurations and adding more documentation (#138). - Introduce shared functions to modify app access for maintainability and simplicity. - Improve comments in generated code - Fix revert codes showing errors by using `2>nul` in `reg delete` commands. - Fix disabling app access to trusted devices disables access to account information, name and picture on older versions of Windows. - Move disabling app access to location in the same category of others. - Add missing privacy settings and configurations. - Add more documentation to scripts - Rename script names for consistency and clarity. - Move disabling access to SMS/MMS to phone access disablement category. - Adjust recommendation levels (discourage more, as #121 suggests): - Discourage disabling app access to notifications on 'Standard' to address #339 where user reports lack of notifications as bug.
undergroundwires
added a commit
that referenced
this issue
May 24, 2024
This commit adjusts the recommendation level for scripts that disable UWP app access to accommodate user issues #121, #339, #350. It also extends their documentation to reflect the new changes and with cautions. Changes: - Add caution text for all scripts about potential impacts. - Move disabling app access to notifications from 'Standard' to 'Strict'. This addresses #121 and #339, where users report lack of notification as unintended side-effects. - Move disabling app access to phone calls from 'Standard' to 'Strict'. This addresses #350 where its effect on the Phone Link app was reported as an unintended side-effect.
0.13.4 is just released 🎉. It improves app disabling to resolve this issue, some of the improvements include:
Please create new issues for further ideas/problems. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
I ran the script a week ago, since then I noticed my Windows does not display notifications to nothing.
I really mean nothing, not even Windows Defender alarms.
Is there any way I can fix it?
Also when I mess around in Settings app, I get a lot of the [System Error:An Overrun of a stack-based buffer in windows] error.
The text was updated successfully, but these errors were encountered: