none
The data present in the reparse buffer is invalid 0x80071128 RRS feed

  • Question

  • I have 1 policy getting the error "The data present in the reparse buffer is invalid "

    I can create new policy without the error message
    No other policy is getting the error
    I can remove the policy and edit the policy with no problem
    I can create a new policy (no error) and when I apply it to the OU I get the error

    Here is the JIT Error:

    See the end of this message for details on invoking 
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.Runtime.InteropServices.COMException (0x80071128): The data present in the reparse point buffer is invalid. (Exception from HRESULT: 0x80071128)
       at Microsoft.GroupPolicy.AdmTmplEditor.IGPMAdmTmplEditorCallback.ApplyChanges()
       at Microsoft.GroupPolicy.AdmTmplEditor.Editor.SaveChanges()
       at Microsoft.GroupPolicy.AdmTmplEditor.Editor.buttonApply_Click(Object sender, EventArgs e)
       at System.Windows.Forms.Control.OnClick(EventArgs e)
       at System.Windows.Forms.Button.OnClick(EventArgs e)
       at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
       at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.ButtonBase.WndProc(Message& m)
       at System.Windows.Forms.Button.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


    ************** Loaded Assemblies **************
    mscorlib
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2117.0 built by: NET47REL1LAST
        CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
    ----------------------------------------
    Microsoft.GroupPolicy.AdmTmplEditor
        Assembly Version: 6.3.0.0
        Win32 Version: 6.3.9600.16384 (winblue_rtm.130821-1623)
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/Microsoft.GroupPolicy.AdmTmplEditor/v4.0_6.3.0.0__31bf3856ad364e35/Microsoft.GroupPolicy.AdmTmplEditor.dll
    ----------------------------------------
    System
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Windows.Forms
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    ----------------------------------------
    System.Drawing
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2053.0 built by: NET47REL1
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    ----------------------------------------
    System.Configuration
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2053.0 built by: NET47REL1
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    ----------------------------------------
    System.Core
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2117.0 built by: NET47REL1LAST
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
    ----------------------------------------
    System.Xml
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2612.0 built by: NET471REL1LAST_B
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    ----------------------------------------
    Accessibility
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2053.0 built by: NET47REL1
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
    ----------------------------------------

    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.

    For example:

    <configuration>
        <system.windows.forms jitDebugging="true" />
    </configuration>

    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.

    Friday, January 12, 2018 4:31 PM

All replies

  • Hi,

    Thank you for your question. 
    I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
    Thank you for your understanding and support.

    Best Regards,

    William


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, January 15, 2018 6:30 AM
  •  

    Hi,

    To determine the issue in an efficient way, could you please help collect the following information at your earliest convenience.

    1. How many clients/OUs have this issue, one or all?
    2. What’s the Operation System on the effected machines? if the Server is 2008, we suggest you can install the below hotfix

    https://support.microsoft.com/en-us/help/967358/you-receive-error-messages-when-you-try-to-create-a-domain-gpo-or-edit

    1. Could you please capture the screen about the error messages in the GUI?
    1. Please create new files under C:\Windows\SYSVOL\domain\Policies on one DC and check whether the file can be replicated to each other, it can check the status of Sysvol replication.
    2. Error “The data present in the reparse buffer is invalid” may be related to corruption on the volume, please check the disks on the DCs

    # as an HRESULT: Severity: FAILURE (1), FACILITY_WIN32 (0x7), Code 0x1128

    # for hex 0x1128 / decimal 4392

      ERROR_INVALID_REPARSE_DATA                                     winerror.h  

    # The data present in the reparse point buffer is invalid.

    If you have any questions, please feel free to contact me.

    Best Regards,

    William


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, January 16, 2018 5:48 AM
  • I have the same issue whenever I want to add or paste a registry value (Computer Configuration / Preferences / Windows Settings / Registry). I guess that it is related to the 2018-01 updates.

    Sometimes it still accepts the key (so when I close and re-open the GPO it is still there), sometimes not.

    (Servers are 2012R2 with latest patches. Same issue with RSAT on Windows 10 1709.)
    • Edited by svhelden Tuesday, January 16, 2018 8:19 AM
    Tuesday, January 16, 2018 7:54 AM
  • Same issue at me.
    Wednesday, January 17, 2018 10:47 AM
  • Same here. Sofar a lot of errors relating to modifying GPPs. Eventually I'm able to poke through and get the required changes accepted.

    Guess Microsoft has some fixing to do.


    • Edited by PolarWolf Wednesday, January 17, 2018 1:54 PM
    Wednesday, January 17, 2018 1:53 PM
  • Having the same issues here as well after installing the 2018-01 Security updates in various areas of GPMC on my Server 2012 R2 domain controllers.  I have one physical DC where KB4056895 and 4056898 had to be rolled back temporarily due to a hardware compatibility issue that needs addressing and some of these SAME POLICIES can be edited there with NO issues.

    From patched systems when editing applocker rules (just trying to add a new publisher rule for everyone for Microsoft Teams updater, this one works on the DC that is missing 4056898 and 4056895):

    When trying to delete a computer-based registry preference item there was also an error, it left "junk" in the registry preference portion of the policy and I had to restore the policy from a backup (don't have screenshots on this one but it happened to two different policies).

    And just when editing normal policy items (ie set an administrative template item to to enabled, disabled, not configured) getting random errors like this, although the setting seems to get correctly changed and will stick.  This one does NOT work from the DC missing 4056895 and 4056898, but that DC does have the remainder of the new January monthly patches.

     

    See the end of this message for details on invoking

    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************

    System.Runtime.InteropServices.COMException (0x80071128): The data present in the reparse point buffer is invalid. (Exception from HRESULT: 0x80071128)

       at Microsoft.GroupPolicy.AdmTmplEditor.IGPMAdmTmplEditorCallback.ApplyChanges()

       at Microsoft.GroupPolicy.AdmTmplEditor.Editor.SaveChanges()

       at Microsoft.GroupPolicy.AdmTmplEditor.Editor.buttonOK_Click(Object sender, EventArgs e)

       at System.Windows.Forms.Control.OnClick(EventArgs e)

       at System.Windows.Forms.Button.OnClick(EventArgs e)

       at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)

       at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

       at System.Windows.Forms.Control.WndProc(Message& m)

       at System.Windows.Forms.ButtonBase.WndProc(Message& m)

       at System.Windows.Forms.Button.WndProc(Message& m)

       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

    ************** Loaded Assemblies **************

    mscorlib

        Assembly Version: 4.0.0.0

        Win32 Version: 4.7.2117.0 built by: NET47REL1LAST

        CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll

    ----------------------------------------

    Microsoft.GroupPolicy.AdmTmplEditor

        Assembly Version: 6.3.0.0

        Win32 Version: 6.3.9600.16384 (winblue_rtm.130821-1623)

        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/Microsoft.GroupPolicy.AdmTmplEditor/v4.0_6.3.0.0__31bf3856ad364e35/Microsoft.GroupPolicy.AdmTmplEditor.dll

    ----------------------------------------

    System

        Assembly Version: 4.0.0.0

        Win32 Version: 4.7.2114.0 built by: NET47REL1LAST

        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

    ----------------------------------------

    System.Windows.Forms

        Assembly Version: 4.0.0.0

        Win32 Version: 4.7.2114.0 built by: NET47REL1LAST

        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

    ----------------------------------------

    System.Drawing

        Assembly Version: 4.0.0.0

        Win32 Version: 4.7.2053.0 built by: NET47REL1

        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

    ----------------------------------------

    MMCEx

        Assembly Version: 3.0.0.0

        Win32 Version: 6.3.9600.16384

        CodeBase: file:///C:/Windows/assembly/GAC_MSIL/MMCEx/3.0.0.0__31bf3856ad364e35/MMCEx.dll

    ----------------------------------------

    MMCFxCommon

        Assembly Version: 3.0.0.0

        Win32 Version: 6.3.9600.16384

        CodeBase: file:///C:/Windows/assembly/GAC_MSIL/MMCFxCommon/3.0.0.0__31bf3856ad364e35/MMCFxCommon.dll

    ----------------------------------------

    System.Configuration

        Assembly Version: 4.0.0.0

        Win32 Version: 4.7.2053.0 built by: NET47REL1

        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

    ----------------------------------------

    System.Core

        Assembly Version: 4.0.0.0

        Win32 Version: 4.7.2117.0 built by: NET47REL1LAST

        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

    ----------------------------------------

    System.Xml

        Assembly Version: 4.0.0.0

        Win32 Version: 4.7.2612.0 built by: NET471REL1LAST_B

        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

    ----------------------------------------

    dnscmmc

        Assembly Version: 6.3.0.0

        Win32 Version: 6.3.9600.16384 (winblue_rtm.130821-1623)

        CodeBase: file:///C:/Windows/system32/dnscmmc.DLL

    ----------------------------------------

    Accessibility

        Assembly Version: 4.0.0.0

        Win32 Version: 4.7.2053.0 built by: NET47REL1

        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll

    ----------------------------------------

    ************** JIT Debugging **************

    To enable just-in-time (JIT) debugging, the .config file for this

    application or computer (machine.config) must have the

    jitDebugging value set in the system.windows.forms section.

    The application must also be compiled with debugging

    enabled.

    For example:

    <configuration>

        <system.windows.forms jitDebugging="true" />

    </configuration>

    When JIT debugging is enabled, any unhandled exception

    will be sent to the JIT debugger registered on the computer

    rather than be handled by this dialog box.


    • Edited by Midnite__A Wednesday, January 17, 2018 3:54 PM
    Wednesday, January 17, 2018 3:01 PM
  • Hello,

    I had this same error after installing the "Windows_ 10_Creators_Update_ADMX.msi" GP upgrade on one of my domain controllers (or maybe it was just a coincidence? I did not view if there were some Windows Updates pending maybe they DID Install when I restarted the server).

    1. I checked the replication and it was fine. (copied file to: C:\Windows\SYSVOL\domain\Policies and checked the replication status with CMDlet: "repadmin /showrepl")
    2. I restarted the server with but there was no effect.
    3. I installed the pending updates and the error stopped. This was the only update that was pending at the time
    • Microsoft .NET Framework 4.7.1 for Windows 8.1 and Windows Server 2012 R2 for x64 (KB4033369)

    Of course it's also possible that simply restarting the DC:s was the key to solve replication between the two domain controllers that we use.

    Monday, January 22, 2018 10:52 AM
  • Hi,
    This is a quick note to let you know that I am currently performing research on this issue and will get back to you as soon as possible. I appreciate your patience.
    If you have any updates during this process, please feel free to let me know.
    Best Regards,
    William

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, January 22, 2018 1:53 PM
  • Hi, I get: 

    The overall error was: The data present in the reparse point buffer is invalid. (Exception from HRESULT: 0x80071128) when trying to deploy a GPO with AGPM, looking forward to your research regarding this problem.

    Monday, January 22, 2018 2:33 PM
  • We are getting the same errors in our environment as well. 2012 R2 level. I just tried to change a GPO and exact same error. We did just patch this past weekend. Any one have a fix?
    Monday, January 22, 2018 10:28 PM
  • I have the same issue. I was able to determine that if you force GPMC to the same server that you are currently logged onto - there is no issue. (At least for me). Also, if I tried to make changes to gpt.ini directly in C:\Windows\Sysvol\domain\policies, it works fine on any server. But if I try to edit the gpt.ini file via \\domain\sysvol\domain\policies, it fails with the same error.
    Monday, January 22, 2018 11:08 PM
  • We are having the same issue. Opening a case with Microsoft.
    • Proposed as answer by bazfum Thursday, January 25, 2018 3:41 PM
    • Unproposed as answer by bazfum Thursday, January 25, 2018 3:41 PM
    Tuesday, January 23, 2018 6:43 PM
  • Same Issue. MS case opened.
    Wednesday, January 24, 2018 11:51 AM
  • I am also having the same issue. We installed updates the past weekend and are unable to update GPO. Error received is the same as the original post. Any update from the current opened MS Cases? 
    Wednesday, January 24, 2018 4:34 PM
  • Any update to this issue? 
    Wednesday, January 24, 2018 4:57 PM
  • Same issue here on 2012R2 domain controllers and after the January 2018 security updates were installed, not able to modify GPO's!
    Wednesday, January 24, 2018 6:46 PM
  • Same issues here in our environment of 2012 R2 Domain Controllers. On our Default Domain Policy and another one. Started after this past weekends updates from Microsoft.
    We been working with Microsoft since this morning and still haven't gotten resolution.
    • Edited by RussellZ Wednesday, January 24, 2018 9:04 PM
    Wednesday, January 24, 2018 9:03 PM
  • you can install the new patch KB4033369 it will fix the edit issue in GPO.
    Thursday, January 25, 2018 5:12 AM
  • Hi,

    I would apologize for the delayed reply.

    We have installed the KB4056895 and 4056898 on the 2012 R2 Domain Controllers in our test lab, but we don’t got the error messages “The data present in the reparse buffer is invalid 0x80071128” when edit the group policy, I assume it could be a random issue after we install the KBs. It may take some time to consult this issue with our related Engineers.

    Here I share some solution which have worked for other customers:

    1. Unlink GPO from its OU and edit. For some customer’s issue was OU specific.
    2. Remove Authenticated Users from SCOPE of GPO and edit, then we can add the Authenticated Users “Read Permission” In the delegation console.
    3. In some cases restoring the GPO from backup or re-creating it works.

    If you have any questions, please feel free to contact me.

    Best Regards,

    William


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, January 25, 2018 8:46 AM
  • Same issue here, opened case with MS and they say it's a huge issue and product team is working on it.

    Thursday, January 25, 2018 12:05 PM
  • Hi,

    I would apologize for the delayed reply.

    We have installed the KB4056895 and 4056898 on the 2012 R2 Domain Controllers in our test lab, but we don’t got the error messages “The data present in the reparse buffer is invalid 0x80071128” when edit the group policy, I assume it could be a random issue after we install the KBs. It may take some time to consult this issue with our related Engineers.

    Here I share some solution which have worked for other customers:

    1. Unlink GPO from its OU and edit. For some customer’s issue was OU specific.
    2. Remove Authenticated Users from SCOPE of GPO and edit, then we can add the Authenticated Users “Read Permission” In the delegation console.

    3. In some cases restoring the GPO from backup or re-creating it works.

    If you have any questions, please feel free to contact me.

    Best Regards,

    William


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact 

    Does not work.

    got same issue while i want to add some registry keys to a gpo.

    i added 7 keys after then i get the error. after some minutes i was able to remove two keys and readd 2 keys again (different keys). then it got again stuck on 7 key entries.

    system: 2012R2 @ Central Store

    little workaround:

    use another DC to implement the next keys, that is working in my case.

    Thursday, January 25, 2018 3:07 PM
  • We're getting same issue when editing GPO.

    In our case its when editing Scheduled Task GPP that we apply to servers.

    If I unlink the GPO from the OU first and then try to edit the same task I don't get the error. If I link it back again and try to edit the same task the error returns.

    Only recent change/patch that has been applied since we started seeing this error is KB4056898.

    Friday, January 26, 2018 10:08 AM
  • Uninstalling KB4056895 and 4056898 worked for me. Now i am able to update the GPO Regkeys on the DC where the Updates are uninstalled. GPME must be connected to the DC where the Updates are uninstalled!!!

    Best Regards,

    Thomas

    Friday, January 26, 2018 10:12 AM
  • When i check the following using handle.exe from sysinternals:

    .\handle.exe c:\windows\sysvol\domain|measure

    I'm getting a huge number of handles from system pid towards sysvol files on the affected DCs compared to other DCs, are you seeing the same?

    On the ones where this is showing i cannot even edit a gpt.ini with notepad without getting the invalid reparse point data...

    Friday, January 26, 2018 1:26 PM
  • Microsoft got back to us this morning saying they identified the issue. For now, the engineer had us take off the KBs on all of our DCs which resolved the issue:

    KB4054170

    KB4056568

    KB4056898

    It is now listed as an known issue on both the January 8th monthly rollup and the January 3rd security-only monthly rollup. 


    • Edited by Ds_aj Friday, January 26, 2018 7:40 PM
    • Proposed as answer by JJones_WoooWooo_ Friday, January 26, 2018 9:37 PM
    Friday, January 26, 2018 7:40 PM
  • I looked on my DC's and these updates are not installed.  I have set my WSUS to remove them from my servers anyway.  I am still having the error occur when trying to edit policies.  Removing the policy from the OU and editing it, then re-applying it however seems to work like a charm.  Its not ideal, but it will get my edits done until there is a viable fix.
    Friday, January 26, 2018 7:55 PM
  • Uninstalling these updates corrected my issue.

    Thank you all for the hard work and relaying information.

    Hopefully the next round of updates do not cause these similar issues.

    Thank you!

    Friday, January 26, 2018 9:39 PM
  • Microsoft got back to us this morning saying they identified the issue. For now, the engineer had us take off the KBs on all of our DCs which resolved the issue:

    KB4054170

    KB4056568

    KB4056898

    It is now listed as an known issue on both the January 8th monthly rollup and the January 3rd security-only monthly rollup. 


    Hi,

    Thanks for share the solution. Since uninstalled the KBs will let our servers risky, hope Microsoft could publish new KB/Hotfix to solve the issue as soon as possible.

    Best Regards,

    William


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, January 31, 2018 2:53 AM
  • Microsoft got back to us this morning saying they identified the issue. For now, the engineer had us take off the KBs on all of our DCs which resolved the issue:

    KB4054170

    KB4056568

    KB4056898

    It is now listed as an known issue on both the January 8th monthly rollup and the January 3rd security-only monthly rollup. 


    Would love to get an update on this issue, uninstalling kb's is not an option in our environment.

    Wednesday, January 31, 2018 12:33 PM
  • FYI: None of these KBs are installed on our DCs (all are 2016) and we're seeing this error.
    Wednesday, January 31, 2018 7:08 PM
  • We are having the exact same issue and it did not start until after the updates were installed. Waiting to hear back from support on our issue as well.
    Wednesday, January 31, 2018 10:30 PM
  • We've got the same error while editing some GPOs.


    my blog: http://shserg.ru/

    Thursday, February 1, 2018 11:14 AM
  • Could you share the answer of MS to your case?

    my blog: http://shserg.ru/

    Thursday, February 1, 2018 11:16 AM
  • If you remove this: "2018-01 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4056890)" then those updates are in there and you will be able to update your GPO's again without error. I just removed that update from my DCs, rebooted then and then updated the GPO's fine.
    Thursday, February 1, 2018 3:45 PM
  • I did not have that kb on my dc.

    I first removed kb 4056568 and 4056898, reboot, still error.

    After that i removed kb4056895, 4055001 and 4054999, rebooted and the error on that dc was gone.

    But that was on 2012 dc, not 2016.



    • Edited by PatrickEv Friday, February 2, 2018 6:50 AM
    Friday, February 2, 2018 6:49 AM
  • support.microsoft.com/en-us/help/4056895 is the page with more info.
    • Edited by PatrickEv Friday, February 2, 2018 1:02 PM
    Friday, February 2, 2018 9:57 AM
  • We've found a workaround, but it's rather involved.  But, it insures that at no point the policy is not in place if a client were to update GP during the change.

    To update a GPO that has been frozen by the recent Windows update:

    1. Open Group Policy Management console
    2. Navigate to the GPO you want to modify under Group Policy Objects
    3. Right-Click and select Backup (backup the GPO to an easily accessible location)
    4. Rename the GPO (appending -OLD works fine)
    5. Create a new GPO and give it the original name of the old GPO
    6. Right-Click the new GPO, select Import (import the backed up GPO)
    7. Make your desired changes to the new GPO
    8. Snapshot the Scope tab on the OLD GPO
    9. For each Location on the list
        -Navigate to the Linked GPO tab under the first OU
        -Right-Click the OU and select "Link an Existing GPO"
        -Select DOT EC Workstation Policy  - Click OK
        -Move it up next to the OLD policy in the list
        -Check whether the link should be disabled
        -Delete the OLD DOT EC Workstation Policy link
        -Navigate to the next OU on the list

    Please note, once the links are re-established the GPO can not be updated.  You'll need to go through the whole process over again.

    Hope this helps...

    ~Craig


    • Edited by RCStrunk66 Friday, February 9, 2018 4:31 PM clarification
    • Proposed as answer by R. Scott Clark Tuesday, February 13, 2018 3:50 AM
    Wednesday, February 7, 2018 8:51 PM
  • I ran into this problem earlier and I needed to make a change to an existing GPO.  I didn't have the option of waiting or removing updates on Domain Controllers.  I'm not sure why this worked, or if it was just coincidence, but after making a copy of the GPO I was able to edit both the copy and the original.  I used powershell to do it from a member server (not a domain controller) --

    Copy-GPO -SourceName "name" -TargetName "name"

    Maybe it helps someone else in a pinch like I was.  I'm hoping this gets fixed next Tuesday -- being locked out of group policy isn't fun!

    Friday, February 9, 2018 10:14 PM
  • Microsoft article still states that it's working on a resolution and will provide an update in an upcoming release....
    Monday, February 12, 2018 7:06 AM
  • My Windows 2012 R2 DCs are affected as well.

    Hoping for a fix in this week's patch Tuesday.

    Tuesday, February 13, 2018 9:14 AM
  • I was informed by Microsoft that an update will arrive today which fixes this issue.
    Tuesday, February 13, 2018 10:41 AM
  • I was informed by Microsoft that an update will arrive today which fixes this issue.

    I'll believe that when I see it...

    I do this cause it pays the bills...

    Tuesday, February 13, 2018 7:47 PM
  • It's out! KB4074594
    https://support.microsoft.com/en-us/help/4074594/windows-81-update-kb-4074594 
    Wednesday, February 14, 2018 1:16 AM
  • Seems to fix the issue for me.
    Wednesday, February 14, 2018 4:48 PM
  • The update does not fix my 2012 R2 DCs.

    Way to go MS. 

    Thursday, February 22, 2018 4:32 PM
  • I had this problem too. I have installed the latest updates on my DC and this has solved the problem.
    Tuesday, February 27, 2018 3:51 PM
  • The update does not fix my 2012 R2 DCs.

    Way to go MS. 


    Didn't fix for me as well.
    Friday, March 16, 2018 12:32 PM
  • This is actually causing SYSVOL replication issues with our DCs stopping DFS Replication on Server 2012.

    I try to delete an old Logon Script from SYSVOL\Scripts and I am also getting

    "An unexpected error is keeping you from deleting the file.
    Error 0x80071128 The data present in the reparse point buffer is invalid"

    Our DC's with this error have not been Replicating SYSVOL since the errors started. The DC's without the error are replicating fine between themselves.


    lforbes

    Friday, March 23, 2018 6:42 PM