| Previous | Next |
| ERROR_DATATYPE_MISMATCH | ERROR_CREATE_FAILED |
ERROR_UNSUPPORTED_TYPE
The requested Windows Installer data type is not supported.
ERROR_UNSUPPORTED_TYPE is Win32 error 1630 (0x65E). Unlike a simple mismatch between a known type and a field, this result indicates that the operation cannot handle the type presented at all. It can expose invalid package schema, an unsupported record representation, a custom table convention used with a standard API, or an interop layer that invents a type code Windows Installer does not recognize.
Where unsupported types appear
- a package generator emits a column definition outside MSI database rules
- an API caller selects a record or summary-information type not accepted by that function
- a transform introduces a stream or object where only standard scalar data is allowed
- automation marshaling produces an unsupported variant or pointer representation
- a newer authoring tool creates data for an older installer engine or API path
Useful evidence
Record the function, type identifier, target table or property, package schema, Windows Installer version, authoring-tool version, transform list, and runtime language binding. Preserve the package and transform hashes. If the type originates from external metadata, capture the parser’s normalized type name before it is converted to an MSI value.
How to investigate
Check the official contract for the exact MSI function and the database column-definition grammar. Open the final built package after all transforms and patches are considered. Compare behavior on the minimum supported Windows Installer version; an authoring tool’s acceptance does not guarantee the runtime engine supports the representation.
For COM or scripting clients, call a minimal test with an explicitly typed value. Review wrapper declarations and enum mappings. If only one machine fails, verify that the same package and installer engine are used rather than immediately changing package data.
Resolution
Convert the data to a supported MSI type or redesign the custom data exchange outside the MSI database. Do not encode arbitrary objects into standard fields and expect implicit conversion. Package validation and compatibility testing should run against the oldest supported installer environment before release.
Difference from datatype mismatch
ERROR_DATATYPE_MISMATCH says a supported type was supplied to the wrong destination. Error 1630 says the operation does not support that type. The first can often be fixed by selecting the correct setter; the second may require changing the package model.
Example
A build plug-in writes a custom object-valued column into an MSI table accepted by its in-memory model. Windows Installer later rejects the record with 1630. Serializing the metadata into a documented string field used only by the custom action restores compatibility.
References
- Microsoft: Windows Installer error codes
- Microsoft: Windows Installer database tables
- Microsoft: MSI column definition format
Looking for a different code? Search another status or error code.