-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Extension 2.2.0.11 fails to instal on Visual Studio 15.2.16430.4 #987
Comments
Same issue as #986 |
@paulomorgado if it's fine with you, we can take this discussion to #986 since I've already replied there. Feel free to reopen if you prefer a separate thread. |
@paulomorgado for the issue where the extension failed to install, could you please run http://aka.ms/vscollect and share the logs with us? That will help us figure out what went wrong with the install. |
Reopening this so other users can track the issue while we're trying to figure out what's going on. |
For reference: while we're not sure yet what's going on, if you run into this problem please follow the instructions above for collecting logs. You can send them to [email protected] if you prefer not to share them here. A workaround to this problem is to uninstall the extension first. If you uninstall from the VS Extensions and Updates menu, you will be taken to the VS installer to uninstall the extension from there (since it was originally installed from the VS installer). Once uninstalled, you can install the latest one from the VS gallery via the Extensions and Updates menu. |
The logs are 1360705 bytes. Do I upload them somewhere? The extension installs just fine in the preview instance I have on both machines. On the release instance it failed on 15.1 and it's failing on 15.2. It might be related to some extension I might have installed on the release instance and not on the preview instance. |
@paulomorgado can you put it on a OneDrive location or somewhere we can access? Thank you! |
Justa sent an e-mail to [email protected] mentioning issues 986 and 987. Please, acknowledge. |
@paulomorgado I got the logs from @grokys, thanks! Trying to narrow down the issue here, can you tell me if you see a folder named "wyhgzaqi.mh1" under Common7\IDE\Extensions for all your instances of VS? If so, could you spit out the contents of that directory (including full path), and let me know if it's the same instance of VS that the extension update failed? Thanks for your help! |
I have no such directory on my systems. |
By the way. I tried to uninstall the GitHub extensions and it also fails. |
@paulomorgado Ok so we're going to have to get a bit more radical with cleaning up whatever the VS installer did to your system that's causing this. If you're running multiple flavors of VS 2017, then you probably have one or more of the following directories on your system:
Shutdown all instances of VS and try the following: Go to each VS 2017 directory (like the ones above) and do a search for Once you've removed all the directories, open a developer command prompt as administrator for each of the VS installations (right click on the developer command prompt short and click
This command will take a while to run. After you've done this to all your VS 2017 installations, run VS so that the catalog is rebuilt. If things go well, the extension will no longer be installed and you should not have errors in the Team Explorer area. After that, you should have no problems installing the extension from the Extensions and Updates menu in VS. |
Strangely enough, I have 2 of those for the release instance and one for the preview:
|
I decided to just delete the directories for the release instance and normally start VS2017. VS complained a bit, but the extension was now available for installation and installed without any issues. Except that it didn't stick. I ended up running ``devenv /setup** (nothing happened) and devenv again to install the extension, but still nothing. Do I need to remove that DLL for all instances? |
@paulomorgado You have two versions in the release instance because you likely installed 2.2.0.10 from the VS installer and then updated to 2.2.0.11 via the gallery, and VS often doesn't delete old versions - and if the old installation failed to uninstall but the new one got installed somehow, then that could cause the problems you got. It's also possible that the installations on the previews are messing up the release VS, or vice versa. If the preview instances are working properly, perhaps uninstalling the extensions from them will fix the release instance, so it's probably worth trying that. If it doesn't, you should probably delete all the directories that you have with the extension, just to get things back to a sane state. DO NOT run VS afterwards until you first run |
@paulomorgado, I would also add that you should remove the GitHub extension for Visual Studio from VS Installer prior to removing the DLLs to make sure you don't corrupt the setup state. To do so, go to VS Installer, and then the Individual Component tab, unselect "GitHub extension for Visual Studio", and then click Modify. |
Yeah, @tinaschrepfer! That's what I was missing. Otherwise, the extension installer happily reports success and does nothing. |
@shana post works great and fixed to problem. thx. For some reason, there was 2 installations of GitHub Extension in my single Visual Studio 2017 installation. |
I'm going to close this issue as it looks like the original issue has been fixed. For anyone having these problems in future, please look at #1394. |
The extension fails to install with the following log:
After that, the Team Explorer window shows this:
The text was updated successfully, but these errors were encountered: