| T O P I C R E V I E W |
| swinefeaster |
Posted - Aug 06 2021 : 1:28:30 PM
I've only been able to install VAX after a clean reboot. Closing VS and killing the devenv.exe is not sufficient, the installer just hangs waiting.
What other processes can I kill manually to avoid a reboot?
thanks |
| 5 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Jul 09 2024 : 07:56:41 AM
After a reboot?! That really is a surprise, I don't think I have ever seen this problem before.
If you have the time to study this for a little bit, could you reboot and then run Process Explorer, which can be downloaded, or run directly, from here:
https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer
unlike task manager process explorer shows the parent process, so you can look to see if the "Microsoft.ServiceHub.Controller.exe" has a parent process. I am wondering if something is being run on start up that would explain why this is running after a reboot without having first loaded Visual Studio. |
| tony.riviere |
Posted - Jul 08 2024 : 2:53:01 PM
I got the error too with the last installer 2522, here is the blocking process:
08/07/2024 20:49:34 - Blocking processes:
08/07/2024 20:49:34 - Microsoft.ServiceHub.Controller.exe (18168) : C:\Program Files\Microsoft Visual Studio\2022\Preview\Common7\ServiceHub\Controller\Microsoft.ServiceHub.Controller.exe
Note that it happens right after a reboot, nothing launch but VAX installer. |
| feline |
Posted - Jul 05 2024 : 06:09:23 AM
The blocking process problem used to be really rare, but seems to be becoming a lot more common of late. We are looking into adding an option to the installer to kill the problem processes when the installer gets blocked:
case=164496 |
| foxmuldr |
Posted - Jul 04 2024 : 1:43:52 PM
In my case it was vctip.exe. It's happened every time I go to update VAX in recent versions.
Can I suggest you add a note to the installer on the "Close all instances of Visual Studio" to check the %TEMP%\vsix*.log files to see which process(es) is(are) blocking?
Would be helpful.
--
Rick C. Hodgin |
| feline |
Posted - Aug 09 2021 : 07:00:55 AM
There are several processes that can cause this. Can you please look in your %TEMP% directory for files called:
vsix*.log
the most recent file(s) should tell you which process is being picked up, which is stopping the installer from running. |
