In this post I would use Perfview /ETW to diagnose the delayed start-up of visual studio.
To analyze the problem start-up VS within Perfview as a run command
This would launch visual studio and collect etw traces. I have also enabled CodeMarkers , which is ETW traces for Visual Studio in case if you want to trace any extensions performance.
After it completes I choose the CPU Stacks and filtered with devenv.exe process.
On the CPU window I choose call-tree tab which displays the threads.The most amount of time is spent on the start-up thread and that is what we want to zoom into.
When I expanded it does not show the information and everything is grouped into OTHER which does not help me.
The reason for that is perfview groups call-stacks for better viewing. I cleared the “groupparts” textbox and then expanded the start-up thread.
From the call-stacks I could make almost 42% of time is spent on Xamarin and DevExpress extensions within VS. Now I could turn them off and have a better performance.
Perfview is great tool for identifying where the time is being spent!