Outlook 2013 Windows 10 Bug – “A required action was not successful because of an unspecified error”

Along with hundreds of thousands of people; I’ve just updated windows to Windows 10. Almost everything has worked flawlessly except Outlook twinned with e-mail signing. Now when I try and send email from Outlook 2013 I’m greeted with the following error: outlook-2013-signed-unspecified-error
“Microsoft Outlook” “A required action was not successful because of an unspecified error.” Un-ticking the option to sign the e-mail then allows it to send. The most information I can find is something to do with Outlook’s access to Windows Crypto API.

To be even more weird I’ve actually managed to send a signed message once.. then it broke again a few minutes later when I went to reply to another message.

I’ve reproduced this problem on a brand new Windows 10 installation with Office 2013 and verified that the problem doesn’t exist on a brand new install of Windows 8.1 with Office 2013. All tests were performed using the same certificate.

I’ve reported the problem to Microsoft and have been assigned the referenceĀ 1298080798. Supposedly someone will contact me for further diagnostics within the next day. UPDATE: I never heard anything more from Microsoft! Pretty poor performance there.

FIX IS HERE!

Thank you to visitor “John” who found the solution on the Microsoft forums.. Simply run sfc /scannow. No reboot required either.
Here is what I tested and found solved the issue:

1) Close Outlook
2) Click start, type in cmd. Right click on CMD and run it as Administrator.
3) Type in sfc /scannow and press enter

C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

C:\WINDOWS\system32>

4) Once it finishes.. close command prompt.
5) Try Outlook again!

However as the problem crops up on a brand new Windows 10 install without a prior Windows 7 or 8 upgrade this means the Office installer is somehow breaking windows, or windows is broken out of the box until you run an sfc.

Advertisements
This entry was posted in Uncategorized. Bookmark the permalink.

10 Responses to Outlook 2013 Windows 10 Bug – “A required action was not successful because of an unspecified error”

  1. Yip says:

    I have the exact same problem.

    I also reinstalled the certificate but to no end.

    Please keep us posted.

  2. John says:

    Me too. tried to reassign the certificate in the Outlook trust centre, but that didn’t help either…

  3. John says:

    Just saw this is in a Microsoft forum “try “sfc /scannow””. Stopped Outlook 2013. Executed it from an Admin prompt. Restarted Outlook. Send with Certificate now works again.

  4. I will try this and report back.

  5. Amazing – that does fix it. No reboot required either.
    Closed Outlook, ran cmd as administrator then typed
    SFC /scannow and pressed enter. Waited for it to complete.
    Job done!

  6. Michael says:

    Same issue with Office 2016 on Windows 10, completely clean install. Thanks for the fix!

  7. Ruslan says:

    unfortunately, it did not help me. Win8.1/Outlook 2016

  8. I wouldn’t have thought so.. this article is about a Windows 10 + Outlook bug :) But thank you for the feedback.

  9. Peter says:

    Perfect fix, thanks

Comment on this topic

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s