1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Resolved [Unable to open Policy Editor (The snap-in referenced in this doc has been restricted by policy)]

Discussion in 'Windows 10' started by ramjet, 2016/07/02.

  1. 2016/07/02
    ramjet

    ramjet Well-Known Member Thread Starter

    Joined:
    2007/08/30
    Messages:
    132
    Likes Received:
    0
    Trophy Points:
    231
    Location:
    SE Ohio
    Computer Experience:
    intermediate
    I just tried to open "GPEDIT.MSC" and get this error "The snap-in referenced in this doc has been restricted by policy. Contact your administrator for details. Group Policy Object Editor." I am the Admin and have been unable to get into the policy editor..Any
    ideas?? Also I did have dual boot with Win 7...How do I delete the Win 10 dual boot menu ??
    Thanks
     
    Last edited by a moderator: 2016/07/02
  2. 2016/07/02
    retiredlearner

    retiredlearner SuperGeek WindowsBBS Team Member

    Joined:
    2004/06/25
    Messages:
    5,455
    Likes Received:
    295
    Trophy Points:
    1,093
    Location:
    New Zealand
    Computer Experience:
    intermediate

  3. to hide this advert.

  4. 2016/07/02
    ramjet

    ramjet Well-Known Member Thread Starter

    Joined:
    2007/08/30
    Messages:
    132
    Likes Received:
    0
    Trophy Points:
    231
    Location:
    SE Ohio
    Computer Experience:
    intermediate
  5. 2016/07/02
    retiredlearner

    retiredlearner SuperGeek WindowsBBS Team Member

    Joined:
    2004/06/25
    Messages:
    5,455
    Likes Received:
    295
    Trophy Points:
    1,093
    Location:
    New Zealand
    Computer Experience:
    intermediate
    Have a look through this link gpedit.msc does not exist in 10074 (windows 10) as I noted from your System specs you installed from the "Insider" program and one of the guys expanded his ISO to see if gpedit was in there. May be worth checking. Neil.
     
  6. 2016/07/02
    ramjet

    ramjet Well-Known Member Thread Starter

    Joined:
    2007/08/30
    Messages:
    132
    Likes Received:
    0
    Trophy Points:
    231
    Location:
    SE Ohio
    Computer Experience:
    intermediate
    Hi N.
    Did checking, GPedit.msc is in windows/system 32 (clicking & got same error) I'm running a much later version Pro 10586.420 (I think this is the latest).
    Still no joy...tried most of what was suggested.(this is not a hardware problem..I have 10 enterprise installed on another drive and GPedit works fine).
    Thanks.
     
  7. 2016/07/06
    ramjet

    ramjet Well-Known Member Thread Starter

    Joined:
    2007/08/30
    Messages:
    132
    Likes Received:
    0
    Trophy Points:
    231
    Location:
    SE Ohio
    Computer Experience:
    intermediate
    Since my first post, I've found that I cannot get into mant of the system functions(gpedit,computer management ect) I get the same error as posted.
    I did a clean install (saving apps,files ect) still get the same error...Any more Ideas ???
     
  8. 2016/07/06
    retiredlearner

    retiredlearner SuperGeek WindowsBBS Team Member

    Joined:
    2004/06/25
    Messages:
    5,455
    Likes Received:
    295
    Trophy Points:
    1,093
    Location:
    New Zealand
    Computer Experience:
    intermediate
  9. 2016/08/25
    ramjet

    ramjet Well-Known Member Thread Starter

    Joined:
    2007/08/30
    Messages:
    132
    Likes Received:
    0
    Trophy Points:
    231
    Location:
    SE Ohio
    Computer Experience:
    intermediate

Share This Page