Unable to Generate DirectAccess Diagnostic Log in Windows 10 v1709

There are numerous reports that generating the DirectAccess troubleshooting log fails on Windows 10 v1709. DirectAccess administrators have been reporting that the process seems to fail during the creation of the log file, leaving it truncated and incomplete. To resolve this issue, open an elevated PowerShell window and enter the following command.

New-ItemProperty -Path “HKLM:\SYSTEM\CurrentControlSet\Services\NcaSvc\” -Name SvcHostSplitDisable -PropertyType DWORD -Value 1 -Force

The computer must be restarted for this change to take effect. If initial testing of this workaround is successful, the registry setting can be pushed out to all DirectAccess clients using Active Directory Group Policy Preferences.

Leave a comment


  1. Hiho Richard,

    thanks alot once again for your profound articles! The solution works like a charm, but after setting the reg-hack a reboot was required on my device.

    Cheers, Karsten…

  2. Hi Richard,

    a customer from us reported, that he had the same problem on Windows 10 1703. The registry-entry also solved the issue on 1703!

    Greets, Karsten…

    • Thanks for the update, Karsten. I’ve been hearing similar reports. Initially my customers were all on 1709, so I assumed it was just that release. Now hearing 1703 is affected too. Good to know the fix works in either case!

  3. Dan Bhatoa

     /  November 8, 2018

    The issue exists on 1803 as well. Also be wary of making the change over DA, it breaks the connection. Gpupdate once you’re in the office and it worked fine.



Leave a Reply to Richard M. HicksCancel reply

%d bloggers like this: