This is spooky behaviour I have seen multiple times on 3.9-support and 4.0 M2 on two different mp deployments.
Three cases, my guess is same root cause (caching?):
1. Connector returns in executeQuery _ENABLED_ = true
- Opening projection from mp however shows adminStatus of the account as disabled.
2. Changing capabilities of the resource is reflected in Resource GUI, but sometimes mp is not aware that e.g. activation capability was enabled.
3. AD connector when switched to rawUserAccountControlAttribute=true mode does not realize the changed setting for some time and quits with error that _enable_ attribute is not in the schema.
Restarting mp, or uploading (unchanged) ResourceType xml fixes these problems usually. Until they occur again... Sometims clicking Test Connection will do the job as well.