New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VSIX install failed #1532

Open
Licantrop0 opened this Issue Dec 7, 2017 · 37 comments

Comments

Projects
None yet
@Licantrop0

Licantrop0 commented Dec 7, 2017

<WTS_team>

What happened
Currently the belief is, on updating, the prior version fails to uninstall for some reason, (maybe a file lock) but the new version still installs and updates the VS configuration. This gets VS extension manager into a state where it sees both but can't uninstall the older version.

First item we need in helping to debug are logs:
We’ll need the full setup logs by running https://aka.ms/vscollect.exe (please place the zip here in the issue). %temp% folder and copy VSLogs.zip. If that fails, please email me them at crutkas@microsoft.com We need the install logs to help see why we are getting into this weird state.

Manual workaround:

  1. Look at logs and validate folder. should be in: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2017\ENTERPRISE\COMMON7\IDE\EXTENSIONS\ with a folder something in tune of: INU2PILL.SXO
  2. delete folder
  3. Open VS command line prompt in admin mode
  4. Run command: devenv /updateconfiguration
  5. VS will now see the newer version / be able to update.

</WTS_team>

Tried to update to latest version, got these screens:
image
image

logs:
VSIXInstaller_c55b6715-c73c-434c-8205-b369bf257f49.log

@sibille

This comment has been minimized.

Show comment
Hide comment
@sibille

sibille Dec 11, 2017

Member

It seems that the VSIX installer did not fully uninstall the previous WTS Version (1.4).
Try to uninstall WTS.
If it fails, try to manually delete the content from C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2017\ENTERPRISE\COMMON7\IDE\EXTENSIONS\INU2PILL.SXO
Then try to install WTS 1.5 again from the gallery, the marketplace or using VS.

If you encounter any issues please let us know.

Member

sibille commented Dec 11, 2017

It seems that the VSIX installer did not fully uninstall the previous WTS Version (1.4).
Try to uninstall WTS.
If it fails, try to manually delete the content from C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2017\ENTERPRISE\COMMON7\IDE\EXTENSIONS\INU2PILL.SXO
Then try to install WTS 1.5 again from the gallery, the marketplace or using VS.

If you encounter any issues please let us know.

@crutkas

This comment has been minimized.

Show comment
Hide comment
@crutkas

crutkas Dec 13, 2017

Member

@sibille can we make the vsix installer more robust in any way?

Member

crutkas commented Dec 13, 2017

@sibille can we make the vsix installer more robust in any way?

@sibille

This comment has been minimized.

Show comment
Hide comment
@sibille

sibille Dec 14, 2017

Member

The vsix installation process is managed by a Visual Studio, I think there is nothing we can do here.

Member

sibille commented Dec 14, 2017

The vsix installation process is managed by a Visual Studio, I think there is nothing we can do here.

@graymatter00

This comment has been minimized.

Show comment
Hide comment
@graymatter00

graymatter00 Dec 14, 2017

Same problem here, using VS 2017 Community.

Tried uninstalling via the Extensions and Updates window. This failed with same error message as the attempted install of the new version.

Had to delete the INU2PILL.SXO folder, then uninstall old version via the Extensions and Updates window, which now succeeded. Then installed new version via the Extensions and Updates window.

Seems OK now.

graymatter00 commented Dec 14, 2017

Same problem here, using VS 2017 Community.

Tried uninstalling via the Extensions and Updates window. This failed with same error message as the attempted install of the new version.

Had to delete the INU2PILL.SXO folder, then uninstall old version via the Extensions and Updates window, which now succeeded. Then installed new version via the Extensions and Updates window.

Seems OK now.

@ralarcon

This comment has been minimized.

Show comment
Hide comment
@ralarcon

ralarcon Dec 14, 2017

Contributor

Thanks for your feedback @graymatter00, looks like sometimes the VsixInstaller didn't completely remove the old version and need to finish manually. Wonder to understand if the root cause is that any resource is in use while trying to unisntall, but it should not as the uninstall process is launched once the Visual Studio instance is closed...

Contributor

ralarcon commented Dec 14, 2017

Thanks for your feedback @graymatter00, looks like sometimes the VsixInstaller didn't completely remove the old version and need to finish manually. Wonder to understand if the root cause is that any resource is in use while trying to unisntall, but it should not as the uninstall process is launched once the Visual Studio instance is closed...

@v-tbert

This comment has been minimized.

Show comment
Hide comment
@v-tbert

v-tbert Dec 15, 2017

I just hit this too and followed same process as @graymatter00 to resolve it. FWIW I had this same problem with Powershell Pro extension a few months ago. It does sound like VS servicing of VSIX installs needs to be made more robust.

v-tbert commented Dec 15, 2017

I just hit this too and followed same process as @graymatter00 to resolve it. FWIW I had this same problem with Powershell Pro extension a few months ago. It does sound like VS servicing of VSIX installs needs to be made more robust.

@crutkas

This comment has been minimized.

Show comment
Hide comment
@crutkas

crutkas Dec 15, 2017

Member

We're proactively looking into this with Visual Studio.

Member

crutkas commented Dec 15, 2017

We're proactively looking into this with Visual Studio.

@Licantrop0

This comment has been minimized.

Show comment
Hide comment
@Licantrop0

Licantrop0 Dec 16, 2017

@sibille also uninstalling failed:
VSIXInstaller_25bde7d9-a8ea-488e-a5e1-4e344438cb26.log
Had to manually remove the folder, uninstall, and reinstall again like you suggested.

Licantrop0 commented Dec 16, 2017

@sibille also uninstalling failed:
VSIXInstaller_25bde7d9-a8ea-488e-a5e1-4e344438cb26.log
Had to manually remove the folder, uninstall, and reinstall again like you suggested.

@crutkas

This comment has been minimized.

Show comment
Hide comment
@crutkas

crutkas Dec 18, 2017

Member

@Licantrop0 @graymatter00 and @v-tbert.

We’ll need the full setup logs by running https://aka.ms/vscollect.exe (please place the zip here in the issue). %temp% folder and copy VSLogs.zip

VS team has two theories we're trying to validate.

Member

crutkas commented Dec 18, 2017

@Licantrop0 @graymatter00 and @v-tbert.

We’ll need the full setup logs by running https://aka.ms/vscollect.exe (please place the zip here in the issue). %temp% folder and copy VSLogs.zip

VS team has two theories we're trying to validate.

@crutkas

This comment has been minimized.

Show comment
Hide comment
@crutkas

crutkas Dec 18, 2017

Member

if you guys feel that you don't want to publicly share them, you can put them on onedrive / dropbox and directly email me a link, crutkas@microsoft.com

Member

crutkas commented Dec 18, 2017

if you guys feel that you don't want to publicly share them, you can put them on onedrive / dropbox and directly email me a link, crutkas@microsoft.com

@v-tbert

This comment has been minimized.

Show comment
Hide comment
@v-tbert

v-tbert Dec 18, 2017

v-tbert commented Dec 18, 2017

@crutkas

This comment has been minimized.

Show comment
Hide comment
@crutkas

crutkas Dec 18, 2017

Member

@v-tbert i believe it will as it is grabbing logs. I'll mention that to the VS team that you did a manual workaround when looking at your logs

Member

crutkas commented Dec 18, 2017

@v-tbert i believe it will as it is grabbing logs. I'll mention that to the VS team that you did a manual workaround when looking at your logs

@crutkas

This comment has been minimized.

Show comment
Hide comment
@crutkas

crutkas Dec 19, 2017

Member

this is odd, i used to hit issues uninstalling / upgrading on one of my boxes but all "just worked" now

Member

crutkas commented Dec 19, 2017

this is odd, i used to hit issues uninstalling / upgrading on one of my boxes but all "just worked" now

@crutkas

This comment has been minimized.

Show comment
Hide comment
@crutkas

crutkas Dec 19, 2017

Member

got a capture! Also updated the question of where the logs actually are, %temp% folder and copy VSLogs.zip

Member

crutkas commented Dec 19, 2017

got a capture! Also updated the question of where the logs actually are, %temp% folder and copy VSLogs.zip

@crutkas crutkas added the bug label Dec 19, 2017

@crutkas crutkas added this to the 1.7 milestone Dec 19, 2017

@crutkas

This comment has been minimized.

Show comment
Hide comment
@crutkas

crutkas Dec 20, 2017

Member

Worked with the Visual Studio extension team this morning. We know what happened but we don't know why. My log capture was missing the install log on what actually got us into a double install state.

What happened
Currently the belief is, on updating, the prior version fails to uninstall for some reason, (maybe a file lock) but the new version still installs and updates the VS configuration. This gets VS extension manager into a state where it sees both but can't uninstall the older version.

First item we need in helping to debug are logs:
We’ll need the full setup logs by running https://aka.ms/vscollect.exe (please place the zip here in the issue). %temp% folder and copy VSLogs.zip. If that fails, please email me them at crutkas@microsoft.com We need the install logs to help see why we are getting into this weird state.

Manual workaround:

  1. Look at logs and validate folder. should be in: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2017\ENTERPRISE\COMMON7\IDE\EXTENSIONS\ with a folder something in tune of: INU2PILL.SXO
  2. delete folder
  3. Open VS command line prompt in admin mode
  4. Run command: devenv /updateconfiguration
  5. VS will now see the newer version / be able to update.
Member

crutkas commented Dec 20, 2017

Worked with the Visual Studio extension team this morning. We know what happened but we don't know why. My log capture was missing the install log on what actually got us into a double install state.

What happened
Currently the belief is, on updating, the prior version fails to uninstall for some reason, (maybe a file lock) but the new version still installs and updates the VS configuration. This gets VS extension manager into a state where it sees both but can't uninstall the older version.

First item we need in helping to debug are logs:
We’ll need the full setup logs by running https://aka.ms/vscollect.exe (please place the zip here in the issue). %temp% folder and copy VSLogs.zip. If that fails, please email me them at crutkas@microsoft.com We need the install logs to help see why we are getting into this weird state.

Manual workaround:

  1. Look at logs and validate folder. should be in: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2017\ENTERPRISE\COMMON7\IDE\EXTENSIONS\ with a folder something in tune of: INU2PILL.SXO
  2. delete folder
  3. Open VS command line prompt in admin mode
  4. Run command: devenv /updateconfiguration
  5. VS will now see the newer version / be able to update.
@LanceMcCarthy

This comment has been minimized.

Show comment
Hide comment
@LanceMcCarthy

LanceMcCarthy Dec 29, 2017

I attempted the manual workaround and it failed with the same error.

Here are the steps I took:

1 - Confirmed the inu2pill.sxo folder exists (it's empty with the exception of a cache.bin file)
2,3 - Ran dev /updateconfiguration from elevated VS2017 developer CLI
4 - Downloaded a fresh copy of the VSIX from the VS Marketplace here
5 - Ran the downloaded VSIX

The same error occurs.

LanceMcCarthy commented Dec 29, 2017

I attempted the manual workaround and it failed with the same error.

Here are the steps I took:

1 - Confirmed the inu2pill.sxo folder exists (it's empty with the exception of a cache.bin file)
2,3 - Ran dev /updateconfiguration from elevated VS2017 developer CLI
4 - Downloaded a fresh copy of the VSIX from the VS Marketplace here
5 - Ran the downloaded VSIX

The same error occurs.

@crutkas

This comment has been minimized.

Show comment
Hide comment
@crutkas

crutkas Dec 29, 2017

Member

i think i forgot the critical "delete folder"

Member

crutkas commented Dec 29, 2017

i think i forgot the critical "delete folder"

@xasx

This comment has been minimized.

Show comment
Hide comment
@xasx

xasx Dec 30, 2017

Interestingly though, when following the Deletion method, i.e.

  1. delete the sub-dir under Extensions
  2. uninstall the extension from VS

I see that the installation log pretends to have the newer version uninstalled, i.e. the one that could not be upgraded to.

Fail to upgrade:
noupgrade-VSIXInstaller_8ac10232-e03b-40ca-b1d3-4b64f14ecc3a.log

Successfully uninstall after delete:
uninstall-after-delete-VSIXInstaller_1254de33-b513-4aad-b9dd-fdcf5f3e96a7.log

xasx commented Dec 30, 2017

Interestingly though, when following the Deletion method, i.e.

  1. delete the sub-dir under Extensions
  2. uninstall the extension from VS

I see that the installation log pretends to have the newer version uninstalled, i.e. the one that could not be upgraded to.

Fail to upgrade:
noupgrade-VSIXInstaller_8ac10232-e03b-40ca-b1d3-4b64f14ecc3a.log

Successfully uninstall after delete:
uninstall-after-delete-VSIXInstaller_1254de33-b513-4aad-b9dd-fdcf5f3e96a7.log

@Morhpeuss

This comment has been minimized.

Show comment
Hide comment
@Morhpeuss

Morhpeuss Jan 3, 2018

Hi, I have the same problem with the extension. But I didn't find the folder "inu2pill.sxo" under Extensions so I can't delete it.

Morhpeuss commented Jan 3, 2018

Hi, I have the same problem with the extension. But I didn't find the folder "inu2pill.sxo" under Extensions so I can't delete it.

@ralarcon

This comment has been minimized.

Show comment
Hide comment
@ralarcon

ralarcon Jan 3, 2018

Contributor

@Morhpeuss That is because the folder inu2pill.sxo is for other version different from what you have blocked... in the log you should be able to find the exact folder for your version within C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2017\ENTERPRISE\COMMON7\IDE\EXTENSIONS. Other option is to find the sub-folder which have, for example, the file "Microsoft.Templates.2017.dll"

Contributor

ralarcon commented Jan 3, 2018

@Morhpeuss That is because the folder inu2pill.sxo is for other version different from what you have blocked... in the log you should be able to find the exact folder for your version within C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2017\ENTERPRISE\COMMON7\IDE\EXTENSIONS. Other option is to find the sub-folder which have, for example, the file "Microsoft.Templates.2017.dll"

@Morhpeuss

This comment has been minimized.

Show comment
Hide comment
@Morhpeuss

Morhpeuss Jan 3, 2018

Thanks, I have found 2 folders with this dll. Should I delete both?

Morhpeuss commented Jan 3, 2018

Thanks, I have found 2 folders with this dll. Should I delete both?

@ralarcon

This comment has been minimized.

Show comment
Hide comment
@ralarcon

ralarcon Jan 3, 2018

Contributor

Yes, delete both. The new installation (as is a higher version) will leave the folders as needed.

Contributor

ralarcon commented Jan 3, 2018

Yes, delete both. The new installation (as is a higher version) will leave the folders as needed.

@crutkas

This comment has been minimized.

Show comment
Hide comment
@crutkas

crutkas Jan 4, 2018

Member

@Morhpeuss any chance you can hook us up with logs?

Member

crutkas commented Jan 4, 2018

@Morhpeuss any chance you can hook us up with logs?

@crutkas

This comment has been minimized.

Show comment
Hide comment
@crutkas

crutkas Jan 4, 2018

Member

@xasx thank you for providing logs, they have been passed to the VS team

Member

crutkas commented Jan 4, 2018

@xasx thank you for providing logs, they have been passed to the VS team

@gordonwatts

This comment has been minimized.

Show comment
Hide comment
@gordonwatts

gordonwatts Jan 5, 2018

I have this exact problem. I've captured logs and sent them to you in an email (let me know if they don't get through). Removing the folder as instructed above seems to have fixed it.

gordonwatts commented Jan 5, 2018

I have this exact problem. I've captured logs and sent them to you in an email (let me know if they don't get through). Removing the folder as instructed above seems to have fixed it.

@DominikErnst

This comment has been minimized.

Show comment
Hide comment
@DominikErnst

DominikErnst Jan 11, 2018

  1. Removing 2 folders "2x24zybx.cdw" and "zfzeussl.kda" did not help on my machine. Found in "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\Extensions" with search for "Microsoft.Templates.2017.dll".
  2. Updated Visual Studio 2017 to 15.5.3.
  3. Reinstalled WTS from here

Now it WORKS!

DominikErnst commented Jan 11, 2018

  1. Removing 2 folders "2x24zybx.cdw" and "zfzeussl.kda" did not help on my machine. Found in "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\Extensions" with search for "Microsoft.Templates.2017.dll".
  2. Updated Visual Studio 2017 to 15.5.3.
  3. Reinstalled WTS from here

Now it WORKS!

@ralarcon ralarcon removed this from the 1.7 milestone Jan 30, 2018

@ralarcon ralarcon added this to the 1.8 milestone Jan 30, 2018

@ralarcon

This comment has been minimized.

Show comment
Hide comment
@ralarcon

ralarcon Jan 30, 2018

Contributor

Moving this to next version as it is still under investigation.

Contributor

ralarcon commented Jan 30, 2018

Moving this to next version as it is still under investigation.

@mrlacey mrlacey modified the milestones: 1.8, 2.0 Feb 1, 2018

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Feb 6, 2018

I have this exact problem. I've captured logs and sent them to you in an email (let me know if they don't get through). Removing the folder as instructed above seems to have fixed it.

ghost commented Feb 6, 2018

I have this exact problem. I've captured logs and sent them to you in an email (let me know if they don't get through). Removing the folder as instructed above seems to have fixed it.

@sibille

This comment has been minimized.

Show comment
Hide comment
@sibille

sibille Apr 11, 2018

Member

Moving to backlog as still under investigation. @crutkas, did we get more info on this?

Member

sibille commented Apr 11, 2018

Moving to backlog as still under investigation. @crutkas, did we get more info on this?

@sibille sibille modified the milestones: 2.0, Backlog Apr 11, 2018

@LanceMcCarthy

This comment has been minimized.

Show comment
Hide comment
@LanceMcCarthy

LanceMcCarthy May 1, 2018

I can confirm this workaround worked on a machine that was having tons of problems. Turns out Microsoft.Templates.2017.dll was in several folders.

LanceMcCarthy commented May 1, 2018

I can confirm this workaround worked on a machine that was having tons of problems. Turns out Microsoft.Templates.2017.dll was in several folders.

@crutkas

This comment has been minimized.

Show comment
Hide comment
@crutkas

crutkas May 1, 2018

Member

@LanceMcCarthy did you have nightlies and what not installed on top of RTM?

Member

crutkas commented May 1, 2018

@LanceMcCarthy did you have nightlies and what not installed on top of RTM?

@LanceMcCarthy

This comment has been minimized.

Show comment
Hide comment
@LanceMcCarthy

LanceMcCarthy May 1, 2018

@crutkas Yep, I started early with the nightlies, and ended up having 3 folders in /Extensions/ that had the DLL in it.

Although it's successfully installing now, I'm not seeing it in the templates list.

image

still investigating... reinstalled a couple times now and ran a manual devenv /updateconfig

LanceMcCarthy commented May 1, 2018

@crutkas Yep, I started early with the nightlies, and ended up having 3 folders in /Extensions/ that had the DLL in it.

Although it's successfully installing now, I'm not seeing it in the templates list.

image

still investigating... reinstalled a couple times now and ran a manual devenv /updateconfig

@crutkas

This comment has been minimized.

Show comment
Hide comment
@crutkas

crutkas Jun 28, 2018

Member

@sibille has there bee any forward movement on this?

Member

crutkas commented Jun 28, 2018

@sibille has there bee any forward movement on this?

@sibille

This comment has been minimized.

Show comment
Hide comment
@sibille

sibille Jun 28, 2018

Member

I don't think so, VS Team was working on this,

Member

sibille commented Jun 28, 2018

I don't think so, VS Team was working on this,

@crutkas

This comment has been minimized.

Show comment
Hide comment
@crutkas

crutkas Jun 28, 2018

Member

can you continue to push on them to get resolution?

Member

crutkas commented Jun 28, 2018

can you continue to push on them to get resolution?

@sibille

This comment has been minimized.

Show comment
Hide comment
@sibille

sibille Jun 28, 2018

Member

sure

Member

sibille commented Jun 28, 2018

sure

@LanceMcCarthy

This comment has been minimized.

Show comment
Hide comment
@LanceMcCarthy

LanceMcCarthy Jun 29, 2018

I'm not sure how this was eventually fixed for me. Ultimately I found many copies of the extension's assembly (the extension had multiple IDs, probably from early or nightly build versions), I deleted them all manually and then ran updateconfig.

Initially the template wasn't listed after updateconfig (as seen in my last reply), but now it is. Maybe it appeared after updating VS because there were a few updates since I had the issue, however I can't confirm if that is actually what fixed it.

LanceMcCarthy commented Jun 29, 2018

I'm not sure how this was eventually fixed for me. Ultimately I found many copies of the extension's assembly (the extension had multiple IDs, probably from early or nightly build versions), I deleted them all manually and then ran updateconfig.

Initially the template wasn't listed after updateconfig (as seen in my last reply), but now it is. Maybe it appeared after updating VS because there were a few updates since I had the issue, however I can't confirm if that is actually what fixed it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment