How can I avoid error 1631 on Windows NT systems?
How can I avoid error 1631 on Windows NT systems?
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
bkelly
20 years ago
On Windows NT systems, Userenv.dll may return an error message when it tries to process the value, and Windows Installer quits.
The following example shows a null value:
Registry Path:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
Value Name: CLASSPATH
Data Type: REG_EXPAND_SZ
String:
(String value is empty)
To work around this behavior, remove null environment variables before you install the program. Removing the variable "could" cause problems. There is a fix available from Microsoft, but you need to request it. Details may be found here.
The following example shows a null value:
Registry Path:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
Value Name: CLASSPATH
Data Type: REG_EXPAND_SZ
String:
(String value is empty)
To work around this behavior, remove null environment variables before you install the program. Removing the variable "could" cause problems. There is a fix available from Microsoft, but you need to request it. Details may be found here.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.