Installation
- How can I install EFLOW in a Windows host?
- Issue: Deployment failed because of errors with the EFLOW VM creation
- Issue: Error when checking EFLOW Pre-requisites on a target device
- Issue: Certificate Trust problem with Deploy-Eflow - Signature is not valid
Follow the steps in Install and provision Azure IoT Edge for Linux on a Windows device to set up a device with IoT Edge for Linux on Windows.
This error could be related to multiple things. However, it's generally attributed to turned off virtualization or having some issues with virtualization settings inside UEFI/BIOS.
- If running Windows 10 on bare-metal: Enable Hyper-V on Windows 10.
- If running Windows Server on bare-metal: Install the Hyper-V role on Windows Server.
- If running inside a VM: Turn on Nested Virtualization
If the problem persists, check that the virtualization is correctly configurated in the UEFI/BIOS settings. You can check if Intel Virtualization is enabled without going to BIOS in Windows 10 using the following guide.
Another potential cause of the problem is the lack of storage needed for the VM to be installed. If you're using the default EFLOW disk size 10 GB), check you have the available 12 GB needed in your targeted drive. If not, free up some space and try again, or use another drive.
Also, check the minimum requirements. It's important to allocate the necessary memory (check Architecture & Requirements). However, it's important not to allocate all the host memory to the VM.
Generally, this problem is caused by a lack of connection to the Windows host. To verify connectivity, start by trying to establish a connection to the Windows target device using WAC. If a connection can't be established, then try to troubleshoot the target device connectivity.
- Run CertMgr on a machine that has internet connectivity
- Expand Trusted Publisher \ Certificates folder
- Open Certificate Issued To Microsoft Corporation
- Open Certificate Path and verify that the certificate chain is complete showing the following
- Open Details tab and select Copy to File
- In the Certificate Export Wizard click Next
- Select DER encoded binary X.509 (.CER) then select Next
- Save file as “Trusted Publisher” then select Next then Finish and OK to confirm Export
- Return to Certificate Path tab and select Microsoft Code Signing PCA 2011 and select View Certificate
- Repeat steps 5-8 naming this one “Intermediate CA”
- Select OK to close this certificate returning back to the view of #4 above
- Select Microsoft Root Certificate Authority 2011 and select View Certificate
- Repeats steps 5-8 naming this one “Root CA”
- Close all certificates and CertMgr
- Copy all three certificates to the target device you need to repair.
- On the Target device right click on “Root CA” and select Install Certificate
- Store Location = Local Machine and select Next
- Select Place all certificates in the following store then select Browse and choose Trusted Root Certification Authorities, OK then Next and Finish and OK to confirmation
- Right click on “Intermediate CA” and select Install Certificate
- Store Location = Local Machine and select Next
- Select Place all certificates in the following store then select Browse and choose Intermediate Certificate Authorities, OK then Next and Finish and OK to confirmation
- Right click on “Trusted Publisher” and select Install Certificate
- Store Location = Local Machine and select Next
- Select Place all certificates in following store then select Browse and choose Trusted Publishers, OK then Next and Finish and OK to confirmation
- Now run CertMgr on the target device
- Under Trusted Publishers\Certificates open Microsoft Corporation and select Certification Path. You should see the same thing from step 4 above.
The EFLOW 1.1.2111.17111 update introduced a bug in the way we handle Static IP. This bug is only present in fresh MSI installations.