I have deployed my .NET assemblies with x-copy for years, without any issue. Since last week, we have a small team that which has the task of build a setup that includes .NET assemblies and exe and c++ legacy exe and dll (more than 200 files). After the first installation, I have an issue on my wpf application: the startup time is very huge.

I have profiled one of my wpf application (ps: .NET assemblies are both GACed and NGened) with procmon and I have seen that the process makes multiples operations (see attached screenshot) on all others unrelated (> 200) files and I think that this the main cause of slow application startup time.

Is this related to .NET publisher policy? How I can disable this behavior to makes my application again fast?

Thanks in advance!