Outlook Failed To Start Correctly Last Time..

One of my clients had a problem with his Microsoft Outlook 2003. Whenever he started Outlook, it gave the following warning message

Outlook failed to start correctly last time. Starting Outlook in safe mode will help you correct or isolate a startup problem in order to successfully start the program. Some functionality may be disabled in this mode. Do You want to start Outlook in safe mode?

Outlook Notification not working! -...
Outlook Notification not working! - Steps to Fix it

No matter we click yes or no, the next time Outlook starts, it gives the same warning message. I found out the problem and writing the solution here for future references.

Why does this occur?

This problem usually occurs with Terminal services installed and running..
When Outlook starts, it creates the following key in registry..
HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Resiliency (HKCU)
If no problem occurs during startup of Outlook, this key is deleted automatically. Otherwise if an error occurs during the Outlook startup testing, subkeys under resiliency are created and Outlook gives the same warning message as stated above.
If the subkey from resiliency key is deleted by another application, while the terminal server is in install mode, this key gets copied to HKLM (HKLM\Software\Microsoft\Windows NT\Current Version\Terminal Server\Install\Software\\Microsoft\Office\11.0\Outlook\Resiliency)
Now when the application tries to access the key again through Terminal server application mode, if it finds it missing, it looks for the key in HKLM and if it finds TermSrvCopyKeyOnce under Resiliency, it copies the resiliency key again to HKCU.
Now Outlook always looks for the resiliency key and when it finds it, it gives the same warning message.


The solution to this problem is rather simple. Only deleting the following key will solve the problem:
HKLM\Software\Microsoft\Windows NT\Current Version\Terminal Server\Install\Software\Microsoft\Office\10.0\Outlook\Resiliency
Please tell us about your experiences if you were having the same problem..

28 thoughts on “Outlook Failed To Start Correctly Last Time..”

  1. Thanks a lot. I got the same problem and bothered me for long time. not mission accomplished.
    Great article.

  2. Worked like a charm. The first time each user starts after you make the repair, you get the message again. After that it looks to be gone for good.

  3. Thanks for your help.
    Solved my problem completely. Same as Karl, first time a user accesses Outlook the problem is still there but resolved thereafter.

  4. Didn’t work I could not find that file to delete it. I am running Microsoft Outlook 2002. Please help I am gettign no where.

  5. I have the same problem but was not able to fix it.
    If I go into the reg I can only reach this point HKLM\Software\Microsoft\Windows NT\Current Version\ There is no Terminal Server folder…
    Thanks for your help.

  6. Using W2K Server and I looked everywhere for correct solution. Worked great. Thanks for taking the time to explain this properly.

  7. I have a HP Pavilion a1320n Pentium4 PC, with Office 2003 and started having the same problem with Outlook 2003 recently, no matter what I try, the problem persists. I have been trying to find solution at MSKB and on the Net, and surfed on to this site. I see the solution , but i am a novice and How do I delete the key. I am scared to mess with the registry. Can anyone plese help.

  8. I equally can’t find the resiliency key – should I be looking on the local machine or on the server ?

  9. glad to here that the problem has been solved for some user but i have no had any luck with that.
    don’t have HKLMSoftwareMicrosoftWindows NTCurrent VersionTerminal ServerInstallSoftwareMicrosoftOffice10.0OutlookResiliency
    please help

  10. This fix works great on a Terminal Server in application mode. After deleting the key I opened outlook and one last time it asked me safe mode… I said no. After that it was fine, no more safe mode questions.

  11. Excellent Solution!
    Worked exactly as stated. First time though went to HKLMSoftwareMicrosoftWindows. Instead of HKLMSoftwareMicrosoftWindows NT. Once did what was actually said it worked.

  12. **This fix is ONLY FOR TERMINAL SERVERS** not home PCs. If you are having this problem on your home PC, dig out your Outlook/Office disks (to have ready for when it asks for them) and go to Outlook>Help>Detect and Repair. That should fix it.

    • Update for those using a Terminal Server Farm, the Key is under HKLMSoftwareWow6432NodeMicrosoftWindows NT……etc.  the rest is the same as above depending on your office version, 10, 11….

  13. Awesome tip! That one saved me some headache.
    btw, folks, it is only for terminal servers, and make sure you go down the path HKLM.Software.Microsoft.Windows NT.Current Version…
    NOT WINDOWS. I was confused for a bit why I didn’t have a Terminal Server folder until I realized that.

  14. Hi. This error started popping up a few days ago on our terminal server for citrix and remote desktop users. No idea why it started doing this but I do not have that key under the “Terminal Server” folder. Any other ideas?

  15. Nevermind, I found it. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\Microsoft\Office\11.0\Outlook\Resiliency]
    Deleting the whole “Resiliency” entry has solved the issue.

  16. Update for those using a Terminal Server Farm, the Key is under HKLMSoftwareWow6432NodeMicrosoftWindows NT……etc. the rest is the same as above depending on your office version, 10, 11….

Comments are closed.