Summary
List of possible causes and solutions for 1406 build time errors.Symptoms
At run time, the installation errors out with one of the following error messages:
- 'Error 1406: Could not write value Folders to key Software\Microsoft\Windows\CurrentVersion\Installer\InProgress. Verify that you have sufficient access to that key, or contact support personnel'.
- 'Error 1406: Could not write value VersionMajor to key HKEY_LOCAL_MACHINES\Software\Microsoft\Windows\CurrentVersion\Uninstall\{ProductCode}...'
- 'Error 1406: Could not write to Key HKEY_LOCAL_MACHINE\Software\Classes\CLSID\{<GUID>}\In ProcServer32...'
- 'Error - 1406: Could not write InstanceIndex to key...'
Note: The running installation's Product GUID replaces <PRODUCTCODE>. A class ID of a file in the installation that is causing the error message replaces <GUID>.
Cause
There are several different causes to this error message.
- Product Version of the setup is specified incorrectly: This error occurs when the Product Version field within Express contains an alphanumeric value. As per the Windows Installer Service requirement, the product version of setup packages should be a numeric value separated by periods.
- The format of the Product Version field is major.minor.build, e.g., 2.00.0000 is a valid product version; however, 2.00.beta is not a valid format as it contains alphanumeric values.
- Product version can be specified in an Express project in the Product Version field, under the Organize Your Setup / General Information section.
- The format of the Product Version field is major.minor.build, e.g., 2.00.0000 is a valid product version; however, 2.00.beta is not a valid format as it contains alphanumeric values.
- Insufficient privileges on the machine where setup is being run: Error 1406 normally occurs when the user does not have sufficient privileges to run the installation. Make sure that the user has administrative rights on the machine. If the user is not the administrator on the machine where the error occurs, make sure that the user running the installation does have elevated privileges.
- Setup is being run with an older version of the Windows Installer Service: If you are using a version prior to MSI 2.0 with your installation, then switch to MSI 2.0 or later as it has been known to fix this error in various cases.
- Setup contains many folders or folder names with long names: This error seems to mainly occur on Windows 95, 98, or ME systems. The error occurs if the setup has many folders created in the Files and Folders section. At build time, Express creates these folders in uppercase to ensure that they are public directories, which are accessible at different points in the installation by the Windows Installer Service. While this does not pose a problem on Windows NT systems, it causes Error 1406 on Win 9.X machines because of a registry size limitation. The registry size limitation on Windows 9.X machines is 16K, which causes Error 1406 when the Windows Installer Service attempts to store these folder paths in the registry. To resolve this behavior, shorten the names of all folders within the Files and Folders section of the Express IDE to less than 9 characters.
- Setup is creating a registry key under the HKEY_LOCAL_MACHINE hive: Make sure that your setup is not attempting to create a registry key directly under the HKEY_LOCAL_MACHINE hive, as the Windows NT system does not support this. The registry key can be created under the HKEY_LOCAL_MACHINE\Software hive. You can check this by going to Registry under the Configure The Target System section of Express 3.x IDE.
Additional Information
For more information on elevated privileges, refer to the following topics in the Windows Installer Help Library:
Also refer to Knowledge Base article listed below for additional information.
Was this helpful?
Related Articles
Windows Installer Error 1406 13Number of Views Windows Installer Error 1310 3Number of Views Windows Installer Error 1706 47Number of Views Windows Installer Error 2732 6Number of Views Windows Installer Error 2705 10Number of Views
Revenera Assistant - Beta
Online
Hi, I am Reva - Ask me anything.
Updates
No new updates
Chat
Home
Updates
/**/
Thanks for the feedback!
Your feedback has been saved.Rate this response:
1
2
3
4
5
Add Additional feedback ( Optional )
0/240
English
English
Language changed successfully
Something went wrong
Email sent successfully
Something went wrong
Case create successfully
Are you sure you want to cancel
the case creation?
Please select a product to submit the case.
Please select a product version to submit the case.
0/255
Upload Attachment
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to cancel the case creation?
Case closed successfully
File Upload
Maximum file size allowed is 3 MB.
File type not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
© 2026 Flexera Software. All Rights Reserved.
Case id: 00001065
Activity: Status change: 2 hours ago