We Keep Coding

UWP Store 0x800701C5

I wrote a UWP program and I used Restricted capability
broadFileSystemAccess
When I published this application I obtained permission from Microsoft, and its now in the Microsoft Store.
But when I tried to install it, it got an error:
My computer: Windows 10 1809
I have tried googling this, and writing to Microsoft, both without finding a positive result.

First, make sure the problem is actually only with your app by trying to install some other app if that will work.
If this happens only with your app, you should definitely contact Windows developer support for this issue. Select Contact us tab, then Windows 10 UWP app development and submit your incident. They should be able to help. You can also post the problem on the publishing Forum for greater visibility.

Deployment to Remote Machine failed - UWP Debugging

I am currently attempting to deploy an app to a Windows 10 tablet running the Creator's Update, over my local network. When I select remote machine and enter my debug settings, I can discover the tablet on my network, and get its address and Authentication mode automatically.
However, when I try to deploy, I get this error:
DEP6957 : Failed to connect to device using Universal Authentication. Please verify the correct remote authentication mode is specified in the project debug settings. 0x8007274C: The network event being waited on triggered an error.
As far as I can tell from the documentation that I've read, this process should be more or less plug and play since the Creator's Update, can anyone explain what I might be doing wrong, or what might be going wrong?
Listed here are my debug settings currently in use.
Update: Since its not the solution I was looking for, I'm not adding it as an answer, but if anyone comes across this looking for a fix and no one has suggested one, the way I ended up working through this is just downloading the remote debugger to the tablet and running the old method for C# apps. I never did find out why the UWP method didn't work.

Determine whether Hyper-V is currently active (not installed or configured)

Hyper-V is used by Visual Studio to run the Windows Phone emulators. Hyper-V is also incompatible with VMware because Hyper-V starts Windows in a mode of permanent virtualisation while VMware would need VT-x as well during runtime only.
Hyper-V can be installed and uninstalled as a Windows role. This will also activate and deactivate permanent Windows virtualisation and allow VMware to run. But then of course the Visual Studio emulators stop working.
Hyper-V can be configured to be active or inactive without uninstalling the Windows role. This involves editing the boot configuration with bcdedit.exe. After doing this change, a restart is required to actually apply the configuration and use or not use Hyper-V. This BCD setting can be read after setting it, but it is unknown whether the system has already been restarted to actually apply it. So this setting only indicates what will happen after a restart, not whether virtualisation is currently running.
Some people say you could look at the Windows service "vmms". Unfortunately this is not helpful because that service is installed with the Hyper-V role and it is always running, no matter whether virtualisation is really active or not. WMI information is also not helpful because it always says that Hyper-V would be running, even when it's not.
Obviously there must be a way to determine the real current status of virtualisation because VMware will tell you when you try to start a 64 bit machine.
So how can this be done in code? Specifically from a .NET application? Administrator privileges are available for this already because bcdedit.exe also needs it.
Should this require native assembler code, would it be possible to run it from C#/.NET somehow?
Update:
I've made a simple tool that puts a one-click GUI over the bcdedit procedure: Hyper-V Switch. You can try it and see for yourself whether you find any reliable indicator of Hyper-V actually being executed right now, not just being configured to run on next boot. Enable or disable Hyper-V but keep an application open that prevents the reboot. Then Hyper-V Switch will tell you the configured state, not the actual state.
Eventually I'd like to incorporate this status test into the application so that everybody can use it.

How to install Windows Phone 8.1 app in other phones in the simplest way?

I have developed a Windows phone 8.1 app. Now I want to distribute it to others.
I have done Create App Packages in Visual Studio, and it passed all the certification tests. So I have the .appx file, but I am not able to install it in other Windows phones.
Its showing this error:
Can't install this company app: There is a problem with this company app. Contact your company's support person for help.
I have googled and found out that there is two ways of distributing the app:
1) Mobile Device Management Tool,
2) Side-Loading
and without having an enterprise-signing certificate from Symantec it is not possible to distribute the app.
Another option is to upload the app to the store, but I don't want to do it at this moment.
So is there any way to install the app in other windows phone?
In a simple way? I don't want any certificates. I just simply want to install the app in my friends phone. Like we can create and install .exe files easily.

There are a few ways to achieve this without getting the certificate required for sideloading.
Beta
First of all - you ask for the simplest way to distribute an app.
I assume that there might be updates in the future (and if only to fix this annoying little bug that might find or whatever). Then submitting it to the store as Beta app is really something you should consider; it won't be visible - it won't be accessible to anyone whom you haven't authorised to use the app. The certification process in Beta is quite fast, as it is merely a sanity check.
Regarding the cost of the dev account: it is quite cheap (https://msdn.microsoft.com/en-us/library/windows/apps/jj863494.aspx) and can even be free, for students and startups through the respective programs (DreamSpark, BizSpark). Also: no recurring fees, even if you're not a student anymore.
But the true benefit is that all you need to do is give the authorised testers the link to your app once it is published and then all the updates are handled through the store. No messy package distribution to the individual people, no notifications - testers will get the updates like for every other app. Long term, that would save you a lot of time and the testers a lot of hassle in preparing their device for being able to play your app, they do not need to developer unlock their phones.
Without Beta submission
If you want to just send them the app package,
they must (also) have a Microsoft account. If I recall correctly, they can have one developer unlocked device even without the dev registration (http://dev.windows.com/en-us/join)
they need the Windows Phone SDK, which comes as part of Visual Studio, which installs the required tools
connect their phone to the computer
to developer unlock their device, they have to run a tool called "Windows Phone Developer Registration" and sign in with their Microsoft account
to deploy the app, use the tool called "Application Deployment".
Everytime an update is distributed, they simply need to use the "Application Deployment" tool.
or use the command line :D

Unless your friend's phone is developer unlocked, you have to submit it to the app store.

Is it possible to have a windows desktop app with metro interface (or a metro app with no intention of going to the windows store)?

Apologies for the noobish question, and I did try to search but couldn't find the right answer (or didn't search properly).
Currently have an app developed in a windows desktop environment because it gives us access to deeper features of the PC such as serial port comms etc. that the normal metro environment wouldn't allow. We're currently developing the UI based on metroUI so we can run it on an 8.1 touchscreen (metroUI looks good, gives us a touch-screen experience with PC features) but we have no intention of putting it on the marketplace.
Just wanted to confirm if this is in fact doable, and we can have this desktop application with a metro UI? Or is my noobishness meaning I'm overlooking some technical feasibility that makes it impossible?

This is doable with the Windows 8.1 Update (from April 2014). It's not supported before that since Windows Store apps were blocked from communicating with desktop processes.
The Windows 8.1 Update adds a feature "Brokered Windows Runtime Components" designed to allow side-loaded Windows Store apps to communicate with a desktop back-end. This will allow your Windows Store app UI to call the desktop component to access API that aren't available in the limited app package environment.
See Brokered Windows Runtime Components for side-loaded Windows Store apps for details.
See Try It Out: Sideload Windows Store Apps on TechNet for how to enable side-loading on your systems. See Windows 8.1 Update: Sideloading Enhancements for updates on how to enable a system for sideloading (no license required when on a domain, and significantly easier to get a sideloading license for non-domain joined systems).
The developer license system is designed for development and test purposes only. You really don't want to use it for production. Use the proper enterprise side-loading system instead.

From my understanding, the whole point here is to make it look like a Windows Store app. If you're app is a WPF one, you can already use Mahapps.metro.

You can create a Windows Store app without going to the store by Sideloading it. You create an app package first. The user has to right click the .ps1 file in that package to see the option Run with PowerShell and install it in a very old fashioned DOS like manor. It will only run when the user has a Microsoft Developer License and renew it every month. However, it is not allowed to keep using a Developer License of the end user to run a Store app. In the end, the system has to be domain bound to be allowed to run these apps, or you have to buy a Enterprise Sideloading key. These come in packages of 100 for $ 3000,- or you can unlock all PC's for 1 client for $ 100-.
It would be nicer if the specific pros of a Store program were available in a desktop environment but with W10 coming up I do expect a bit more integration and less restrictions.
Hope this answers your question.