### Windows IoT

#### Custom IoT Image Crashes On Boot

I'm unable to get a custom Raspberry Pi 3 image to load after following the instructions at https://msdn.microsoft.com/en-us/windows/hardware/commercialize/manufacture/iot/create-a-basic-image?f=255&MSPPError=-2147217396.
If I use the built in "Raspberry Pi 2 & 3" in the IoT Core Dashboard image everything works perfectly.
However, the custom image loads with a spinner and reboots and comes up with a "Welcome to Windows 10 IoT Core; Please wait while we get things ready" screen and reboots and repeats this a time or two and then it just goes black forever.
I even get the same error if I buildimage SampleA Test and use that image.
I have the 1703 version of Windows and the ADK and the WDK, etc (see https://social.msdn.microsoft.com/Forums/en-US/38ebfd31-fb71-4163-88d9-d75993227e8f/iot-image-creation-fails-ppkg-doesnt-exist?forum=WindowsIoT).
What am I doing wrong? Where can I find the logs on the device? How do I debug this further?
Thanks,
Lee
http://rapidapplicationdevelopment.blogspot.com
Solved!!! Thank you! That last suggestion gave me exactly the hint I needed. SampleA does build just fine. So I did a binary search replacing each file and then each line in \Products\ProductA\ and \Products\SampleA\ until it worked, and
guess what the key difference ended up being? Hint: It's in the code snippet you just provided.
The answer is: ComputerName. Computer names cannot be more than 15 characters in windows, yet the customizations_RS2.xml template sets the value to "{OEMNAME}{Product}". ContosoProductA hits that 15 character limit perfectly, so if
you change OEM_NAME per the first step in Lab1a to anything over 7 characters and follow the remaining steps exactly, you'll get
this error.
The funny thing is, I had a hunch the company name might be too long so I even shortened "AutomatedArchitecture" to "AutoArch"
thinking 8 should be fine ... except it was still 1 character too many.
What a relief!
You mentioned "in the latest github update the default is changed to keep this disabled always" and indeed in \Templates\customizations.xml
the Accounts section is commented out. Except, it isn't commented out in the raspberry pi template file:
customizations_RS2.xml.
Regardless, thanks again for all your help I can't wait to start customizing this image for real now.http://rapidapplicationdevelopment.blogspot.com
Incidentally, the retail build also fails, but in a different way. It always shows a black screen and eventually settles into the green light blinking seven times.
https://social.msdn.microsoft.com/Forums/en-US/4037b06e-e0d4-4e7f-a792-400d55449d51/raspberry-pi-2-b-with-windows-10-iot-core-boot-failure-after-update-green-led-flashes-7-times?forum=WindowsIoT it could be
I tried setting up a 2nd technician computer and building and flashing from there, but same result. It couldn't be the windows updates like in that article because it never connected to the Internet (test or Retail).
My SD card is 16 gig ScanDisk
Class 10 UHS-I card. But if it were the card the built in "Raspberry Pi 2 & 3" image would also fail, right?
What does seven blinks mean? Is that a clue?http://rapidapplicationdevelopment.blogspot.com
Hi Lee,
The RPi LED codes are defined by the RPi manufacturer. You will have to go to their site to know what 7 blinks mean.
In the case of the black screen, in your previous question you were having difficulty getting the default app included. It should be launching at that point so my suspicion/guess is that you have not added an application to be launched hence the blank screen.
Sincerely,
IoTGirl
Thanks IoTGirl. I'm following Lab 1a, which I believe just uses the default Bertha app.
However, I have some additional info on this increasingly odd issue. I ordered another SD Card on a hunch after reading the other article, and flashed the Test ffu I created earlier to the new card. My old card looked about the same, but I ordered
the exact one in the IoT Hardware compat list just to be 100% sure, and maybe it's a little faster.
It acted oddly and rebooted twice as before. But then it came up with a blue screen of death with a QR code (that I can paste in if it's helpful) and a "CRITICAL PROCESS DIED" message. Then it rebooted another couple of times and eventually
asked me to select my language. If I waited too long on that page or the next (select WiFi) page it would eventually crash and reboot.
However the 3rd time I quickly clicked through those pages and now it's on the default Bertha app and is acting stable.
What's going on? I hope I don't need to tell my customers to quickly tap through the 1st two screens.http://rapidapplicationdevelopment.blogspot.com
Hi Lee,
Does the default app eventually launch? Your original error was "Error : Failed to create Appx.IoTCoreDefaultApp.ppkg. See C:\dev\iot-adk-addonkit\Build\arm\pkgs\logs\Appx.IoTCoreDefaultApp.prov.log" and the behavior you are describing sounds
like the default app is not actually there to be launched after OOBE.
The experience as documented here:
https://developer.microsoft.com/en-us/windows/iot/samples/iotdefaultapp
The "Quick setup experience" is the OOBE part of the experience. When this is complete or a timeout occurs the default application should launch.
Can you confirm that you do eventually get to the default application with the picture of the board?
Sincerely,
IOTGirl

Yes, the default app (Bertha, right? As in <Feature>IOT_BERTHA</Feature>) finally launched successfully with the faster SD Card, and when I very quickly moved through the select language and choose WiFi screens.
The default app always failed to launch with the slower SD Card.
The default app also always failed to launch (died and rebooted) if I spent more than about 10 seconds on either the select language or choose WiFi screens.
It's almost like there was a background task that was crashing the OS after a certain amount of time, and with the slower SD card the startup process couldn't get far enough before that time elapsed. But once the the app successfully launched (with
the faster SD card and by moving quickly through the intro screens), the main screen of the default app didn't run that background task.
By the way the "Error : Failed to create Appx.IoTCoreDefaultApp.ppkg"
was from an earlier thread and was an issue that you already helped me to resolve. I suppose it could be related, but I no longer get errors in package creation now that I've updated my OS and reinstalled all my tools.
Also, here's the bsod I mentioned earlier: http://rapidapplicationdevelopment.blogspot.com
Hi Lee,
I was specifically asking about the screen progression as outlined at the link for the default application. The blue screens with the initial choices are OOBE. Once that is complete, or times out, then the Default App is launched. From you explanation
it seems like the OOBE happens but the IOT Default App does not.
Can you please be as explicit as possible as to exactly when the error occurs?
Also are you saying there is no issue with the same image on a faster card or is the behavior different? Again, please be explicit so we are not assuming a behavior.
NOTE: The current theory here is that you are still getting a failure at the app registration and there is a known issue,
Custom QDB image will not build with 16190 ADK based on the message in your previous post around ICD and ApplicationManagement
“ICD.exe : ERROR: Parse error (0x80070490): 'ApplicationManagement' is not a valid child node for /
ICD.exe : ERROR: C:\Users\Lee\Documents\Windows Imaging and Configuration Designer (WICD”
Please understand that this error should only occur using the latest ADK but the version numbers you gave should not have ahs the problem. If indeed you were actually using the 16190 ADK, the fix on the github is already public.
This is the new one
old one is here to compare the differences
Sincerely,
IOTGirl
Hi IotGirl, sorry for the long delay I've been at Build, lots going on. Let me try to answer your questions one by one:
> Can you please be as explicit as possible as to exactly when the error occurs?
Yes, I have recorded the exact screen progressions and will post below.
> Also are you saying there is no issue with the same image on a faster card or is the behavior different?
The behavior is different. There is still an issue, just a different one (see the blue screen of death screenshot in my prior post). However, after spending a few more hours on this I have seen the original behavior with the new card. My
new theory is that each time I create or flash the image I end up with a different bad behavior on startup. See below for details.
I switched to develop and pulled latest. Same issue. I will now provide explicit steps. These are all using the new SD
card I bought.
Round 1 (Re-imaged with exact same ffu as earlier)
I used the
exact same ffu as in my Monday, May 08, 2017 10:09 PM post.
Except this time I did not get the blue screen of death with eventual successful load of default app, I got a different error.
1. Imaged old ffu to new sd card using Windows IoT Core Dashboard
2. Plugged in Pi
60 sec - Welcome to Win 10 IoT Core Please wait while we get things ready
It rebooted
65 sec - Welcome to Win 10 IoT Core Please wait while we get things ready
It Rebooted
48 sec - Black screen
48 sec - Black screen & reboot
30 sec - Error screen (see screenshot below) "windows failed to start boot manager 0xc000014c the boot configuration data for your pc is missing or contains
errors file \efi\microsoft\boot\bsd"
It rebooted
30 sec -
Error screen (see screenshot below) the boot configuration data for your pc is missing or contains errors
It rebooted
30 sec -
Error screen (see screenshot below) the boot configuration data for your pc is missing or contains errors
It rebooted
15 sec - Black screen
Forever -
Error screen (see screenshot below) the boot configuration data for your pc is missing or contains errors
﻿
Round 2 (Same ffu, tried with flashsd MyImage Test 1)
The IoT group at Build (including Jason Farmer) suggested flashing with command line tool. So I used the exact same ffu as earlier. This time I ended up with the exact same behavior as on Monday,
May 08, 2017 10:09 PM
(I didn't record exact timing or precise steps, but it's basically this:
Welcome to Win 10 IoT Core Please wait while we get things ready
Welcome to Win 10 IoT Core Please wait while we get things ready
Blue screen of death (see bsod screenshot from earlier)
Welcome to Win 10 IoT Core Please wait while we get things ready
Machine reboots after about 20 seconds
Machine reboots after about 20 seconds
Machine reboots after about 20 seconds
Default app starts
Round 3 (with a fresh build from dev branch)
Taking your suggestion I switched to the dev branch. I cleaned out my c:\dev\iot-adk-addonkit directory and re-pulled. I also deleted and re-downloaded the bsd directory. Then I followed the instructions exactly:
> Set Environment for Architecture
1 (ARM)
cd ..\..\bsp
build.cmd
buildpkg All
I always get this one error but it seems to be qualcom specific:
Processing QCDB410CFMFileList.xml
newproduct SirenOfShame rpi2
buildimage SirenOfShame test
flashsd SirenOfShame Test 1
Plug in Raspberry Pi
60 sec - Welcome to Win 10 IoT Core Please wait while we get things ready
Reboot
60 sec - Welcome to Win 10 IoT Core Please wait while we get things ready
Reboot
60 sec - Blank screen
42 sec - Blank screen
56 sec - Blank screen
Forever (aka I gave up after 5min) - Blank screen
Unplug/Replug
30 minutes! - Blank screen
Forever - Blank screen
So there you are. Incidentally, in C:\dev\iot-adk-addonkit\Build\arm\SirenOfShame_test.log there are some suspicious warnings. Do these offer any insight to you:
info: [00:00:01] Warning - File collision detected, file '\Windows\System32\netapi32.dll' found in packages 'Microsoft-IoT-PowerShell-Package' and 'Microsoft-IoTUAP-Product-Package'.
info: [00:00:01] Warning - File collision detected, file '\Windows\System32\ntdsapi.dll' found in packages 'Microsoft-IoT-PowerShell-Package' and 'Microsoft-IoTUAP-Product-Package'.
info: [00:00:01] Warning - File collision detected, file '\Windows\System32\w32topl.dll' found in packages 'Microsoft-IoT-PowerShell-Package' and 'Microsoft-IoTUAP-Product-Package'.
info: [00:00:01] Warning - File collision detected, file '\windows\winsxs\manifests\arm_microsoft-windows-d..oryservices-ntdsapi_31bf3856ad364e35_10.0.15063.0_none_83d4f67371a4b7cf.manifest' found in packages 'Microsoft-IoT-PowerShell-Package' and 'Microsoft-IoTUAP-Product-Package'.
info: [00:00:01] Warning - File collision detected, file '\windows\winsxs\manifests\arm_microsoft-windows-netapi32_31bf3856ad364e35_10.0.15063.0_none_422bcb2081fe452a.manifest' found in packages 'Microsoft-IoT-PowerShell-Package' and 'Microsoft-IoTUAP-Product-Package'.
info: [00:00:01] Warning - File collision detected, file '\windows\winsxs\manifests\arm_microsoft-windows-d..s-ntdsapi.resources_31bf3856ad364e35_10.0.15063.0_en-us_c8cfe2ff8b187ff6.manifest' found in packages 'Microsoft-IoT-PowerShell-Package_Lang_en-US' and
'Microsoft-IoTUAP-Product-Package_Lang_en-US'.
info: [00:00:01] Warning - File collision detected, file '\Windows\servicing\CbsApi.dll' found in packages 'Microsoft-IoTUAP-Product-Package' and 'Microsoft-OneCore-ServicingStack-Lite-Package'.
info: [00:00:01] Warning - File collision detected, file '\Windows\servicing\TrustedInstaller.exe' found in packages 'Microsoft-IoTUAP-Product-Package' and 'Microsoft-OneCore-ServicingStack-Lite-Package'.
info: [00:00:01] Warning - File collision detected, file '\windows\winsxs\manifests\arm_microsoft-windows-cbsapi_31bf3856ad364e35_10.0.15063.0_none_0359832370d55dec.manifest' found in packages 'Microsoft-IoTUAP-Product-Package' and 'Microsoft-OneCore-ServicingStack-Lite-Package'.
info: [00:00:01] Warning - File collision detected, file '\windows\winsxs\manifests\arm_microsoft-windows-trustedinstaller_31bf3856ad364e35_10.0.15063.0_none_4604e391cd951cf3.manifest' found in packages 'Microsoft-IoTUAP-Product-Package' and 'Microsoft-OneCore-ServicingStack-Lite-Package'.
info: [00:00:01] Warning - File collision detected, file '\Windows\servicing\en-US\TrustedInstaller.exe.mui' found in packages 'Microsoft-IoTUAP-Product-Package_Lang_en-US' and 'Microsoft-OneCore-ServicingStack-Lite-Package_Lang_en-US'.
info: [00:00:01] Warning - File collision detected, file '\windows\winsxs\manifests\arm_microsoft-windows-t..installer.resources_31bf3856ad364e35_10.0.15063.0_en-us_1c2247064319fc6c.manifest' found in packages 'Microsoft-IoTUAP-Product-Package_Lang_en-US' and
'Microsoft-OneCore-ServicingStack-Lite-Package_Lang_en-US'.
info: [00:00:01] Warning - File collision detected, file '\Windows\servicing\CbsApi.dll' found in packages 'Microsoft-OneCore-ServicingStack-UpdateOS-Package' and 'Microsoft-OneCoreUpdateOS-Product-Package'.
info: [00:00:01] Warning - File collision detected, file '\windows\winsxs\manifests\arm_microsoft-windows-cbsapi_31bf3856ad364e35_10.0.15063.0_none_0359832370d55dec.manifest' found in packages 'Microsoft-OneCore-ServicingStack-UpdateOS-Package' and 'Microsoft-OneCoreUpdateOS-Product-Package'.
Thanks again for all your helpfulness and thoroughness and promptness. I was certainly singing your praises to Jason Farmer. Debugging remotely like this can't be easy.
http://rapidapplicationdevelopment.blogspot.com
I am getting the same "Windows failed to start..." black screen after updating from the windows update. The original image burned by iot core dashboard seemed to work fine until the updates were applied. What is the resolution for the issue.
This issue is definitely hardware related I suppose.
Similar issues here. Using Dashboard I can flash the provided pi image and it boots and operates. Following the instructions for a basic image fails on boot. Everything up to booting completes without error. I have tried starting from scratch several times
and I have tried both the dev and master branches. :(
I decided to drop back and punt for now and I am trying to get my store certified / downloaded app onto devices using a provisioning package. I follow the instructions on the site and everything works but when I place the file into the c:\Windows\Provisioning\Packages
folder and reboot nothing appears to happen and the app is not listed on the Apps page of the portal.
Did this all work before creators update? If so is it possible to access all of the needed files? I really need to get my app onto the device and updating from the store so that my customer can test updates w/o using the portal.
Frustrated
Hi Folks,
I completely understand your frustration and the difficulty we have is replicating your exact environment as what Lee states is absolutely true. Without a direct reproduction locally we are guessing at what might be happening in your case.
So specific to the recent update, take a look at Zeeshan's latest post regarding custom images:
Packages &
Provisioning ).
The "Yellow brick road" here is that all tools, kits and related items *must* be in alignment. As noted, in the link above, a change versioning changes how it is interpreted by the tools and cascades through the build process.
There are two changes that impact building images with kits:
Provisioning versioning number is now a four part number ( earlier it was two part , treated as a single long number)
The <ApplicationManagement> tag is now under <Policies> - earlier this was under root.
Customizations.xml under appx folder needs to change.
Customizations.xml under product folder needs to change.
The suspicion is that you are being hit by the same issues in different ways based on your configuration differences. Lee, specific to your message regarding "Application Management" the node location changed so it is no longer valid at the
root (And yes, Jason is a good friend of mine and thank you for the reference!).
Sincerely,
IoTGirl

Would the following constitute the magic path?
New Windows 10 Pro VM
VS 2015 community latest
Everything linked on the instruction site:
Lab 1a
Thanks,
Dan

IOTADK_ROOT : C:\iot-adk-addonkit-master
WDK_VERSION : 10.0.15063.0
COREKIT_VER : 15063.0
OEM_NAME : Contoso
Set Environment for Architecture
Choose 1 for ARM, 2 for x86 and 3 for x64 : 1
Configuring for arm architecture
BSP_ARCH : arm
BSP_VERSION : 10.0.0.0
Is that all correct?
Thank You!

What version of Windows 10 is on your build PC?
Windows 10, 1703, 15063.296
With the above the initial OS boot completes after rebooting with the blue "welcome" once. After rebooting it returns to the blue "welcome" screen and then proceeds into the onboarding (language, wifi, etc). I enter the information and
the default app appears. Yay.
Feeling like I had made it through the hard part I continued with the Lab to try and get my store app installed but I am stuck again. I download the zip from the Store and I run all of the commands and change all of the xml and build the new image and everything
builds w/o error but the app is not listed. I open a network share and the provisioning package is located in C:\Windows\Provisioning\Packages.
Can you point me to a log file or anything that might help me understand why my app / prov package is not successfully being installed? Digging through the directories for the built-in apps I see they have a cert and security package file that the package
Any help locating log files etc to help diagnose are very much appreciated.
Dan

Tried with package created from Visual Studio (Create App Package -> Not for Store) and same result. Everything builds clean and OS boots after 1 reboot during initial startup but the app is not installed. Its like whatever is supposed to be installing
packages is not functioning.
Any advice welcome. I give up for now.
Dan
Hi IoTGirl,
From your suggestion about the four part version number and the ApplicationManagement tag, it sounds like the steps in Lab 1a may no longer be accurate. I tried to make the modifications to the Products\[product]\prov\customizations_RS2.xml file as
you described but I get errors like ppkg doesn't exist. The errors go away if I just follow the steps in Lab 1a verbatim (although then I get errors, I just tried it again after getting latest on dev and got the CRITICAL PROCESS DIED BSOD on boot with
eventual success, same as "Round 2" from above).
So that I can try to emulate a successful environment and better isolate the issue, can you please either carefully review and modify my steps below or (better) post the exact set of steps that you use to successfully create a new image (without an appx)?
If it's not too much trouble can you please including your version of windows, sdk, and adk, the commit hash in iot-adk-addonkit, complete session log, and any file modifications you make along the way?
Ideally I would like to know if you also get that QCDB410CFMFileList.xml error or the "File collision detected," warnings
I'll do the same so that we can compare:
Windows 10 version: 10.0.15063 Build 15063
Delete C:\dev\iot-adk-addonkit\Build\armDelete C:\dev\iot-adk-addonkit\Source-arm\Products\ProductAEdit C:\dev\iot-adk-addonkit\Tools\setOEM.cmd to set OEM_NAME=AutoArchLaunch C:\dev\iot-adk-addonkit\IoTCoreShell.cmd
WDK_VERSION : 10.0.15063.0
COREKIT_VER : 15063.0
OEM_NAME : AutoArch
Set Environment for Architecture
Choose 1 for ARM, 2 for x86 and 3 for x64 : 1
Configuring for arm architecture
BSP_ARCH : arm
BSP_VERSION : 10.0.0.0
IoTCore arm 10.0.0.0
IoTCore arm 10.0.0.0
C:\dev\bsp>build.cmd
signing C:\dev\bsp\bcm2836pwm.sys
signing C:\dev\bsp\bcm2836sdhc.sys
signing C:\dev\bsp\bcmauxspi.sys
signing C:\dev\bsp\bcmgpio.sys
signing C:\dev\bsp\bcmi2c.sys
signing C:\dev\bsp\bcmspi.sys
signing C:\dev\bsp\pi_miniuart.sys
signing C:\dev\bsp\rpiq.sys
signing C:\dev\bsp\rpisdhc.sys
signing C:\dev\bsp\rpiwav.sys
signing C:\dev\bsp\SerPL011.sys
signing C:\dev\bsp\vchiq.sys
signing C:\dev\bsp\vchiq_arm_kern.dll
signing C:\dev\bsp\vcos_win32_kern.dll
Building packages in C:\dev\bsp\
Processing bcm2836pwm.pkg.xml
Processing bcm2836sdhc.pkg.xml
Processing bcmauxspi.pkg.xml
Processing bcmgpio.pkg.xml
Processing bcmi2c.pkg.xml
Processing bcmspi.pkg.xml
Processing piminiuart.pkg.xml
Processing rpiq.pkg.xml
Processing rpisdhc.pkg.xml
Processing rpiwav.pkg.xml
Processing SerPL011.pkg.xml
Processing SV.PlatExtensions.pkg.xml
Processing vchiq.pkg.xml
IoTCore arm 10.0.0.0
C:\dev\bsp>buildpkg All
Building all provisioning packages
Processing all provisioning packages
Processing Provisioning.Enroll
Processing Appx.IoTCoreDefaultApp
Processing SampleA
Processing SampleB
Processing SecureSample
[sys files]
No sys files.
[dll files]
No dll files.
Processing Custom.Cmd.pkg.xml
Processing Device.SystemInformation.pkg.xml
Processing DeviceLayout.GPT2GB.pkg.xml
Processing DeviceLayout.GPT4GB.pkg.xml
Processing DeviceLayout.MBR2GB.pkg.xml
Processing DeviceLayout.MBR4GB.pkg.xml
Processing Provisioning.Auto.pkg.xml
Processing Provisioning.Enroll.pkg.xml
Processing Registry.Version.pkg.xml
Processing Security.Bitlocker.pkg.xml
Processing Security.DeviceGuard.pkg.xml
Processing Security.SecureBoot.pkg.xml
Processing Settings.HotKey.pkg.xml
Processing Appx.IoTCoreDefaultApp.pkg.xml
Building all bsps without re-signing
Sign all bsp binaries...
SIGNFILES set to NONE. Signing skipped.
Building all bsp packages
Processing CustomRPi2.GPIO.pkg.xml
Processing RPi.Customization.pkg.xml
Running FeatureMerger for OEM packages
Exporting OEMFM files
Processing OEMFMFileList.xml
Running FeatureMerger for CustomRpi2
Exporting CustomRpi2 FM files
Processing CustomRpi2FMFileList.xml
Running FeatureMerger for QCDB410C
Exporting QCDB410C FM files
Processing QCDB410CFMFileList.xml
Running FeatureMerger for Rpi2
Exporting Rpi2 FM files
Processing Rpi2FMFileList.xml
IoTCore arm 10.0.0.0
C:\dev\bsp>newproduct ProductA rpi2
Creating ProductA Product with BSP rpi2
IoTCore arm 10.0.0.0
C:\dev\bsp>buildimage ProductA test
IoTCore arm 10.0.0.0
C:\dev\bsp>flashsd SirenOfShame Test 1
Running Dism : SirenOfShame on PhysicalDrive1
Deployment Image Servicing and Management tool
Version: 10.0.15063.0
Applying image
[==========================100.0%==========================]
The operation completed successfully.
IoTCore arm 10.0.0.0
C:\dev\bsp>
Thanks,
Lee
p.s. #shredfoot if you can make it past lab 1a it might be useful to start a new thread. I'm afraid the chances are good I'll join you on that thread once I get past 1a, but until then it might make things easier for those that follow in our footsteps
to separate topics.http://rapidapplicationdevelopment.blogspot.com
Oh, and I'm using 2eda5bb2e1fe4657cfaf8995a8af6805115b5337 from iot-adk-addonkithttp://rapidapplicationdevelopment.blogspot.com
Also I modified setOEM.cmd to set OEM_NAME=AutoArch prior to step 1.
And when I tried to modify
customizations_RS2.xml it was right after newproduct ProductA rpi2.
Finally, when I tried to load on a pi from this session I got the blank screens results ("Round 3")http://rapidapplicationdevelopment.blogspot.com
Hi Lee,
If your steps are incorrect you can go back and edit prior posts to correct them. THis can help encapsulate the issue in one post for review rather than digging through multiple.
Are you certain the blank screen means the image is failing to load or potentially does the screen you are using not support the default resolution?
Sincere thanks,
IoTGirl

Hi IotGirl,
The blank screen is just one of three possible different failures. See "Round 1", "Round 2" and "Round 3" from my earlier post when I spent several hours compiling extremely detailed descriptions of the failures,
at your request. Also, I've seen the same results on 3 different monitors now.
I've spent what feels like an enormous amount of time and energy on this issue now, time which I could have spent furthering my app. I'm begging to wonder if Windows IoT is more work than it's worth.
But let's try a different tack. Can you provide a working virtual machine, docker image, or Azure instance that is capable of successfully generating images?
At this point I would happily pay for Azure time, or whatever is required to get back to working on features that will make my users happy.
If that's not an option can we please escalate this in some other way? Could we move to a Skype session, or perhaps ping someone with more experience building images?
Thanks,
Leehttp://rapidapplicationdevelopment.blogspot.com
Hi Lee,
I can confirm that your issue is already escalated. In fact you are remembered from meeting folks at Build. I'll reach out to the email address you have on Linked in for direct communication but the current feedback is:
Suggestion:
Build sampleA in the github and see if the device boots and functions properly. This way it ensures the setup and the device(SD card) are all good. Then proceed to creating own product.
Reboot info:
During the first boot, the device will reboot once to apply the computername. If you don’t desire this, you can comment out the following section in the customizations.xml under prov in the product folder.
In the latest github update, the default is changed to keep this disabled always.
<!--Accounts>
<ComputerAccount>
<ComputerName>ContosoQCTest</ComputerName>
</ComputerAccount>
</Accounts-->
After the reboot, the device will install the application and launch the application.
Sincerely,
IoTGirl

Sample A builds and boots (Test) every time for me. I think that Retail fails but I am not 100% positive as I was including my pre-install package.
I would like to second Lee's suggestion of a known working VM. I have spent Sunday-Wednesday trying to use the instructions posted in the Labs and I have very little to show for it other than a feeling that there is not a stable set of tools capable of producing
a custom image with my app installed that updates via the store.
Dan
Solved!!! Thank you! That last suggestion gave me exactly the hint I needed. SampleA does build just fine. So I did a binary search replacing each file and then each line in \Products\ProductA\ and \Products\SampleA\ until it worked, and
guess what the key difference ended up being? Hint: It's in the code snippet you just provided.
The answer is: ComputerName. Computer names cannot be more than 15 characters in windows, yet the customizations_RS2.xml template sets the value to "{OEMNAME}{Product}". ContosoProductA hits that 15 character limit perfectly, so if
you change OEM_NAME per the first step in Lab1a to anything over 7 characters and follow the remaining steps exactly, you'll get
this error.
The funny thing is, I had a hunch the company name might be too long so I even shortened "AutomatedArchitecture" to "AutoArch"
thinking 8 should be fine ... except it was still 1 character too many.
What a relief!
You mentioned "in the latest github update the default is changed to keep this disabled always" and indeed in \Templates\customizations.xml
the Accounts section is commented out. Except, it isn't commented out in the raspberry pi template file:
customizations_RS2.xml.
Regardless, thanks again for all your help I can't wait to start customizing this image for real now.http://rapidapplicationdevelopment.blogspot.com
Hi Lee,
Great catch and many thanks for the follow up!
Sincerely,
IoTGirl
Lee Thanks for all of the time and effort to to debug this. Are you able to build Retail and Test both? Thanks Dan

Encrypt Message

code
soft
python
ios
c
html
jquery
cloud
mobile