You can resolve the problem by taking a backup of the build 2266 Symantec Ghost Console database, importing that backup into a build 2165 installation of Symantec Ghost Solution Suite, and then re-upgrading to build 2266.  The issue is typically resolved after installing the update a second time. 

Part 1:  Backing up the Symantec Ghost Console database:

1. Click Start.
2. Click Run.
3. Type Services.msc and click OK.
4. Locate the services that start with Symantec Ghost.  Right-click on the first Symantec Ghost service and stop it.  When you stop the first service, the second is typically automatically stopped as well.
5. Copy the following files/folders to a backup folder on your Symantec Ghost Server:
   • c:\Program Files\Symantec\Ghost\db
   • c:\Program Files\Symantec\Ghost\pubkey.crt
   • c:\Program Files\Symantec\Ghost\privkey.crt
6. Click Start > Run.
7. Type CMD and click OK.
8. When the command prompt opens, type these commands to change to the Symantec Ghost installation directory and to export the Symantec Ghost Console database credentials:
   • cd\
   • cd "Program Files\Symantec\Ghost"
   • ngserver -export
9. Close out of the command window.
10. Click Start > Run.
11. Type regedit and click OK.
12. Navigate to the following registry key:  HKEY_LOCAL_MACHINE\SOFTWARE\SYMANTEC\GHOST\NGSERVER
13. Right-click on the NGSERVER key and click Export.
14. Browse to your database backup folder, provide a filename, and click Save.

Once the backup has been captured, it is ready to be imported into a build 2165 version of Symantec Ghost Solution Suite.  In order to maintain customizations like driver template updates or custom copies of Windows PE on the original Symantec Ghost Server, Symantec recommends that you install the build 2165 version of Symantec Ghost Solution Suite on a separate computer.  You will fix the database in a clean installation of Symantec Ghost and then import the fixed database back into your original build 2266 version of Symantec Ghost Solution Suite.  This serves to fix the database corruption while still maintaining Symantec Ghost customizations that have already been made on the Symantec Ghost Server computer. 

Part 2:  Restoring the database backup in a build 2165 version of Symantec Ghost Solution Suite:

1. Click Start.
2. Click Run.
3. Type Services.msc and click OK.
4. Locate the services that start with Symantec Ghost.  Right-click on the first Symantec Ghost service and stop it.  When you stop the first service, the second is typically automatically stopped as well.
5. Copy the following set of files/folders from your Symantec Ghost database backup into C:\Program Files\Symantec\Ghost:
   • pubkey.crt [file]
   • privkey.crt [file]
   • db [folder]
6. Double-click on the REG backup key to import the database credentials into the registry. Click Yes first the first question that appears. Click OK on the second message.
7. Open the Symantec Ghost Console and verify that the database backup was successfully restored.
8. Click Help > Live Update.
9. Allow Live Update to download/install build 2266 again.
10. After Live Update has successfully upgraded your Symantec Ghost software to build 2266, open the Symantec Ghost Console.
11. Click Tools > Supported Sysprep Versions...
12. Verify that the previously missing entry for Windows 7 Sysprep is now present.
13. Close out of the Symantec Ghost Console.

Part 3:  Capturing a backup of the new, fixed Symantec Ghost Console database. Take the same steps that are listed in Part 1 above to capture a new database backup.

Part 4: Restoring the new fixed Symantec Ghost Console database to the original Symantec Ghost Server, already at build 2266. Take the same steps that are listed in Part 2 above to restore the new database backup to the original Symantec Ghost Console. 

Part 5:  Verification that the missing Windows 7 Sysprep entry was restored:

1. Open the Symantec Ghost Console.
2. Click Tools.
3. Click Supported Sysprep Versions...
4. Verify that Windows 7 Sysprep is listed.

If the missing Microsoft Windows 7 Sysprep entry is restored, you don't need to take any further steps.  If the missing Windows 7 Sysprep entry is still missing, please contact Symantec Technical Support for further assistance. Symantec Technical Support will need access to the database backup that you captured using the steps above.