Uninstalling .NET Core VS2015 Tooling Preview 2 requires the original exe. #876
Comments
|
Hitting this issue too. Any workaround ? |
|
/cc @joeloff |
|
Having the original EXE is required as it needs to run the installer to remove all the products. This is more than a single MSI. The bundle wraps a large number of installers and also contains the manifest that's needed to remove everything. The work-around is to download the original bundle (EXE). For the build you highlighted, that can be obtained from https://download.microsoft.com/download/2/F/8/2F864C4E-6980-4AFC-B64E-0AC04837FD6C/DotNetCore.1.0.0-VS2015Tools.Preview2.0.1.exe |
|
where can i find the DotNetCore.1.0.0-VS2015Tools.Preview2.0.3.exe? |
|
@joeloff Thank you sir |
|
@joeloff when i try to open the link this error comes - The webpage at https://download.microsoft.com/download/5/5/7/557D02A5-C3D0-4EF6-A570-4F75CD0DA5BF/DotNetCore.1.0.1-VS2015Tools.Preview2.0.3.exe might be temporarily down or it may have moved permanently to a new web address. |
|
@SpyKing, my apologies, I grabbed the 2.0.2 URL. 2.0.3 is here: https://download.microsoft.com/download/F/6/E/F6ECBBCC-B02F-424E-8E03-D47E9FA631B7/DotNetCore.1.0.1-VS2015Tools.Preview2.0.3.exe |
|
@joeloff That worked! |
|
I think the problem here is that due to the focus on newer versions of .NET Core it can be difficult to track down the exact version that's required (see the several requests above). |
|
@balachir would it be possible to put together a previous releases page as @DamienDennehy mentioned? |
|
according joeloff 's advice, my issue solved. |
|
I ran into the same problem. I could not uninstall "Microsoft .NET Core 1.0.1 VS 2015 Tooling Preview 2", as it needed the original .exe file (which was not available). The error message was not helpful: it said that it needed "Preview2.0.2.exe", whereas in fact it needed "DotNetCore.1.0.1-VS2015Tools.Preview2.0.2.exe". Solved it by locating the original .exe using the links above. Thanks! |
It does actually say "DotNetCore.1.0.1-VS2015Tools.Preview2.0.2.exe" (or "DotNetCore.1.0.1-VS2015Tools.Preview2.0.3.exe") but the text is shifted so that only the bit starting from "Preview..." is visible. |
|
I found 1.0.0-VS2015-Preview2 from another link:
And here is 1.0.0RC2-VS2015-Preview1.
By the way, I found all listed post.
Why didn't they list all versions on "Release Build Archive"?
|
|
I tried the link that @joeloff posted ( https://download.microsoft.com/download/F/6/E/F6ECBBCC-B02F-424E-8E03-D47E9FA631B7/DotNetCore.1.0.1-VS2015Tools.Preview2.0.3.exe ). When I go through the uninstall and select that executable it fails with this error [ 0x80091007 - The hash value is not correct. ] (See screenshot below) I don't know what version of the installer I need or how to find that information. The log file was completely empty when I clicked on the link to view it. Any Ideas?
|
|
@joeloff It was version 1.0.20908.53, and that linked worked perfectly. Interestingly it never prompted me for the location of the installer I downloaded, it just automagically worked. Thank you much for your help. |
|
Thanks a lot! |
|
For me I just repaired the installation for Preview 2 and then uninstalled it without the need for the origional exe. |
|
At this link below solution works My recommendation for the future is remove all tools dependent on VS first, before removing VS itself. Then remove things VS depends on. I found some related issue here, after I figured it out. https://social.msdn.microsoft.com/Forums/vstudio/en-US/ae380a17-60e0-43a4-a481-6e58915e7897/net-core-errors-on-installation-webtoolsextensionsvs14-encountered-error-0x80070643?forum=vssetup " |
|
Me Too, Thanks a lot! |
|
@joeloff The DotNetCore.1.0.1-VS2015Tools.Preview2.0.2.exe link was what I needed! Thanks! So frustrating that you can't just google the filename and find it anywhere. |
|
Trying to uninstall 2.0.2 results in a loop showing the message "The specified account already exists." |
|
2.0.2 is in #789 |
|
Same problem here "The specified account already exists." .... |
|
Log: #789 (comment) |
|
I had to use different versions of the installer files but I was able to successfully remove the three installations I had. Thanks everybody for sharing the links. |
|
See also https://stackoverflow.com/questions/37624775/how-do-i-uninstall-microsoft-net-core-1-0-0-rc2-vs-2015-tooling-preview-1 "viewed 11006 times" |
|
For those stuck in the "specified account already exists" loop, see #1024 for solution. |
|
I used version 1.0.20811.48, could you please share any original executable for the same. |
|
For 1.0.20811.48 the direct link is https://download.microsoft.com/download/2/F/8/2F864C4E-6980-4AFC-B64E-0AC04837FD6C/DotNetCore.1.0.0-VS2015Tools.Preview2.0.1.exe |
|
IMHO it's absolutely unacceptable to require the user to download something in order to uninstall. the uninstall should be self-contained and retained as part of the install. especially since the installer constitutes less than 0.08% of the size of the total install. |
|
I am having the same problem with a newer version. When I want to uninstall the program, it asks me to provide the original kit which I deleted. Its name is DotNetCore.1.0.1-VS2015Tools.Preview2.0.4.exe but its is unavailable on Microsoft's download platform... This is really annoying and it makes me wastes a lot of time to track and fix the issue. |
|
The tooling bundle is an EXE that wraps the individual MSIs. All Add/Remove Programs has is a few registry keys, one of which points to the original location from where the install was launched. That path is used for uninstalls/upgrades/repairs. You can find the download here |
|
joeloff: I am glad to hear that you found a solution to my issue. I am currently off
work so I will try tomorrow this solution, hoping it will resolve my
problem. Thank you fr your time
|
|
joeloff that last link was the one that I needed. How are you finding these? How would one go about locating the correct version other than asking you to acquire it for us? |
|
I've kept track internally of all the releases for 2015 as they were updated. For VS2015, the last few updates were published through the Visual Studio Marketplace, which typically only records the latest download location. Unfortunately, the marketplace site does offer an easy way to track previous releases as any updates requires replacing existing items with the new downloads. I'll have a chat with my team and see whether we can maybe post the previous links as a comment or something on the market place entry |
|
That sounds like a good idea to me. Thanks! |
|
DotNetCore.1.0.1-VS2015Tools.Preview2.0.4.exe anyone? I have 1.9gb of disk space that I'd like to reclaim, and all I can find is the 2.0.3 version, 2.0.4 seems to not exist anywhere. Needless to say, it's refusing to let me uninstall it without the exe. four or five hours later ------>Iv'e just realised that "joeloff"'s comment 5 above this one has the word "Here" right on the end, if you look carefully, it's a link to the 2.0.4 version!!! |
|
I want to uninstall |
|
@bestpika Read the comment I wrote just before yours. |
|
Try this link |
|
how to uninstall DotNetCore.1.0.1-VS2015Tools.Preview2.0.4.exe, please help |
|
Same way you uninstall any windows software, go into your Add/Remove programs and select it from there. |
|
it's missing file therefore shows the error |
|
@webenformasyon solution works for me! Thanks! |
and others
Uninstalling .NET Core VS2015 Tooling Preview 2 requires the original exe.
When uninstalling a version of .NET Core VS2015 Tooling Preview 2, you are asked to specify the location of the original install file.
Functional impact
You have to track down the exact version (in my case DotNetCore.1.0.0-VS2015Tools.Preview2.0.1.exe) and download it to your PC to uninstall the Tooling. This can be time consuming if your team has slightly different versions.
Minimal repro steps
Expected result
The Tooling should simply uninstall.
Actual result
Failure to uninstall unless the original .exe is specified.
Further technical details
This was replicated on two separate machines, one running 2.0.1, the other 2.0.3.
The text was updated successfully, but these errors were encountered: