[Repository:] Everything about Windows RT (WOA) v8-x-x and v10 ARM

You need to login to view this posts content.

 

Thanks very much for the files. I thought it wasn't even made for arm64. LOL
Now the last thingie, which isn't arm64 is recdisc.exe.
It was present in WRT81 as arm32, then removed in W10, then lately added again, but I can't find it as arm64 + mui.

 

I have to look, in which 1st W10 build it was re-added. RecDisc.exe was removed in W8-1 b9600 and re-added in W10 TH1 b10240. SoundRecorder.exe was removed in W10 TH1 b10240. Those two are only things, what I don't have in arm64.

 

During some searching for abandonned programs I have found win32 Sound Recorder arm32 in "extended files" of b8400.
There is a DLL, which needs to be registered to classes:
C:\Windows\System32\regsvr32.exe "C:\Program Files\SoundRecorder\WavDest.dll"

 

I have new interesting issue:
I alligned new Kingston DataTraveler Max 1TB USB-C v3-1 stick as follows in DiskPart:

GPT Partition 1 System 1024 MB ESP FAT32 Z:
GPT Partition 2 Reserved 256 MB MSR
GPT Partition 3 Primary 952 GB OS NTFS X:

Then I placed:
-arm64 bootmgfw.efi to Z:\EFI\Boot\bootaa64.efi
-default MS made BCD file (with modded paths) + boot.sdi to Z:\EFI\Microsoft\Boot\*.*
(Yep, it was 1st-ly made with: bcdboot X:\Windows /s Z: /f UEFI , then it was customised.)
-arm64 24H2 winre.wim to X:\WinRE\winre.wim (where winre.wim has 56 boot-critical drivers)
So, under Boot-Menu-Item 2 I can successfully boot to USB 24H2 arm64 winre.wim placed on boot.sdi ram-disk:
ramdisk=[X:]\WinRE\winre.wim

Then I applied also 24H2 Enterprise arm64 install.wim to X: (where install.wim has 144 complete drivers):
dism /apply-image /imagefile:C:\ISO\sources\install.wim /index:1 /applydir:X:\
But under Boot-Menu-Item 1 I couldn't successfully boot to USB 24H2 full Windows, because I got "Inacessible Boot Device" (USB) BSOD.

So, I mounted remote registry:
reg load HKLM\WimRegistry x:\windows\system32\config\system
and imported settings to load USB drivers sooner:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\WimRegistry\HardwareConfig]
"LastConfig"="{de4e5acc-2d98-11b2-a85c-9d70f64634bc}"
"LastId"=dword:00000000
[HKEY_LOCAL_MACHINE\WimRegistry\HardwareConfig\{de4e5acc-2d98-11b2-a85c-9d70f64634bc}]
"Id"=dword:00000000
"BootDriverFlags"=dword:0000001c
[HKEY_LOCAL_MACHINE\WimRegistry\HardwareConfig\Current]
"Id"=dword:00000000
"BootDriverFlags"=dword:0000001c
and dismounted remote registry:
reg unload HKLM\WimRegistry

While I got MotherboardUUID {de4e5acc-2d98-11b2-a85c-9d70f64634bc} from working 24H2 arm64 winre.
But under Boot-Menu-Item 1 I still can't successfully boot to USB 24H2 full Windows, because I got "IO1 Initialization Failed" BSOD this time.

(BTW: I also have bootarm.efi, bootx64.efi and bootia32.efi (all are bootmgfw.efi) in Z:\EFI\Boot and winre_arm32, winre_x64.wim and winre_x32.wim (all with boot-critical drivers) in X:\WinRE,
so under Boot-Menu-Items 3, 4, 5 I am able to successufully boot USB arm32, x32 and x64 WinRE on my other PCs).

So in the end I have boot stick with boot menu on arm64 PC (Secure-Boot is Off), where under option 2 I can boot to USB WinRE 24H2 arm64 (with 56 boot-critical drivers),
but where under option 1 can't boot to USB full Windows 24H2 arm64 (with 144 complete drivers).

I will yet try to place only 56 bootcritical drivers in install.wim, but other than that, I am completelly stuck.

Any hint?

 

So:
-booting WinRE works only because of ram-disk.
-"BootDriverFlags"=dword:0000001c or dword:00000014 solves "Inacessible Boot Device" (USB) BSOD.
-"IO1 Initialization Failed" BSOD remains unsolved.

It almost looks like the driver for the USB drive would be completelly missing.

 

You need to login to view this posts content.

 

bcdedit /set {default} bootlog yes
...it does nothing. No log anywhere. Nice boot logging MS.

 

Offtopic BTW:
These programs have real troubles with ReFS (access denied, permitions):
1. VMware Workstation (VM storage folder),
2. Steam (Games storage folder),
3. Epic Games (client update gets to never ending loop),
4. Google Picasa (pictures on ReFS drives can't be crawled)...

 

OK, so I replicated/confirmed "arm64-booting-full-Windows-from-USB-problem" on my 2nd arm64 device.

 

Again, I replicated/confirmed "arm32-booting-full-Windows-from-USB-problem" on my arm32 device.

So the conclusion is, no arm64/arm32 device is able to boot from USB "Windows2Go". Only thing you can boot from USB is boot.sdi ramdisk's solutions, because ramdisk driver works OK.

The cause is non-generic and special USB driver for each SoC. Maybe also MS doesn't want the full Windows USB arm booting to work.
That is probably the reason, why Windows2Go was never introduced on arm64 OSes and maybe also the reason, why Windows2Go was scrapped in general.
Maybe some advanced player skilled with drivers (like the beautiful fr owl guy) could look on the issue and compare the difference between ramdisk driver or USB one.

 

You need to login to view this posts content.

 

So, when you select on Chrome's homepage to download standalone arm64 installer, Google will in fact give you the x32 one. Great work Google.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.