INI/CFG Files Corruption Issue with Windows NT 4.0, Terminal Server Edition

This article was previously published under Q180163
This article has been archived. It is offered "as is" and will no longer be updated.
When a user application is installed using the Add/Remove Programs tool in Control Panel, the application-specific INI and CFG files are copied to the Windows folder.

If the application is installed using the "All users begin with common application settings" option the application-specific INI and/or CFG files are propagated to each user's personal Windows folder (%SystemRoot%\Profiles\user name\Windows).

If any of the INI or CFG files have a line containing more than 512 characters, the files may not be copied correctly, resulting in the destination files containing corrupted data. When this happens, the application works as normal in Install mode (change user /install) but may not work correctly in Execute (default) mode.
Terminal Server does not properly handle a line having more than 512 characters in INI and CFG files. The designed limit for line length is 1,024 characters.
To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

Microsoft has confirmed that this is a problem in Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

Article ID: 180163 - Last Review: 10/07/2013 17:46:23 - Revision: 2.1

Microsoft Windows NT Server 4.0, Terminal Server Edition

  • kbnosurvey kbarchive kbbug kbfix kbqfe KB180163
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)