Troubleshooting: Full Server (file system and registry) restores.

Microsoft (and most other software providers) install their programs, according to a certain methodology due to which a problem may occur if a computer's file system and Registry are restored.


When Microsoft (and most other software providers') software is installed on a computer, the Windows 8.3 filename is used in the Registry. Some programs make associations with the file extensions, thereby allowing the program to launch automatically when an associated file is double clicked.

Windows 8.3 filenames appear with first few characters of the long filename, followed by the tilde (~) and a number (e.g. MICROS~4). This method allows long file names to be limited to eight characters, while remaining unique.

The problem is that the Windows 8.3 name is assigned chronologically (i.e. based on the order in which program files were installed on the computer). However, when the DS-Client restores files, the Windows 8.3 name may be different because files can be restored in a different order than they were originally installed.

For example, the folder 'Microsoft Image Composer' might have originally had the 8.3 name 'MICROS~2' (since there may be several folders with long folder names, beginning with Microsoft). Upon restoration of the file system, it is possible that the 8.3 name could be something else (e.g. MICROS~5), depending on the order that it was restored to the computer by the DS-Client.

If such a problem exists on the restored computer, it will appear when you try to open a file by double clicking on it. You will get a "Program Not Found" error dialog, prompting you to specify the location of the program that will launch the selected file. (For more info see Microsoft Knowledge Base article 240240.)


We have a solution for this problem that is applied automatically for Windows. In the Program Not Found dialog, click Locate, and respecify the source program. The exact program name will be listed in the dialog. You can perform a filename search in the event you cannot remember where the source program is located.
If the work around does not resolve the issue, you may have to reinstall the failed program.