Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Windows may fail to boot from an iSCSI drive if networking hardware is changed

Windows may fail to boot from an iSCSI drive if networking hardware is changed

View products that this article applies to.

Source: Microsoft Support

↑ Back to the top

RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

↑ Back to the top

Symptoms

Consider the following scenario:
  • You have a computer that is running Windows Server 2008 R2.
  • The computer is configured to boot from an iSCSI disk.
  • A secondary network adapter is configured for the iSCSI disk. This adapter is not configured when Windows is installed on the iSCSI disk.
  • You boot the computer from the secondary iSCSI network adapter. Or the iSCSI network adapter is re-enumerated by Windows. For example, if the computer is running IBM UEFI firmware Version 1.40, the iSCSI network adapter will be re-enumerated if you upgrade the firmware to a later version.
In this scenario, you may receive the following Stop error message:
STOP 0x0000007B (parameter1, parameter2, parameter3, parameter4) INACCESSIBLE_BOOT_DEVICE

Note
  • The four parameters in this Stop error message may vary, depending on the configuration of the computer.
  • Not all "0x0000007B" Stop error messages are caused by this problem.

↑ Back to the top

Cause

In Windows Server 2008 R2, a new NDIS Light Weight Filter (LWF) driver is introduced called “WFP Lightweight Filter”. When Windows is installed on a local disk, this filter driver is installed and bound to all network adapters, including the network adapter to be used for iSCSI boot. If Windows is installed directly on an iSCSI disk, Windows Setup makes sure that the LWF driver does not get installed on the network adapter used with iSCSI boot. If, however, there are secondary iSCSI boot adapters (like in a fail-over environment) in the machine that are not configured for such roles during the Windows installation (e.g. an iSCSI Bios Firmware Table (iBFT) is not presented at install time or such devices are added later), the LWF driver is installed and bound on all such secondary or fail-over devices.



The NDIS LWF driver is neither a boot-start driver nor is it compatible with paging I/O. When any of the above systems, where NDIS LWF driver is bound to an iSCSI boot adapter, are started, Windows may fail to boot and/or causes a bugcheck 0x7B (INACCESSIBLE_BOOT_DEVICE).



Note The preferred method of creating an iSCSI boot image for deployment is to perform a standard Windows Setup-based installation from Windows installation media, and then if desired to capture the image for deployment to systems with identical iSCSI boot hardware.

↑ Back to the top

Resolution

To resolve the problem, apply the hotfix before the iSCSI network adapter is replaced or changed. If the computer is running IBM UEFI firmware Version 1.40, apply the hotfix before the IBM firmware is upgraded.

Note If you apply the hotfix that is described in this article together with update 2862152 or hotfix 2925489 on the computer, the version of Bfe.dll file becomes or stays being 6.1.7601.17514. But the binary file content inside the Bfe.dll file is updated, even though the versions of Bfe.dll file are shown incorrectly.

If you do not apply the hotfix, follow the steps in the Workaround section to resolve the problem.

Hotfix information

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
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 be running one of the following operating systems:
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)
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:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

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

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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 notes
  • 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:
    VersionProductMilestoneService branch
    6.1.760
    0.
    16xxx    		Windows Server 2008 R2RTMGDR
    6.1.760
    0.
    21xxx    		Windows Server 2008 R2RTMLDR
    6.1.760
    1.
    17xxx    		Windows Server 2008 R2SP1GDR
    6.1.760
    1.
    21xxx    		Windows Server 2008 R2SP1LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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 x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Bfe.dll6.1.7600.16912703,48805-Nov-201105:21x64
Fwpuclnt.dll6.1.7600.16912324,09605-Nov-201105:22x64
Ikeext.dll6.1.7600.16912845,82405-Nov-201105:22x64
Networksecurity-ppdlic.xrm-msNot Applicable3,02805-Nov-201105:40Not Applicable
Nshwfp.dll6.1.7600.16912830,46405-Nov-201105:25x64
Wfp.mofNot Applicable82222-Jul-200923:19Not Applicable
Bfe.dll6.1.7600.21085705,02405-Nov-201105:25x64
Fwpuclnt.dll6.1.7600.21085324,09605-Nov-201105:26x64
Ikeext.dll6.1.7600.21085849,40805-Nov-201105:27x64
Networksecurity-ppdlic.xrm-msNot Applicable3,02805-Nov-201105:47Not Applicable
Nshwfp.dll6.1.7600.21085832,00005-Nov-201105:30x64
Wfp.mofNot Applicable82222-Jul-200923:32Not Applicable
Bfe.dll6.1.7601.17720705,02405-Nov-201105:36x64
Fwpuclnt.dll6.1.7601.17720324,09605-Nov-201105:37x64
Ikeext.dll6.1.7601.17720853,50405-Nov-201105:37x64
Networksecurity-ppdlic.xrm-msNot Applicable3,02805-Nov-201106:00Not Applicable
Nshwfp.dll6.1.7601.17720830,46405-Nov-201105:39x64
Wfp.mofNot Applicable82212-Nov-201023:19Not Applicable
Bfe.dll6.1.7601.21855706,56005-Nov-201105:31x64
Fwpuclnt.dll6.1.7601.21855324,09605-Nov-201105:32x64
Ikeext.dll6.1.7601.21855854,52805-Nov-201105:33x64
Networksecurity-ppdlic.xrm-msNot Applicable3,02805-Nov-201105:55Not Applicable
Nshwfp.dll6.1.7601.21855832,00005-Nov-201105:35x64
Wfp.mofNot Applicable82212-Nov-201023:52Not Applicable
Wfplwf.sys6.1.7600.1691219,82405-Nov-201105:31x64
Wfplwf.sys6.1.7600.2108519,82405-Nov-201105:37x64
Wfplwf.sys6.1.7601.1772019,82405-Nov-201105:48x64
Wfplwf.sys6.1.7601.2185519,82405-Nov-201105:42x64
Fwpuclnt.dll6.1.7600.16912216,57605-Nov-201104:33x86
Nshwfp.dll6.1.7600.16912656,38405-Nov-201104:35x86
Wfp.mofNot Applicable82222-Jul-200923:12Not Applicable
Fwpuclnt.dll6.1.7600.21085216,57605-Nov-201104:33x86
Nshwfp.dll6.1.7600.21085657,92005-Nov-201104:35x86
Wfp.mofNot Applicable82222-Jul-200923:17Not Applicable
Fwpuclnt.dll6.1.7601.17720216,57605-Nov-201104:30x86
Nshwfp.dll6.1.7601.17720656,38405-Nov-201104:33x86
Wfp.mofNot Applicable82212-Nov-201023:14Not Applicable
Fwpuclnt.dll6.1.7601.21855216,57605-Nov-201104:30x86
Nshwfp.dll6.1.7601.21855657,92005-Nov-201104:31x86
Wfp.mofNot Applicable82212-Nov-201023:57Not Applicable
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Bfe.dll6.1.7600.169121,071,61605-Nov-201104:11IA-64
Fwpuclnt.dll6.1.7600.16912566,27205-Nov-201104:13IA-64
Ikeext.dll6.1.7600.169121,469,95205-Nov-201104:13IA-64
Networksecurity-ppdlic.xrm-msNot Applicable3,02805-Nov-201104:32Not Applicable
Nshwfp.dll6.1.7600.169121,112,06405-Nov-201104:16IA-64
Wfp.mofNot Applicable82222-Jul-200923:20Not Applicable
Bfe.dll6.1.7600.210851,074,17605-Nov-201104:15IA-64
Fwpuclnt.dll6.1.7600.21085566,27205-Nov-201104:17IA-64
Ikeext.dll6.1.7600.210851,475,07205-Nov-201104:17IA-64
Networksecurity-ppdlic.xrm-msNot Applicable3,02805-Nov-201104:36Not Applicable
Nshwfp.dll6.1.7600.210851,114,11205-Nov-201104:20IA-64
Wfp.mofNot Applicable82222-Jul-200923:58Not Applicable
Bfe.dll6.1.7601.177201,071,61605-Nov-201104:03IA-64
Fwpuclnt.dll6.1.7601.17720566,27205-Nov-201104:03IA-64
Ikeext.dll6.1.7601.177201,483,77605-Nov-201104:03IA-64
Networksecurity-ppdlic.xrm-msNot Applicable3,02805-Nov-201104:19Not Applicable
Nshwfp.dll6.1.7601.177201,112,06405-Nov-201104:03IA-64
Wfp.mofNot Applicable82212-Nov-201023:19Not Applicable
Bfe.dll6.1.7601.218551,074,17605-Nov-201104:21IA-64
Fwpuclnt.dll6.1.7601.21855566,27205-Nov-201104:23IA-64
Ikeext.dll6.1.7601.218551,486,84805-Nov-201104:23IA-64
Networksecurity-ppdlic.xrm-msNot Applicable3,02805-Nov-201104:45Not Applicable
Nshwfp.dll6.1.7601.218551,114,11205-Nov-201104:26IA-64
Wfp.mofNot Applicable82212-Nov-201023:53Not Applicable
Wfplwf.sys6.1.7600.1691233,64805-Nov-201104:23IA-64
Wfplwf.sys6.1.7600.2108533,64805-Nov-201104:26IA-64
Wfplwf.sys6.1.7601.1772033,64805-Nov-201104:06IA-64
Wfplwf.sys6.1.7601.2185533,64805-Nov-201104:33IA-64
Fwpuclnt.dll6.1.7600.16912216,57605-Nov-201104:33x86
Nshwfp.dll6.1.7600.16912656,38405-Nov-201104:35x86
Wfp.mofNot Applicable82222-Jul-200923:12Not Applicable
Fwpuclnt.dll6.1.7600.21085216,57605-Nov-201104:33x86
Nshwfp.dll6.1.7600.21085657,92005-Nov-201104:35x86
Wfp.mofNot Applicable82222-Jul-200923:17Not Applicable
Fwpuclnt.dll6.1.7601.17720216,57605-Nov-201104:30x86
Nshwfp.dll6.1.7601.17720656,38405-Nov-201104:33x86
Wfp.mofNot Applicable82212-Nov-201023:14Not Applicable
Fwpuclnt.dll6.1.7601.21855216,57605-Nov-201104:30x86
Nshwfp.dll6.1.7601.21855657,92005-Nov-201104:31x86
Wfp.mofNot Applicable82212-Nov-201023:57Not Applicable

↑ Back to the top

Workaround

To work around this issue without applying the hotfix, before creating an iSCSI bootable Windows image to be deployed on an iSCSI target or after configuring the secondary/fail-over boot-adapters, unbind NDIS LWF driver from any network adapters being used for iSCSI boot.

NDIS LWF driver can be unbound from the target miniport via BindView or NvspBind (among other tools).

Bindview is graphic user interface tool available from the Windows WDK. For instructions how to download the latest Windows WDK, please visit:
http://www.microsoft.com/whdc/devtools/wdk/wdkpkg.mspx

Nvspbind is a command line tool available from the following location:
http://archive.msdn.microsoft.com/nvspbind

To unbind the NDIS LWF driver using BindView, do the following:
  1. Build the BindView sample from Windows Developer Kit (WDK). It is located in the <WDK Root>\ src\network\config\bindview directory, where <WDK Root> is the root directory where WDK is installed.
  2. Run BindView application built in step one above.
  3. In “Show bindings for” – Select “All Services”
  4. You will see “WFP Lightweight filter” node. Expand it to see its binding paths.
  5. Right-Click on “Binding Path #” for the iSCSI boot NIC and select “Disable”. If the Disable option is not available, it means the binding is already disabled.
To unbind the NDIS LWF Driver with Nvspbind, do the following:
  1. Identify the GUID for the boot NIC by displaying the NIC information with the command: nvspbind –n
    For example each NIC will appear similar to the following:
    {091786BC-FC48-4CDB-B7C5-94994C83C8CF}
    "vmbus\{f8615163-df3e-46c5-913f-f2d2f965ed0e}"
    "Microsoft Virtual Machine Bus Network Adapter #2"
    "iSCSI1":
  2. Determine if NDIS LWF driver is enabled on the NIC with the command: nvspbind.exe {guid}
    For example: nvspbind {091786BC-FC48-4CDB-B7C5-94994C83C8CF}
  3. When enabled the NDIS LWF driver will appear as follows:
    enabled: ms_wfplwf (WFP Lightweight Filter)
  4. Disable the NDIS LWF driver with the command: nvspbind.exe /d {guid} ms_wfplwf
    For Example: nvspbind /d {091786BC-FC48-4CDB-B7C5-94994C83C8CF} ms_wfplwf
  5. Verify the NDIS LWF driver was disabled with the command: nvspbind.exe {guid}
    For example: nvspbind {091786BC-FC48-4CDB-B7C5-94994C83C8CF}
  6. When disabled the NDIS LWF driver will appear as follows:
    disabled: ms_wfplwf (WFP Lightweight Filter)
For additional information and examples on how to use Nvspbind please refer to the Readme.doc included in Nvspbind tool download.

Once LWF is unbound successfully from all boot-devices, proceed to create an image for deployment as usual.

Note
  • The user must have Administrative privileges to perform the unbind operations.
  • ALL network adapters that will be used for booting (like primary and secondary/failover boot-adapters) must have NDIS LWF driver unbound from them.

↑ Back to the top

Status

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

↑ Back to the top

More Information

For more information about iSCSI Boot, refer to the following:
Microsoft iSCSI Boot Step-by-Step Guide
For more information about a related issue, click the following article number to view the article in the Microsoft Knowledge Base:
2507616 "0x0000007B" Stop error after replacing or switching to an alternate iSCSI boot adapter on a Windows Server 2008 R2-based or Windows 7-based computer

2344941 "0x0000007B" Stop error when you replace an iSCSI or PCI Express network adapter or a motherboard with an identical device on a Windows Server 2008 R2-based or Windows 7-based computer

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

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_109d6c4824bc0963d8439e69f389d6b9_31bf3856ad364e35_6.1.7600.21085_none_caa7c04a61485aaa.manifest
File versionNot Applicable
File size1,058
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameAmd64_4cf33a457fdad24d5b099d3b84e9ea5f_31bf3856ad364e35_6.1.7600.21085_none_d4756d43c17d7cc7.manifest
File versionNot Applicable
File size708
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameAmd64_6c968385b0bed5044f8df540a0070364_31bf3856ad364e35_6.1.7601.17720_none_20d593602c9318c9.manifest
File versionNot Applicable
File size1,058
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameAmd64_7d872145d5a029d960db73b5672c10e7_31bf3856ad364e35_6.1.7600.16912_none_4e859c8deff5f6ce.manifest
File versionNot Applicable
File size708
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameAmd64_99a415e0a1d68fcba0e64e075f71e1bd_31bf3856ad364e35_6.1.7601.21855_none_e6de1354f8c91a09.manifest
File versionNot Applicable
File size708
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameAmd64_9d85c1d6c7f6703afe355b113cc85850_31bf3856ad364e35_6.1.7601.21855_none_826b2b7133cccbdf.manifest
File versionNot Applicable
File size1,058
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameAmd64_ba92d405a3fd5c9f7bae34cbe7365273_31bf3856ad364e35_6.1.7601.17720_none_9f560802a994b0ac.manifest
File versionNot Applicable
File size708
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameAmd64_c41cf1160a7c942d5a003e4c041200e3_31bf3856ad364e35_6.1.7601.21855_none_9f4373eb21fb7162.manifest
File versionNot Applicable
File size698
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameAmd64_c7e4e7e819e144b663123b5062f8f05d_31bf3856ad364e35_6.1.7600.16912_none_eabb3e8e4030e8b9.manifest
File versionNot Applicable
File size1,058
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameAmd64_eff31c8ae019e71c6ce2abefc5396985_31bf3856ad364e35_6.1.7600.21085_none_287b32b42aaf53a7.manifest
File versionNot Applicable
File size698
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameAmd64_f255d720daddabb6de923dc8b39988fc_31bf3856ad364e35_6.1.7600.16912_none_138e1c599fd3d375.manifest
File versionNot Applicable
File size698
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameAmd64_f2bb26ac308aafc4b016dc1c141cb4af_31bf3856ad364e35_6.1.7601.17720_none_dc48f276d9179251.manifest
File versionNot Applicable
File size698
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameAmd64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7600.16912_none_29621b8a4405bdfe.manifest
File versionNot Applicable
File size154,831
Date (UTC)05-Nov-2011
Time (UTC)05:54
PlatformNot Applicable
File nameAmd64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7600.21085_none_29a2dffb5d59a37f.manifest
File versionNot Applicable
File size154,831
Date (UTC)05-Nov-2011
Time (UTC)05:56
PlatformNot Applicable
File nameAmd64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.17720_none_2b3ba8104136132d.manifest
File versionNot Applicable
File size154,831
Date (UTC)05-Nov-2011
Time (UTC)06:09
PlatformNot Applicable
File nameAmd64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21855_none_2ba9d6895a67857d.manifest
File versionNot Applicable
File size154,831
Date (UTC)05-Nov-2011
Time (UTC)06:10
PlatformNot Applicable
File nameAmd64_microsoft-windows-wfplwf_31bf3856ad364e35_6.1.7600.16912_none_585a3fad680959dd.manifest
File versionNot Applicable
File size3,080
Date (UTC)05-Nov-2011
Time (UTC)05:57
PlatformNot Applicable
File nameAmd64_microsoft-windows-wfplwf_31bf3856ad364e35_6.1.7600.21085_none_589b041e815d3f5e.manifest
File versionNot Applicable
File size3,080
Date (UTC)05-Nov-2011
Time (UTC)05:59
PlatformNot Applicable
File nameAmd64_microsoft-windows-wfplwf_31bf3856ad364e35_6.1.7601.17720_none_5a33cc336539af0c.manifest
File versionNot Applicable
File size3,080
Date (UTC)05-Nov-2011
Time (UTC)06:12
PlatformNot Applicable
File nameAmd64_microsoft-windows-wfplwf_31bf3856ad364e35_6.1.7601.21855_none_5aa1faac7e6b215c.manifest
File versionNot Applicable
File size3,080
Date (UTC)05-Nov-2011
Time (UTC)06:12
PlatformNot Applicable
File nameUpdate-bf.mum
File versionNot Applicable
File size3,521
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size3,591
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameWow64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7600.16912_none_33b6c5dc78667ff9.manifest
File versionNot Applicable
File size94,348
Date (UTC)05-Nov-2011
Time (UTC)04:54
PlatformNot Applicable
File nameWow64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7600.21085_none_33f78a4d91ba657a.manifest
File versionNot Applicable
File size94,348
Date (UTC)05-Nov-2011
Time (UTC)04:57
PlatformNot Applicable
File nameWow64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.17720_none_359052627596d528.manifest
File versionNot Applicable
File size94,348
Date (UTC)05-Nov-2011
Time (UTC)04:55
PlatformNot Applicable
File nameWow64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21855_none_35fe80db8ec84778.manifest
File versionNot Applicable
File size94,348
Date (UTC)05-Nov-2011
Time (UTC)04:48
PlatformNot Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_03a028731b3fa34f9a080d7aa5ca65ea_31bf3856ad364e35_6.1.7601.21855_none_e38a538b3adc647c.manifest
File versionNot Applicable
File size696
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameIa64_08195d1505087be2272419309546db7d_31bf3856ad364e35_6.1.7600.16912_none_b448a9ec5bec46f7.manifest
File versionNot Applicable
File size696
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameIa64_217fcb22a0af73fda16cfcd3e2c89091_31bf3856ad364e35_6.1.7601.21855_none_dfe8482f0ddd01c8.manifest
File versionNot Applicable
File size1,056
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameIa64_6944a5cecd225745b1eb7fcc5dd11082_31bf3856ad364e35_6.1.7600.16912_none_2e01f0b84edc1563.manifest
File versionNot Applicable
File size1,056
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameIa64_6cf42b719024a776ba810b2ca02c12e0_31bf3856ad364e35_6.1.7601.17720_none_18c8a88060033faf.manifest
File versionNot Applicable
File size696
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameIa64_766902bba2186b7f95c999fe8f30701b_31bf3856ad364e35_6.1.7601.17720_none_ba614a8ad0f2a204.manifest
File versionNot Applicable
File size1,056
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameIa64_bbe0582ffed4e7ac5c1bb5f15888cb65_31bf3856ad364e35_6.1.7600.21085_none_3289320eb6b152e2.manifest
File versionNot Applicable
File size1,056
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameIa64_fef899f352fa0dbe721fe9f09cff0587_31bf3856ad364e35_6.1.7600.21085_none_aeeddc69fd8c3f2a.manifest
File versionNot Applicable
File size696
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameIa64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7600.16912_none_cd4523fc8ba655c4.manifest
File versionNot Applicable
File size154,828
Date (UTC)05-Nov-2011
Time (UTC)05:59
PlatformNot Applicable
File nameIa64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7600.21085_none_cd85e86da4fa3b45.manifest
File versionNot Applicable
File size154,828
Date (UTC)05-Nov-2011
Time (UTC)05:53
PlatformNot Applicable
File nameIa64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.17720_none_cf1eb08288d6aaf3.manifest
File versionNot Applicable
File size154,828
Date (UTC)05-Nov-2011
Time (UTC)05:51
PlatformNot Applicable
File nameIa64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21855_none_cf8cdefba2081d43.manifest
File versionNot Applicable
File size154,828
Date (UTC)05-Nov-2011
Time (UTC)05:49
PlatformNot Applicable
File nameIa64_microsoft-windows-wfplwf_31bf3856ad364e35_6.1.7600.16912_none_fc3d481fafa9f1a3.manifest
File versionNot Applicable
File size3,079
Date (UTC)05-Nov-2011
Time (UTC)06:01
PlatformNot Applicable
File nameIa64_microsoft-windows-wfplwf_31bf3856ad364e35_6.1.7600.21085_none_fc7e0c90c8fdd724.manifest
File versionNot Applicable
File size3,079
Date (UTC)05-Nov-2011
Time (UTC)05:56
PlatformNot Applicable
File nameIa64_microsoft-windows-wfplwf_31bf3856ad364e35_6.1.7601.17720_none_fe16d4a5acda46d2.manifest
File versionNot Applicable
File size3,079
Date (UTC)05-Nov-2011
Time (UTC)05:53
PlatformNot Applicable
File nameIa64_microsoft-windows-wfplwf_31bf3856ad364e35_6.1.7601.21855_none_fe85031ec60bb922.manifest
File versionNot Applicable
File size3,079
Date (UTC)05-Nov-2011
Time (UTC)05:51
PlatformNot Applicable
File nameUpdate-bf.mum
File versionNot Applicable
File size1,901
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size1,941
Date (UTC)05-Nov-2011
Time (UTC)10:14
PlatformNot Applicable
File nameWow64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7600.16912_none_33b6c5dc78667ff9.manifest
File versionNot Applicable
File size94,348
Date (UTC)05-Nov-2011
Time (UTC)04:54
PlatformNot Applicable
File nameWow64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7600.21085_none_33f78a4d91ba657a.manifest
File versionNot Applicable
File size94,348
Date (UTC)05-Nov-2011
Time (UTC)04:57
PlatformNot Applicable
File nameWow64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.17720_none_359052627596d528.manifest
File versionNot Applicable
File size94,348
Date (UTC)05-Nov-2011
Time (UTC)04:55
PlatformNot Applicable
File nameWow64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21855_none_35fe80db8ec84778.manifest
File versionNot Applicable
File size94,348
Date (UTC)05-Nov-2011
Time (UTC)04:48
PlatformNot Applicable

↑ Back to the top

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.


TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

↑ Back to the top

Keywords: kb, kbnoloc, kbrapidpub, kbnomt, kbqfe, kbexpertiseadvanced, kbhotfixserver, kbautohotfix

↑ Back to the top

Article Info
Article ID : 976042
Revision : 3
Created on : 4/18/2018
Published on : 4/19/2018
Exists online : False
Views : 507