-
-
Notifications
You must be signed in to change notification settings - Fork 257
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
Comments
|
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 |
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. |
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. |
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:
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](https://private-user-images.githubusercontent.com/111425505/338784091-712401d9-e58c-4861-a66c-b115c67f21a1.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA2ODI0NDUsIm5iZiI6MTcyMDY4MjE0NSwicGF0aCI6Ii8xMTE0MjU1MDUvMzM4Nzg0MDkxLTcxMjQwMWQ5LWU1OGMtNDg2MS1hNjZjLWIxMTVjNjdmMjFhMS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNzExJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDcxMVQwNzE1NDVaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT00NTMzNmYwMzE4YmY0Y2U0M2UwYjA1NjkwNTAzNzVmZjMwZDg4N2RhYTljMWY5YjI1MWMwZDBkZGE4ZTljNWU0JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.O2VEGb9TrE-OrQYZpNh2vYA3TSNSpj_pknbQYqzj_sI)
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.
The text was updated successfully, but these errors were encountered: