This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario:
You develop an application that sends an IOCTL_SFFDISK_DEVICE_COMMAND request to a Secure Digital (SD) card.
You compile the application on a 32-bit version of Windows Vista.
In this scenario, the application obtains a "Success" value from the SD card. However, when a 64-bit version of Windows Vista uses the Microsoft Windows-32-on-Windows-64 (WOW64) subsystem to run the 32-bit application, the application obtains the following error message from the SD card:
This issue occurs because a 64-bit version of Windows Vista does not support an IOCTL_SFFDISK_DEVICE_COMMAND request for the SD card on the WOW64 subsystem for a 32-bit application that is compiled on a 32-bit version of Windows Vista. The SFFDISK_DEVICE_COMMAND_DATA structure has a ULONG_PTR member that supports an 8-bytes length on the WOW64 subsystem. However, the SFFDISK_DEVICE_COMMAND_DATA structure has a ULONG_PTR member that supports a 4-bytes length on a 32-bit version of Windows Vista. This causes the issue that is mentioned in the "Symptoms" section.
Service pack information
To resolve this problem, obtain the latest service pack for Windows Vista. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
935791 How to obtain the latest Windows Vista service pack
Hotfixes and security updates that are included in SP2 for Windows Vista Service and for Windows Server 2008
For more information about the hotfixes and the security updates that are included in SP2 for Windows Vista and for Windows Server 2008, visit the following Microsoft TechNet Web site: -
Note:Currently, the list of hotfixes and security updates is available only in English.
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. 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:
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.
No prerequisites are required.
You must restart the computer after you apply this hotfix.
Hotfix Replacement Information
This hotfix does not replace a previously released hotfix.
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.