Missing Data or Program Settings After You Upgrade to Windows XP

Support for Windows XP has ended

Microsoft ended support for Windows XP on April 8, 2014. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article was previously published under Q314931
This article has been archived. It is offered "as is" and will no longer be updated.
When you try to upgrade your operating system to Windows XP, Setup may stop responding (hang) or encounter an error while finalizing settings. In Task Manager, Svchost.exe may appear not to respond. When Windows starts, data may be missing or you may not be able to access data that is stored in your user profile folder. This data may include Start menu shortcuts, items in the Startup group, items in your Desktop folder, e-mail messages, or documents, pictures, or music files that are stored in the My Documents folder.
This problem occurs if you had files that were stored in a folder structure that exceeded MAX_PATH (256 characters) before you upgraded to Windows XP.
Click Yes, download the updated Setup files (Recommended) in the Get Updated Setup Files dialog box during Setup. After Setup is complete, you may need to rename files (or folders) that you cannot access because the folder structure exceeds MAX_PATH (256 characters).

To work around this problem, press SHIFT+F10 and XCOPY User~tmp.@01 to a safe location before you restart your computer and then continue Setup.

After Setup is complete, try to search for missing data files by using the first part of the file name. Data files that were stored in a deep path may have truncated file names or no file extensions. For example, "March Sales Forecast.doc" may have been truncated to "March Sales Fore" (with no file extension).

If you cannot find your data files that have truncated file names, restore missing data from a backup.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
maximum path limitation too long

Article ID: 314931 - Last Review: 01/12/2015 19:30:27 - Revision: 2.2

Microsoft Windows XP Home Edition, Microsoft Windows XP Professional

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