@Philippe NONORGUES ,
Use a SQL query to find the location of the missing setup file and then a Window PowerShell script to remove the file reference from SharePoint Sever.
To reduce the risk of locking or other performance issues it is preferable to run these queries should be against backup copy or snapshot of the database.
SQL sample for listing setup file information:
USE SP_ContentPortal(backup or snapshot)
SELECT id, SiteID, DirName, LeafName, WebId, ListId
FROM AllDocs (NOLOCK) where SetupPath = 'Features\BCEE.recettage....\Workflow.xaml'
PowerShell sample for removing setup files by ID:
#File Information
$setupFileID = "xxx"
$siteID = "xxx"
$WebID = "xxx"
#Get file
$site = Get-SPSite -Identity $siteID
$web = Get-SPWeb -Identity $WebID -Site $siteID
$file = $web.GetFile([GUID]$setupFileID)
#Report on location
$filelocation = "{0}{1}" -f ($site.WebApplication.Url).TrimEnd("/"), $file.ServerRelativeUrl
Write-Host "Found file location:" $filelocation
#Delete the file, the Delete() method bypasses the recycle bin
$file.Delete()
$web.dispose()
$site.dispose()
More information for your reference:
https://sharepointhelpmm.wordpress.com/2018/05/08/post-upgrade-cleanup-missing-server-side-dependencies/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.