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.

"Installation Prevented by Policy" warning is not displayed in Windows 8.1 or Windows 8


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a computer that's running Windows 8.1 or Windows 8.
  • The computer is joined to a domain that has the Device Installation Restriction Group Policy Object enabled.
  • You insert a device into the computer, such as a USB device.

In this scenario, the device is not installed, but you do not receive the following warning as expected:

Installation Prevented by Policy

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft Support. 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, go to 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.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

File information
The English (United States) 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 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.1RTMGDR
  • 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" 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
Devicesetupmanager.dll6.3.9600.17668167,42428-Jan-201501:04x86
Devicesetupmanagerapi.dll6.3.9600.1741593,69629-Oct-201400:57x86
Dsmusertask.exe6.3.9600.1766823,55228-Jan-201501:09x86
For all supported x64-based versions of Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Devicesetupmanager.dll6.3.9600.17668206,84828-Jan-201501:18x64
Devicesetupmanagerapi.dll6.3.9600.17415119,29629-Oct-201401:15x64
Dsmusertask.exe6.3.9600.1766827,64828-Jan-201501:26x64

Windows 8 file information and notes

Important Windows 8 and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" 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.2.920 0.16 xxxWindows 8RTMGDR
    6.2.920 0.20 xxxWindows 8RTMLDR
  • 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" 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 x86-based versions of Windows 8
File nameFile versionFile sizeDateTimePlatform
Devicesetupmanager.dll6.2.9200.20872162,30408-Nov-201304:55x86
Devicesetupmanagerapi.dll6.2.9200.1638486,52826-Jul-201203:18x86
Dsmusertask.exe6.2.9200.2087222,52808-Nov-201304:56x86
For all supported x64-based versions of Windows 8
File nameFile versionFile sizeDateTimePlatform
Devicesetupmanager.dll6.2.9200.20872207,87208-Nov-201305:15x64
Devicesetupmanagerapi.dll6.2.9200.16384112,12826-Jul-201203:05x64
Dsmusertask.exe6.2.9200.2087227,13608-Nov-201305:18x64

↑ 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


Additional file information

Additional file information for Windows 8.1

Additional files for all supported x86-based versions of Windows 8.1
File propertyValue
File nameX86_aa0e41e019d278fb8e28f9b0af90ae1e_31bf3856ad364e35_6.3.9600.17668_none_a96e0e42c8378bad.manifest
File versionNot applicable
File size713
Date (UTC)28-Jan-2015
Time (UTC)15:46
PlatformNot applicable
File nameX86_f6d37bea63fe4648e95feab44ab5cf71_31bf3856ad364e35_6.3.9600.17668_none_842f802a1f3847c9.manifest
File versionNot applicable
File size709
Date (UTC)28-Jan-2015
Time (UTC)15:46
PlatformNot applicable
File nameX86_microsoft-windows-d..setupmanagerservice_31bf3856ad364e35_6.3.9600.17668_none_878ac95e19b0885d.manifest
File versionNot applicable
File size7,625
Date (UTC)28-Jan-2015
Time (UTC)03:24
PlatformNot applicable
File nameX86_microsoft-windows-devicesetupmanagerapi_31bf3856ad364e35_6.3.9600.17668_none_0c6f0d8d29682c5e.manifest
File versionNot applicable
File size15,400
Date (UTC)28-Jan-2015
Time (UTC)15:50
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 8.1
File propertyValue
File nameAmd64_5404d972564f6f713cd9fa4271712cf3_31bf3856ad364e35_6.3.9600.17668_none_c66d175a4de2ae79.manifest
File versionNot applicable
File size717
Date (UTC)28-Jan-2015
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_ccd587fe8bcf29849084e457503e58f4_31bf3856ad364e35_6.3.9600.17668_none_e685a98f8716f514.manifest
File versionNot applicable
File size713
Date (UTC)28-Jan-2015
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_microsoft-windows-d..setupmanagerservice_31bf3856ad364e35_6.3.9600.17668_none_e3a964e1d20df993.manifest
File versionNot applicable
File size7,629
Date (UTC)28-Jan-2015
Time (UTC)04:11
PlatformNot applicable
File nameAmd64_microsoft-windows-devicesetupmanagerapi_31bf3856ad364e35_6.3.9600.17668_none_688da910e1c59d94.manifest
File versionNot applicable
File size15,404
Date (UTC)28-Jan-2015
Time (UTC)15:53
PlatformNot applicable

Additional file information for Windows 8

Additional files for all supported x86-based versions of Windows 8
File nameX86_4eae94be063202d3b69f2af4c288b1ef_31bf3856ad364e35_6.2.9200.20872_none_59919cb98cda1be5.manifest
File versionNot Applicable
File size706
Date (UTC)08-Nov-2013
Time (UTC)13:08
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameX86_microsoft-windows-devicesetupmanager_31bf3856ad364e35_6.2.9200.20872_none_70458536aa9b3c62.manifest
File versionNot Applicable
File size20,137
Date (UTC)08-Nov-2013
Time (UTC)13:08
SHA-1 hashNot Applicable
MD5 hashNot Applicable
Additional files for all supported x64-based versions of Windows 8
File nameAmd64_0146f02890edb442125584964e07920b_31bf3856ad364e35_6.2.9200.20872_none_686ed95c6897c69b.manifest
File versionNot Applicable
File size710
Date (UTC)08-Nov-2013
Time (UTC)13:09
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_microsoft-windows-devicesetupmanager_31bf3856ad364e35_6.2.9200.20872_none_cc6420ba62f8ad98.manifest
File versionNot Applicable
File size20,141
Date (UTC)08-Nov-2013
Time (UTC)13:09
SHA-1 hashNot Applicable
MD5 hashNot Applicable

↑ Back to the top


References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2908802
Revision : 1
Created on : 1/7/2017
Published on : 3/9/2015
Exists online : False
Views : 282