I'm considering picking up a new SD card for this because the best I have now is a 16GB Class 10 SD card. Windows 10 works, but according to task manager, the SD card is maxed almost 100% of the time. It can barely keep up and it's very noticeble.

So you recommend using an A1 card, but why? A2 cards have better specs and they're barely more expensive. Is there an issue with hardware support or does the performance advantage of A2 cards not really materialize on the Pi?

Everything needed is in "C:\DDP\MMO\product.dat".

I don't have a Lumia device, but I really want to try to explore WoA on my Mi4, could you help me?

Whenever I open up Installer.Raspberry.Application.exe it just crashes with CLR20r3 error.
I'm running Windows 7 Home Premium x64.

I am having issues with downloading the iso file. Some files are downloading normally and some are failing.

Here is my download log:
https://pastebin.com/517pH2j5

Builds higher than 17134 won't boot on the Lumia 950 (XL) anymore. So it would be nice if you could add support for the bootaa64.efi in your Core Package. This way we can install newer builds where the bootaa64.efi gets replaced with the one 17134 automatically.

Maybe add a manually check for it, so after updates bootaa64.efi can be replaced with it too.

After setting up account and password when booting windows 10 for first time I keep getting , something went wrong "OOBESETTINGS", and setup never completes

Drive Selection does not work. Opening the Installer results in the above error message. No disk drives can be found to use for writing to the SD Card because of the Get-Disk error.

I get "There has been a problem during deployment: DISM exited with code 2".

• Dism.exe /Cleanup-MountPoints <- to see if cleaning up the mountpoints fixed the issue.
• Use Diskpart to 'clean' the SDCard.
• Re-downloaded the 'WoA-Installer-Rpi'

Windows 10 build: 1809
Core-Utils: 1.4.0

Can anyone point me in the right direction?

WoA-Installer_Rpi log:

2019-02-15 11:58:00.579 +01:00 [Verbose] Default directory for WimFolder has been set to "C:\Users\justi\Desktop\Win10Arm\WoA.Installer.for.Raspberry.Pi" 2019-02-15 11:58:00.616 +01:00 [Information] Importing Core Package from "C:\Users\justi\Desktop\Win10Arm\WoA.Installer.for.Raspberry.Pi\Core Package 1.4.0 (with USB and Ethernet).zip" 2019-02-15 11:58:00.657 +01:00 [Information] Extracting from "C:\Users\justi\Desktop\Win10Arm\WoA.Installer.for.Raspberry.Pi\Core Package 1.4.0 (with USB and Ethernet).zip" 2019-02-15 11:58:00.661 +01:00 [Verbose] Ensuring that '"Files"' is empty 2019-02-15 11:58:04.600 +01:00 [Verbose] Default directory for WimFolder has been set to "C:\Users\justi\Desktop\Win10Arm\WoA.Installer.for.Raspberry.Pi" 2019-02-15 11:58:04.609 +01:00 [Verbose] Trying to load WIM metadata file at '"C:\Users\justi\Desktop\Win10Arm\WoA.Installer.for.Raspberry.Pi\install.wim"' 2019-02-15 11:58:04.675 +01:00 [Verbose] Getting WIM stream 2019-02-15 11:58:04.678 +01:00 [Verbose] (WIM) Finding Magic Bytes... 2019-02-15 11:58:04.679 +01:00 [Verbose] (WIM) Found Magic Bytes at 0 2019-02-15 11:58:04.679 +01:00 [Verbose] (WIM) Finding WIM XML Data... 2019-02-15 11:58:04.679 +01:00 [Verbose] (WIM) Found WIM XML Data at 043431349642 2019-02-15 11:58:04.763 +01:00 [Verbose] Wim metadata deserialized correctly WimMetadata { TotalBytes: "4343134964", Images: [ImageMetadata { DirectoryCount: "22565", FileCount: "98622", TotalBytes: "17051468701", HardLinkBytes: "6590715483", CreationTime: Time { HighPart: "0x01D44CED", LowPart: "0x43022989" }, LastModificationTime: Time { HighPart: "0x01D4C3E0", LowPart: "0xE4EADD89" }, WimBoot: "0", Windows: Windows { Arch: "12", ProductName: "Microsoft® Windows® Operating System", EditionId: "Professional", InstallationType: "Client", ServicingData: ServicingData { GdrDuRevision: "0", PKeyConfigVersion: "10.0.17763.1;2016-01-01T00:00:00Z" }, ProductType: "WinNT", ProductSuite: "Terminal Server", Languages: Languages { Language: "en-US", Default: "en-US" }, Version: Version { Major: "10", Minor: "0", Build: "17763", SpBuild: "292", SpLevel: "0" }, SystemRoot: "WINDOWS" }, Name: "Windows 10 Pro", Description: "Windows 10 Pro", Flags: null, DiplayName: "Windows 10 Pro", DisplayDescription: "Windows 10 Pro", Index: "1" }] } 2019-02-15 11:58:04.772 +01:00 [Verbose] WIM metadata file at '"C:\Users\justi\Desktop\Win10Arm\WoA.Installer.for.Raspberry.Pi\install.wim"' retrieved correctly 2019-02-15 11:58:04.776 +01:00 [Information] Extraction successful from "C:\Users\justi\Desktop\Win10Arm\WoA.Installer.for.Raspberry.Pi\Core Package 1.4.0 (with USB and Ethernet).zip" 2019-02-15 11:58:06.850 +01:00 [Information] Core Package imported 2019-02-15 11:58:08.913 +01:00 [Information] Flashing GPT image... 2019-02-15 11:58:08.920 +01:00 [Verbose] We are about to run Etcher: "Files\Tools\Etcher-Cli\x86\Etcher" "-d \\.\PHYSICALDRIVE1 \"Files\Core\Gpt.zip\" --yes --no-unmount" 2019-02-15 11:58:08.924 +01:00 [Verbose] Starting process { FileName: "Files\Tools\Etcher-Cli\x86\Etcher", Arguments: "-d \\.\PHYSICALDRIVE1 \"Files\Core\Gpt.zip\" --yes --no-unmount" } 2019-02-15 11:58:09.224 +01:00 [Verbose] Process started sucessfully 2019-02-15 11:59:12.783 +01:00 [Information] Validating flashed image... 2019-02-15 11:59:53.873 +01:00 [Information] GPT image flashed 2019-02-15 11:59:53.881 +01:00 [Verbose] Getting "EFIESP" volume 2019-02-15 11:59:54.346 +01:00 [Verbose] Couldn't find any partition in "Number: 1, Size: 28.97 GB, AllocatedSize: 28.97 GB". Updating Storage Cache... 2019-02-15 11:59:54.785 +01:00 [Verbose] Retrying Get Partitions... 2019-02-15 11:59:58.383 +01:00 [Verbose] Copying directory "Files\UEFI" to "." 2019-02-15 11:59:58.386 +01:00 [Verbose] Copying file "C:\Users\justi\Desktop\Win10Arm\WoA.Installer.for.Raspberry.Pi\Files\UEFI\bootcode.bin" to "E:\bootcode.bin" 2019-02-15 12:00:01.405 +01:00 [Verbose] Copying file "C:\Users\justi\Desktop\Win10Arm\WoA.Installer.for.Raspberry.Pi\Files\UEFI\config.txt" to "E:\config.txt" 2019-02-15 12:00:01.549 +01:00 [Verbose] Copying file "C:\Users\justi\Desktop\Win10Arm\WoA.Installer.for.Raspberry.Pi\Files\UEFI\fixup.dat" to "E:\fixup.dat" 2019-02-15 12:00:01.614 +01:00 [Verbose] Copying file "C:\Users\justi\Desktop\Win10Arm\WoA.Installer.for.Raspberry.Pi\Files\UEFI\readme.md" to "E:\readme.md" 2019-02-15 12:00:01.653 +01:00 [Verbose] Copying file "C:\Users\justi\Desktop\Win10Arm\WoA.Installer.for.Raspberry.Pi\Files\UEFI\RPI_EFI.fd" to "E:\RPI_EFI.fd" 2019-02-15 12:01:18.298 +01:00 [Verbose] Copying file "C:\Users\justi\Desktop\Win10Arm\WoA.Installer.for.Raspberry.Pi\Files\UEFI\start.elf" to "E:\start.elf" 2019-02-15 12:01:24.129 +01:00 [Information] Deploying Windows 10 ARM64... 2019-02-15 12:01:24.129 +01:00 [Information] Cleaning existing Windows 10 ARM64 partitions... 2019-02-15 12:01:24.137 +01:00 [Information] Creating Windows partition... 2019-02-15 12:01:25.673 +01:00 [Verbose] Mounting volume "Label: , Size: 0 b, Partition: Disk: Number: 1, Size: 28.97 GB, AllocatedSize: 28.97 GB, Number: 3, Letter: " 2019-02-15 12:01:38.000 +01:00 [Information] Windows Partition created successfully 2019-02-15 12:01:38.003 +01:00 [Verbose] Getting "WindowsARM" volume 2019-02-15 12:01:39.148 +01:00 [Information] Applying Windows Image... 2019-02-15 12:01:39.154 +01:00 [Verbose] Checking image at "C:\Users\justi\Desktop\Win10Arm\WoA.Installer.for.Raspberry.Pi\install.wim", with index "C:\Users\justi\Desktop\Win10Arm\WoA.Installer.for.Raspberry.Pi\install.wim" 2019-02-15 12:01:39.154 +01:00 [Verbose] Image file at '"C:\Users\justi\Desktop\Win10Arm\WoA.Installer.for.Raspberry.Pi\install.wim"' exists 2019-02-15 12:01:39.154 +01:00 [Verbose] Getting WIM stream 2019-02-15 12:01:39.154 +01:00 [Verbose] (WIM) Finding Magic Bytes... 2019-02-15 12:01:39.154 +01:00 [Verbose] (WIM) Found Magic Bytes at 0 2019-02-15 12:01:39.154 +01:00 [Verbose] (WIM) Finding WIM XML Data... 2019-02-15 12:01:39.154 +01:00 [Verbose] (WIM) Found WIM XML Data at 043431349642 2019-02-15 12:01:39.174 +01:00 [Verbose] Wim metadata deserialized correctly WimMetadata { TotalBytes: "4343134964", Images: [ImageMetadata { DirectoryCount: "22565", FileCount: "98622", TotalBytes: "17051468701", HardLinkBytes: "6590715483", CreationTime: Time { HighPart: "0x01D44CED", LowPart: "0x43022989" }, LastModificationTime: Time { HighPart: "0x01D4C3E0", LowPart: "0xE4EADD89" }, WimBoot: "0", Windows: Windows { Arch: "12", ProductName: "Microsoft® Windows® Operating System", EditionId: "Professional", InstallationType: "Client", ServicingData: ServicingData { GdrDuRevision: "0", PKeyConfigVersion: "10.0.17763.1;2016-01-01T00:00:00Z" }, ProductType: "WinNT", ProductSuite: "Terminal Server", Languages: Languages { Language: "en-US", Default: "en-US" }, Version: Version { Major: "10", Minor: "0", Build: "17763", SpBuild: "292", SpLevel: "0" }, SystemRoot: "WINDOWS" }, Name: "Windows 10 Pro", Description: "Windows 10 Pro", Flags: null, DiplayName: "Windows 10 Pro", DisplayDescription: "Windows 10 Pro", Index: "1" }] } 2019-02-15 12:01:39.174 +01:00 [Verbose] We are about to run DISM: "C:\Windows\SysNative\dism.exe" "/Apply-Image /ImageFile:\"C:\Users\justi\Desktop\Win10Arm\WoA.Installer.for.Raspberry.Pi\install.wim\" /Index:1 /ApplyDir:F:\" 2019-02-15 12:01:39.175 +01:00 [Verbose] Starting process { FileName: "C:\Windows\SysNative\dism.exe", Arguments: "/Apply-Image /ImageFile:\"C:\Users\justi\Desktop\Win10Arm\WoA.Installer.for.Raspberry.Pi\install.wim\" /Index:1 /ApplyDir:F:\" } 2019-02-15 12:01:39.186 +01:00 [Verbose] Process started sucessfully 2019-02-15 12:09:03.460 +01:00 [Error] An error has ocurred Installer.Core.Exceptions.DeploymentException: There has been a problem during deployment: DISM exited with code 2. at Installer.Core.FullFx.DismImageService.<ApplyImage>d__1.MoveNext() in C:\Users\super\source\repos\Install\Installer.Core.FullFx\DismImageService.cs:line 39 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Installer.Raspberry.Core.RaspberryPiWindowsDeployer.<ApplyWindowsImage>d__9.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Installer.Raspberry.Core.RaspberryPiWindowsDeployer.<Deploy>d__5.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Installer.Raspberry.Core.RaspberryPiDeployer.<DeployWindows>d__7.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Installer.Raspberry.Core.RaspberryPiDeployer.<DeployCoreAndWindows>d__3.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Installer.Raspberry.ViewModels.MainViewModel.<DeployUefiAndWindows>d__59.MoveNext() 2019-02-15 12:09:03.478 +01:00 [Information] Error: There has been a problem during deployment: DISM exited with code 2.

Dism log:

2019-02-15 12:01:39, Info DISM DISM.EXE: Dism.exe version: 10.0.17763.1 2019-02-15 12:01:39, Info DISM DISM.EXE: Executing command line: "C:\Windows\SysNative\dism.exe" /Apply-Image /ImageFile:"C:\Users\justi\Desktop\Win10Arm\WoA.Installer.for.Raspberry.Pi\install.wim" /Index:1 /ApplyDir:F:\ 2019-02-15 12:01:39, Info DISM DISM Provider Store: PID=4928 TID=2496 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection 2019-02-15 12:01:39, Info DISM DISM Provider Store: PID=4928 TID=2496 Connecting to the provider located at C:\Windows\system32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2019-02-15 12:01:39, Warning DISM DISM Provider Store: PID=4928 TID=2496 Failed to load the provider: C:\Windows\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e) 2019-02-15 12:01:39, Info DISM DISM Provider Store: PID=4928 TID=2496 Connecting to the provider located at C:\Windows\system32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2019-02-15 12:01:39, Info DISM DISM Provider Store: PID=4928 TID=2496 Connecting to the provider located at C:\Windows\system32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2019-02-15 12:01:39, Info DISM DISM Provider Store: PID=4928 TID=2496 Connecting to the provider located at C:\Windows\system32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2019-02-15 12:01:39, Info DISM DISM Provider Store: PID=4928 TID=2496 Connecting to the provider located at C:\Windows\system32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2019-02-15 12:01:39, Info DISM DISM Provider Store: PID=4928 TID=2496 Connecting to the provider located at C:\Windows\system32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2019-02-15 12:01:39, Warning DISM DISM Provider Store: PID=4928 TID=2496 Failed to load the provider: C:\Windows\system32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e) 2019-02-15 12:01:39, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table. 2019-02-15 12:01:39, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider 2019-02-15 12:01:39, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager 2019-02-15 12:01:39, Info DISM DISM.EXE: Attempting to add the commands from provider: FfuManager 2019-02-15 12:01:39, Info DISM DISM.EXE: Succesfully registered commands for the provider: FfuManager. 2019-02-15 12:01:39, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager 2019-02-15 12:01:39, Info DISM DISM.EXE: Succesfully registered commands for the provider: WimManager. 2019-02-15 12:01:39, Info DISM DISM.EXE: Attempting to add the commands from provider: VHDManager 2019-02-15 12:01:39, Info DISM DISM.EXE: Attempting to add the commands from provider: GenericImagingManager 2019-02-15 12:01:39, Info DISM DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager. 2019-02-15 12:01:39, Info DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager 2019-02-15 12:01:39, Info DISM DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager. [4928] [0x80070002] RestoreDirMetadata:(2544): The system cannot find the file specified. [4928] [0x8144012d] 2019-02-15 12:09:03, Warning DISM DISM WIM Provider: PID=4928 [RestoreDirMetadata:(2550) -> Error restoring directory metadata] F:\Windows\WinSxS\arm64_microsoft-windows-p..ctivescan.resources_31bf3856ad364e35_10.0.17763.1_en-us_06992b36f3e2b22f (HRESULT=0x80070002) - CWimManager::WimProviderMsgLogCallback [4928] [0x80070002] RestoreDirMetadata:(2710): The system cannot find the file specified. [4928] [0x80070002] WimCreateDirectory:(3272): The system cannot find the file specified. [4928] [0xc144012e] 2019-02-15 12:09:03, Error DISM DISM WIM Provider: PID=4928 F:\Windows\WinSxS\arm64_microsoft-windows-p..ctivescan.resources_31bf3856ad364e35_10.0.17763.1_en-us_06992b36f3e2b22f (HRESULT=0x80070002) - CWimManager::WimProviderMsgLogCallback [4928] [0x80070002] RestoreDirTree:(3523): The system cannot find the file specified. [4928] [0x80070002] WIMApplyImageInternal:(709): The system cannot find the file specified. 2019-02-15 12:09:03, Error DISM DISM WIM Provider: PID=4928 TID=2496 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:1036 - CWimManager::Apply(hr:0x80070002) 2019-02-15 12:09:03, Error DISM DISM Imaging Provider: PID=4928 TID=2496 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:2813 - CGenericImagingManager::InternalCmdWimApply(hr:0x80070002) 2019-02-15 12:09:03, Error DISM DISM Imaging Provider: PID=4928 TID=2496 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:547 - CGenericImagingManager::ExecuteCmdLine(hr:0x80070002) 2019-02-15 12:09:03, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.

I downloaded the required files and started the installation, but it seems to work fine until I get up to 64 %, and then it says, Error code 112, there has been a problem during your deployment: DISM exited with code 112

Download fails if Downloads folder is moved. My Downloads folder was moved to D: drive and image download fails with a path not found error. If I run the cmd from the empty Downloads folder on my boot dive, all is good.

Hii! This its not a report of a bug but still I need some info or help about this topic. I have some doubts about how its the actual state of woa. The msoffice implementation of office its still on emulation?If the answer is yes, it use a 32 bit arm msoffice or 64bit arm build instead? I ask these thing because i want to use microsoft office app under wine natively. I need, if it possible, a few advices of how to extract the binary to run it on linux, if its compiled to arm 32 bits... i search a lot time ago inside a windows rt image and i could find microsoft offfice rt version... and if there its a 32 bit arm office it would be great than we could launch it natively out of the box on linux distro. Iva compiled wine several times on my pi 3, just for test the notaz recompiled binaries of diablo II, starcraft, etc. But the only program i could execute from other source its rufus... and it didnt work properly because its really windows api demanding. The same happend on x86 system, so for me was a succes. If you wanna help i would be extremly greatful with you. Thanks anyway.

Just like the tittle, could you please send me the package, [email protected] thanks!!

What's the purpose of this project ?

With linux you can do a loooot more ...
(And even recompile the entire system for your own needs)

Here's the epitome of bad ideas: WoA installer creating a running install on Google Pixel ARM devices.

(Please close this issue/suggestion. This is the worst idea ever.)

Hello, I'm getting this error during deployment : there is a problem during deployment DISM code 1314.
during the process, windows 10 pro is asking me to format some discs, first I had cancelled, then, I've tried to accept each one, but stills fails.
thw wim version is 18247.1001.arm64.
should i try to proceed under win 7 instead of win 10?
kind regards.
phil

I'm trying to flash an sdcard with Windows 10 ARM for my raspberry pi. I did everything according to the tutorial, and it flashes fine but after flashing GPT image(and validating it) it just crashes with the error in the title. This is the error log of the last few lines:

2019-02-14 14:39:09.085 +00:00 [Verbose] Default directory for WimFolder has been set to "F:\sources"
2019-02-14 14:39:09.088 +00:00 [Verbose] Trying to load WIM metadata file at '"F:\sources\install.wim"'
2019-02-14 14:39:09.107 +00:00 [Verbose] Getting WIM stream
2019-02-14 14:39:09.108 +00:00 [Verbose] (WIM) Finding Magic Bytes...
2019-02-14 14:39:09.108 +00:00 [Verbose] (WIM) Found Magic Bytes at 0
2019-02-14 14:39:09.108 +00:00 [Verbose] (WIM) Finding WIM XML Data...
2019-02-14 14:39:09.108 +00:00 [Verbose] (WIM) Found WIM XML Data at 032812550832
2019-02-14 14:39:09.127 +00:00 [Verbose] Wim metadata deserialized correctly WimMetadata { TotalBytes: "3281255083", Images: [ImageMetadata { DirectoryCount: "19154", FileCount: "86519", TotalBytes: "14402294320", HardLinkBytes: "6416458914", CreationTime: Time { HighPart: "0x01D44CED", LowPart: "0x43022989" }, LastModificationTime: Time { HighPart: "0x01D4C471", LowPart: "0x278FC22F" }, WimBoot: "0", Windows: Windows { Arch: "12", ProductName: "Microsoft® Windows® Operating System", EditionId: null, InstallationType: null, ServicingData: null, ProductType: null, ProductSuite: null, Languages: null, Version: Version { Major: "10", Minor: "0", Build: "17763", SpBuild: "1", SpLevel: "0" }, SystemRoot: "WINDOWS" }, Name: "Windows 10 Pro", Description: "Windows 10 Pro", Flags: null, DiplayName: "Windows 10 Pro", DisplayDescription: "Windows 10 Pro", Index: "1" }] }
2019-02-14 14:39:09.132 +00:00 [Verbose] WIM metadata file at '"F:\sources\install.wim"' retrieved correctly
2019-02-14 14:39:35.563 +00:00 [Verbose] The '""' does not exist
2019-02-14 14:39:49.261 +00:00 [Verbose] Default directory for WimFolder has been set to "C:\Users\Tim\Downloads"
2019-02-14 14:39:49.264 +00:00 [Information] Importing Core Package from "C:\Users\Tim\Downloads\Core Package 1.4.0 (with USB and Ethernet).zip"
2019-02-14 14:39:49.286 +00:00 [Information] Extracting from "C:\Users\Tim\Downloads\Core Package 1.4.0 (with USB and Ethernet).zip"
2019-02-14 14:39:49.288 +00:00 [Verbose] Ensuring that '"Files"' is empty
2019-02-14 14:39:52.661 +00:00 [Information] Extraction successful from "C:\Users\Tim\Downloads\Core Package 1.4.0 (with USB and Ethernet).zip"
2019-02-14 14:39:54.577 +00:00 [Information] Core Package imported
2019-02-14 14:39:56.227 +00:00 [Verbose] The '"Files\Drivers\Pre-OOBE"' exists
2019-02-14 14:39:56.227 +00:00 [Verbose] The '"Files\Core"' exists
2019-02-14 14:39:56.227 +00:00 [Verbose] The '"Files\UEFI"' exists
2019-02-14 14:39:56.227 +00:00 [Verbose] The '"Files\Drivers"' exists
2019-02-14 14:39:56.227 +00:00 [Verbose] The '"Files\Tools"' exists
2019-02-14 14:39:56.228 +00:00 [Information] Flashing GPT image...
2019-02-14 14:39:56.232 +00:00 [Verbose] We are about to run Etcher: "Files\Tools\Etcher-Cli\x86\Etcher" "-d \\.\PHYSICALDRIVE2 \"Files\Core\Gpt.zip\" --yes --no-unmount"
2019-02-14 14:39:56.234 +00:00 [Verbose] Starting process { FileName: "Files\Tools\Etcher-Cli\x86\Etcher", Arguments: "-d \\.\PHYSICALDRIVE2 \"Files\Core\Gpt.zip\" --yes --no-unmount" }
2019-02-14 14:39:57.245 +00:00 [Verbose] Process started sucessfully
2019-02-14 14:40:48.837 +00:00 [Information] Validating flashed image...
2019-02-14 14:41:09.223 +00:00 [Information] GPT image flashed
2019-02-14 14:41:09.227 +00:00 [Verbose] Getting "EFIESP" volume
2019-02-14 14:41:10.173 +00:00 [Verbose] Couldn't find any partition in "Number: 2, Size: 28.97 GB, AllocatedSize: 28.97 GB". Updating Storage Cache...
2019-02-14 14:41:11.292 +00:00 [Verbose] Retrying Get Partitions...
2019-02-14 14:41:11.733 +00:00 [Error] An error has ocurred
System.NullReferenceException: Object reference not set to an instance of an object.
   at Installer.Raspberry.Core.RaspberryPiDeployer.<DeployUefi>d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Installer.Raspberry.Core.RaspberryPiDeployer.<DeployCoreAndWindows>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Installer.Raspberry.ViewModels.MainViewModel.<DeployUefiAndWindows>d__61.MoveNext()
2019-02-14 14:41:11.736 +00:00 [Information] Error: Object reference not set to an instance of an object.

I believe I did everything according to the tutorial, I downloaded the Windows 10 arm64 cmd thing, ran it, mounted the ISO, downloaded CorePackage 1.4.0 with USB and Ethernet, opened both in your tool, and pressed deploy, and it still gave me an error.

Do you know what's wrong?

Thanks!

Edit:
I also tried different SD cards. I checked what the partition table looked like when it crashed, and it appears to burn the 100mb boot image(rpi also gives me the colors when I plug the sd card in), but it doesn't seem to write the system files.

EDIT2:
I actually just noticed that when generating the ISO it gives an DISM error 1450. This is when making boot.wim. Does this matter?

Trying to run mono Installer.Raspberry.Application.exe (the one from https://github.com/WOA-Project/WoA-Installer/releases/tag/1.5) results in following message:

The entry point method could not be loaded due to Could not load file or assembly 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies.

and exits immediately afterwards.

I want to report an error when deploying windows 10 arm64 (See the screenshot below)

after I investigate. I found this (see screenshot below)

I don't know what caused it.

Subj. Device even has the next gen SoC (e.g. Snapdragon 82x).

when try windows 10 arm64 flash to sdcard : display log Method not found : 'system.runtime.interopservices.architectureInstaller.Core.Services.Wim.DiskImageMetaData.get_Architecture()'
Screenshots:
https://ibb.co/t8JL28w
https://ibb.co/Jd0J6fh
log file: 20190213.txt

Solved : install .NET Framework

As stated above, the link does only led to a OneDrive site which tells that the file does not exist anymore

Hi thanks for this nice project. can I install the OS in the USB flash drive ?
thanks

Prerequisites: Windows 1809 sk version, WoA 1.2, Core 1.4.0.

Issue: after boot system stays in UEFI Shell.

Quick Fix: reboot (with command), press ESC to go to setup, then there is a menu (my system is still booting, after that I will post exact menu location) You can choose to boot UEFi or Windows. If You choose Windows it will boot up successfully.

Proper fix: UEFI setup to boot to the right partition (or how is it called in UEFI)...

help please,when i put the file core package.rar in "windows on arm installer" it say that file :file/cores doesn't exist
i try with differents version

I am trying to install Windows 10 on my 950XL
I have used the Windows Phone Internals to unlock the phone. (I think)
However, when I try to install window 10 using the WoA Installer, it tells me that it can't access the phone disk, that I need to place the phone in mass storage mode.
screens.pdf

I must be missing a step, but I can't figure out what it is. Any suggestions?

When do we need to install the GPU driver, before installation of Windows 10 or after?

It's experimental. What can you tell about stability?

And what performance do we gain with the GPU driver?

Hi,
Is there any way to back to to Windows 10 mobile? Basically revert the process. If there is such it will be good if it is in the document.
Thanks!

I've installed several versions of windows 10 including 17134 builds and both home and pro on the latest installer and core package versions. I can't get windows to see the either the 4G or the wifi only the Bluetooth is detected. I also can't use the USB cable to charge the phone as it's draining the battery too fast for the QI charging to keep up.

The website RG-adguard.net looks generally fishy to new visitors, and it isn't clear where the binaries are downloaded from (e.g. piracy). I actually had a real argument with someone on the Raspberry Pi Forum who took one look at the RG-adguard.net site and thought we were doing piracy.

https://uupdump.ml/ is a similar website, but is easier to use, clear on where the files are downloaded from, no ads, and overall safer-looking. And not from Russia.

How to connect to internet after setting up windows 10

It is currentlly not possible to find out which version of app and core pack is used, displaying it in app would be useful. Also maybie bump the version in exe properties (currently 1.0.0.0).

• Display app version
• Display core pack version

I'm using rpi 3 and Core Package 1.3.0 (with MCCI's USB)

It boots up into the UEFI shell. It was hard to tell what it was, the font is so bad it's hard to read. Once I realized that it was UEFI, I booted into setup and changed the default boot option to Broadcom, saved the setup, and rebooted again, and was finally greeted with the Windows Logo. But after running for about 15 minutes, it went back to the UEFI shell.

I did everything as it was written in the instructions and the installation started normally but when the installer reached 98%(in applying Windows Image) it just stuck there and is not going any further.
Please can anyone tell what is happening wrong or what additionally I will have to do?

Can you add support for making a qemu disk image or something so we can test the OS out?