Some of these settings are hidden or managed by your organization message showing on Privacy Settings page

Anonymous
2020-04-13T18:12:20+00:00

When In Settings>Privacyonly under Windows permissions>diagnostics&feedback and App permissions>Camera do I get ***Some of these settings are hidden or managed by your organization.**I am the only one using this laptop and am shown as administrator.  How can I resolve this issue.  I have exhausted all supposed cures suggested when I search that topic.

****Original title:*Privacy settings***

Windows for home | Windows 10 | Settings

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2020-11-10T00:11:48+00:00

I finally resolved the problem I was having today, involving using the Local Group Policy Editor.  As far as I understand, this is available on Windows 10 Pro, not the Home edition.  Hopefully this will help a few of you.

  • Press Windows key + R to open the 'Run' window.  Type gpedit.msc and press enter.
  • Under Computer Configuration, expand Administrative Templates, then expand Windows Components.
  • Click on App Privacy.  Double-click on the relevant issue, e,g,. if you cannot use your webcam, double-click on 'Let Windows apps access the camera'.
  • On the left under Options, there should be a 'Default for all apps' setting.  In my case this was set to 'Force Deny'.  Change this to 'User is in control', then click OK at the bottom.
  • Click on the Start button, click Settings, then click Privacy.  Hopefully the relevant permission button is no longer greyed out.

You are correct.  The group policy editor is not available in the Home version. 

Pro users has other tools as well to fix this. Like system center.

Home users can reset policies by using powershell commands. Pro users can do this as well.

The group policy editor is just a tool that uses the cmd/powershell commands. (Why those tools are not in win 10, I dont understand)

Microsoft released 2 days ago problems in 20H2 with exectly this.

Resetting the PC does work. But only because you reset your policies with that. Thats like buying a new car when you get a flat tire ;).

Here is how you fix the problem of "managed" when your PC IS NOT MANAGED!!! (Some are).

1. Open a powershell or cmd windows (With Admin rights)How to open a cmd or powershell windows.- Click start - Find Windows Powershell folder in the application tree.

  • RIGHT CLICK on the Windows powershell that only say powershell (Not Powershell ISE, x86).

2. Choose open with admin rights.

3. Copy all these commands. And paste them into the powershell

reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\Policies" /f

reg delete "HKCU\Software\Microsoft\WindowsSelfHost" /f

reg delete "HKCU\Software\Policies" /f

reg delete "HKLM\Software\Microsoft\Policies" /f

reg delete "HKLM\Software\Microsoft\Windows\CurrentVersion\Policies" /f

reg delete "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsStore\WindowsUpdate" /f

reg delete "HKLM\Software\Microsoft\WindowsSelfHost" /f

reg delete "HKLM\Software\Policies" /f

reg delete "HKLM\Software\WOW6432Node\Microsoft\Policies" /f

reg delete "HKLM\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Policies" /f

reg delete "HKLM\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\WindowsStore\WindowsUpdate" /f

4. Reboot your system. <---skip this and it does not work

Check the setting that had "managed by" in yellow text. If its gone = fixed and its policies you change with a tool that creates a registry mix that Microsoft yet have to fix.

If you are still "managed", then I suggest Malware removal operation. Then contact Microsoft support. They will help you.

Was this answer helpful?

200+ people found this answer helpful.
0 comments No comments

131 additional answers

Sort by: Oldest
  1. Anonymous
    2021-01-19T00:11:17+00:00

    Does this fix work differently on Windows 10 Pro?  I get the same problem "Some of these. . . " shows up in several places.  I am a part of Windows Insider and this prevents me from changing my settings on my computer.  I have a build number of 19042.746 which I don't believe is the current build number for the slow track.

    So if I do the above deletions it will solve my problem and allow me to be back on the slow track for insiders build?  Were you able to solve some of the issues that are mentioned above that you experienced after you deleted the items listed?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-01-19T03:35:41+00:00

    I have read virtually all the posts in this stream and tried multiple solutions with no success.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2021-01-24T04:25:51+00:00

    I have read virtually all the posts in this stream and tried multiple solutions with no success.  

    Have you tried turning it off and on again? :p

    Just kidding.

    To get rid of the "Managed by your organization" bug you need to reset certain values. (And dont change them again).

    Check my post about what commands you can put in a powershell to reset them.

    (Its harmless to run them)

    They reset just like msc, but works for Home version as well.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2021-01-24T04:29:44+00:00

    Thank you so much for this solution, you rock!

    I was swearing at my Dell laptop, yes "MY" Dell laptop because of this stupid MS bug with Win10 Home Edition that somehow thinks your machine is administered by some mystical organisation. Peace finally restored!!

    Again, thank you!

    NP =)

    It was "Fixwin 10.1" that made the bug for me. Tore my hair out before I went looking into commands to reset things.

    Win 10 update "January 16th", had the "Managed by your organization" bug as FIXED, so just update should be enough now.

    Was this answer helpful?

    0 comments No comments