How does DISM /Cleanup-Image with /ResetBase remove "permanent" packages?

Using DISM to try to remove a superseded package that has been marked as "permanent" results in the following error:

Spoiler

Code:

>dism /online /RemovePackage /PackageName:Package_for_KB2939471~31bf3856ad364e35~x86~~6.3.1.0

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

Processing 1 of 1 - An error occurred - Package_for_KB2939471 Error: 0x800f0825

Error: 0x800f0825

DISM failed. No operation was performed.

For more information, review the log file.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Using "dism /online /Cleanup-Image /StartComponentCleanup", the information in the CBS.log is:

Spoiler

Code:

Skipping package [Package_for_KB2919355~31bf3856ad364e35~x86~~6.3.1.14] since it is permanent
Skipping package [Package_for_KB2919442~31bf3856ad364e35~x86~~6.3.1.8] since it is permanent
Skipping package [Package_for_KB2932046~31bf3856ad364e35~x86~~6.3.1.5] since it is permanent
Skipping package [Package_for_KB2937220~31bf3856ad364e35~x86~~6.3.1.0] since it is permanent
Skipping package [Package_for_KB2937592~31bf3856ad364e35~x86~~6.3.1.0] since it is permanent
Skipping package [Package_for_KB2938439~31bf3856ad364e35~x86~~6.3.1.0] since it is permanent
Skipping package [Package_for_KB2938772~31bf3856ad364e35~x86~~6.3.1.0] since it is permanent
Skipping package [Package_for_KB2939471~31bf3856ad364e35~x86~~6.3.1.0] since it is permanent
Skipping package [Package_for_KB2949621~31bf3856ad364e35~x86~~6.3.2.0] since it has a release-type [Hotfix] that makes it not superseded

Using "dism /online /Cleanup-Image /StartComponentCleanup /ResetBase", the information in the CBS.log is:

Spoiler

Code:

Appl: Evaluating package applicability for package Package_for_KB2939471~31bf3856ad364e35~x86~~6.3.1.0, applicable state: Installed
Appl: Evaluating package applicability for package Package_for_KB2939471_RTM~31bf3856ad364e35~x86~~6.3.1.0, applicable state: Installed
Appl: Evaluating package applicability for package Package_for_KB2939471_RTM_GM~31bf3856ad364e35~x86~~6.3.1.0, applicable state: Installed
Appl: Evaluating package applicability for package Package_1_for_KB2939471~31bf3856ad364e35~x86~~6.3.1.0, applicable state: Absent
Appl: Evaluating package applicability for package Package_2_for_KB2939471~31bf3856ad364e35~x86~~6.3.1.0, applicable state: Installed

External EvaluateApplicability, package: Package_for_KB2939471~31bf3856ad364e35~x86~~6.3.1.0, package applicable State: Installed, highest update applicable state: Superseded, resulting applicable state:Superseded
External EvaluateApplicability, package: Package_for_KB2939471_RTM~31bf3856ad364e35~x86~~6.3.1.0, package applicable State: Installed, highest update applicable state: Superseded, resulting applicable state:Superseded
External EvaluateApplicability, package: Package_for_KB2939471_RTM_GM~31bf3856ad364e35~x86~~6.3.1.0, package applicable State: Installed, highest update applicable state: Superseded, resulting applicable state:Superseded
External EvaluateApplicability, package: Package_1_for_KB2939471~31bf3856ad364e35~x86~~6.3.1.0, Package applicability: Absent.
External EvaluateApplicability, package: Package_2_for_KB2939471~31bf3856ad364e35~x86~~6.3.1.0, package applicable State: Installed, highest update applicable state: Superseded, resulting applicable state:Superseded

Maint: Deepclean: Trying to uninstall package 
Package_for_KB2939471~31bf3856ad364e35~x86~~6.3.1.0

Exec: Uninstall package: Package_for_KB2939471~31bf3856ad364e35~x86~~6.3.1.0
Exec: Uninstall package: Package_for_KB2939471_RTM~31bf3856ad364e35~x86~~6.3.1.0
Exec: Uninstall package: Package_for_KB2939471_RTM_GM~31bf3856ad364e35~x86~~6.3.1.0
Exec: Uninstall package: Package_2_for_KB2939471~31bf3856ad364e35~x86~~6.3.1.0

Maint: Deepclean: packages removed: 1

So, how is the package being removed if it marked as permanent?

 

Here is my list of updates for Windows 8.1 Pro with Update (2014, December 12):

Baseline Source: IR3_CCSA_{X86|X64}FRE_EN-US_DV9 install.wim (index:1)

x86 ISO File Name: en_windows_8.1_with_update_x86_dvd_4065105.iso
SHA-1: 54B8572556B316A6BECE54C5033564E3296F5951

x64 ISO File Name: en_windows_8.1_with_update_x64_dvd_4065090.iso
SHA-1: 4652DC6EBFEBE02C6A63E167C36E3FAEDFB93999


9(x86)/9(x64) baseline updates included in source install.wim:

Spoiler

Code:

KB2919442     Servicing Stack Update, prerequisite for KB2919355
KB2919335     Windows 8.1 Update
KB2932046{d}  Feature Pack for Windows 8.1 Update
KB2937592{d}  Feature Pack for Windows 8.1 Update
KB2938439{d}  Feature Pack for Windows 8.1 Update
KB2949621-v2  Hotfix for Windows 8.1 Update
KB2937220
KB2938772
KB2939471     Refer to comments below.

There is no information on KB2937220 and KB2938772, and neither .msu nor .cab files are available. So, the Windows 8.1 RTM install.wim cannot be used as a "baseline" install.wim.

KB2949621-v2 and KB2939471 are superseded by KB2934018, but are not removed using "dism /online /Cleanup-Image /StartComponentCleanup". KB2939471 is removed using "dism /online /Cleanup-Image /StartComponentCleanup /ResetBase" as mentioned in the 1st post. So, DISM does not always remove "permanent" superseded updates (packages). Hotfixes are specifically skipped. By removing the <permanence="permanent"> setting from the <package identifier=KBnumber> line in the %windir%\servicing\Packages\*KBnumber*.mum files, sometimes a "permanent" update can be uninstalled, but not always.

So, the question is, what is DISM doing differently with the /ResetBase option to remove "permanent" packages. I would like to remove KB2949621-v2 and KB2939471 to have a "clean" Windows 8.1 Update install.wim before integrating the following updates, which are post-Windows 8.1 Update. The IR4 install.wim(esd) has updates included that have already been replaced and superseded.


7(x86)/7(x64) baseline updates that are integrated in order listed:

Spoiler

Code:

Update 14-04:    Update 14-11:
-------------    -------------
KB3012199{a}!    KB3000850
KB2920189{b}!    KB3003057#
KB3013769{c}^    KB3014442
KB2934018{d}

32(x86)/32(x64) additional updates that are integrated:

Spoiler

Code:

KB2894852-v2*    KB2967917^          KB2978122*       KB3008923{g}#
KB2898847*       KB2968296*          KB2979573*       KB3008925@
KB2898850+       KB2972103-v2*       KB2979576+       KB3011110-v2{h}%
KB2899189&       KB2972213*          KB2989930        KB3011780
KB2954879-v2     KB2973114*          KB2994290=       KB3013126
KB2962409^       KB2976536?          KB2995518{f}     KB3013375{i}*
KB2966826*       KB2976978-v5{e}~    KB3003667{e}&    KB3013410{j}:
KB2966828*       KB2977765+          KB3004394        KB3013816

18(x86)/18(x64) replaced updates that are integrated to satisfy WU:

Spoiler

Code:

KB2955164^       KB2965142           KB2976627{m}#    KB2995388^
KB2958262        KB2965500{l}        KB2980654{n}$    KB2998174
KB2959977{k}     KB2971203           KB2984006^       KB3002885{q}
KB2961072        KB2973351           KB2993100{o}
KB2962140        KB2975719^          KB2995004{p}

5 updates that cannot be integrated; install using SETUPCOMPLETE.CMD:

Spoiler

Code:

KB2267602     Definition Update for Windows Defender
KB2881553{r}  English Input Personalization Dictionary (16.1.1261.1)
KB2990967{s}  OneDrive serviceability fix (2014/09/23)
KB3011970{t}  Microsoft Silverlight 5.1.31211.0 (2014/12/12)
KB890830      Malicious Software Removal Tool - December 2014

Symbols key; also refer to NOTES section:

Spoiler

Code:

^  (7x) Monthly update rollup for Windows 8.1
!  (2x) Update that cannot be uninstalled
&  (2x) Update for Microsoft Camera Codec Pack
~  (1x) Compatibility update for systems participating in the WinCEIP
$  (1x) OneDrive reliability update rollup - July 2014
?  (1x) Platform update for Windows Defender - November 2014
=  (1x) Language Interface Pack - November 2014
:  (1x) Cumulative time zone update - December 2014
#  (3x) Cumulative Security Update for Internet Explorer 11
@  (1x) Security Update for Internet Explorer Flash Player
* (11x) Security Update for Microsoft .Net Framework 3.5
+  (3x) Security Update for Microsoft .Net Framework 4.5.1 and 4.5.2
%  (1x) Microsoft .NET Framework 4.5.2 for Windows 8.1 (2014/11/25);
        the .msu file is extracted from Offline Installer (KB3009678)

NOTES:

Spoiler

Code:

Update 14-04: April 2014 Windows 8.1 Update (KB2919355); revised
              with prerequisite updates KB3012199 (2014/12/09) and
              KB2920189 (2014/11/11) replacing KB2989647.  Also,
              with the December update rollup KB3013769 (2014/12/09)
              replacing KB2959977.  However, KB2959977 still needs
              to be installed to satisfy Windows Update (WU).

Update 14-11: November 2014 Cumulative Update Rollup (KB3000850);
              including the replaced update KB3003057, which is the
              Cumulative Security Update for Internet Explorer 11,
              because it still needs to be installed to satisfy
              Windows Update (WU).  KB3003057 also can be downloaded
              separately from the Microsoft Download Center and the
              Microsoft Update Catalog.

{a} Supersedes KB2989647, KB2975061, KB2969339, and KB2919442.
    KB3012199 does not require KB2919355 as a prerequisite, although
    the Microsoft Support Article ID 3012199 indicates that it does.
{b} Re-released 2014/11/11 to bundle KB2975061.  However, KB2975061
    is superseded by KB3012199, and does not need to be integrated.
    KB2920189 requires KB2919355 as a prerequsite.
{c} Supersedes KB3008188, KB2989542, and KB2959977.
{d} Feature Pack is not listed with the Installed Updates.  Use
    administrator command: dism /online /Get-Packages /Format:Table
    to verify Feature Pack install status and date.
{e} Cannot be downloaded from the Microsoft Download Center,
    but can be downloaded from the Microsoft Update Catalog.
{f} Was listed in the Microsoft Support Article ID 2984006, but
    cannot be downloaded from the Microsoft Download Center or
    the Microsoft Update Catalog.  For download links, refer to
    My Digital Life Forums, Thread: Windows 8.1 Hot-Fix Repository,
    Page: 172, Post: #1711, Date: 2014/09/10, Member ID: abbodi1406.
{g} Replaces KB3003057 bundled with the November 2014 Update Rollup
    (KB3000850).
{h} Hotfix rollup that replaces KB2934520, KB2978041, and KB2978126.
    For download links, refer to My Digital Life Forums, Thread:
    Windows 8.1 Hot-Fix Repository, Page: 221, Post: #2201,
    Date: 2014/11/25, Member ID: ricktendo64.  Or, request download
    link via e-mail from Microsoft Support using URL: 
    support2.microsoft.com/hotfix/KBHotfix.aspx?kbnum=3009678
    &kbln=en-US.
{i} Hotfix rollup for Microsoft .Net Framework 3.5.  For download
    links, refer to My Digital Life Forums, Thread: Windows 8.1
    Hot-Fix Repository, Page: 221, Post: #2201, Date: 2014/11/25,
    Member ID: ricktendo64.  Or, request download links via e-mail
    from Microsoft Support using URL: support2.microsoft.com/
    hotfix/KBHotfix.aspx?kbnum=3013375&kbln=en-US.
{j} Update that supersedes the August 2014 cumulative time zone
    update (KB2981580), the September 2014 time zone update for
    Russia (KB2998527), and the 2014 DST change for Fiji time zone
    hotfix (KB3011843-v2).
{k} Bundled with the April 2014 Windows 8.1 Update (KB2919355) when
    downloaded from the Microsoft Update Catalog; and also can be
    downloaded separately from the Microsoft Download Center.  If
    KB2959977 is not installed, when a  Windows Update check is
    performed, it will not be listed separately.  Instead it will
    be bundled with "Windows 8.1 Update (KB2919355)".
{l} Bundled with the May 2014 update rollup (KB2955164) when
    downloaded from the Microsoft Update Catalog.  KB2965500
    cannot be downloaded from the Microsoft Download Center.  If
    KB2965500 is not installed, when a  Windows Update check is
    performed, it will not be listed separately.  Instead it will
    be bundled with "Update for Windows 8.1 (KB2955164)".
{m} Superseded by KB3008923; was indicated by Microsoft as replaced
    by KB3003057.  However, this update also was needed because it
    contains the inetres.adml file needed to prevent an error when
    GPEDIT.MSC is run.
{n} Bundled with the June 2014 update rollup (KB2962409) when
    downloaded from the Microsoft Update Catalog.  KB2980654
    is not bundled with the June 2014 update rollup (KB2962409)
    when downloaded from the Microsoft Download Center, but must
    be downloaded separately from the Microsoft Download Center.
    If KB2980654 is not installed, when a  Windows Update check is
    performed, it will not be listed separately.  Instead it will
    be bundled with "Update for Windows 8.1 (KB2962409)".
{o} Bundled with the August 2014 update rollup (KB2975719).
    If KB2993100 is not installed, when a  Windows Update check is
    performed, it will not be listed separately.  Instead it will
    be bundled with "Update for Windows 8.1 (KB2975719)".
{p} Bundled with the September 2014 update rollup (KB2984006) and
    also bundled with the August 2014 update rollup (KB2975719);
    KB2995004 was added on 2014/09/09 and replaces KB2990532.
    If KB2995004 is not installed, when a Windows Update check is
    performed, it will not be listed separately.  Instead it will
    be bundled with both "Update for Windows 8.1 (KB2984006)" and
    "Update for Windows 8.1 (KB2975719)".
{q} Supersedes KB2994897 that is bundled with the September 2014
    update rollup (KB2984006).
{r} This update is applied only to devices that have the English
    language pack installed as an input language and that have the
    touch keyboard enabled.  This update is delivered by Windows
    Update only if you use the touch keyboard to type at least 50
    words per day.  The update can be downloaded from the Microsoft
    Update Catalog, however, it cannot be downloaded from the
    Microsoft Download Center.  Install by using .msi file extracted
    from the .cab file downloaded from the Microsoft Update Catalog.
{s} The .msu file contains a .exe file in addition to a .cab file;
    and the .exe file must be installed before the .cab file.  So,
    KB2990967 cannot be properly integrated into an offline image.
{t} Supersedes Security Update for Microsoft Silverlight (KB2932677)
    and Update to Microsoft Silverlight (KB2977218).  Do not install
    Microsoft Silverlight 5.1.31010.0 (KB3011970), which was released
    2014/12/09, becaused it is defective.  If KB3011970 is not
    installed, when a Windows Update check is performed, KB2977218
    will be listed instead of KB3011970.

By carefully choosing the order that the updates are integrated, no updates are removed by using the command "dism /online /Cleanup-Image /StartComponentCleanup" and only KB2939471 is removed by adding the "/ResetBase" option to the DISM command. Additionally, Windows Update is satisfied, meaning no updates are listed, except for those updates not installed by the running the SETUPCOMPLETE.CMD command.

So, the question remains: What is DISM doing differently with the /ResetBase option to remove "permanent" packages?

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Thank for finding the Registry key and value to change. I really appreciate the time and effort it took to find a solution.

I tested the Registry fix on a live system also, so I can understand your solution. I do understand how to edit the registry in the Recovery Environment (load SOFTWARE hive, etc) so I usually edit the registry offline when there are online permission issues. It does require a system restart before and after editing the Registry.

I will try changing the registry on an offline system to uninstall KB2949621-v2 and KB2939471 before integrating the new updates. Obviously, KB2919442 would not be included since it is the Servicing Stack and is needed before KB3012199 would be installed.

Thanks again abbodi1406.