I've asked a similar question in the NG too but maybe this forum as a better coverage.
I am unable to finish installing VS 2017 (Community). Especially it goes wrong on this:
Package 'Win10SDK_10.0.14393.795,version=10.0.14393.79501' failed to install.
After an update, this same message changed from version 14393 to 10.0.15063.15 but the result is the same. Also when I separately install the SDK it ends with a directory which couldn't be created (because it is already there...). VS works for regular projects but I can not open or create Universal Apps. Many users seem to have this problem; I have seen the question multiple times and against 100 users follow the several open questions which do not get a useful reply from VS development. Before I installed VS 2017, I did a a W10 re-installation with the Media Creation Tool which solved some upgrade problems for W10 and an app so I expect the environment to be pretty "clean".
What I wonder is if anyone here has attempted the same installation (see picture) and succeeded (the current screen does show the installation size as --- instead of the amount of GB, but I have seen this working previously. But you can't expect VS installers to keep working correctly on what did work before, can you....)
Okay then - I will try and help, as my recent VS 2017 Community version does let me make a new project of type Universal, as you can see below in the images I just made for you.
The only obvious thing that I did, and presumably you did not do, was install the full (complete) workload. For other reasons I will not go into here, I always install the complete VS set of offerings / options.
Can you try to make a new install for Community, selecting each of the workload options ?
At the moment I even have this VS instance open, as well as another which is the Enterprise version of 2017, and all VS are the latest updates - using the VS installer.
P.S. FYI I never have to mess with folders at all, ever. I just install what is sent to me, but install the whole thing.
Here is some image detail which may help in some ways :-
Phil Hepburn wrote: The only obvious thing that I did, and presumably you did not do, was install the full (complete) workload. For other reasons I will not go into here, I always install the complete VS set of offerings / options.
Well, you can't blame him - wasn't "slim install", "install only what you want/need to use" one of the biggest selling talks associated with V17? <g,d&r>
However, this was the only reason I could see why my install worked and Dick's did not. Of cause we don't know what else he did to install non-default paths etc.
I don't get any real issues with VS, and never did, so I can't be any more helpful. And many different versions seem to live happily side by side. Problems seem to come for others when they try to remove bits of earlier installs.
I will try and install it on my laptop for Cologne and see if I can force an issue or two there.
Thanks for your input. I did a standard installation although I skipped some unused options. In the meantime I've done the same on my laptop and there it works. I am not sure why; the laptop is setup more or less the same and on the desktop where it failed I refreshed Windows using the Media Creation Tool so I would expect it to be pretty "clean".
Not sure what to do next. I can again try to use one of my "incidents" but so far nobody at Microsoft helped me with anything there; standard reply is that whatever I ask is "not there department".
The most likely scenario will be that I de-install VS2015 Professional when my Action Pack ends this month, and then hope that I can install VD Community 2015 again.
The re-installation fixed 2 other long lasting problems: the fact that W10 didn't 14393.969 (also a Install failed) and the fact that the Universal App Desktop Bridge - to post regular Windows in the Store didn't work anymore, not even after a re-installation. So I hoped that it would also fix the VS 2017 installation problem. Although it works on the laptop, and not on my desktop, it seems to be a more common problem. I've currently posted is as an issue within my Action Pack - if they solve it would be the first time this year. I currently didn't even find my incident back on their website despite it being confirmed by mail. So I chatted Microsoft. They said "It should be there, maybe there was some kind of maintenance/update on the site which caused that" and I should call Microsoft in Amsterdam.
Current status is that someone 'scaled up' the seemingly lost issue and I can expect a call today.....
Dick - Good Luck with MS - I recognise your story, about not being in their knowledge area or whatever! Had one myself less than a week ago and ended up sorting myself.
Now then, On the Universal apps issue / topic, please be aware that I have been using the Template in C# and that X# still needs some improvements on the level of integration, and a larger selection of Templates to choose from is one area we are all waiting for.
So for now Universal apps in C#, unless you are a genius or a guru
Personally, I am convinced that all VS installation (different versions etc.) are all independent and faith in uninstalling a 2015 version solving your problem is NOT very hopeful I fear.
It is something to do with folders in your Windows 10 system, an issue caused by another app.
What about noting the folder name and path the default install is to use, and then go outside the installer and make sure that this folder is totally removed ?
Installed the Win SDK successfully on the machine
Repairing the VS 2017 Community
This did not solve it completely. The error changed to Package 'Microsoft.SmartDevice.Connectivity,version=15.0.26315.0' failed to install.
It says: Details
MSI: C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.SmartDevice.Connectivity,version=15.0.26315.0\WPSDK_en.msi, Properties: REBOOT=ReallySuppress ARPSYSTEMCOMPONENT=1 MSIFASTINSTALL="7"
I found these to be linked with Phone Tools and performed the same trick on the directories involved for this.
First I renamed C:\ProgramData\Microsoft\Phone Tools\CoreCon\12.0 to !12.0.
Then I got a message that it didn't have sufficient rights etc in the directory.
After that I renamed C:\ProgramData\Microsoft\Phone Tools to !Phone Tools and then it finally installed without errors.
It looks like the new VS installer could do with a bit of overhaul & testing....
Any reason we see the larger part of your post twice?
BTW, just finally managed to convince WindowsUpdate to run successfully on wife's laptop - after it tried in vain for some hours. One of the real nasties is, that you can't stop the updater in it's tries.
a) net stop wuauserv from admin prompt,
b) failed: "couldn't stop service"
c) after some long time, updater told (wrongly): failed because of reboot ,
d) retry a)
e) now stop succeeds <g>
f) regsvr32 %windir%\system32\wups2.dll
h) net start wuauserv
i) open winupdate - and finally: Success!
Any reason we see the larger part of your post twice?
Out of completely joy that I finally got something working I guess...
I edited it. I had some collateral damage in the installation - the Phone emulators were gone and after reinstalling I got one of the always helpful VS messages in VS2015:
but in VS2017 it actually worked. Loading the project is terribly slow compared to VS 2015 (hilarious that VS2017 is actually advertised as many times faster as VS 2015, what was I thinking when attempting to install it...) but it does work.
BTW, just finally managed to convince WindowsUpdate to run successfully on wife's laptop - after it tried in vain for some hours.
You tried to get the Creator's Update? Very, very brave Karl. How do the new Microsoft advertisements look in Explorer? Did they find more ways to annoy the user?
Thanks for this interesting feed-back, it does fit all the facts and observations at this end it would seem.
The VS Installer for 2017 definitely needs some work to make it 100% okay. And plenty of testing up front.
Since it is designed to allow individual developers to 'Modify' what is contained in the VS installation - from a visual IDE perspective, then Modifying should work and definitely NOT break the VS installations on a PC system.
Remember I had both an 'Enterprise' and a 'Community' version of 2017 working happily, and side by side on my office desktop platform.
In trying to modify the install of Community, and a couple of other sensible related similar 'things' I must have had the Installer remove one or more 'bits' or 'workload' sets. This then broke everything it would appear, by not removing a folder it later checked and would not over-write.
Yes, MS in their wisdom (and it does make sense to me) have installs so that Folders are parts used by multiple versions of 2017. So break things for one version and you have broken things for them all - I call that brittle design even though it may save lots of disk space.
YES, I suppose I could install a Hyper-V virtual machine etc., etc. - BUT - I can't be bothered, AND, the Installer checks itself for updates regularly so, just maybe, they fix it soon. Maybe a fix will come before I get a VM up and running.
Fingers crossed - I will report back if things change for the better / good.