Blog
Document Security in Bluebeam Revu
Secure your PDFs with BlueBeam Revu's advanced security settings. Control access, require passwords, and manage permissions effortlessly. Discover more!
Install Failure: Error 997. Overlapped I/O Operation is in Progress
You are attempting to install Autodesk software and the install fails. During the install process you may receive the following error:
Error 997. Overlapped I/O operation is in progress.
When you look at the install log, you may see errors relating to SECREPAIR and SECUREREPAIR.
The entries in the install log will be similar to the following:
MSI (s) (D8:38) [14:20:10:710]: SECREPAIR: CryptAcquireContext succeeded
MSI (s) (08:A4) [14:22:31:690]: SECUREREPAIR: SecureRepair Failed. Error code: 35F03B34B8
Causes:
This is a known issue sometimes caused by the Microsoft security update KB2918614. This issue occurs because update 2918614 uses cryptographic keys and certificates for hashing the installation files together with the logged-in user profile. However, cryptographic keys and certificates cannot be used by mandatory or temporary user profiles. Therefore, when a user uses a mandatory or temporary user profile to install any MSI package, the MSI package installation fails and the error message returns.
Solution:
Solution #1 – Change the name of the following folder
- Rename the following folder:C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18
to
C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18_BAK - Try installing the Autodesk software again.
Solution #2 – Apply the following hotfix
Microsoft recommends applying a hotfix that addresses this issue.
See: The profile for the user is a temporary profile” error when you install an MSI package in Windows
Solution #3 – Remove the updates triggering the errors
- Go to Control Panel > Uninstall a program (or Programs and Features).
- In the left menu, click View installed updates.
- In the search box at the top-right, search for KB2918614.If you find it, uninstall it.
- Do another search for KB3072630, KB3000988 and KB3008627.If you find them, uninstall them as well.
- Reboot the computer and try installing the Autodesk software again.
Solution #4 – Edit the Registry
If the install still fails, add the product code of the product you are trying to install to the SecureRepairWhitelist in the Windows registry.
Warning! Use the Microsoft® Registry Editor only at your own risk and only after backing up the registry and the system.dat anduser.dat files, as outlined for your operating system in the Microsoft Knowledge Base and in How to back up the system registry . More information about the registry is available in Help topics in the Microsoft Registry Editor.
- Click Start, click Run, type Regedit in the Open box. Then click OK.
- Locate and then click the following subkey in the registry. (Create it if it doesn’t exist.)
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer - On the Edit menu, point to New, and then click DWORD Value.
- Type SecureRepairPolicy for the name of the DWORD, and then press Enter.
- Right-click SecureRepairPolicy, and then click Modify.
- In the Value data box, type 2, and then click OK.
- Locate and then click the following subkey in the registry:HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer
- On the Edit menu, point to New, and then click Key.
- Type SecureRepairWhitelist for the name of the key, and then press Enter.
- Double-click the SecureRepairWhitelist key to open it.
- On the Edit menu, point to New, and then click String Value. Create String Values that contain the product codes (including braces {}) of the products that have to be added to the Safe Recipients list.The NAME of the String Value is the “product code” and the VALUE can be left blank. To obtain the product code see How to Find the Product Code for an Autodesk Product.
- Close the Registry Editor and try installing the Autodesk software again.
NOTES: AutoCAD LT 2015 has 3 additional MSI entries that must be added to the security exceptions list: AutoCAD LT 2015 (acadlt.msi) , AutoCAD LT 2015 Language Pack (AcadltLP.msi) and AutoCAD 2015 PSP (AcadltPS.msi). Below is a registry key example that you can use to review to allow you to install AutoCAD LT 2015:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer\SecureRepairWhitelist]
“{5783F2D7-E009-0000-0102-0060B0CE6BBA}”=””
“{5783F2D7-E009-0409-1102-0060B0CE6BBA}”=””
“{5783F2D7-E009-0409-2102-0060B0CE6BBA}”=””
For ACAD LT 2016:
“{5783F2D7-F009-0000-0102-0060B0CE6BBA}”=””
“{5783F2D7-F009-0409-1102-0060B0CE6BBA}”=””
“{5783F2D7-F009-0409-2102-0060B0CE6BBA}”=””
For ACAD LT 2017
“{28B89EEF-0009-0000-0102-CF3F3A09B77D}”=””
“{28B89EEF-0009-0409-1102-CF3F3A09B77D}”=””
“{28B89EEF-0009-0409-2102-CF3F3A09B77D}”=””
For ACAD LT 2018
“{28B89EEF-1009-0000-0102-CF3F3A09B77D}”=””
“{28B89EEF-1009-0409-1102-CF3F3A09B77D}”=””
“{28B89EEF-1009-0409-2102-CF3F3A09B77D}”=””
For Revit LT 2016
“{941030D0-1600-0510-0000-818BB38A95FC}”=
“{7346B4A0-1600-0410-0000-705C0D862004}”=
“{0BB716E0-1400-0810-0000-097DC2F354DF}”=
“{0BB716E0-1600-0710-0000-097DC2F354DF}”=
For AutoCAD 2016
“{5783F2D7-F001-0000-0102-0060B0CE6BBA}”=
“{5783F2D7-F001-0000-3102-0060B0CE6BBA}”=
“{5783F2D7-F001-0409-1102-0060B0CE6BBA}”=
“{5783F2D7-F001-0409-2102-0060B0CE6BBA}”=
“{5783F2D7-F004-0000-5102-0060B0CE6BBA}”=
For AutoCAD 2017
“{28B89EEF-0001-0000-0102-CF3F3A09B77D}”=””
“{C0954809-F5DC-426C-847E-8409DE14E4C0}”=””
“{28B89EEF-0001-0000-3102-CF3F3A09B77D}”=””
“{28B89EEF-0004-0000-5102-CF3F3A09B77D}”=””
“{EB6FE58F-8576-4272-BB9C-6B47D9EDFA4D}”=””
“{28B89EEF-0001-0409-2102-CF3F3A09B77D}”=””
“{7592A2EC-0F9E-0401-B9BA-5E190481F49A}”=””
“{28B89EEF-0001-0409-1102-CF3F3A09B77D}”=””
“{5F0F7049-0000-1033-0102-73A6DA3D7FA6}”=””
For AutoCAD Architecture 2017 (include codes for AutoCAD 2017 above)
“{28B89EEF-0004-0000-0102-CF3F3A09B77D}”=””
“{28B89EEF-0004-0409-1102-CF3F3A09B77D}”=””
“{28B89EEF-0004-0409-2102-CF3F3A09B77D}”=””
“{28B89EEF-0004-0409-4102-CF3F3A09B77D}”=””
C++ Redist. 2005 to 2013
“{4B6C7001-C7D6-3710-913E-5BC23FCE91E6}”=””
“{5FCE6D76-F5DC-37AB-B2B8-22AB8CEDB1D4}”=””
“{1D8E6291-B0D5-35EC-8441-6616F567A0F7}”=””
“{CF2BEA3C-26EA-32F8-AA9B-331F7E34BA97}”=””
“{1F1C2DFC-2D24-3E06-BCB8-725134ADF989}”=””
“{9BE518E6-ECC6-35A9-88E4-87755C07200F}”=””
“{F0C3E5D1-1ADE-321E-8167-68EF0DE699A5}”=””
“{BD95A8CD-1D9F-35AD-981A-3E7925026EBB}”=””
“{52B37EC7-D836-0410-0464-3C24BCED2010}”=””
“{57E92DED-DC7C-41E5-B9E1-76D83BD2EABE}”=””
“{8C5F38D2-9EFE-49A4-B3F5-BF3210FED168}”=””
“{8C5F38D2-9EFE-49A4-B3F5-BF3210FED168}”=””
“{E0820BD5-930B-43EC-A3C1-2634D38A1931}”=””
“{9167CA34-4E58-49E3-8892-3C439739D2D3}”=””
“{0BB716E0-1600-0610-0000-097DC2F354DF}”=””
“{7A12802C-4864-423D-9732-3A22577CE006}”=””
“{B33F7E81-3398-4FC5-B947-C5989A103D91}”=””
“{3905B678-DC8D-4D5E-AA95-EA254D6C1239}”=””
“{06EC8EFF-0768-4D06-AAAE-DCBE7DC63B0D}”=””
“{D0F82C64-3E66-4B12-B12C-3F79C0F731C1}”=””
“{7592A2EC-0F9E-0301-B9BA-5E190481F49A}”=””
“{F6FD1651-0000-1033-0102-387BAF9B3B0A}”=””
“{EEB8F213-FF32-470F-B409-47DC28E658FF}”=””
Final solution:
If the above steps fail, remove KB3072630. Also remove other windows hotfixes, which were installed around the same time as KB3072630 or contact our Technical Support Team by clicking here.
