That’s my issue too.
17763 (which supposedly works) + Core Package 1.2 = Failure.
In my case, it would sit at “Getting ready…” for ~5 minutes, then a blank screen for another ~5 minutes, and then a blue screen would appear for about 1/5 of a second (no joke) before immediately disappearing and trying to restart (although this also fails and hangs, I think I read somewhere that the USB driver interferes with rebooting).
I am switching to 17134 + Core Package 1.1 to see what happens. I will post the results of how that goes soon.
I don’t know if this is relevant, but in the Core Package 1.1 the SD-card loader is “arisanSD” or something like that, whereas in 1.2 it is “uSD.” Something around how the SD card loads changed. Also in 1.2, the “Exiting UEFI and booting OS Kernel!” message does not appear, whereas it does in 1.1. I’m more concerned about the SD Card (driver?) change.
EDIT: I have successfully got to Windows Setup on 17134 + Core 1.1.
1 Like
I keep getting crashing with driver issues using the most current core package. Weird.
there may be a corrupt file after the Windows installation to the SD card. because it happened to me in the same build. I have tried experimenting by changing the tool. driver. and uefi. but this problem was resolved after I used the wimlib and MBR scheme in the Windows tool on Raspberry imager. and also I check corrupt data with the CHKDSK command in cmd
note: inside the core package it uses old UEFI and drivers. so my advice. use the drivers and uefi that you think work
edit : for uSD controller use the default controller (broadcom). because I tried arasan it was slow
Just go into the bios and change it to arisanSD and it will work in CORE1.2
Please, don’t use 17763 (Windows 10 Version 1809)
It will BSOD (Blue screen) while loading the Windows Setup.
I’m using 17134 and it works quite fine.
17763 does blue screen. Apparently there are some workarounds, but it’s unclear as to whether or not they are consistent. I have stopped testing 17763 for the time being.
I currently use the latest version of Windows 10 (build 18334) and work without BSOD. but rather heavy on raspberry pi 3 B+
All: Please be sure you’re using the latest UEFI. USB won’t work otherwise, there was a required patch to make cache coherency work properly. I believe this means you must use Core 1.3, but @SuperJMN will have to confirm.
Have you tried booting with nothing plugged in the USB after sorting out the options in the bios settings. Had a few BSOD because of that… when the OUT OF BOX stuff loads you will be fine then to plug in everything and leave it there as all of the drivers will then be loaded
1 Like
@ndg_2000 Do you mean that I should unplugged the USB keyboard also? (after setting a BIOS and ready to restart)
Yes set bios settings start then remove keyboard until yo get to the oobe part
Sounds like you’re still using the old usb drivers. Until now, I have not heard of any problems with booting with devices plugged in with the new drivers.
I’m working from worst case scenario just to get him booted. On first install I removed everything until drivers were loaded then have had no issues with it since.
Terry is correct. Just by the error, you’re operating on old drivers. You’ll need the new USB drivers to be able to make this a manageable machine.
Hi All
I have now tried both “Core Package 1.3.0 (with USB)” and “Core Package 1.4.0 (with USB and Ethernet)” from link below with 17763.292 and no Luck. Get BSOD initially and if you leave it to reboot a few times while keyboard is connected, you get to “Choose keyboard layout” but Keyboard drivers does not appear to be loaded as keyboard is not working.
https://onedrive.live.com/?authkey=!AAg1P7lDOqOnZ9g&id=C8B0DBB75540E8D5!1189489&cid=C8B0DBB75540E8D5
Any Ideas, would really like to test this and see the performance ans what is possible.
Thanks in Advance.
Just curious - has anyone looked into removing packages (Remove-AppxPackage) or such, like DWS Lite, on these ARM editions to lighten the load? It does make a significant difference on regular Windows 10/Server 2019 builds.
(Speaking of which, there is a leaked Server 2016 or 2019 ARM build out there, iirc. 10.0.14324.1001.rs1_onecore_mqsrv_sc.160414-1853_arm64fre_server-serverarm64_
Might be interesting to try…)