SharePoint 2019 Products Configuration Wizard issue due to orphaned feature

SGH 1,221

Failed to upgrade SharePoint Products using GUI. How to fix this ?

This is a critical task. You have to fix the failures before you can continue. Follow this link for more information about how to troubleshoot upgrade failures: https://go.microsoft.com/fwlink/?LinkId=866803

An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information:
Feature (Name = [Form_webservice], Id = [1bb9d6bf-3d6c-a83b-685f-43708c2d885c], Description = [Microsoft InfoPath Form template.], Install Location = [FT-01-1bb9d6bf-3d6c-a83b-685f-43708c2d885c]) is referenced in database [WSS_Content_Intranet], but isn't installed on the current farm. The missing feature might cause upgrade to fail. If necessary, please install any solution that contains the feature and restart upgrade. (EventID:ajxkh)

Only solution is running the below powershell.

psconfig.exe -cmd helpcollections -installall -cmd secureresources -cmd services -install -cmd installfeatures -cmd applicationcontent -install -cmd upgrade -inplace b2b -force -wait

Elsie Lu_MSFT 9,761 Reputation points

2021-07-27T07:18:41.607+00:00

Hi @SGH , does the issue still exist after running this powershell?
SGH 1,221 Reputation points

2021-07-27T07:28:02.983+00:00

Previously during the Feb 2021 Security update, the same issue came. Then run the above power shell and it worked. This time, same issue came for June 2021 Security update. So the issue exists even after running powershell. But the upgrade works fine.
Elsie Lu_MSFT 9,761 Reputation points

2021-07-28T09:18:50.177+00:00

Hi @SGH , this is a quick note to let you know that we are testing this issue. Any updates will be posted here. Thanks for your patience.
SGH 1,221 Reputation points

2021-07-28T09:22:24.057+00:00

Is there any latest update on this. There are third party tools for removing Orphaned Feature.

Also there is another requirement of migrating SharePoint 2016 to SharePoint 2019. The custom solutions used in 2016 will not be used in 2019. However, when we do an attach and dettach database approach, these will be deployed as orphaned features.

Please suggest and advise a proper approach for this.