If you’re patching a feature or features of a Windows Installer package and see that a feature you know to be installed locally is now advertised, look for the following in your Windows Installer log:<\/p>\n
MSI (c) (B8:C0) [12:00:00:000]: SELMGR: ComponentId ‘{01234567-89AB-CDEF-0123-456789ABCDEF}’ is registered to feature ‘FeatureA’, but is not present in the Component table. Removal of components from a feature is not supported!
\nMSI (c) (B8:C0) [12:00:00:000]: SELMGR: Removal of a component from a feature is not supported<\/p>\n
The reason is documented is\n\nChanging the Product Code<\/a> in the Windows Installer SDK: components can be\nadded to new features – or existing features starting with Windows Installer 2.0\n– but cannot be removed. In order to remove the component or make a change that\nwould otherwise require a change in the component code – which is no different\nthan removing one component and adding another – the\n\n This applies even with obsolescence and supersedence. Recall in\nHow\nPatching Works<\/a> that when you obsolesce or supersede a previous patch Windows\nInstaller removes the patch transform from the in-memory view of the product.\nThis effectively removes a component from a feature or features and violates\nupgrade components rules. The result is that your feature you’re trying to patch\nbecomes advertised and it will not be patched because – as Windows Installer\nsees it – it’s not installed.<\/p>\n This makes sense if you think about it. To obsolesce or supersede another\npatch the new patch must contain everything from the old patch that it’s\nreplacing. This includes not only files, registry values, and the like but\ncomponents as well. By definition, if you install a new component any obsolescing or\nsuperseding patch must contain that component as well.<\/p>\n If you’re adding new components that are specific to individual patches,\nconsider instead using transitive component conditions without supersedence to\neffectively remove the component when the new patch is installed. This is one solution I presented in\nA Better\nWay of Working with ARPSYSTEMCOMPONENT<\/a>.<\/p>\n To catch the violation to the upgrade component rules you can pass the public\n\n If you’re patching a feature or features of a Windows Installer package and see that a feature you know to be installed locally is now advertised, look for the following in your Windows Installer log: MSI (c) (B8:C0) [12:00:00:000]: SELMGR: ComponentId ‘{01234567-89AB-CDEF-0123-456789ABCDEF}’ is registered to feature ‘FeatureA’, but is not present in the Component table. […]<\/p>\n","protected":false},"author":389,"featured_media":3843,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[15,20,23,40],"class_list":["post-2513","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-diagnosing","tag-installation","tag-logging","tag-troubleshooting"],"acf":[],"blog_post_summary":" If you’re patching a feature or features of a Windows Installer package and see that a feature you know to be installed locally is now advertised, look for the following in your Windows Installer log: MSI (c) (B8:C0) [12:00:00:000]: SELMGR: ComponentId ‘{01234567-89AB-CDEF-0123-456789ABCDEF}’ is registered to feature ‘FeatureA’, but is not present in the Component table. […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/posts\/2513","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/users\/389"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/comments?post=2513"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/posts\/2513\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/media\/3843"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/media?parent=2513"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/categories?post=2513"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/tags?post=2513"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}ProductCode<\/code> property<\/a> must be changed, which constitutes a major upgrade.<\/p>\nMSIENFORCEUPGRADECOMPONENTRULES<\/code> property<\/a> or set the\nEnforceUpgradeComponentRules\npolicy<\/a> that will affect any install on the machine. This will cause small\nand minor updates to fail with either\n\nWindows Installer error<\/a> 2771 if a component is removed from a feature (which\nalso includes if a component GUID is changed since that would technically\nconstitute a new component), or error 2772 if the feature tree is rearranged\nwith the exception of adding a new feature as a leaf feature to an existing\nfeature. In either case\nWindows error<\/a> ERROR_INSTALL_FAILURE<\/code> (1603) is returned\nfrom the process or Windows Installer API.<\/p><\/p>\n","protected":false},"excerpt":{"rendered":"