Home » How To » How to resolve: Error 997. Overlapped I/O operations is in progress while installing SQL Server 2014

How to resolve: Error 997. Overlapped I/O operations is in progress while installing SQL Server 2014

Recently I was trying to install SQL Server 2014 Express on my laptop and struck at an error.

Error 997. Overlapped I/O operations is in progress.

Error 997

I still couldn’t figure out the root cause for this error, but as per this MSDN blog post, it is because of some Microsoft Windows Updates, but even after following the steps mentioned by some users in the comments after removing all the patches related to this error, I still got the same error.

There was a comment by user M, where he was able to resolve the issue by adding some keys to Windows Registry. Since the MSDN blog was specific to Visual Studio, I am writing this post specific to Microsoft SQL Server 2014.

From what I have learned, the SQL Server 2014 installation is an MSI of multiple components, each of this component is installed separately and has its own workflow.

Here are the steps:

  1. Start installing SQL Server 2014 and wait till you get the Error 997
  2. Once you see the Error dialog, click on OK to continue.
  3. Once the progress is complete, it returns to the status page showing the components failed and a link to log file at the bottomSQL Server 2014 Progress
  4. Open the log file, this log file will have information about the component specific log file, copy the path of the component log file, and open it again.Error Log
  5. Open the component log file, and search SourceHash, this hash is specific to the component which we need to update in the Windows Registry.Source Hash
  6. Copy the SourceHash along with flower braces ( { )Copy SourceHash
  7. Open regedit.exe from Windows Run.
  8. Locate the following section in the registry [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
  9. On the Edit menu, point to New, and then click DWORD Value.
  10. Type SecureRepairPolicy for the name of the DWORD, and then press Enter
  11. Right-click SecureRepairPolicy, and then click Modify.
  12. In the Value data box, type  2, and then click OK.
  13. On the Edit menu, point to New, and then click Key.
  14. Type SecureRepairWhitelist for the name of the key, and then press Enter.
  15. Double-click the SecureRepairWhitelist key to open it.
  16. On the Edit menu, point to New, and then click String Value. Create String Values that contain the SourceHash (including braces {}) of the component that have to be added to the Safe Recipients list.
  17. The NAME of the String Value is the {SourceHash value} and the VALUE can be left blank.Regedit InstallerRegedit SecureRepairWhitelist
  18. This children of Installer register should look similar to this. The above steps should be repeated for each component i.e., when ever you receive the Error 997.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer] “Logging”=”voicewarmupx”

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer\SecureRepairWhitelist] “{0EEBDCCA-EF5D-4896-9FEA-D7D410A57E8A}”=””


  1. Major thanks for the article. Really Great.

  2. “You have noted very interesting details! ps nice site.”

  3. new era beanies

    “Wonderful work! This is the type of info that should be shared around the internet. Shame on Google for not positioning this post higher! Come on over and visit my web site . Thanks =)”

  4. I really appreciate this post. I’ve been looking all over for this! Thank goodness I found it on Bing. You’ve made my day! Thanks again!

  5. My brother recommended I might like this website. He was totally right. This post truly made my day. You cann’t imagine simply how much time I had spent for this info! Thanks!

  6. Its like you read my thoughts! You appear to know so much approximately this, like you wrote the guide in it or something. I think that you can do with some percent to pressure the message home a little bit, however other than that, that is excellent blog. An excellent read. I’ll definitely be back.