Update to support NVM Express by using native drivers in Windows 7 or Windows Server 2008 R2

To apply this update, we have released hotfixes for Windows 7 or Windows Server 2008 R2.

Before you install this hotfix, check the prerequisite of the hotfix, and additional steps of configuration is required.

Hotfix for Windows 7 or Windows Server 2008 R2

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 to create a separate service request, visit the following Microsoft website: 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, you must first install SP1 in Windows 7 or Windows 2008 R2. For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

How to insert the hotfix package into the .wim file

Method 1

1. Create two local folder C:\mount and C:\nvme.
2. Rename the hotfix package extension to .cab, and extract the injectable offline.cab file.
3. Install Windows OEM Preinstallation Kit (OPK) tools on the computer.
4. Mount each the boot.wim image and insert into the offline hotfix package by using the following commands in the DISM tools:
   dism /mount-wim /WimFile:"C:\sources\boot.wim" /Index:1 /MountDir: C:\mount
   
   dism /image:C:\mount /Add-Package /PackagePath:"C:\nvme"
   
   dism /unmount-wim /mountdir: C:\mount /commit
   
   
   dism /mount-wim /WimFile:" C:\sources\boot.wim " /Index:2 / MountDir: C:\mount
   
   dism /image: C:\mount /Add-Package /PackagePath:"C:\nvme"
   
   dism /unmount-wim /mountdir: C:\mount /commit
   
5. Mount each the install.wim image and insert into the hotfix package offline by using the following commands in the DISM tools:
   dism /mount-wim /WimFile:"C:\sources\install.wim" /Index:1 / MountDir: C:\mount
   
   dism /image: C:\mount /Add-Package /PackagePath:"C:\nvme"
   
   dism /unmount-wim /mountdir: C:\mount /commit
   
   
   dism /mount-wim /WimFile:"C:\sources\install.wim" /Index:2 / MountDir: C:\mount
   
   dism /image: C:\mount /Add-Package /PackagePath:"C:\nvme"
   
   dism /unmount-wim /mountdir: C:\mount /commit
   
   
   dism /mount-wim /WimFile:"C:\sources\install.wim" /Index:3 /Mountdir:e:\mount
   
   dism /image: C:\mount /Add-Package /PackagePath:"C:\nvme"
   
   dism /unmount-wim /mountdir: C:\mount /commit
   
   
   dism /mount-wim /WimFile:"C:\sources\install.wim" /Index:4 /Mountdir:e:\mount
   
   dism /image: C:\mount /Add-Package /PackagePath:" C:\nvme"
   
   dism /unmount-wim /mountdir: C:\mount /commit
6. Create a flat copy of the original media contents, and replace the boot.wim and install.wim with the changed versions that you created in the previous steps.
7. Extract the hwcompat.txt file from the hotfix package.
8. Manually replace the hwcompat.txt file in the sources directory of the media flat copy.
9. Create an ISO by using the following command:
   C:\oscdimg -m -o -u2 -udfver102 -bootdata:2#p0,e,b C:\etfsboot.com#pEF,e,b C:\efisys.bin C:\nvme C:\win7patched2.iso
10. Restart to the media and deploy Windows.

Method 2

1. Restart from media, and install Windows 7 from media to a disk that attaches other storage controllers (such as SATA).
2. Press Ctrl+Shift+F3 to enter the audit mode during Out-of-box experience (OOBE) process.
3. Install the hotfix package, and restart the computer.
4. Reseal the system with sysprep - generalize - shutdown options.
5. Capture and move the generalized image over to the disk that attaches the NVMe controller.

How to extract the hwcompat.txt file for method 1

1. Rename the hotfix package extension to .cab.
2. Execute the following command in Command Prompt:
   Md expandedfiles
   
   Expand Windows6.1-KB2990941-v3-x64.cab –F:* expandedfiles
   
   Cd expandedfiles
   
   Md expandedfiles2
   
   Expand Windows6.1-KB2990941-v3-x64.cab –F:* expandedfiles2

Note The hwcompat.txt file is in the following path:

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 7 and Windows Server 2008 R2 file information and notes

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

• The 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

  Version	Product	Milestone	Service branch
  6.1.760 1.18xxx	Windows 7 and Windows Server 2008 R2	SP1	GDR
  6.1.760 1.22xxx	Windows 7 and Windows Server 2008 R2	SP1	LDR

• The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows 7

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

Third-party information disclaimer

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.