I installed Visual Studio 15 Preview 5 on my office pc successfully and signed in with my hotmail account into it. There it says the license for this pre-release software is licensed to my hotmail account which will end on 31 January 2017 as shown below:
When I installed the same Visual Studio 15 Preview 5 on my home pc and tried setting up the same hotmail account then it gives licensing error. It says
License: Prerelease software. Your license has expired.
Is anyone aware of such an issue? Is there any limitation on configuring Visual Studio 15 preview 5 build on several machines with same live id?
As for me, this error was solved after I've restarted Windows to install the updates. When I logged in after the system restart, VS 15 Preview 5 installer has auto-started and finished its job - and my VS 15 installation is fully working since then.
I was facing the same issue - it seams that the installer doesn't finish successfully.
Starting the installer again told me that it was interrupted.
Running the installer solved the issue for me.
Take a hat de discussions here: https://blogs.msdn.microsoft.com/visualstudio/2016/10/05/announcing-visual-studio-15-preview-5/
Related
Deploying a UWP app locally from Visual Studio 2015 (Update 3) fails with the error message:
DEP0700 : Registration of the app failed. error 0xC000003A: Deployment
of package 6dd81a71-9c3a-4204-abaf-886a9b0c29bb_1.0.0.0_x86__kcdnnw7pbsh48 was
blocked by AppLocker. (0x80073cf9)
The full output doesn't add further insight:
Restoring NuGet packages...
To prevent NuGet from restoring packages during build, open the Visual Studio Options dialog, click on the Package Manager node and uncheck 'Allow NuGet to download missing packages during build.'
1>------ Build started: Project: App2, Configuration: Debug x86 ------
1> App2 -> c:\users\<username>\documents\visual studio 2015\Projects\App2\App2\bin\x86\Debug\App2.exe
2>------ Deploy started: Project: App2, Configuration: Debug x86 ------
2>Updating the layout...
2>Copying files: Total <1 mb to layout...
2>Checking whether required frameworks are installed...
2>Registering the application to run from layout...
2>DEP0700 : Registration of the app failed. error 0xC000003A: Deployment of package 6dd81a71-9c3a-4204-abaf-886a9b0c29bb_1.0.0.0_x86__kcdnnw7pbsh48 was blocked by AppLocker. (0x80073cf9)
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
This has been created as new project via File > New > Project... > Blank App (Universal Windows), with no other changes being made.
Visual Studio is running as Administrator.
Windows 10 (1607 Build 14393) is set up with Developer mode on.
Other suggestions include deleting the app directory from %LocalAppData%\Packages, but there is no directory corresponding to this app.
What could the issue be here? Is there any advice on next steps to troubleshoot this?
Had this same error popping up with Visual Studio 2017 every time I tried to open a XAML file in UWP project. Fixed it by simply creating the folder C:\Windows\System32\AppLocker.
I faced the exact same situation you described last week. It’s taken some time to come back to you as I wanted to go through all the “fix it” options first. I tried all you mentioned and to no avail. You don’t mention it, but I’m guessing you are also using the Pro edition?
I then looked a little more broadly, and found many other users having the same problem installing or updating apps from the Windows store after “upgrading” to the anniversary edition of Windows 10, which you mention you are using. The error code is the same and AppLocker is again the culprit, so it would be worth you testing a new download from the store to see if this is also true for you.
If so, it seems to be because Microsoft has decided to limit some of the useful policy configuration which was previously available in Pro, and now only available in Enterprise or Education. One of the changes that is affecting us is to limit the usage of AppLocker. It’s a real shame and at odds with the push to make a really polished version of Visual Studio and Xamarin (ok – Xamarin is still a little buggy) available on a community license, but then at the same time, changing the OS so that to use the free development tools, you will need an Enterprise license. And normally, the Enterprise edition for Win 10 is only available with a bulk purchase! This blog is a good summary of the changes that have been made in the anniversary edition.
There are two more fixes you could try – run wsreset.exe from a command prompt with admin rights or download this trouble shooter from the MS site. These will try to fix your Windows store configuration, which might also help with UWP deployment. Neither worked for me, but some people online mentioned it worked for them.
So I am facing the tedium of a fresh Windows 10 install – either to go back to the previous version and stop the update to the anniversary edition by tweaking the wifi access… or finding a fresh install of the anniversary edition. I’m going to try the former first as it is one less download, though I’ll still need to download all of the whopping 35gb of Visual Studio and Xamarin again so will wait until I have some spare time!
This worked for me:
Delete all the CI policies here
C:\windows\System32\CodeIntegrity\CiPolicies\Active* (Should be p7b files)
Reboot
I have been facing the same issue as asked in this other post
Visual Studio 2015 Windows Phone Emulator not deploying
but the solution worked here is not working for me.
Windows 10 pro upgraded from home version
Visual Studio 2015
Apache Cordova "Sample" app.
In Emulator it is showing as "Starting
in the behind "Hyper-V" "Summary" it is visible but if double click the the Hyper-V "instance" it is not visible there but only in "Summary"
What am I missing here?
For the developer sake and investment, MS must make sure that the solutions are tested everywhere before releasing them.
This link will direct you to print screen of the error. https://prnt.sc/cykrgg
in the VS output we get the following last message.
My OS is 64 bit.
2>The build configuration was changed to x86 for x86-based emulator deployment.
could this be impact of 64 to 86 bit version difference or anything else?
I have Norton antivirus
I am getting
Hyper-v administrator pop up every time I try to run the app.
This case is resolved by Microsoft Support Team over a Ticket and Rohit, support engg from MS did really helped me a lot.
The reason why it was not coming up.....
My machine has a AdWareAntiVirus from Lavasoft by Name WebCompanion that was not allowing it work.
I removed it then it started working.
if any body have any problem with VS 2015 Emulator definitely focus on the Antivirus and include the Emulator XDE into exception list and also include in Firewall.
Thanks,
Ekambar
I have a crazy Licence issue with my VS2015 Enterprise. I'm a student and my school provide us many MS products. In the past and for the other version of VS, I download the iso in my account, and they generate a licence key and i just need applied it after the installation. With VS2015 Enterprise, i have do the same, I have a legit key on my OntheHub MS account when I have take the iso.
The Expire date finish in 2017 and my school tell me that my account is valid (for the other product of MS it works well).
But something is wrong in VS 2015. I can't apply the key. So at first, i have use the trial licence, but now, it will expire in 3 days.
I go to the licence key windows but when I touch "apply", nothing happen.
I have try :
format my computer
download a new ISO
repair VS
Uninstall and install again VS, with a clean in registry too.
I also look a lot of solution in Stackoverflow and MS Community.
Nothing work...
I'm running on Windows 10 with VS 2015 Enterprise Update 3.
Any Help ?
I am moving towards Xamarin for cross-platform application development. I already had VS2015 installed, I downloaded Xamarin tools(vstoolsforxamarin.exe) from their website and when I install them after a long wait VS says "setup completed with errors"and it does not download and install Android SDK for API 19,20,23, It always say:"Please check your internet connection and try again" and i am sure that my internet connection doesn't get disturbed during all this process. I have tried this 3 times now, tried by uninstalling VS2015, installing it again but got the same error. What is the problem that is causing this? I already have Android Studio installed, with its SDK manager. Any help would be appreciated, that to get Xamarin running in VS2015.
EDIT:
Solution:
I already had Android Studio and its SDK on my system, going to Tools>Options>Xamarin from Visual Studio and giving path of the Android SDK solved my problem. Read this answer on StackOverflow somewhere!
Seems like this issue is caused because Visual Studio is trying to download thrid-party libraries (Android SDK). You can fix this from Control-Panel
Have a look at this post.
Make sure you have installed Java JDK, I had similar issue reported here
Visual Studio 2015 Enterprise Reports Internet Connectivity Issue while there is no issues with networking
As mwilson64 answered in response to Android SDK Setup API not installed (same as linked above on "Have a look at this post."), my steps to resolve:
Create file %USERPROFILE%.android\androidtool.cfg
Paste the following into new file (created in step 1):
# Settings for Android Tool
# Last updated: Wed May 19 17:09:27 UTC 2017
http.proxyPort=8888
sdkman.enable.previews=false
http.proxyHost=127.0.0.1
sdkman.ask.adb.restart=false
sdkman.show.update.only=true
sdkman.force.http=false
sdkman.use.dl.cache=true
Replace values in proxyPort and proxyHost with your company's proxy settings.
When I try to debug even a simple template project from Windows App store 8.1 in VS2013. Ii can't have the application. I have no proble with ressources in my computer. It still giving me the text in the output Registration of the application to run from the disposal .... And no launch for the apps.
Should I repair my VS2013? Where am I wrong?
EDIT
I repaired but it doesn't launch the windows store apps.
I finally came accross this bug. I don't what was the proble but I spent like one day reapairing VS 2013 but it didn't helped me.
The solution was to REPAIR my Windows 8.1 which took like less than 10 minutes. An advice from my colleague