Symptoms

When you use Group Policy Software Installation to uninstall a managed application in a Windows Server 2012-based or a Windows Server 2012 R2-based domain, the application isn’t uninstalled from all domain members the next time that a user logs on or restarts the computer.  

Note This issue doesn’t occur if Uninstall this application when it falls out of the scope of management is selected under Deployment options.

Resolution

To resolve this issue, install the update rollup 2903939 or 2876415, or install the hotfix that is described in this article.

Note After you apply the update or hotfix, you still can’t uninstall applications that were installed by using Group Policy Software Installation before the update or hotfix was applied. To uninstall these applications, use logon scripts, or select the Uninstall this application when it falls out of the scope of management option.

Update information

To resolve this issue in Windows Server 2012 R2, install update rollup 2903939. For more information about how to obtain this update rollup package, click the following article number to go to the article in the Microsoft Knowledge Base:

2903939 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: December 2013  
To resolve this issue in Windows Server 2012, install update rollup 2876415.  For more information about how to obtain update rollup 2876415, click the following article number to view the article in the Microsoft Knowledge Base:

2876415 Windows RT, Windows 8, and Windows Server 2012 update rollup: September 2013

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, go to the following Microsoft website:

http://support.microsoft.com/contactus/?ws=supportNote 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.

PrerequisitesTo apply this hotfix, you must be running Windows Server 2012.

Registry information To apply this hotfix, you do not have to make any changes to the registry.

Restart requirementYou must restart the computer after you apply this hotfix.

Hotfix replacement informationThis 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 Server 2012 file information notesImportant 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:

    Version

    Product

    Milestone

    Service branch

    6.2.920 0.16 xxx

    Windows Server 2012

    RTM

    GDR

    6.2.920 0.20 xxx

    Windows Server 2012

    RTM

    LDR

  • 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 2012" 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 2012

File name

File version

File size

Date

Time

Platform

Appmgr.dll

6.2.9200.16666

459,776

13-Jul-2013

06:15

x64

Appmgr.dll

6.2.9200.20774

459,776

13-Jul-2013

07:49

x64

Appmgr.dll

6.2.9200.16666

366,592

13-Jul-2013

04:23

x86

Appmgr.dll

6.2.9200.20774

366,592

13-Jul-2013

04:41

x86


Status

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

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

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012

File name

Amd64_4da1734cf1277691a40dc71307847067_31bf3856ad364e35_6.2.9200.16666_none_3693568bd183d2cb.manifest

File version

Not applicable

File size

1,072

Date (UTC)

16-Jul-2013

Time (UTC)

18:38

Platform

Not applicable

File name

Amd64_550f7a00a35dd56e7b46841e7da0858a_31bf3856ad364e35_6.2.9200.20774_none_2ca6f2da2eceb3e0.manifest

File version

Not applicable

File size

1,072

Date (UTC)

16-Jul-2013

Time (UTC)

18:38

Platform

Not applicable

File name

Amd64_microsoft-windows-g..policy-admin-appmgr_31bf3856ad364e35_6.2.9200.16666_none_539aa9843fab9ddd.manifest

File version

Not applicable

File size

13,479

Date (UTC)

13-Jul-2013

Time (UTC)

07:14

Platform

Not applicable

File name

Amd64_microsoft-windows-g..policy-admin-appmgr_31bf3856ad364e35_6.2.9200.20774_none_541775cf58d326ea.manifest

File version

Not applicable

File size

13,479

Date (UTC)

13-Jul-2013

Time (UTC)

08:47

Platform

Not applicable

File name

Update-bf.mum

File version

Not applicable

File size

1,803

Date (UTC)

16-Jul-2013

Time (UTC)

18:38

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

1,833

Date (UTC)

16-Jul-2013

Time (UTC)

18:38

Platform

Not applicable

File name

X86_microsoft-windows-g..policy-admin-appmgr_31bf3856ad364e35_6.2.9200.16666_none_f77c0e00874e2ca7.manifest

File version

Not applicable

File size

13,473

Date (UTC)

13-Jul-2013

Time (UTC)

05:14

Platform

Not applicable

File name

X86_microsoft-windows-g..policy-admin-appmgr_31bf3856ad364e35_6.2.9200.20774_none_f7f8da4ba075b5b4.manifest

File version

Not applicable

File size

13,473

Date (UTC)

13-Jul-2013

Time (UTC)

06:33

Platform

Not applicable


Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×