Windows 10 mail client returns 0x86000c2a syncing ActiveSync

When trying to sync with Exchange ActiveSync it works for about a day then starts returning the error 0x86000c2a "We weren't able to apply the security policy that's required by "eas.xxxxxx.com". Contact your company's support person to fix the problem."

But since I'm that support person it doesn't tell me what to do about it or who else I can contact. I can't imagine what I could change on the Exchange server to fix this when it works with every other platform including the Windows 8/8.1 email client.

I've just downloaded the latest version of the email client (version 17.6017.42001.0) and it still has the problem. With Win 10 build 10240.

Any additional information on this problem would be appreciated.

July 19th, 2015 9:48am

See if you or someone else has defines mobile device mailbox policies.

https://technet.microsoft.com/en-us/library/bb123783%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

Free Windows Admin Tool Kit Click here and download it now
July 20th, 2015 1:13am

I have the very same problem, has been a problem also with Windows 10 Insider Preview for Phones however latest phone build works, PC version does not, so if RTM of 10 does not work then I will have to roll back to 8.1 to ensure enterprise email access.

This is not an ActiveSync problem, this is a bug

Free Windows Admin Tool Kit Click here and download it now
July 21st, 2015 5:56pm

I have found that switching to a local account instead of the MSA login one solves the issue.
July 30th, 2015 1:57am

I have found that switching to a local account instead of the MSA login one solves the issue.
  • Proposed as answer by Ed CrowleyMVP Thursday, July 30, 2015 6:34 AM
Free Windows Admin Tool Kit Click here and download it now
July 30th, 2015 5:55am

I have found that switching to a local account instead of the MSA login one solves the issue.
  • Proposed as answer by Ed CrowleyMVP Thursday, July 30, 2015 6:34 AM
July 30th, 2015 5:55am

This is not much of a solution though, is it? It is useful for debugging the problem, but I need to use the Microsoft account for logging in.
Free Windows Admin Tool Kit Click here and download it now
August 5th, 2015 2:14am

I too have this same issue and error. But it worked on my surface pro 3 with Win 8.1. I'm continuing to debug but would love an answer.
August 5th, 2015 11:50am

Interesting development, and not sure what changed but after attempting to get the Exchange server to allow me access per the 0x86000c2a error message, now I don't get that message any longer but now when I set up the account, it continues to prompt me "please update the password for this account". But after several attempts to load the my password, deleting the account and starting over, I get the same new prompt.

Thought this might help if someone is tying all the data points together to debug the issue.

Free Windows Admin Tool Kit Click here and download it now
August 5th, 2015 2:35pm

Same problem here, Surface Pro 3 running 8.1 worked great, applied Windows 10 update and now email returns 0x86000c2a
August 11th, 2015 6:31pm

Tried this. But have the same issue. I hope the answer is comming soon. We have multible users with this problem.
Free Windows Admin Tool Kit Click here and download it now
August 12th, 2015 2:39am

I have the same problem. waiting for a fix. this gets annoying

August 27th, 2015 5:18pm

I have found some success by making a change to our ActiveSync policy. I've set the "MinDevicePasswordComplexCharacters" property from the default value of "3" to "1". For whatever reason this has caused the issue to go away.

The policy still has "MinDevicePasswordLength" as "4" so it didn't reduce the password length and since we only require digits the number of complex characters didn't really matter. So in the end we didn't feel it compromised the policy at all and has fixed the issue on all of my test cases.

I'd rather know the issue is fixed in the client but this is an acceptable workaround for us.

Free Windows Admin Tool Kit Click here and download it now
August 28th, 2015 4:15pm

I have spent sometime on this looking at ActiveSync settings, differences with Win10 Mobile and Win10 Pro configuration etc, in the end this is what I found worked:

* The SP3 CANNOT be configured to use an MSA account, LOCAL accounts only, so no Insider Builds

* The user profile MUST be an Administrator

Once I configured these two settings the ActiveSync started to work

Best of luck!

September 14th, 2015 6:07am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics