Group Policy Mitigation Options Warning

Discussion in 'other software & services' started by Zorak, Nov 5, 2017.

  1. Zorak

    Zorak Registered Member

    Joined:
    Jan 2, 2010
    Posts:
    182
    Location:
    Australian Capital Territory
    Having successfully upgraded to Win 10 1709 (I'm not calling it Fall Creators Update because it is spring here!!) I get a Group Policy Event ID 1085 warning stating "Windows failed to apply the MitigationOptions settings.." whenever I restart my computer. There are 2 mitigation options listed in Group Policy under "Administrative Templates\System\Mitigation Options\Process Mitigation Options", but neither one of them are enabled.

    Could this warning be referring to any other exploit mitigations I have set (eg. Attack Surface Reduction rules) or is this just a bug? Is anyone else seeing the same warning?
     
  2. plat1098

    plat1098 Guest

    Yes. I got the event 1085 by enabling Block Untrusted Fonts via group policy, Windows 10 Pro Fall CU. Microsoft did not list this as a deprecated feature in the FCU but it is. I had to reset the gpe in order to get rid of the warning.
     
  3. Zorak

    Zorak Registered Member

    Joined:
    Jan 2, 2010
    Posts:
    182
    Location:
    Australian Capital Territory
    I even un-enabled all Group Policy settings and still get Event ID 1085 :thumbd:
     
  4. RockLobster

    RockLobster Registered Member

    Joined:
    Nov 8, 2007
    Posts:
    1,812
    Sounds like Windows tried to apply a group policy template but was unable to.
    Maybe because it applied to mitigation settings that is disabled?
     
  5. plat1098

    plat1098 Guest

    I clearly said it was necessary to reset the group policy--to defaults--not fiddling around with individual mitigation settings. Good luck.
     
  6. Zorak

    Zorak Registered Member

    Joined:
    Jan 2, 2010
    Posts:
    182
    Location:
    Australian Capital Territory
    I only had to reverse 3 settings - not much fiddling involved ;)
     
  7. Zorak

    Zorak Registered Member

    Joined:
    Jan 2, 2010
    Posts:
    182
    Location:
    Australian Capital Territory
    OK, so I did a "hard reset" of Group Policy Objects and what do you know - the error is gone. I will add back the 3 changes one by one and see if the error re-appears.

    Thanks @plat1098 - I've learnt something today :thumb:
     
  8. plat1098

    plat1098 Guest

    OK, no problem. :)
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.