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.

Some services are preloaded unexpectedly on an IIS server in Windows


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You install the Windows Server AppFabric feature on an Internet Information Services (IIS) server that is running Windows 8.1, Windows Server 2012 R2, Windows 7 service Pack 1 (SP1), or Windows Server 2008 R2 SP1.
  • You create a website, and then you add multiple applications to the website.
  • These applications are running under different application pools.
  • You enable the auto-start feature for different services in these applications.
  • You deploy a new service to run under the same website. Or, you restart an existing service.
In this scenario, all the services in these applications are preloaded in all the application pools. The expected behavior is that the services are isolated to their specific application pools.

For example, you create a website that is named MySite on an IIS server. MySite includes two applications, which are named App1 and App2. MySite and App1 run in an application pool that is named AppPool1. App2 runs in an application pool that is named AppPool2. In App1, you enable the auto-start feature for a service that is named service_App1. In App2, you enable the auto-start feature for a service that is named service_App2. When you deploy a new service_App3 in application App3, and then run the service in application pool AppPool3, service_App1 and service_App2 are also loaded in the application pool AppPool3. However, only service_App3 should be loaded.

↑ Back to the top


Cause

This issue occurs because of an error in the W3wphost.dll file. This error causes services to be preloaded in multiple application pools after a configuration change.

↑ Back to the top


Resolution

Hotfix information

Important Do not install a language pack after you install this hotfix. If you do, the language-specific changes in the hotfix will not be applied, and you will have to reinstall the hotfix. For more information, see Add language packs to Windows.

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 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 have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows 8.1 or Windows Server 2012 R2. Or, install Service Pack 1 for Windows 7 or Windows Server 2008 R2.

Registry information

To apply 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 the hotfix if IIS is running when you apply the 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 8.1 and Windows Server 2012 R2 file information and notes

Important Windows 8.1 hotfixes and Windows Server 2012 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 8.1/Windows Server 2012 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:

    VersionProductMilestoneService branch
    6.3.960 0.17xxxWindows 8.1 and Windows Server 2012 R2RTMGDR
  • 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 8.1 and for Windows Server 2012 R2" 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 8.1
File nameFile versionFile sizeDateTimePlatform
Iisw3adm.dll8.5.9600.17783501,24826-Mar-201502:44x86
W3tp.dll8.5.9600.1778322,01626-Mar-201502:06x86
W3wphost.dll8.5.9600.1778366,04826-Mar-201502:01x86
Wbhstipm.dll8.5.9600.1778325,60026-Mar-201502:56x86
Wbhst_pm.dll8.5.9600.1778325,08826-Mar-201502:53x86
For all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Iisw3adm.dll8.5.9600.17783570,88026-Mar-201504:04x64
W3tp.dll8.5.9600.1778328,16026-Mar-201503:09x64
W3wphost.dll8.5.9600.1778375,26426-Mar-201503:02x64
Wbhstipm.dll8.5.9600.1778330,20826-Mar-201504:19x64
Wbhst_pm.dll8.5.9600.1778328,16026-Mar-201504:16x64
Iisw3adm.dll8.5.9600.17783501,24826-Mar-201502:44x86
W3tp.dll8.5.9600.1778322,01626-Mar-201502:06x86
W3wphost.dll8.5.9600.1778366,04826-Mar-201502:01x86
Wbhstipm.dll8.5.9600.1778325,60026-Mar-201502:56x86
Wbhst_pm.dll8.5.9600.1778325,08826-Mar-201502:53x86

Windows 7 and Windows Server 2008 R2 file information 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:
    VersionProductSR_LevelService branch
    6.1.760 1. 21xxxWindows 7 and Windows Server 2008 R2SP1LDR
  • 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 7 and for Windows Server 2008 R2" 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
File nameFile versionFile sizeDateTimePlatform
W3wphost.dll7.5.7600.2114155,29601-Feb-201205:36x86
W3wphost.dll7.5.7601.2191255,29601-Feb-201206:52x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
W3wphost.dll7.5.7600.2114160,92801-Feb-201206:29x64
W3wphost.dll7.5.7601.2191260,92801-Feb-201206:36x64
For all supported IA-64–based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
W3wphost.dll7.5.7600.21141144,38401-Feb-201205:15IA-64
W3wphost.dll7.5.7601.21912144,38401-Feb-201205:25IA-64

Additional file information

Additional file information for Windows 8.1 and for Windows Server 2012 R2
Additional files for all supported x86-based versions of Windows 8.1
File propertyValue
File nameX86_f1c682ac1cedf13fa518a1c976ca9fab_31bf3856ad364e35_6.3.9600.17783_none_8064f587a18d781e.manifest
File versionNot applicable
File size717
Date (UTC)26-Mar-2015
Time (UTC)12:05
PlatformNot applicable
File nameX86_microsoft-windows-p..ellibrariesbinaries_31bf3856ad364e35_6.3.9600.17783_none_0f5ab6658a55a466.manifest
File versionNot applicable
File size11,784
Date (UTC)26-Mar-2015
Time (UTC)05:32
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File propertyValue
File nameAmd64_1e3897e9a5d6da3819f46315cfb76c22_31bf3856ad364e35_6.3.9600.17783_none_71c98fb5f6ebe592.manifest
File versionNot applicable
File size721
Date (UTC)26-Mar-2015
Time (UTC)12:05
PlatformNot applicable
File nameAmd64_5018c3660734c2c503d2df8dd2afb2bc_31bf3856ad364e35_6.3.9600.17783_none_02b7be38b77c038f.manifest
File versionNot applicable
File size721
Date (UTC)26-Mar-2015
Time (UTC)12:05
PlatformNot applicable
File nameAmd64_microsoft-windows-p..ellibrariesbinaries_31bf3856ad364e35_6.3.9600.17783_none_6b7951e942b3159c.manifest
File versionNot applicable
File size11,790
Date (UTC)26-Mar-2015
Time (UTC)05:37
PlatformNot applicable
File nameWow64_microsoft-windows-p..ellibrariesbinaries_31bf3856ad364e35_6.3.9600.17783_none_75cdfc3b7713d797.manifest
File versionNot applicable
File size10,115
Date (UTC)26-Mar-2015
Time (UTC)05:32
PlatformNot applicable
Additional file information for Windows 7 and for Windows Server 2008 R2
Additional files for all supported x86-based versions of Windows 7
File nameUpdate.mum
File versionNot Applicable
File size3,295
Date (UTC)01-Feb-2012
Time (UTC)09:25
File nameX86_84728235a201c41a012da7869236ae15_31bf3856ad364e35_6.1.7600.21141_none_c679fc69265ca403.manifest
File versionNot Applicable
File size709
Date (UTC)01-Feb-2012
Time (UTC)09:25
File nameX86_c6f75a2026e1e77fe40eee8a968a58a9_31bf3856ad364e35_6.1.7601.21912_none_81b700deb0d27f68.manifest
File versionNot Applicable
File size709
Date (UTC)01-Feb-2012
Time (UTC)09:25
File nameX86_microsoft-windows-processmodellibraries_31bf3856ad364e35_6.1.7600.21141_none_db2371ce2536dd54.manifest
File versionNot Applicable
File size12,568
Date (UTC)01-Feb-2012
Time (UTC)06:04
File nameX86_microsoft-windows-processmodellibraries_31bf3856ad364e35_6.1.7601.21912_none_dd2b68a62243d8a9.manifest
File versionNot Applicable
File size12,568
Date (UTC)01-Feb-2012
Time (UTC)07:19
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_605f2910fb3671de81638af6b238c1ff_31bf3856ad364e35_6.1.7601.21912_none_b3e3997337e4b4e0.manifest
File versionNot Applicable
File size1,068
Date (UTC)01-Feb-2012
Time (UTC)09:26
File nameAmd64_64cb8c2bfcd6b3f3de844585a24df84c_31bf3856ad364e35_6.1.7600.21141_none_391da4727eab82a6.manifest
File versionNot Applicable
File size1,068
Date (UTC)01-Feb-2012
Time (UTC)09:25
File nameAmd64_microsoft-windows-processmodellibraries_31bf3856ad364e35_6.1.7600.21141_none_37420d51dd944e8a.manifest
File versionNot Applicable
File size12,574
Date (UTC)01-Feb-2012
Time (UTC)06:57
File nameAmd64_microsoft-windows-processmodellibraries_31bf3856ad364e35_6.1.7601.21912_none_394a0429daa149df.manifest
File versionNot Applicable
File size12,574
Date (UTC)01-Feb-2012
Time (UTC)07:58
File nameUpdate.mum
File versionNot Applicable
File size3,737
Date (UTC)01-Feb-2012
Time (UTC)09:26
File nameWow64_microsoft-windows-processmodellibraries_31bf3856ad364e35_6.1.7600.21141_none_4196b7a411f51085.manifest
File versionNot Applicable
File size12,249
Date (UTC)01-Feb-2012
Time (UTC)05:54
File nameWow64_microsoft-windows-processmodellibraries_31bf3856ad364e35_6.1.7601.21912_none_439eae7c0f020bda.manifest
File versionNot Applicable
File size12,249
Date (UTC)01-Feb-2012
Time (UTC)07:10
Additional files for all supported IA-64–based versions of Windows Server 2008 R2
File nameIa64_d773d20ff46a7701701faa1622957e22_31bf3856ad364e35_6.1.7601.21912_none_f63492bc43093399.manifest
File versionNot Applicable
File size1,066
Date (UTC)01-Feb-2012
Time (UTC)09:25
File nameIa64_ef4c205d40865aee2a1f212fb99fe379_31bf3856ad364e35_6.1.7600.21141_none_6b26810813307ad8.manifest
File versionNot Applicable
File size1,066
Date (UTC)01-Feb-2012
Time (UTC)09:25
File nameIa64_microsoft-windows-processmodellibraries_31bf3856ad364e35_6.1.7600.21141_none_db2515c42534e650.manifest
File versionNot Applicable
File size12,571
Date (UTC)01-Feb-2012
Time (UTC)06:52
File nameIa64_microsoft-windows-processmodellibraries_31bf3856ad364e35_6.1.7601.21912_none_dd2d0c9c2241e1a5.manifest
File versionNot Applicable
File size12,571
Date (UTC)01-Feb-2012
Time (UTC)08:03
File nameUpdate.mum
File versionNot Applicable
File size2,767
Date (UTC)01-Feb-2012
Time (UTC)09:25
File nameWow64_microsoft-windows-processmodellibraries_31bf3856ad364e35_6.1.7600.21141_none_4196b7a411f51085.manifest
File versionNot Applicable
File size12,249
Date (UTC)01-Feb-2012
Time (UTC)05:54
File nameWow64_microsoft-windows-processmodellibraries_31bf3856ad364e35_6.1.7601.21912_none_439eae7c0f020bda.manifest
File versionNot Applicable
File size12,249
Date (UTC)01-Feb-2012
Time (UTC)07:10

↑ 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 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

For more information about Windows Server AppFabric, visit the following Microsoft website:For more information about the auto-start feature, visit the following Microsoft website:For more information about how to configure auto-start, visit the following Microsoft website:

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseinter

↑ Back to the top

Article Info
Article ID : 2672277
Revision : 1
Created on : 1/7/2017
Published on : 7/2/2015
Exists online : False
Views : 488