KERNEL_SECURITY_CHECK_FAILURE at boot + no network/mouse/kb

[rookieone]

Trying the Windows IoT image, I get a:

KERNEL_SECURITY_CHECK_FAILURE

About 3 times, and then it boots, but USB keyboard and mouse not working and "no internet connection".

Then I get stuck at this screen (see attached file):

Anyone similar experiences?

[Terra854]

Trying the Windows IoT image, I get a:

KERNEL_SECURITY_CHECK_FAILURE

About 3 times, and then it boots, but USB keyboard and mouse not working and "no internet connection".

Then I get stuck at this screen (see attached file):

Anyone similar experiences?

I have the same issue, except that I did not get the KERNEL_SECURITY_CHECK_FAILURE.

Probably driver support is not there yet as it has only been released for a few days, but I expect that support will improve over time.

[MarkHaysHarris777]

The bleeding edge can be fun and exciting, but also frustrating and nerve wracking !   

[tllim]

I have communicated with the involved engineer and will pass the response once available.

[dkryder]

the download is a .ffu which requires several windows programs , ICD/ADK to be on a win10 box? is this the installation path?

[tllim]

the download is a .ffu  which requires several windows programs , ICD/ADK to be on a win10 box? is this the installation path?

For the Pine A64 Windoiws IoT installation process, please refer to https://github.com/Azure/azure-iot-sdks/...-csharp.md

[martinzheng]

Hi this is a known issue and we are working on it.

Once you encounter this issue, please remove power and reboot again, the device should boot successfully.

Martin

---

For mouse and KB support.Yes Pine 64 windows iot core do support them, but it is a little bit complex.

windows does not support OHCI and EHCI dynamic switch, which means we have to make a choice to support mouse and KB or usb udisk.

Your may wounder why RPI2/3 can support both? the answer is that there is a on board usb hub. which can transform the OHCI command into TT format. But Pine64 does not have a USB hub. We also have a another method: As Pine64 has two usb port, we can make one support mouse and KB(OHCI) and the other one supports(EHCI) udisk.

So the solution with the ffu at your hand is: please attach a usb hub and then attach mouse and KB via hub.

For the network, we are still work on WIFI and Eth. currently the WIFI is still not stable and Eth is still under coding.
you can use a usb wifi or usb Eth that supported by RPI2/3 to have the internet access.

Further more, we are working hard to publish our code(BOOT0/ATF/UEFI/WIDNWOS BSP/build toolset) and Docs onto GitHub. At that time,

Any one can have the full source code access and can totally have the ability to develop drivers/functionality by yourself, Which is not available for RPI2/3,as there is no UEFI code and acpi tables there.

Martin

---

the download is a .ffu  which requires several windows programs , ICD/ADK to be on a win10 box? is this the installation path?

As you just need to Flash ffu onto your device, you can only use one tool: IoT Dash board.
If you want to dev Apps, you can download ADK/SDK/VS2015 from MS website and get it start.

Martin

[dkryder]

this is from DISM.log after a failed flash. the flash process had proceeded to the 30% mark successfully before issueing the error. the dashboard reported that the SDcard was not formatted, but of course it had been. most recently by windows after the first time this message appeared. it's a good card. any ideas?
2016-08-07 21:16:58, Error DISM FFU Provider: PID=7652 While reading image data, a hash check failed. - CFfuManager::FfuLog
2016-08-07 21:16:58, Error DISM FFU Provider: PID=7652 While applying the image to disk, a read failed to return all of the blocks specified in the current data descriptor. hr = 0x2dbe260b. - CFfuManager::FfuLog
2016-08-07 21:16:58, Error DISM FFU Provider: PID=7652 TID=9676 onecore\base\ntsetup\opktools\dism\providers\ffuprovider\dll\ffumanager.cpp:240 - CFfuManager::Apply(hr:0x8007000e)
2016-08-07 21:16:58, Error DISM FFU Provider: PID=7652 TID=9676 onecore\base\ntsetup\opktools\dism\providers\ffuprovider\dll\ffumanager.cpp:163 - CFfuManager::ApplyImage(hr:0x8007000e)
2016-08-07 21:16:58, Error DISM DISM Imaging Provider: PID=7652 TID=9676 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:2581 - CGenericImagingManager::InternalCmdFFUApply(hr:0x8007000e)
2016-08-07 21:16:58, Error DISM DISM Imaging Provider: PID=7652 TID=9676 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:535 - CGenericImagingManager::ExecuteCmdLine(hr:0x8007000e)
2016-08-07 21:16:58, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2016-08-07 21:16:58, Info DISM DISM.EXE:
2016-08-07 21:16:58, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2016-08-07 21:16:58, Info DISM DISM.EXE:

[martinzheng]

this is from DISM.log after a failed flash. the flash process had proceeded to the 30% mark successfully before issueing the error.   the dashboard reported that the SDcard was not formatted, but of course it had been. most recently by windows after the first time this message appeared. it's a good card.  any ideas?
2016-08-07 21:16:58, Error                 DISM   FFU Provider: PID=7652 While reading image data, a hash check failed. - CFfuManager::FfuLog
2016-08-07 21:16:58, Error                 DISM   FFU Provider: PID=7652 While applying the image to disk, a read failed to return all of the blocks specified in the current data descriptor. hr = 0x2dbe260b. - CFfuManager::FfuLog
2016-08-07 21:16:58, Error                 DISM   FFU Provider: PID=7652 TID=9676 onecore\base\ntsetup\opktools\dism\providers\ffuprovider\dll\ffumanager.cpp:240 - CFfuManager::Apply(hr:0x8007000e)
2016-08-07 21:16:58, Error                 DISM   FFU Provider: PID=7652 TID=9676 onecore\base\ntsetup\opktools\dism\providers\ffuprovider\dll\ffumanager.cpp:163 - CFfuManager::ApplyImage(hr:0x8007000e)
2016-08-07 21:16:58, Error                 DISM   DISM Imaging Provider: PID=7652 TID=9676 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:2581 - CGenericImagingManager::InternalCmdFFUApply(hr:0x8007000e)
2016-08-07 21:16:58, Error                 DISM   DISM Imaging Provider: PID=7652 TID=9676 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:535 - CGenericImagingManager::ExecuteCmdLine(hr:0x8007000e)
2016-08-07 21:16:58, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2016-08-07 21:16:58, Info                  DISM   DISM.EXE:
2016-08-07 21:16:58, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2016-08-07 21:16:58, Info                  DISM   DISM.EXE:

This is because the ffu file that you are using is broken. I think Tim would update a new image.

[dkryder]

the file on the pine64 site is 300MB, the file on onedrive is no longer there.