text: Release notes for Microsoft Windows Code Named "Longhorn" preview release
  This article discusses a preview release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.
  No formal product support is available from Microsoft for this pre-release product. For information about how to obtain support for this preview release, see the documentation that is included with the preview product files.
  SUMMARY
  These release notes contain important information that was not available when the product documentation for Microsoft Windows Code-Named "Longhorn" was written.
  Unless stated otherwise, all information included here applies to Microsoft Windows Code-Named "Longhorn," Microsoft Windows Code-Named "Longhorn" for Itanium-based systems, and Microsoft Windows Code-Named "Longhorn" for 64-bit extended systems.
  How to use these notes
  Microsoft recommends that you check whether any of these notes apply to your specific setup. Click the topics to verify whether there is any important information that might apply.
  MORE INFORMATION
  General
  ? This pre-release product uses product activation technology. You must activate your copy of "Longhorn" within 14 days of installation. You have been provided with a product key that permits 31 activations. All activations will expire after 365 days. After expiration, you cannot log on to this pre-release product.
  ? This pre-release product cannot be used to upgrade any version of Windows, including "Longhorn." Additionally, this pre-release product cannot be upgraded to any other versions of Windows, including "Longhorn."
  ? Write support is turned off for Universal Disk Format (UDF) media types (writable CDs and writable DVDs) in the "Longhorn" Shell. Therefore, entry points for CD writing (such as the CD Writing Wizard and the Copy to Audio CD task) are not available in the "Longhorn" Shell. To turn on write support (for example, to turn on Format and Close Session) for UDF media types in the "Longhorn" Shell, set the DisableUDFWritesInShell DWORD value to 0 in the following registry key:
  HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Explorer\CD Burning
  ? Data corruption may occur when you write to a CD-R, DVD-R, or DVD+R disc.
  ? The following media types and UDF versions are supported for the various UDF-related tasks in the "Longhorn" Shell: ? All writable CD and DVD media types are supported.
  ? Format.com and Chkdsk.exe support UDF versions 2.00, 2.01, and 2.50.
  ? The file system supports reading and writing UDF versions 1.02, 1.50, 2.00, and 2.01.
  ? The extensions to Microsoft Windows XP CD writing capabilities do not work in this pre-release product, and the "Longhorn" extensions for CD writing capabilities are not yet implemented. For additional information about extensions to Windows XP CD writing capabilities, visit the following Microsoft Web site:
  ? Data corruption and other errors (such as an unsuccessful format error) may occur when you format or write to a recordable CD or DVD disc. To work around this problem, stop the IMAPI CD-Burning Component Object Model (COM) service when you format or write to a CD or DVD disc. To prevent the IMAPI CD-Burning COM service from starting automatically, set the startup type to Disabled. To stop or disable the IMAPI CD-Burning COM Service, follow these steps: 1. In Control Panel, open Performance and Maintenance.
  2. Click Administrative Tools, and then open Computer Management.
  3. Under Services and Applications, click Services.
  4. Right-click IMAPI CD-Burning COM Service, and then click Properties.
  5. Click Stop to stop the service. If you want to prevent the service from starting automatically, click Disabled for Startup type.
  ? When you click Start, and then click Help and Support, nothing occurs. For this pre-release product, the Help and Support Center does not function.
  ? Windows File Protection (WFP) has been disabled for this pre-release product. This means WFP cannot help to protect the critical Windows system files on the WFP list, and the SfcGetNextProtectedFile and SfcIsFileProtected application programming interfaces (APIs) are not supported in this pre-release product. As a result of the lack of WFP, applications can replace critical Windows system files. For additional information about WFP, click the following article number to view the article in the Microsoft Knowledge Base:
  222193 Description of the Windows File Protection Feature
  Note WFP is being replaced by Windows Resource Protection. This feature will be included with the final release of "Longhorn."
  ? You may not be able to schedule tasks in Task Scheduler. This problem occurs if you are not an administrator. Only an administrator can schedule tasks. However, an administrator can schedule tasks to run as any other user. If a password is not specified for the other user, the task can access local computer resources only and will not be able to access network resources. If a valid password is supplied for the other user, the task can access any network resources that are accessible to the other user.
  ? Scheduled tasks may not run. This problem occurs if a task is scheduled to start 30 days or more in the future. When you restart your computer, this 30 day clock is reset. Therefore, all tasks will run if you restart your computer at least one time every 30 days.
  ? Scheduled tasks are run in isolated sessions in the context of a specific user and can be run in either interactive or non-interactive mode. The Task Scheduler service will run all tasks for a specific user's context in the mode that is specified by the first task that is run. Settings for interactive or non-interactive mode on subsequent tasks are ignored.
  ? Contacts scenarios do not work in "Longhorn" for Itanium-based Systems and "Longhorn" for 64-bit Extended Systems.
  ? Keyboard accessibility is limited or does not exist for many contacts scenarios.
  ? For this pre-release product, Microsoft Outlook Express 7 is not enabled on "Longhorn" for Itanium-based Systems or on "Longhorn" for 64-Bit Extended Systems.
  ? You must be logged on as an administrator on your local computer to use Outlook Express 7.
  ? Incoming Internet Message Access Protocol (IMAP) messages are not automatically shown in the message list in Outlook Express 7. To work around this problem, update the message list. To do this, click another folder, and then click the Inbox folder.
  ? The following features are not enabled in Outlook Express 7: ? Work Offline
  ? Secure Mail (S/MIME)
  ? Import or export of mail messages
  ? HTTP Mail server support
  ? BCC
  ? Find messages
  ? You must be a member of the Administrators group to use Search.
  ? It may take up to an hour for Help content to be indexed for search. Therefore, you may not be able to search Help content for up to one hour after you install "Longhorn" and restart your computer. If you restart your computer before Help indexing is complete, some topics may be excluded from your search. After Setup is complete and an administrator logs on, do not restart your computer for one hour to permit full indexing to complete.
  ? To search multiple disks (volumes), the searched volumes must use the NTFS file system.
  Hardware
  Your computer may automatically restart and you may receive the following serious error after you log on to a Dell computer (for example, a Dell 450, 530, or 650) that uses an ATI Radeon video adapter (for example, the Radeon 7000, 9600, 9700, or 9800):
  STOP 0x000000EA: THREAD_STUCK_IN_DEVICE_DRIVER
  To work around this problem, update your computer basic input/output system (BIOS). For information about how to update your BIOS, see the following Dell Web sites:
  Software applications
  ? Your computer may stop responding when you quit the "Surfin" demo program from the "Longhorn" CD. This problem occurs on computers that use the ATI Radeon 7000, 8500, or 9000 video adapters. Updated drivers from ATI will be available in the next public release of "Longhorn."
  ? Your computer may stop responding when you run Microsoft Money versions 2002, 2003, or 2004.
  ? You may receive an access violation when you select an animation design in Microsoft Picture it! Publishing 2002.
  ? When you install Adobe Acrobat 6.0 Professional or Standard, you may receive error messages that are similar to the following:
  Adobe Acrobat 6.0 Professional Installer Information
  Warning 20225. Adobe Acrobat 6.0 Setup was unable to create a new item: Adobe PDF Converter. The Adobe PDF Printer may be unavailable.
  GetLastError: The parameter is incorrect.
  Adobe Acrobat 6.0 Professional Installer Information
  Warning 20225. Adobe Acrobat 6.0 Setup was unable to create a new item: Adobe PDF. The Adobe PDF Printer may be unavailable.
  GetLastError: The parameter is incorrect.
  After you receive these error messages, the Adobe PDF Printer is unavailable. By using Adobe PDF Printer, you can convert documents to Adobe PDF format by printing to the Adobe PDF Printer from the program that you use to create the document.
  This issue occurs because Adobe Acrobat 6.0 Professional and Standard Setup look for an earlier version of Windows and do not install correctly when the earlier version of Windows is not detected.
  To work around this problem, use Print, Print to File, or Save As on the File menu to save a PostScript (.ps) file by using an installed PostScript printer. Then open the PostScript (.ps) file in Adobe Acrobat Distiller to create the Adobe PDF file.
  Note The PDF files that you create in this way are black and white.
  For additional information about Adobe Acrobat 6.0 Professional and Standard, visit the following Adobe Web site:
  ? Printing on AMD64-based computers is not yet functional.
  ? When you use Outlook Express to send a new fax, only one page of text is sent as part of the coversheet. Coversheet text that not does fit on a single coversheet page will not be sent with the fax. This does not affect attachments to the fax.
  Network and communications
  ? The TCP/IP stack has been completely rewritten for "Longhorn." There are some limitations in this release: ? TCP Large Send offload & Checksum offload is temporarily disabled regardless of the offload capabilities of your network adapter.
  ? The Packet Scheduler (Psched) is on but will not shape traffic flows.
  ? Domain Name Service (DNS) netsh commands are not yet available.
  ? Teredo (IPv6 NAT traversal technology) is not yet available for the "Longhorn" TCP/IP stack.
  ? By default, Internet Protocol Version 6 (IPv6) Inter-Site Automatic Tunnel Addressing Protocol (ISATAP) and 6to4 support is not enabled. Additionally, off-subnet IPv4 static routes are not handled correctly and must be manually added by using the netsh command after your computer starts. You can use default IPv4 routes to off-subnet addresses by manually adding the route. To do this, use the netsh command after your computer starts. Microsoft recommends that you stop the SharedAccess service if you plan to use ISATAP or 6to4. Additionally, the 6to4 service must be started to use 6to4.
  ? By default, Internet Connection Firewall (ICF) is turned on for all network interfaces. By default, ICF permits all outbound network traffic, but unsolicited inbound network connections are blocked. Therefore, your computer cannot act as a server unless you configure the firewall to open the required ports for the appropriate services or applications. For example, file or print sharing requires TCP ports 139 and 445, and User Datagram Protocol (UDP) ports 137, 138, and 445 to be open. To open ports in ICF, follow these steps: 1. In Control Panel, open Network and Internet Connections.
  2. Click Network Connections.
  3. Right-click the connection where you want to open ports, and then click Properties.
  4. On the Advanced tab, click Settings., typically it is best to use the IP address 127.0.0.1.
  8. In the External port and Internal port boxes, type the port number. Generally this number is the same for both boxes. For example, type 445 in both boxes.
  9. Click either TCP or UDP, and then click OK.
  10. Repeat this process for each port to be opened.
  ? ICF does not block or filter IPv6 network traffic in this pre-release product. IPv6 filtering will be enabled in a future release of "Longhorn."
  ? ICF is not available on "Longhorn" for Itanium-based Systems and "Longhorn" for 64-bit Extended Systems. This issue will be addressed in a future release of "Longhorn."
  ? ICF does not prevent instant messaging with Microsoft MSN Messenger or Microsoft Windows Messenger, but other Messenger features may be affected. For example, voice and video features work for administrators only. Additionally, File Transfer is blocked for all users. These issues will be addressed in a future release of "Longhorn."
  ? When ICF is turned on, H.323/LDAP proxy functionality is not supported in this release of "Longhorn." Therefore, Microsoft Windows NetMeeting may not work.
  ? When ICF is turned on, you cannot run a File Transfer Protocol (FTP) client in active mode or host an FTP server in passive mode. This will be addressed in a future release of "Longhorn."
  ? When ICF is turned on, you will not automatically receive notifications of new e-mail messages in Outlook 2002. This will be addressed in a future release of "Longhorn." To work around this problem, click Send/Receive (or press F5) to look for new e-mail or to turn on polling mode by editing the registry. For additional information about how to turn on polling mode in the registry, click the following article number to view the article in the Microsoft Knowledge Base:
  305572 OL2002: You Cannot Receive New E-mail Notifications in Environments That Use the Network Address Translation
  ? When you sign in to both MSN and Window Messenger by using four different accounts on two computers, Remote Access does not work from one computer to the other.
  Security and privacy
  ? To obtain security patches for this pre-release product, visit the following Microsoft Web site:
  ? When you install this pre-release product for x86 systems, Windows Setup will assign a blank (or null) password to the administrator account. Although you can log on locally with this account, the administrator account and any other local user accounts that have blank passwords cannot be accessed by a remote user through a network connection to your computer. This helps to protect your computer from attacks over the network. To help make local access to your computer secure, set a password on the local administrator account and any other user accounts. To do this, open User Accounts in Control Panel. Microsoft recommends that you set a strong password. For information about strong passwords, visit the following Microsoft Web site:
  ? Multiple Outlook Express 7 users on the same computer can see each other's e-mail messages.
  ? For this pre-release product, Microsoft's Next-Generation Secure Computing Base (NGSCB) emulation will not work on multi-processor computers or on 64-bit computers. You must use a single-processor, 32-bit computer to use NGSCB emulation. For additional information about NGSCB, visit the following Microsoft Web site:
  ? For this pre-release product, NGSCB emulation will not run if you use the /3GB or /PAE switches in your Boot.ini file. That is, providing 3 gigabytes (GB) of memory for applications or enabling "36-bit" addresses by using Physical Address Extension prevents the NGSCB emulator from starting. To work around this problem, remove the /3GB and /PAE switches from your Boot.ini file.
  ? Interrupting NGSCB configuration can result in inaccessible devices. When you configure NGSCB on your computer, the Configuration tool (Ngconfig.exe) catalogs all the Universal Serial Bus (USB) devices that are on the computer. This process can take up to 5 minutes. If this process is interrupted by starting the NGSCB services from the command line, any devices that are currently being configured (and any devices that are waiting to be configured) may not respond. If you have problems using USB devices under NGSCB, restart your computer, clear the current NGSCB configuration (by running Ngconfig /clear), and then reconfigure your computer for NGSCB (by running Ngconfig /config). Wait until all New Hardware Device Found dialogs are complete, and then start the NGSCB emulation (by running Ngconfig /start).
  ? Managed code applications that use the new Windows Management Instrumentation (WMI) model should not expose security sensitive state or methods whose execution can cause damaging effects on the computer. Additionally, clients should not call WMI probes of applications that are not trusted because WMI probes impersonate the calling client.
  Administration
  ? When you use Wmimgen.exe version 1.0, you may receive the following error message:
  Warning:
  [MyAssembly, Version=1.0.1.0, Culture=en-US, PublicKeyToken=50853b6922572178:]
  Note You may receive this message even if the assembly contains instrumentation attributes.
  Additionally, an empty manifest may be created. To work around this problem, make sure the assembly is not being loaded from a network drive or from a share. You must also make sure that WMI can create an instance of the class in the assembly by placing the Probe attribute on either a constructor or a static accessor.
  ? When you use the /set switch or the /invoke switch with Wmicmd.exe version 1.0, you may receive the following error message:
  Value cannot be null.
  Parameter name: s
  You can ignore this error message. The value is correctly modified by the /set switch. To verify that the value is modified, use the /get switch on the corresponding Uniform Resource Identifier (URI).
  ? When you use the /get switch with Wmicmd.exe version 1.0 to retrieve a probe from a running program or service, you may receive the following error message even if the URI is defined in the catalog:
  IPC call failed:IpcFailure
  The attributed code that implements the probe may throw an exception, but Wmicmd.exe does not report the exception to the console. Make sure that the code is functioning correctly. The probe may be returning an array of complex objects that are not serializable. For example, you may experience this problem if the probe uses the following pattern to return an array of instances of the class MyObject from a collection object: [Probe(ResultType=typeof(MyObject))]
  public object[] GetArray() {
  return contents.ToArray();
  }
  To work around this issue, create a wrapper object as follows: [Probe]
  public ArrayObject GetArray() {
  return new ArrayObject(contents.ToArray());
  }
  [XmlInclude(typeof(MyObject))]
  public class ArrayObject {
  public object [] data;
  public ArrayObject () {}
  public ArraryObject (object [] data) {this.data = data;}
  } you use the /get switch with Wmicmd.exe version 1.0 to retrieve a probe, you may receive the following error message even if the URI is defined in the catalog:
  The specified URI cannot be found/reached
  The attributed code that implements the probe may have thrown an exception, but Wmicmd.exe does not report the exception to the console. Make sure that your code is functioning correctly.
  ? When you use the /get switch with Wmicmd.exe version 1.0, a non-empty list of instance IDs may be returned even if no instances are currently running when you use the enumerator URI (such as #System/MyApp/MyId=*). This behavior occurs when an instance of attributed program did not shut down correctly and was not able to call System.Management.Instrumentation.Application.Unre gister(). To work around this issue, delete the subkeys for the program from the following registry key:
  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\Instrum entation\ApplicationROT
  Software development
  ? You cannot install Microsoft Visual Studio 6.0 and Microsoft Visual Java ++ 6.0. This issue occurs because Visual Studio 6.0 and Visual Java ++ 6.0 look for a Windows version that is equal to Windows XP.
  To install Visual Studio 6.0 from a CD-ROM, follow these steps: 1. In Windows Explorer, locate Setup.exe on Disk 1 of the Visual Studio 6.0 CD-ROM disk set.
  2. Right-click Setup.exe, and then click Properties.
  3. Click Other properties, and then click Compatibility.
  4. Click Run this program in compatibility mode for, and then click Windows XP.
  5. Click OK.
  6. Run Setup.exe.
  To install Visual Studio 6.0 from a network share, follow these steps: 1. Download the Application Compatibility Toolkit (CompatAdmin). To do this, visit the following Microsoft Web site:
  2. Install the toolkit. You only have to install the Microsoft Compatibility Administrator 3.0.
  3. Run the Compatibility Administrator Tool (Compatadmin.exe).
  4. On the Database menu, point to Create new, and then click Application Fix.
  5. In the Name of the program to be fixed box, type Visual Studio 6.0.
  6. In the Name of the vendor for this program box, type Microsoft.
  7. Click Browse, and then locate and double-click Setup.exe on Disk 1 of the Visual Studio 6.0 CD-ROM disk set.
  8. Click Next, and make sure that Operating System Modes is set to None.
  9. Click Next, click to select the PropogateProcessHistory check box, and then click to select the WinXPVersionLie check box.
  10. Click Next, and then click Finish.
  11. Run Setup.exe.
  12. To remove the custom database, use the appropriate entry in Add or Remove Programs in Control Panel.
  ? When you run Visual Studio code that calls the Contact Picker dialog box, you receive the following error message:
  Runtime Error!
  Program: This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.
  To work around this problem, follow these steps: 1. Create the following registry key:
  HKEY_LOCAL_MACHINE\Software\Microsoft\Visual Studio\8.0\vsproject
  2. In this key, create a DisableHostingProcess string value and set its value data to 1.
  ? You receive a build error when you try to build a project that calls the TrustComputeDigest function from C++ source code. To work around this problem, move the TrustComputeDigest function call to a file that has a .c extension or rename the C++ (.cpp) file that has a .c file name extension. To do this, right-click the file in the Solution Explorer window in Visual Studio, rename the file name extension from cpp to c, and then rebuild your project. C++ callers will be supported in a future release of "Longhorn."
  ? Unhandled managed exceptions are not reported to the debugger in mixed (interop) debugging mode. For example, when the following C# program is debugged in mixed (interop) debugging mode with Visual Studio, the debugger is not notified that an unhandled exception is hit
  ublic class bugublic class bug
  {
  public static void Main(string[] args)
  {
  throw new System.Exception();
  }
  } this issue occurs, the debugging session quits, and the debugger output window contains text indicating the program has exited. This issue occurs in the following scenarios: ? You run your debugger on "Longhorn" and debug, in mixed mode, a program running on the same computer.
  ? You run your debugger on another operating system and remotely debug, in mixed mode, a program running on "Longhorn."
  Note If you debug the same program on another Windows operating system the debugger correctly stops and reports that an unhandled exception is thrown. Additionally, unhandled native exceptions are correctly reported to the debugger when you debug a program running on "Longhorn.".
  This issue will be fixed in the Common Language Runtime (CLR) included with later versions of "Longhorn." To work around this issue, use the appropriate method:
  Method 1: Run the debugger in native, or managed only, mode
  If mixed (interop) debugging is not needed, run the debugger in managed only or native debugging mode. Native and managed only debugging modes correctly report unhandled exceptions on "Longhorn."
  Method 2: Enable breaking into the debugger when managed exceptions are thrown
  If mixed (interop) debugging is necessary, enable breaking into the debugger when managed exceptions are thrown. When an exception is thrown in the program the debugger gets notified and a ?1st chance exception? dialog will be displayed. You can then break into the program. The "1st chance exception" dialog will be correctly displayed for all exceptions thrown in a program. You must manually detect if the exception will be handled or not by looking at the source code of the program. If the managed exception will not be handled and you continue execution, then the debugging session will stop. If the exception will be handled, program execution continues. To enable breaking into debugger on "1st chance exceptions" with Visual Studio, follow these steps: 1. Start debugging your program.
  2. Click Debug, and then click Exceptions.
  3. In the Exceptions dialog box, click to select the Common Language Runtime Exceptions check box to stop the debugger when a managed exception is thrown..
  Bookmarks