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

‘Some settings are managed by your organization’ Message Appearing in Taskbar Settings #68

Closed
Othmane-ElAlami opened this issue Jun 12, 2024 · 5 comments
Assignees

Comments

@Othmane-ElAlami
Copy link

Issue: "Some settings are managed by your organization" message after using the script

Describe the bug
After running the Win11Debloat script, the message "Some settings are managed by your organization" appears in the Taskbar settings of Windows 11.

To Reproduce
Steps to reproduce the behaviour:

  1. Run the Win11Debloat script using the Quick method with default settings.
  2. Navigate to Settings -> Personalization -> Taskbar.
  3. Observe the message "Some settings are managed by your organization" at the top of the page.

Expected behavior
The settings should not show the "Some settings are managed by your organization" message if no policies are applied that restrict the user's ability to manage these settings.

Screenshots
image

Possible Solution
It seems like some registry changes or policies applied by the script might be causing this message. A review of the changes made to the registry and group policies could help identify the cause.

@zoicware
Copy link

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Dsh] "AllowNewsAndInterests"=dword:00000000
just remove this key

@Othmane-ElAlami
Copy link
Author

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Dsh] "AllowNewsAndInterests"=dword:00000000 just remove this key

Thank you, the solution worked! However, I'm unsure if I should keep the issue open or if this behaviour is expected from the script.

@zoicware
Copy link

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Dsh] "AllowNewsAndInterests"=dword:00000000 just remove this key

Thank you, the solution worked! However, I'm unsure if I should keep the issue open or if this behaviour is expected from the script.

you can use this key to disable widgets without using a policy [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "TaskbarDa"=dword:00000000
however some things you will get that msg no matter what since theres no other way without using a policy

@Raphire
Copy link
Owner

Raphire commented Jun 13, 2024

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Dsh] "AllowNewsAndInterests"=dword:00000000 just remove this key

Thank you, the solution worked! However, I'm unsure if I should keep the issue open or if this behaviour is expected from the script.

you can use this key to disable widgets without using a policy [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "TaskbarDa"=dword:00000000 however some things you will get that msg no matter what since theres no other way without using a policy

This key will disable the widgets button, but if I recall correctly it won't disable the widgets service from running in the background. That's because widgets panel can also be accessed from a shortcut (WIndows + W).

The current implementation in the script uses the policy key to disable the widgets service entirely, but this does mean the widget setting becomes inaccessible. I'll look into alternatives later today once I have access to a W11 pc, but like @zoicware said some things can only be done using policies.

@Raphire Raphire self-assigned this Jun 13, 2024
Repository owner deleted a comment from sylv256 Jun 26, 2024
@Raphire
Copy link
Owner

Raphire commented Jun 26, 2024

I haven't been able to find a way to disable the Widgets service without resorting to a policy. I'll keep my eye on it. If anybody does find a way to achieve this without a machine policy, please let me know.

But for now I'll close this issue.

@Raphire Raphire closed this as not planned Won't fix, can't repro, duplicate, stale Jun 26, 2024
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

3 participants