Why some features are overriden after installation This is my hook_install:

function moocollar_web_install() {

  // enable features
  $global_features = array ('display_modes_feature' , 'field_bases_feature' , 'image_styles_feature' , 'roles_permissions_feature' , 'sitewide_feature'  , 'wysiwyg_feature' , 'menus_feature');
  $functionality_features = array ('blog_feature');

  $enable_dependencies = TRUE;
  module_enable($global_features, $enable_dependencies);
  module_enable($functionality_features, $enable_dependencies);

  // create editor user
  $role = user_role_load_by_name ('editor');
  $new_user = new stdClass();
  $new_user-&gt;name = 'editor';
  $new_user-&gt;pass = user_password(8); // random password.
  $new_user-&gt;mail = 'editor@example.com';
  if ($role) {
    $new_user-&gt;roles = array ($role-&gt;rid =&gt; $role-&gt;name);
  } 
  $new_user-&gt;status = 1;
  $new_user-&gt;is_new = TRUE;
  user_save($new_user);

  variable_set('features_default_export_path', 'profiles/moocollar_web/modules/features');
}


After install the blog_feature is overriden:

drush features-diff blog_feature
Legend: 
Code:       drush features-revert will remove the overrides.
Overrides:  drush features-update will update the exported feature with the displayed overrides


Component type: info
  features[field_instance][] = node-blog_post-body
  features[field_instance][] = node-blog_post-field_image
&lt; features[menu_links][] = menu-editor-menu_aadir-post:node/add/blog-post
  features[node][] = blog_post
  features[user_permission][] = create blog_post content


Component type: menu_links
&lt; array(
&lt;   'menu-editor-menu_aadir-post:node/add/blog-post' =&gt; array(
&lt;     'customized' =&gt; 1,
&lt;     'link_path' =&gt; 'node/add/blog-post',
&lt;     'link_title' =&gt; 'Añadir post',
&lt;     'menu_name' =&gt; 'menu-editor-menu',
&lt;     'module' =&gt; 'menu',
&lt;     'options' =&gt; array(
&lt;       'identifier' =&gt; 'menu-editor-menu_aadir-post:node/add/blog-post',
&lt;     ),
&lt;     'router_path' =&gt; 'node/add/blog-post',
&lt;   ),
&lt; )
---
&gt; array()


But if I execute revert features via drush, the features is on default state:

drush features-revert blog_feature
Do you really want to revert blog_feature.menu_links? (y/n): y
Reverted blog_feature.menu_links.                                                                       [ok]
vagrant@precise32 (linkinicio *) httpdocs$ drush fd blog_feature
Feature is in its default state. No diff needed. 


On the blog_feature.info I've the dependency and the item:

...
dependencies[] = menu
dependencies[] = menus_feature
....
features[menu_links][] = menu-editor-menu_aadir-post:node/add/blog-post
....


Thanks you all for your time.
Normally Features automatically detects ctools exportables and add the modules containing those exportables to the dependency list, unless a module requirement for an exportable was not detected, or dependent modules were installed since feature was enabled.

Based on your menu link machine name (menu-editor-...), it seems it relies on Menu Editor module and you've missing dependency to that module, therefore Features module didn't detect that component as a requirement, so it become overridden and unrevertable.

The solution is to add the missing module into dependencies list. Then either disable the feature module and reenable it, or manually enable any dependencies not enabled (see Feature Diff to expose them).

See: Troubleshooting: Reasons Features may be stuck as Overridden at Drupal.org