Raspberry Pi 3 B+ Windows IOT Core Boot Work Around

Question

Hey All,

Turns out it is possible to boot Windows IOT Core on the new Raspberry Pi 3 B+. Simply head over to the Pi Git https://github.com/raspberrypi/firmware/tree/master/boot and download the following updated boot files-

fixup.dat

fixup_x.dat

fixup_cd.dat

start.elf

start_x.elf

start_cd.elf

Replace these six files on your SD Card boot partition. I can confirm this works with Windows IOT version 16299. We don't have working Ethernet or Wifi Drivers yet.. However it might be possible to get those working with a bit of ingenuity.

Answer 1

We don't have working Ethernet or Wifi Drivers yet.. However it might be possible to get those working with a bit of ingenuity.

Drivers for Ethernet were no trouble.. Head over to MicroChip http://www.microchip.com/SWLibraryWeb/product.aspx?product=OBJ-LAN78xx-WINDOWS and download LAN7800-WDF-v17.04.21.0.zip then extract ndis650/arm32, transfer the following files over to c:\drivers on a Pi with working ethernet (Rpi2 or Rpi3 b)-

lan7800-arm-n650f.cat

lan7800-arm-n650f.sys

net7800-arm-n650f.inf

Then run the following commands from SSH or powershell-

devcon dp_add c:\drivers\net7800-arm-n650f.inf

shutdown -r -f -t 0

After that boot the SD in your Rpi3 B+. If the indicator lights are not functioning this is most likely caused by the following behavior as noted by the Linux Devs-

The default LED modes put 1000Mb/activity on orange and 100Mb/activity
on green, but this leaves no indication for a 10Mb link.

Network Screenshot showing RPi3 B+ LAN7800 gigabit adapter-

https://photos.app.goo.gl/LyZUlTRLkRuPcDo43

Answer 2

Further observations show the current Wifi and bluetooth drivers are problematic and can cause boot issues. There does not appear to be an out of the box solution for the Broadcom Wireless SDIO Adapter on the RPi 3 B+. I recommend disabling these devices with the following commands-

reg add hklm\system\controlset001\services\BtwSerialH5Bus /v Start /t REG_DWORD /d 4

reg add hklm\system\controlset001\services\bcmsdh43xx /v Start /t REG_DWORD /d 4

You can encounter endless boots (circle spin) with these device services active.

The ball is in Microsoft's court! Microsoft please add support for RPi 3 B+ in the next insider and major release. While your at it please add USB support to the UEFI bootloader so we can boot from USB devices and add support for the dwcUsbOtg USB provider in the WinPE recovery environment.

Answer 3

Hi Andy,

Thank you for sharing your efforts in Windows IoT Core.

Currently there are some ones also make efforts about Windows IoT Core on Raspberry Pi 3B+.

Please follow the response of this thread:

https://social.msdn.microsoft.com/Forums/en-US/547a6084-7c7f-40da-911a-37bc6e087d6f/raspberry-pi-3b?forum=WindowsIoT

Best Regards,

Michael

---

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 4

Is it possible for you to create an image of that windows installation with the inserted lan driver?

I do not have an older raspberry pi model and I tried to add the driver with dism and pnputil, but that doesn't work on the 3b+ when it's running.

Answer 5

Hi Andy,

Thanks for the workaround, with this, I was able to boot my Pi 3 B+. However, I don't have another (older) Pi to use for installing the Ethernet driver you've linked. devcon dp_add fails, I guess because of the lack of Administrative privileges. I couldn't find a way to elevate or run processes as the Administrator account on the default IoT shell, so I tried some methods, all of which have failed:
- I tried to change HKLM\Microsoft\Windows NT\CurrentVersion\Winlogon\FirstUserAccount from DefaultAccount to "Administrator" -> caused a hang on boot (even with disabling the two drivers you advised)
- I tried to set the usual keys @ HKLM\Microsoft\Windows NT\CurrentVersion\Winlogon to make <g class="gr_ gr_73 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="73" id="73">winlogon</g> use the Administrator account (AutoAdminLogon-DefaultUserName-DefaultPassword): had no effect
- I tried to execute a PowerShell script locally that would run <g class="gr_ gr_21 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling" data-gr-id="21" id="21">devcon</g> as the Administrator user (Start-Process with the -Credential option) -> failed (I don't see the output of the script, unfortunately, but it's syntactically and semantically correct)
- I hacked together a small Win32 executable that tries to use CreateProcessWithLogonW to run devcon.exe as the Administrator user. Here's the source: https://pastebin.com/HpbF10Uq According to IDA, CreateProcessWithLogonW exists in advapi32legacy.dll, and has an actual implementation (it's not just a stub that returns a constant error code). -> The program successfully loads advapi32legacy.dll and finds the address of CreateProcessWithLogonW. However, the function fails and last error is set to 0x424, ERROR_SERVICE_DOES_NOT_EXIST

Any ideas? I don't want my brand new Pi to collect dust for 3 months or something...

Answer 6

Hey Peter,

Gaining elevated permissions to install the driver might be tricky. A better route to take would be following the manufacturing guide for creating custom images. The following link describes the process well-

https://docs.microsoft.com/en-us/windows-hardware/manufacture/iot/create-a-basic-image

Following the instructions in Lab 1a (Create a basic image) and Lab 1e (Add a driver to an image) will allow you to incorporate the Ethernet drivers. You could also use Lab 1c (Add a file and a registry setting to an image) to install the correct boot files to the boot partition, the elfs and dats I posted above. However this would require altering the BSP to not include Boot Firmware, it might be easier for testing to just add them after flashing the FFU.

For other users that are not capable of completing the ADK manufacturing labs, I did the work for you. Below is a custom full flash images with the Ethernet drivers rolled in, updated boot firmware and removal of Rpi 3 b WiFi and Bluetooth services. WiFi and Bluetooth have been removed because we currently do not have drivers for those and the existing drivers cause long boot times.

(Raspberry Pi 3 B+ Compatible ETHERNET ONLY Windows IOT Core 16299.15 FFU)

Download-

https://1drv.ms/u/s!AsvmyE1dw3yggvEafd_lLUqghA1UCw

Flash the image to a memory card

1. Start the Windows IoT Core Dashboard.

2. Plug your micro SD card into your technician PC, and select it in the tool.

3. From Setup a new device, select Device Type: Custom.

4. From Flash the pre-downloaded file (Flash.ffu) to the SD card, click Browse, browse to your FFU file then click Next.

5. Optional: Change the default device name (Default is minwinpc.)

6. Enter your device password.

7. Accept the license terms, and then click Install. The Windows IoT Core Dashboard formats the micro SD card and installs the new image.

WARNING - If you flash this image for testing I recommend disabling windows updates. Microsoft Update can and most likely will overwrite your boot firmware with the old elfs/dats. (run the following from ssh or powershell sc.exe config wuauserv start=disabled)

Answer 7

For those looking to create their own FFU's I uploaded my IoT-ADK-Addonkit folder for reference-

https://1drv.ms/u/s!AsvmyE1dw3yggvEbJEcGOBgJ7JSRBQ

Refer to the following file for alterations removing old boot firmware and WiFi/Bluetooth drivers-
IoT-ADK-AddonKit\Source-arm\BSP\Rpi2\Packages\RPi2FM.xml

Refer to the following folder for copying new boot firmware to boot partition-
IoT-ADK-AddonKit\Common\Packages\Registry.FilesAndRegKeys

Refer to the following file For Ethernet driver additions-
IoT-ADK-AddonKit\Source-arm\Packages\OEMFM.xml

Product Build for Rpi3 B+ is located in the following Folder-
IoT-ADK-AddonKit\Source-arm\Products\RaspberryPi3BPlus

Just in case the Mircosoft IOT Core Dev Team is reading this please add the following-

1. Support for RPi 3 B+ in the next insider and major release.
2. USB support to the UEFI bootloader so we can boot from USB devices.
3. Support for the dwcUsbOtg USB provider in the WinPE recovery environment so we can update devices with an FFU in the field.
   

Answer 8

Many thanks for modified image! I am running my b+ now with that. 

One question regarding.. What settings i should change when new windows version with wifi & bt drivers are available and i would like to enable connections?

Thanks!

br. Jens

Answer 9

Many thanks for modified image! I am running my b+ now with that. 

One question regarding.. What settings i should change when new windows version with wifi & bt drivers are available and i would like to enable connections?

Thanks!

br. Jens

Reflash your SD Card with the Windows IOT Core Dashboard if/when RPi 3 B+ support is added.

Answer 10

Hi!

Flashed my Rpi 3b+ with that custom image from Andy12986. Got further than previously but next error is from Windows Boot Manager with error code: 0xc000014c
Message: "An unexpected error occured"

Answer 11

Hi!

Flashed my Rpi 3b+ with that custom image from Andy12986. Got further than previously but next error is from Windows Boot Manager with error code: 0xc000014c
Message: "An unexpected error occured"

Sounds like an error happened while flashing the card. Clearing with DiskPart before writing the flash.ffu with Windows IOT Core Dashboard may fix the problem.

Clear Procedure with DISKPART

----------------------------------------

Start a command prompt, and start the DISKPART console. List all of your disks by typing LIST DISK, then select the proper disk with SELECT DISK # (where # is the SD card). You can then type CLEAN to clear the partition table on the card, effectively blanking it. MAKE SURE YOU SELECTED THE PROPER DISK BEFORE RUNNING THE CLEAN COMMAND! Create a primary partition to reuse the space on the card, type CREATE PARTITION PRIMARY. This will then reallocate the previously "cleaned" space.

Answer 12

Hi Andy,

In the meantime I actually solved this. The default "shell" is just a UWP application that is open source, actually. I figured that the code that enables command-line access must have admin privileges somehow, so I located that part, and it turns out there is an HTTP endpoint that you can use to run arbitrary commands as an arbitrary user.

It's a POST request that has the following format: http://127.0.0.1:8080/api/iot/processmanagement/runcommand?command=[Base64 encoded command]&runasdefaultaccount=[Base64 encoded "false" or "true"]. The Base64 string must be "URL percent-encoded", so for instance, "=" padding characters become %3D each. The username and password of the account go into the Basic authentication header (also Base64).

I quickly hacked together a Win32 program based on wininet (the code quality is utter garbage, but it does the job nicely): https://pastebin.com/VLETpGHq

Anyone can use this, all you have to do is Base64-encode your command and auth info, compile, copy to the SD card, run from the command line, and done. 

Answer 13

Thank you Andy! I can confirm your custom flash image works for Raspberry Pi 3 B+ with ethernet cable, not WiFi, but it's something. I can see my Raspberry Pi 3 B+ in Windows 10 IoT Core Dashboard and have been able to install a custom App and it works perfectly.

Thanks again!!

Answer 14

Hi Andy

thanks for your help on this. I recently bought the new B+ to replace a broken one without paying enough attention to what I was buying. It would be in the trash by now if not for your assistance.

I am keen to get the Wireless up and running and understand this is in the hands of Microsoft and others so I assume I will be waiting for a new release or at least an insider preview.

Is there an official forum I should be watching or some resource to follow any progress.

I have searched a few locations and this appears to be the only thread with real progress..

Thanks again for the assist..

 

Answer 15

It does not work on my RP 3 b+.

The green light showes once wenn i turn on it, but nothing works. 

What should I do? 

I replace the six files in EFIESP. Did i do anything wrong?

Answer 16

Thanks Peter....I am new to these PI board and was almost about to return it to Amazon...thast when I humped into your post....

You saved my day...

Thanks

Answer 17

Here's my take on the "Raspberry Pi 3 B+" , as of now i.e. "April 12th 2018" without a custom FFU it would not boot Windows 10 IOT core , so for all those new bees like me its recommended to stick to a "Raspberry Pi 3 B" board the one without a "+" and Win 10 IOT would boot without any issues provided instructions are followed..no issues with wireless, Bluetooth and Ethernet port whatsoever all works as expected.

Here is a direct amazon link from where I got my board after getting frustrated with a B+ board:

https://www.amazon.com/gp/product/B01CD5VC92 

So to cut is short, for now stick to the "PI 3 B" board and not the "PI 3 B +", avoid the board with a PLUS for now, until we hear something from Microsoft about a new release or in this forum.

Answer 18

Hey!

I am Beginner of Raspberry Pi. I bought my first Raspberry Pi(the 3 model B+) two weeks ago. I tried to install Windows Iot on it, but my Pi does not boot (the green LED doesnt glow). 

Later I realize that Rp 3 b+ is too new to be supported. I found a method to solve it: 

https://social.msdn.microsoft.com/Forums/en-US/64f33778-4c86-4460-9e4e-53348c73733e/raspberry-pi-3-b-windows-iot-core-boot-work-around?forum=WindowsIoT 

I replaced the six files in EFIESP, then i tried to boot again. This time the green LED glows once at the beginning, but nothing comes out on my display. 

Why does it not work? What should I do? I need help!!!Please!!!

SummerGroot

Answer 19

@SummerGroot

Why does it not work? What should I do? I need help!!!Please!!!

Raspberry Pi3B+ is currently not supported and if above steps did not help you need to wait until its officially supported

br
Andre

Answer 20

SHRIMANT PATEL gives good advice - I have both and it's challenging enough to be on the cutting edge on one or two things (e.g. IoT core, Azure), then adding workarounds for drivers likely will slow down any good you might want to actually do with the solution! :)

Shout out for Adafruit because they give so much to the community through their videos and materials - regardless of where you buy them. Coincidently here's a link to their "non +" Pi 3

Raspberry Pi 3 - Model B $35 https://www.adafruit.com/product/3055

Even if you don't want a bundle I like to refer to the description https://www.adafruit.com/product/3058 as a nice list of things and why you _might_ want them. Two off the top that can make everything else better

Pi Cobbler Plus with cable - can break out pins to a breadboard

Jumper wires in rainbow colors

Another option is female/female jumpers you can attach directly to Pi and kind of stick the leads of components into the other end..

Answer 21

FWIW: I just tried Window Insider Build 17115 and it still doesn't boot on Pi 3B+.

Answer 22

Any news on wifi support for the Raspberry Pi 3B+ ?

Answer 23

FYI: I just allowed the Pi 3B+ to auto-update from the FFU provided by Andy12986 above in this thread. It updated from 16299.15 to 16299.371 and booted without losing the Ethernet support. Still no Bluetooth or WiFi support though.

Answer 24

i have tried @Andy12986 FFU but on my rp3b+ is stuck on loading screen, any suggestion?

Thanks!

Alessio

Answer 25

i have tried @Andy12986 FFU but on my rp3b+ is stuck on loading screen, any suggestion?

Thanks!

Alessio

Could be a failure to expand the data partition on the first boot or a failed flash. Usually you would see an endless spinning circle when that occurs. Try flashing the SD card again after clearing the SD Card with the "Clear Procedure with DISKPART" posted above. If that fails try another SD Card.

Answer 26

Hey Peter,

Gaining elevated permissions to install the driver might be tricky. A better route to take would be following the manufacturing guide for creating custom images. The following link describes the process well-

https://docs.microsoft.com/en-us/windows-hardware/manufacture/iot/create-a-basic-image

Following the instructions in Lab 1a (Create a basic image) and Lab 1e (Add a driver to an image) will allow you to incorporate the Ethernet drivers. You could also use Lab 1c (Add a file and a registry setting to an image) to install the correct boot files to the boot partition, the elfs and dats I posted above. However this would require altering the BSP to not include Boot Firmware, it might be easier for testing to just add them after flashing the FFU.

For other users that are not capable of completing the ADK manufacturing labs, I did the work for you. Below is a custom full flash images with the Ethernet drivers rolled in, updated boot firmware and removal of Rpi 3 b WiFi and Bluetooth services. WiFi and Bluetooth have been removed because we currently do not have drivers for those and the existing drivers cause long boot times.

(Raspberry Pi 3 B+ Compatible ETHERNET ONLY Windows IOT Core 16299.15 FFU)

Download-

https://1drv.ms/u/s!AsvmyE1dw3yggvEafd_lLUqghA1UCw

Flash the image to a memory card

1. Start the Windows IoT Core Dashboard.

2. Plug your micro SD card into your technician PC, and select it in the tool.

3. From Setup a new device, select Device Type: Custom.

4. From Flash the pre-downloaded file (Flash.ffu) to the SD card, click Browse, browse to your FFU file then click Next.

5. Optional: Change the default device name (Default is minwinpc.)

6. Enter your device password.

7. Accept the license terms, and then click Install. The Windows IoT Core Dashboard formats the micro SD card and installs the new image.

WARNING - If you flash this image for testing I recommend disabling windows updates. Microsoft Update can and most likely will overwrite your boot firmware with the old elfs/dats. (run the following from ssh or powershell sc.exe config wuauserv start=disabled)

Just in case someone need to use the MAC of the Ethernet port for Andy's packaged image. 

The MAC address of Ethernet port is 00:80:0F:11:70:00 rather than the original Pi's MAC. 

Regards, 

Answer 27

Hi everyone,

Im currently facing a problem with my Raspberry PI 3B+ due to the fixed IP address that is in the custom image.

I have set up multiple Rasberry PI's with this image and put on the same network. Because all my raspberry's have now the same MAC address this doesn't work, only one raspberry works on my network.

Any idea how I can change my MAC address?

Regards,

Answer 28

connect with powershell then:

Set-NetAdapter -Name "Ethernet" -MacAddress "B8-27-EB-89-7F-BE"

Answer 29

Thanks, that got me started. Now i can wait for the official support of the raspi 3b+ :-)

Answer 30

Has anyone tried the 17661 release to see if any of the issues are resolved??

Answer 31

There will be a public preview for Raspberry Pi 3 Model B+ soon
if nothing unforeseen occurs may be later this month

br
Andre

Answer 32

17661 (Flashed from IOT Core Dashboard) still doesn't boot.

Answer 33

same here, 17661 does not boot

Answer 34

RaspberryPi 3B+ Technical Preview Build 17661

https://social.msdn.microsoft.com/Forums/en-US/1cd4a6d3-96e2-46de-8555-fae468962c52/raspberrypi-3b-technical-preview-build-17661?forum=WindowsIoT

Answer 35

I tried it.. touch capability, wifi & Bluetooth are not supported. Guess we will have to wait. :D

Answer 36

Hi,

I just flashed the Image but I am stucked in Windows "Getting things ready" Welcome to Windows 10 IoT Core. 

I don't Know what it's wrong because I am Reading that it is working for the others users.

Thanks for your help 

Answer 37

San Disk Ultra Pro 32GB
Formatted using Windows disk management
IOT Dashboard
Setup Up New Device
OS Build - Windows Insider Preview 17686
Copied files Git https://github.com/raspberrypi/firmware/tree/master/boot and download the following updated boot files-fixup.dat fixup_x.dat fixup_cd.dat start.elf start_x.elf start_cd.elf

setup, loaded successfully, no bluetooth, no wifi. 

Answer 38

The official tehnical preview of IoT core for the 3b+ from microsoft also exhibits this problem.

Every single MAC address is the same... i don't know what reason would they possibly have to not use the hardware mac....

Answer 39

Thank you so much for this fix. I tried multiple installs and even a different power supply before I finally found a thread that said the Pi 3B+ is unsupported. nd then found your fix. Finally I can continue phew.

Answer 40

It actually took two reboots for the complete boot. Still no network. I also found 17661 preview build for Pi 3B+ that might work, downloading now... 

https://www.microsoft.com/en-us/software-download/windowsiot 

Answer 41

17744 is what is available now. Does anyone have this working, and how?

Answer 42

https://social.msdn.microsoft.com/Forums/en-US/64f33778-4c86-4460-9e4e-53348c73733e/raspberry-pi-3-b-windows-iot-core-boot-work-around?forum=WindowsIoT

you need to replace some files in boot, i just go mine to boot

Answer 43

MisterShow any experience around the latest build to share with us?
regarding WiFi, touch capability?

Answer 44

Your image works really well.  It boots faster than the 3b+ image that microsoft put out after the fact.  One question I have, "Is there a way to limit the network speed to only communicate on 10/100?".  I'm using a POE hat and only 10/100 network speeds are supported.  When I boot up your image with the POE hat connected, I get no ethernet/internet connectivity whatsoever.  Any ideas you may have would be greatly appreciated.

Thanks,

Michael

Answer 45

Your image works really well.  It boots faster than the 3b+ image that microsoft put out after the fact.  One question I have, "Is there a way to limit the network speed to only communicate on 10/100?".  I'm using a POE hat and only 10/100 network speeds are supported.  When I boot up your image with the POE hat connected, I get no ethernet/internet connectivity whatsoever.  Any ideas you may have would be greatly appreciated.

Thanks,

Michael

I would assume the network card would auto negotiate to 10/100. Is it possible you are confusing lack of connectivity because of no indicator lights? Take note of the Rpi 3 B+ default behavior:

The default LED modes put 1000Mb/activity on orange and 100Mb/activity
on green, but this leaves no indication for a 10Mb link.

Answer 46

Thanks Andy.  I would have assumed as well that the card would auto negotiate to 10/100 but unfortunately, it wasn't.  However it negotiates, it didn't seem to be aware of the limitation.  I was able to manually configure the NIC to operate at 10/100 and then I was good to go.  Thank you for your reply.

Answer 47

Many thanks for modified image! I am running my b+ now with that. much appreciated!

Answer 48

Hi Andre;

I'm having the same problem. I have a Raspberry PI 3 B+ i got from a CannaKit. I am using a Samsung Evo 32gb class 10 microSD card. I have tried the installation using the Windows 10 IoT Core Dashboard numerous times. It has never booted. I can insert the raspian card that came with the kit and it will boot right up. I'm not sure where to go from here.

---

Shawn

Answer 49

Isso ajudou muito, mas ainda não conseguir conectar na internet nem cabo nem wifi

Answer 50

Ola, não conseguir fazer o procedimento, poderia me ajudar?

Answer 51

Do you have an updated version of this workspace that works with the latest PowerShell implementation of the ADK addons? I've tried converting what you did here over to the PowerShell method but keep running into problems.

Answer 52

Andy teria como você fazer uma imagem com a versão 17763 do windows iot core??

Answer 53

Well Done ! Ive been trying for months and months !!

Thank you ~!

Using Version 17763 !

Answer 54

hello my friend and happy new year

i've foloow all 

and now i can boot on windows 10 IOT one

problems is

when i start devcon dp_add c:\drivers\net7800-arm-n650f.inf

nothing run

and i can't go to " drivers " folder by cd drivers command

so no ethernet connection, only ok with usb wifi donggle

i just find how statr powersheel 

by this commands

net start WinRM

Set-Item WSMan:\localhost\Client\TrustedHosts 192.168.0.158

Enter-PSSession -ComputerName 192.168.0.158 -Credential 192.168.0.158

new prompt windows open for the password

i can enter in the raspberry

when i type

devcon dp_add c:\driver\net7800-arm-n650f.inf - " the name of the directory is driver not drivers "

this is the answer

********************************** WARNING **********************************
devcon : devcon.exe failed.
    + CategoryInfo          : NotSpecified: (devcon.exe failed.:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError
This Devcon command should only be used for development/testing purposes.
Driver package INF files should be added/updated into the offline OS image
using the supported offline package deployment process in order to ensure
that they are properly configured and integrated into the Windows OS state.
Updating driver package INF files from within the runtime environment of
this OS product may lead to unexpected OS state conflicts, resulting in the
inability to apply future updates to core OS components and/or drivers on
retail/consumer systems.
********************************** WARNING **********************************
Adding the specified driver package to the machine failed.
[192.168.0.158]: PS C:\>

oups what append

your help pls

could you help me

Answer 55

This worked for me...

Answer 56

Hi Andy, do you a ffu for 17763, that has working network ?

Answer 57

Hi Andy, do you a ffu for 17763, that has working network ?

I could make one for 17763, however I'd rather not give the Microsoft dev team any excuse to not officially release the RPi 3 B+ with WiFi and Bluetooth.

Answer 58

Hey

Anyone know how i could reenable the touch capabillity from touch screen on Raspberry 3B+ ?

Answer 59

This fix also worked with the latest build (17763) on Windows 10 IOT on a Raspberry Pi 2 v1.2.

Answer 60

Is Microsoft serious about Win10 IoT Core or is it just a toy to them? I have real product development that requires real support, not some here-today-gone-tomorrow demo release never to be updated again.

No wonder Microsoft has no traction in the embedded CPU market with Win10 IoT Core if this fiasco with the 3B+ is any indication of the kind of support they offer.

I just finished an upgrade of a real shipping product from CE 5 to WEC 2013 on iMX7, with Win10 IoT Core not even being an option because of lack of vendor support.

Answer 61

Thanks, This works,

I replaced the 6 files and am able to boot 17763 ISO. Works like a charm.

Regards,

Yogesh

Answer 62

I also ran into the problem of installing Windows 10 IoT Core on a Raspberry Pi 3B +. I started from the Raspberry Pi 3B+ Technical Preview Build 17661 version but soon after an update to 17763.1 started. I now have a card with the usual 17661 version
problems but at least I can install applications from Visual Studio and I even managed to install a Huawei K5160 LTE stick. I also hope in a solution to the problems of WiFi and Bluetooth and to a more stable and reliable version but this depend on the dev team priorities...if a dev team is active yet

---

Moreno Borsalino

Answer 63

Excuse me with automatic translation

I am opening Windows 10 IoT Core Insider Preview page every day

However, Microsoft development team will not update

Since I want to create a personal app for RasberryPi3B +, can you tell me how to install the built-in WiFi driver?

Answer 64

Hi Freskito, I am getting "failed to write provisioning file to the microsd card" while installing my flash file .ffu(auto as well as custom OS build, I have tried both) into my SD Card. I confirmed that my SD card is eligible for IoT Core. I am also having Raspberry Pi 3 B+. Please help if you have any idea about this issue.

Answer 65

Did we ever get further than this? Did you ever make a version for 17763?

---

Chris Shields

Answer 66

Thank you Andy12986 it's working.