You cannot use the IPv6 protocol to connect to the remote VDS on a Windows Vista Service Pack 1-based computer from a Windows Server 2008-based computer

Symptoms
Consider the following scenario:You try to connect to the remote Virtual Disk Service (VDS)on a Windows VistaService Pack 1 (SP1)-based computerfrom a Windows Server 2008-based computer.Both computers are located on a domain that is managed by a Windows Server 2003 R2-based domain controller.You use an Internet Protocol version 6 (IPv6) address to connect.You use the Windows Server 2008 Disk Management UI to connect to VDS.You enable a single exception in the firewall settings of both the Windows Vista SP1-based computer and the Windows Server 2008-based computer. The exception is as follows:
Remote Volume Management Exception In this scenario, the connection fails. Additionally, you receive the following error message in the Disk Management console:

Disk Management could not start Virtual Disk service (VDS) on 2001:4898:1000:412E:D7D1:DF52:9F83. This can happen if the remote computer does not support VDS, or if a connection cannot be established because it was blocked by Windows Firewall.
For additional information about diagnosing and correcting this problem, see Troubleshooting Disk Management in Disk Management Help.Note You can connect to the remote VDS by using a NetBIOS name, a DNS name, or an IPv4 address.
Resolution
This issue is specific to a domain that is managed by a Windows Server 2003 R2-based domain controller. If you have a Windows Vista SP1 computer and a Windows Server 2008 computer in a domain that is managed by aWindows Server 2008-based domain controller, you do not receive the error message that is mentioned in the “Symptoms” section.

Write protection does not always work on SD memory cards that are plugged into a computer that runs Windows XP, Windows Vista, or Windows Server 2008

Symptoms
Your computer runs Windows XP, Windows Vista, or Windows Server 2008. You plugged a Secure Digital (SD) memory card into the computer while the write protection on the SD memory card was turned off. Then, you put the computer to sleep or in hibernation. When the computer was asleep or in hibernation, you turned on the write protection on the SD memory card. Finally, you resumed the computer, and then you tried to write to the SD memory card.
When you tried to write to the SD memory card, you experienced one of the following issues:The write operation was committed on the SD memory card instead of being prevented by the write protection.Therefore, you may have overwritten the data on the SD memory card unexpectedly.You received a warning, and therefore expected that the operation would be canceled. However, the operation seemed to be successful. When you tried to access the newly written data, however, you received an error message that reportedthat the disk is corrupted.To fix this problem, you can either download a hotfix or you can do a workaround. To download the hotfix, see the “Resolution” section. To run the workaround, see the “Workaround” section.
Resolution
This problem occurs because some incorrect parameters are written into the registry when the Sdbus.sys driver initializes.
Hotfix informationWindows XP A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or tocreate a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support(http://support.microsoft.com/contactus/?ws=support)Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.Prerequisites To apply this hotfix on a Windows XP-based computer, you must have Windows XP Service Pack 2 or Windows XP Service Pack 3 installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
322389?(http://support.microsoft.com/kb/322389/) How to obtain the latest Windows XP service packRestart requirement You must restart the computer after you apply this hotfix. Hotfix replacement information This hotfix does not replace any other hotfixes. File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows XP with Service Pack 2, x86-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementSdbus.sys6.0.4069.349379,36015-Dec-200810:22x86SP2Sffdisk.sys6.0.4069.349313,82415-Dec-200810:14x86SP2Sffp_mmc.sys6.0.4069.349310,24015-Dec-200810:14x86SP2Sffp_sd.sys6.0.4069.349311,52015-Dec-200810:14x86SP2Sdbus.infNot Applicable3,70115-Dec-200808:17Not ApplicableSP2Sffdisk.infNot Applicable4,43315-Dec-200808:17Not ApplicableSP2Sdbus.infNot Applicable3,70115-Dec-200808:17Not ApplicableSP2Sffdisk.infNot Applicable4,43315-Dec-200808:17Not ApplicableSP2Windows XP with Service Pack 3, x86-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementSdbus.infNot Applicable3,66215-Dec-200809:06Not ApplicableSP3Sdbus.infNot Applicable3,66215-Dec-200809:06Not ApplicableSP3Windows Vista and Windows Server 2008Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support(http://support.microsoft.com/contactus/?ws=support)Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.Prerequisites To apply this hotfix on a Windows Vista-based computer, you must have Windows Vista Service Pack 1 installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
935791?(http://support.microsoft.com/kb/935791/) How to obtain the latest Windows Vista service pack No prerequisites are required for Windows Server 2008-based computers. Restart requirementYou must restart the computer after you apply this hotfix. Hotfix replacement information This hotfix does not replace any other hotfixes. File information The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Windows Vista and Windows Server 2008 file information notesThe files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Collapse this tableExpand this table
VersionProductMilestoneService branch6.0.6000.16xxxWindows VistaRTMGDR6.0.6000.20xxxWindows VistaRTMLDR6.0.6001.18xxxWindows Vista SP1 and Windows Server 2008 SP1SP1GDR6.0.6001.22xxxWindows Vista SP1 and Windows Server 2008 SP1SP1LDRService Pack 1 is integrated into Windows Server 2008.The MANIFEST files (.manifest) and MUM files (.mum) installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.For all supported x86-based versions of Windows Server 2008 and Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSdbus.infNot Applicable7,98011-Nov-200823:34Not ApplicableSdbus.sys6.0.6001.2230789,08812-Nov-200802:55x86For all supported x64-based versions of Windows Server 2008 and Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSdbus.infNot Applicable8,02012-Nov-200800:15Not ApplicableSdbus.sys6.0.6001.22307111,10412-Nov-200803:30x64For all supported Itanium-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSdbus.infNot Applicable8,00012-Nov-200800:20Not ApplicableSdbus.sys6.0.6001.22307268,80012-Nov-200802:54IA-64

When you try to install a Web Services for Devices (WSD) printer on a Windows Server 2008-based computer, the operation fails

Symptoms
When you try to install a Web Services for Devices (WSD) printeron a Windows Server 2008-based computer, the operation fails. You do not receive an error message.
Resolution
This problem occurs if the Print Services role has not been added onthe computer.By default, the Print Services role is not added in Windows Server 2008. Additionally, the WSD print proxy is not installed.When you add the Print Services role, the WSD print proxy is also installed.

Video performance may decrease when a Windows Server 2008 or Windows Server 2008 R2 based computer has the Hyper-V role enabled and an accelerated display adapter installed

Symptoms
When you run Windows Server 2008or Windows Server 2008 R2 with the Hyper-V role enabled, video performance may decrease when you perform certain actions. For example, you may experience this issue when you press CTRL+ALT+DELETE to switch from the desktop to the logon screen or when you run certain graphics-intensive applications.
Resolution
This issue occurs when a device driver or other kernel mode component makes frequent memory allocations by using the PAGE_WRITECOMBINE protection flag set while the hypervisor is running. When the kernel memory manager allocates memory by using the WRITECOMBINE attribute, the kernel memory manager must flush the Translation Lookaside Buffer (TLB) and the cache for the specific page. However, when the Hyper-V role is enabled, the TLB is virtualized by the hypervisor. Therefore, every TLB flush sends an intercept into the hypervisor. This intercept instructs the hypervisor to flush the virtual TLB. This is an expensive operation that introduces a fixed overhead cost to virtualization. Usually, this is an infrequent event in supported virtualization scenarios. However, some video graphics drivers may cause this operation to occur very frequently during certain operations. This significantly magnifies the overhead in the hypervisor.

The computer stops responding when you access some shared files from a computer that is running Windows Server 2008 or Windows Vista

Symptoms
When you access some shared files from a computer that is running Windows Server 2008 or Windows Vista, the computer stops responding under a heavy stress situation. Additionally, the computer does not recover until you force the computer to restart.
Resolution
This issue occurs because of a deadlock between the memory manager and the Redirected Drive Buffering SubSystem (Rdbss.sys) driver.

Stop error when you start a Windows Vista-based computer even though hotfix 946084 is installed on the computer: “0x0000C1F5″

Symptoms
When you start a Windows Vista-based computer, you receive the following Stop error message on a blue screen even though hotfix 946084 is installed onthe computer:

0x0000C1F5 This problem also occurs when you start Windows Vista from a Microsoft Windows Preinstallation Environment (Windows PE) 2.1 image.
Note This issue occurs if the $TxfLog file is corrupted. When this issue occurs, you have to remove the hard disk that contains the corrupted $TxfLog file to start the computer.
Resolution
This issue occurs because the Common Log File System (Clfs.sys) driver does not fix the corrupted $TxfLog file.