Cannot launch Visual Studio Emulators (both Android and Windows Phone) - Says cannot verify digital signature - hyper-v

I'm unable to launch both the visual studio emulator for android and the window phone 8 emulator. I'm using VS2015 CTP 6.
Windows Phone Emulator
Windows Phone Emulator is unable to set the VHD on the virtual machine:
Couldn't change Virtual hard drive of the virtual machine: 'Emulator 8.1 WVGA 4 inch 512MB.x' failed to add device 'Virtual Hard Disk'. (Virtual machine ID 60573DDO—9F9F—4002—9E40—8A46BDAADCFE)
Failed to open attachment 'C:\Users\x\AppData\Local\Microsoft\XDE\8.1\dd.480x800.512.vhd'. Error: ‘Windows cannot verily the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.'.
'Emulator 8.1 WVGA 4 inch 512MB.x': Cannot get information for attachment
'C:\Users\x\AppData\Local\Microsoft\XDE\8.1\dd.480x800.512.vhd'. (Virtual machine ID 60573DDO—9F9F—4002—9E40—8A46BDAADCFE)
Failed to open attachment 'c:\users\x\AppData\Local\Microsott\xDE\s.1\dd.48ox3oo.512.ylrd'. Error: ‘Windows cannot verily the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.'.
Visual Studio Emulator for Android
The emulator is unable to verily that the virtual machine is running:
something happened while starting a virtual machine: 'vs — Android Phone‘ failed to start. (virtual machine ID 2481D99r—6537—4l37B—9AcAB9s27rr24srA)
'VS — Android Phone' Microsoft Emulated IDE Controller (Instance ID 83F8638B—8D(J-\—4152—9EDA—2G4\8B33039B4): Failed to Power on with Error ‘Windows cannot verily the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown
source.' (Ox80070241). (Virtual machine ID 2481D99P6587—4B7B—9AG4\—B9827FF248FA)
'vs — Android Phone‘: Failed to open attachment
'C:\Users\x\AppData\Loc.a|\Microsoft\XDE\Android\vsemulator.phone.android.vhd'. Error: ‘Windows cannot verily the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.' (0x80070241). (Virtual machine ID 2431D99r—6537—4B7B—9AcA—B9s27rr24srA)
'vs — Android Phone': Failed to open attachment
'C:\Users\x\AppData\Local\Microsoft\XDE\Android\vsemulator.phone.android.vhd'. Error: ‘Windows cannot verily the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.' (0x80070241). (Virtual machine ID 2431D99r—6537—4B7B—9AcA—B9s27rr24srA)
I'm not sure whether it had to do with hyper-v or not. I did a report on the visual studio installation and got the same result.

This is a known issue on Windows 10, it has to do with the folder structure of the Android emulator that conflicts with the WP emulator. The "workaround" was that you can only have one installed at a time
However, you're in luck, as Microsoft has published an updated version of the Android emulator that will work side by side. Download it form here:
http://go.microsoft.com/fwlink/?LinkID=532868

Related

Genymotion unable to start the virtual device opengl error

I try to start a virtual device by Genymotion. But I get the error:
Unable to start the virtual device
To start virtual devices, make sure thet your video card supports OpenGL 2.0 and update the drivers.
Details: Failed to create framebuffer image (error: 15)
If possible, update your vido card drivers.
As advised at Stackoverflow I have tried to update my video card drivers. But it did not help.
I have suggested that this was due to the fact that I replaced opengl32.dll file in SysWOW64 directory. I replaced it during copy to this folder glut32.dll, glu32.dll and glut.dll files.
How to resolve the problem?
OS: Windows 10
I have resolved the problem.
I have asked for another copy of opengl32.dll from my friend's computer SysWOW64 and put it in my SysWOW64 directory.

Can't get WinAppDeployCmd for Appx deployment to work

During the App Packaging and Deployment for Universal Windows Apps presentation (fast forward to 00:36:00) one specific command line utility - WinAppDeployCmd - was used for deployment Windows 10 Universal application to the phone running Windows 10 Mobile. This utility could be found here:
"c:\Program Files (x86)\Windows Kits\10\bin\x86\WinAppDeployCmd.exe"
But every time I'm trying to deploy sample .appx package to the Lunia 635 phone with Windows Mobile v10.0.12562.84 or Surface 3 device with Windows 10 Pro Insider Preview (all devices on the same network as my dev machine) - I'm getting the same "connection failed" error:
Windows App Deployment Tool Version
10.0.0.0 Copyright (c) Microsoft
Corporation. All rights reserved.
Opening connection to device at '192.168.1.139'.
0x80131500 - Connection Failed
0x800705B4 - Timed out waiting for
network events.
Just in case - I could ping both of the devices from my dev machine without problem and can also deploy to any of them from VS2015RC (also tried with renamed WinAppDeployCmd.exe - to make sure that VS2015RC doing deployment somehow differently without using this tool).
So, I'm wondering - are there anyone who succeeded with app deployment using WinAppDeployCmd.exe?
This is a known issue in the current release. There is no workaround and it will light up in a future Windows 10 Insider Preview SDK and tools release.
https://social.msdn.microsoft.com/Forums/en-US/5c8d6f20-699c-4da2-9460-f73e89bf27c3/known-issue-cannot-sideload-applications-using-winappdeploycmd-windows-10-insider-preview-sdk-and?forum=Win10SDKToolsIssues
I have succeeded to deploy an .appx using the WinAppDeployCmd command line tool. Probably the issue have been correct at the latest versions.
For the ones that are not familiar with this tool, it allows you to deploy an Universal Windows app from a Windows 10 machine to any Windows 10 Mobile device via USB or WiFi (since they're on the same subnet). That's a perfect solution if you doesn't have Visual Studio, doesn't have the app source code or if you're under a Hyper-V Virtual Machine.
Basically you will need:
Windows 10 SDK
Generate the .appx package (PC)
Enable the developer mode (Mobile)
Turn on the discovery mode (Mobile)
Get the code to pair devices (Mobile)
Get mobile IP address using WinAppDeployCmd tool (PC)
Run command (PC)
The command will look like this
WinAppDeployCmd install -file “<path>” -ip <ip> -pin <pin>
The tool can be found at C:\Arquivos de Programas (x86)\Windows Kits\10\bin\x86\WinAppDeployCmd.exe
You can find a detailed step-by-step tutorial here
This happened to me once when the USB socket was faulty and Windows compained about the device not being recognized. I switched sockets and everything worked. So make sure you try other sockets (or even a different computer, to rule out the specific machine).
This tool let's you install but does not run the app after install like it did the first version in windows 8.1

Can't install published Adobe AIR application

Hi I create a flash game using adobe flash player 6 (AIR).
If I test it using "Test Scene", it run very well.
I set it to run on Adobe AIR desktop target 3.2 (my PC is 4.0)
I publish the game in format .air and create a certificate.
The problem : I can't install my game (in AIR package) on my computer.
The warning is:The application could not be installed because the installer file is damaged. Try obtaining a new installer file from the application author.
I already use administrator account but it does n't work. Can you help me??
I found the solution. It is because my system clock is not accurate and I use self certificate (using time stamp).
So, I must repair my system clock and publish adobe AIR application again with new certificate.

Sign cat file that uses Winusb.sys as kernel-mode code

I'm trying to make an USB driver to be installable in Windows 8, this USB driver uses only WinUSB.
According to this post Signed INF driver works on the computer where it was signed, not
others and also this website Practical Windows Code and Driver Signing all I have to do is to generate an .inf file, to generate a .cat file and sign this .cat file, but I'm having trouble with the signing part, the other steps are ok.
The sites I listed above makes clear that to sign a catalog file which the driver uses only WinUSB is not necessary to purchase any certification from any authorized Certification Authority.
The kernel modules you are using have already been signed by Microsoft
and you will have no trouble getting them loaded into the kernel after
the driver package is installed.
I have the SignTool.exe in a folder along with the mscvr-cross-gdroot-g2.crt. In a subfolder, let's say MyFolder I have my driver package.
MyFolder
├─ remsir.cat
├─ remsir.inf
│
├─┐ amd64\
│ ├ WdfCoInstaller01011.dll
│ ├ WinUSBCoInstaller2.dll
│ ├ WUDFUpdate_01011.dll
│
└─┐ i386\
├ WdfCoInstaller01011.dll
├ WinUSBCoInstaller2.dll
├ WUDFUpdate_01011.dll
So, basically I'm stuck at this point:
SignTool.exe sign /v /ac "mscvr-cross-gdroot-g2.crt" /n "Pololu Corporation" /t http://tsa.starfieldtech.com MyFolder\remsir.cat
This command line was copied from the other questions, but it isn't working for me. I tried to change some of the parameters but still without success, it doesn't matter what I do I always get the error message:
SignTool Error: No certificates were found that met all the given criteria.
First of all, I not really sure if I should change any of the parameters from this command line. They aren't really clear for me what they mean.
So.. Do I have to change any of the parameters in that command line? Do I have to install the mscvr-cross-gdroot-g2.crt or even the Pololu Corporation? If yes, how?
You need to buy a signing certificate from some company like GlobalSign. Yes, Windows trusts the winusb components of your driver, but Windows 8 will not allow you to install the INF file unless it is signed by a real certificate.
Your quote from me is:
The kernel modules you are using have already been signed by Microsoft and you will have no trouble getting them loaded into the kernel after the driver package is installed.
This quote is still true. The point is that you will not even be able to install the driver package unless you sign the INF file.
The Pololu Corporation you saw in my examples is the name of my company and that part needs to be changed to be your company name. It needs to exactly match the company name embedded in the certificate you purchase.
Edit 1: Windows 8 doesn't require an INF file for WinUSB actually
If you are able to change the firmware of the device then you can avoid buying a certificate for your WinUSB device. For Windows 8 support, you should follow these instructions from the USB Core Team to get your device loaded without needing an INF file:
http://blogs.msdn.com/b/usbcoreblog/archive/2012/09/26/how-to-install-winusb-sys-without-a-custom-inf.aspx
Because you aren't supplying the INF file or the SYS files, I strongly expect that you won't need to sign anything for Windows 8.
For Windows 7 and earlier, you would need to supply an INF file to associate your device with WinUSB, but the INF file would not need to be signed because those versions do not require it.
Target:
Install an .inf file that uses WinUSB as kernel-mode code.
Solution:
I solved my problem, not exactly as my initial idea of signing the .cat file.
My answer may be disappointing for most of people and I may receive lots of critics for not using the best practices and etc. It's inelegant and sounds more like an workaround than a really solution. But considering the main business of the company and the hurry for using the driver in Windows 8 I've reached a solution that is satisfactory for the company.
The main difference between Windows 7 to Windows 8 when talking about installing an unsigned driver is that Windows 7 shows an annoying red warning message that recommends the user to not install the unsigned driver, and Windows 8, under normal circumstances just doesn't install it anyway.
We coexisted all this time with this warning in Windows 7, so what I've done is to reconfigure Windows 8 to act like Windows 7.
Step 1:
At the end of my software's installation the installer runs a program that verifies the Windows' version, if it is Windows 8 it prompts a dialog asking for installing the drivers and advices that it will demand to reboot the Windows. If the user agrees, it will run a batch file that does:
Adds to HKLM..RunOnce a path for Batch File 2
Disable Driver Signature Enforcement
Restart the computer
Step 2:
When the user logs on it will run the second batch file, that was set to run into the RunOnce. It will do:
Run the DPInst.exe
Enable the Driver Signature Enforcement
Restart the computer.
At this point the driver will be installed and the original settings are restored. The annoying red warning message remains, just like it was in Windows 7, and life goes on..

installation of cab was unsuccessful for windows mobile 6.5. No error details in log

I have a provisioning file setup.xml that I want to install on a windows mobile 6.5 phone. I created a cab file, signed and copied to phone, and ran the cab file.
However I get:
'installation of foo.cab was unsuccessful’
I go to Application Data\Volatile\setup.log
The log simply contains the setup.xml file but no error details nor messages.
How to know why it failed?