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

[BUG]: Script that breaks calendar in taskbar #314

Open
Julynx opened this issue Jan 30, 2024 · 11 comments
Open

[BUG]: Script that breaks calendar in taskbar #314

Julynx opened this issue Jan 30, 2024 · 11 comments
Labels
bug Something isn't working

Comments

@Julynx
Copy link

Julynx commented Jan 30, 2024

Description

I just wanted to know which script is the one that breaks the calendar menu in the taskbar, preventing it from opening when clicking the time/date/bell icon in the taskbar in Windows 11.

I must have applied it by mistake, and when fuzzy searching for terms like Notifications or Action Center, I havent been able to find the correct script to revert it.

OS

Windows 11 Pro 23H2

Reproduction steps

I remember I applied at least the Strict settings, plus some extra script I dont remember exactly which tho.

Scripts

Strict + extra ones I dont remember

Screenshots

Calendar flashes a bit too fast when I click the date menu but doesnt really stay open to show up in a screenshot. I have recorded a video though, in case it helps:

2024-01-30.15-16-43.mp4
@Julynx Julynx added the bug Something isn't working label Jan 30, 2024
@undergroundwires
Copy link
Owner

Hi, did you execute it using desktop application? In that case we can find out your script file to debug this further.

@undergroundwires undergroundwires added the blocked/need-repro Needs a test case to reproduce the bug label Feb 9, 2024
@undergroundwires
Copy link
Owner

undergroundwires commented Jul 6, 2024

Hi @oculi38, as I understand from the link you consider Disable Windows Push Notifications to be the root cause.

I ran the script on (Disable Windows Push Notifications) on Windows 11 23H2 Pro, but I cannot reproduce this.

Calendar on taskbar and calendar app works fine for me. This is most likely caused by some another script.

We need to find out the exact script that's causing this to find a potential way to do the same thing without breaking stuff, or just document it better.

Do you have the script file you executed? If you used the desktop version, it's stored locally on your computer.

@undergroundwires
Copy link
Owner

You are right:

  • "Strict" does not cause this.
  • Disable Windows Push Notifications causes this.

It started breaking after restarting Windows 11 23H2 Pro. It works fine on Windows 10 versions (does not break taskbar).

Does reverting that solve the issue for you?

@undergroundwires
Copy link
Owner

Thank you for the report and sorry for my late response.
I will remove disabling WpnUserService for Windows later than 19H2 in next patch as a quick action.
Later, I will research alternative ways to get rid of this functionality, add them in privacy.sexy.

I'm not sure about #225 though and would appreciate any feedback/opinion.


Confirmed side effects per Windows version after disabling WpnUserService and rebooting:

Windows Version Taskbar Notifications Center (#314) Notifications & Actions Settings (#227) Network Settings (#110)
Windows 11 23H2 🔴 Affected 🔴 Affected 🟢 Unaffected
Windows 11 22H2 🔴 Affected 🔴 Affected 🟢 Unaffected
Windows 11 21H2 🔴 Affected 🟢 Unaffected 🟢 Unaffected
Windows 10 22H2 🟢 Unaffected 🟢 Unaffected 🔴 Breaks
Windows 10 21H2 🟢 Unaffected 🟢 Unaffected 🔴 Breaks
Windows 10 20H2 🟢 Unaffected 🟢 Unaffected 🔴 Breaks
Windows 10 19H2 🟢 Unaffected 🟢 Unaffected 🟢 Unaffected
Windows 10 19H1 🟢 Unaffected 🟢 Unaffected 🟢 Unaffected

@undergroundwires undergroundwires removed the blocked/need-repro Needs a test case to reproduce the bug label Aug 12, 2024
undergroundwires added a commit that referenced this issue Aug 13, 2024
This change addresses issues #227 and #314 by preventing unintended side
effects on newer Windows versions while still offering WNS control on
supported systems.

Changes:

- Constrain `WpnUserService` disabling to Windows 10 v1909 and earlier.
- Update documentation for WNS and related services.
- Remove redundant warnings (in generated code and script title).
- Improve DisablePerUserService function:
  - Add documentation and generated comments
  - Implement Windows version constraint capability
undergroundwires added a commit that referenced this issue Aug 13, 2024
This change addresses issues #227 and #314 by preventing unintended side
effects on newer Windows versions while still offering WNS control on
supported systems.

Changes:

- Constrain `WpnUserService` disabling to Windows 10 v1909 and earlier.
- Update documentation for WNS and related services.
- Remove redundant warnings (in generated code and script title).
- Improve DisablePerUserService function:
  - Add documentation and generated comments
  - Implement Windows version constraint capability
@undergroundwires
Copy link
Owner

This is well documented now and the script does no longer disable WpnUserService after 19H2 since 0.13.6 🚀

@undergroundwires
Copy link
Owner

No it does not, see commit 50ba00b for more details.
I'm not closing the issue as I may have found some other ways to disable cloud-based notifications more reliably. I'm still researching.

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

No branches or pull requests

3 participants
@undergroundwires @Julynx and others