I can reliably reproduce this issue now and finally managed to capture the extension log as well. Somehow starting VS with the /log switch wouldn't create the log file at the default (AppData/Roaming/...) location even though the error dialog that popped up indicated exactly that. I had to specify the log file path explicitly for the logging to kick in. Anyhow, please find ActivityLog.xml attached. To reproduce the issue I have to start two VS instances. The second instance triggers a "Loading user settings (...)" dialog while starting up (and this is the root cause of the issue, I think), then the usual error dialog pops up saying that there may be problems with some extensions. Records 690, 691, and 693 contain the pertaining exceptions.
ActivityLog.zip
I can reliably reproduce this issue now and finally managed to capture the extension log as well. Somehow starting VS with the /log switch wouldn't create the log file at the default (AppData/Roaming/...) location even though the error dialog that popped up indicated exactly that. I had to specify the log file path explicitly for the logging to kick in. Anyhow, please find ActivityLog.xml attached. To reproduce the issue I have to start two VS instances. The second instance triggers a "Loading user settings (...)" dialog while starting up (and this is the root cause of the issue, I think), then the usual error dialog pops up saying that there may be problems with some extensions. Records 690, 691, and 693 contain the pertaining exceptions.
ActivityLog.zip