Additional release information for Windows Server 2008 Foundation

Applies To: Windows Server 2008 Foundation

Windows Server 2008 Foundation does not support the use of language packs

The end user license agreement (EULA) for Windows Server 2008 Foundation does not permit you to download language packs from the Microsoft Web site to install on Windows Server 2008 Foundation. Installing a language pack on Windows Server 2008 Foundation causes the branding images to be rendered incorrectly and may result in other unknown problems. If you installed a language pack on Windows Server 2008 Foundation, uninstall it.

To uninstall a language pack

  1. Open Control Panel, and then double-click Regional and Language Options.

  2. On the Keyboards and Languages tab, click Install/uninstall languages.

  3. On the User Account Control page, click Continue.

  4. In the Install or Uninstall Display Languages Wizard, click Remove languages.

  5. Select the languages that you want to remove, and then click Next.

  6. Follow the instructions to finish the wizard.

  7. If prompted, restart the server.

An invalid task appears in Task Scheduler

After you install Windows Server 2008 Foundation, a task named MP Scheduled Scan appears in the Task Scheduler console tree, even though the associated feature is not installed. The task does not affect server licensing or product functionality. However, when the task runs as scheduled, it cannot locate the associated files, so it logs an error in the event log. Microsoft plans to correct this issue in a future release.

Windows Software Licensing Manager displays “ServerSBSPrime” as the server edition

When you run the Windows Software Licensing Manager tool from a command prompt, a dialog box appears and specifies that the operating system and edition installed on the computer is Windows Server ®, ServerSBSPrime edition. The fact that the edition does not refer to Windows Server 2008 Foundation does not interfere with server licensing or product functionality. Microsoft plans to correct this issue in a future release.