Skip to content
This repository has been archived by the owner on Feb 19, 2019. It is now read-only.

Installer fails with "Error: Object reference not set to an instance of object." #36

Closed
ghost opened this issue Feb 14, 2019 · 14 comments
Closed

Comments

@ghost
Copy link

ghost commented Feb 14, 2019

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?

@mattgahs
Copy link

I'm having the identical issue.

@cdw2286
Copy link

cdw2286 commented Feb 14, 2019

I am having the same issue

Edit:
I tried formatting SD card as both NTFS and FAT32 which did not make a difference.

@SuperJMN
Copy link
Member

It seems the tool isn't recovering access to the disk after it's been flashed. Sorry guys, just can tell you to try to upgrade Windows 10 to the latest version (non Insider) that is Windows 10 version 1809. It may be a problem of PowerShell.

I haven't heard of such a problem until today!

@SuperJMN
Copy link
Member

@cdw2286 You don't have to format any partition on the card. The flash part should make they partition layout ready for the deployment.

@pgrinstead1
Copy link

Same issue for me as well. I am running the latest ver of windows 10. Any idea's?

@cdw2286
Copy link

cdw2286 commented Feb 15, 2019

It seems the tool isn't recovering access to the disk after it's been flashed. Sorry guys, just can tell you to try to upgrade Windows 10 to the latest version (non Insider) that is Windows 10 version 1809. It may be a problem of PowerShell.

I haven't heard of such a problem until today!

Thank you for the response. I am currently upgrading Windows to build 1809 and will report back the results.

@ghost
Copy link
Author

ghost commented Feb 15, 2019

I tried updating to 1809, and it still won't work. Always the same issue. I'll try on another PC to see if that works.

@julienrobin28
Copy link

Hi,
Had the issue when trying to do it from D:
Also, I believe it was running as Administrator.

No problem while running from the Desktop

@cdw2286
Copy link

cdw2286 commented Feb 15, 2019

It seems the tool isn't recovering access to the disk after it's been flashed. Sorry guys, just can tell you to try to upgrade Windows 10 to the latest version (non Insider) that is Windows 10 version 1809. It may be a problem of PowerShell.
I haven't heard of such a problem until today!

Thank you for the response. I am currently upgrading Windows to build 1809 and will report back the results.

UPDATE:
After upgrading Windows to Build 1809 and following @julienrobin28 comment about running WOA Installer from the Desktop (I was previously running from the F: Drive), I was able to successfully install to my SD card.

However, when I put the SD card into the RPi and turn it on, it just goes to a Shell> prompt. Am I missing something?

@abedhaque
Copy link

@cdw2286 If it just goes to the Shell> prompt, follow the instructions here: https://discourse.pi64.win/t/frequently-asked-questions-faq/49

@pgrinstead1
Copy link

Thanks @abedhaque but it still wont boot.

@cdw2286
Copy link

cdw2286 commented Feb 15, 2019

@cdw2286 If it just goes to the Shell> prompt, follow the instructions here: https://discourse.pi64.win/t/frequently-asked-questions-faq/49

That did the trick for me @abedhaque . Thank you!

@DJDirtboy
Copy link

DJDirtboy commented Feb 16, 2019

Same issue.
Run as admin from c:\win10arm64

I'm on Win 10 1809

2019-02-16 16:09:14.374 +01:00 [Verbose] Default directory for WimFolder has been set to "D:\Users\DJDirtboy\Downloads\Win10arm64"
2019-02-16 16:09:14.393 +01:00 [Verbose] Trying to load WIM metadata file at '"D:\Users\DJDirtboy\Downloads\Win10arm64\install.wim"'
2019-02-16 16:09:14.409 +01:00 [Verbose] Getting WIM stream
2019-02-16 16:09:14.410 +01:00 [Verbose] (WIM) Finding Magic Bytes...
2019-02-16 16:09:14.411 +01:00 [Verbose] (WIM) Found Magic Bytes at 0
2019-02-16 16:09:14.411 +01:00 [Verbose] (WIM) Finding WIM XML Data...
2019-02-16 16:09:14.411 +01:00 [Verbose] (WIM) Found WIM XML Data at 043379069812
2019-02-16 16:09:14.437 +01:00 [Verbose] Wim metadata deserialized correctly WimMetadata { TotalBytes: "4337906981", Images: [ImageMetadata { DirectoryCount: "23184", FileCount: "99531", TotalBytes: "17077763926", HardLinkBytes: "6589632387", CreationTime: Time { HighPart: "0x01D44D1D", LowPart: "0x3CE913F7" }, LastModificationTime: Time { HighPart: "0x01D4C553", LowPart: "0x5F2DDBAE" }, WimBoot: "0", Windows: Windows { Arch: "12", ProductName: "Système d’exploitation Microsoft® Windows®", 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: "fr-FR", Default: "fr-FR" }, 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-16 16:09:14.441 +01:00 [Verbose] WIM metadata file at '"D:\Users\DJDirtboy\Downloads\Win10arm64\install.wim"' retrieved correctly
2019-02-16 16:09:20.026 +01:00 [Verbose] Default directory for WimFolder has been set to "D:\Users\DJDirtboy\Downloads\Win10arm64"
2019-02-16 16:09:20.028 +01:00 [Information] Importing Core Package from "D:\Users\DJDirtboy\Downloads\Win10arm64\Core Package 1.4.0 (with USB and Ethernet).zip"
2019-02-16 16:09:20.047 +01:00 [Information] Extracting from "D:\Users\DJDirtboy\Downloads\Win10arm64\Core Package 1.4.0 (with USB and Ethernet).zip"
2019-02-16 16:09:20.051 +01:00 [Verbose] Ensuring that '"Files"' is empty
2019-02-16 16:09:21.643 +01:00 [Information] Extraction successful from "D:\Users\DJDirtboy\Downloads\Win10arm64\Core Package 1.4.0 (with USB and Ethernet).zip"
2019-02-16 16:09:24.384 +01:00 [Information] Core Package imported
2019-02-16 16:09:27.634 +01:00 [Information] Flashing GPT image...
2019-02-16 16:09:27.638 +01:00 [Verbose] We are about to run Etcher: "Files\Tools\Etcher-Cli\x86\Etcher" "-d \.\PHYSICALDRIVE3 "Files\Core\Gpt.zip" --yes --no-unmount"
2019-02-16 16:09:27.640 +01:00 [Verbose] Starting process { FileName: "Files\Tools\Etcher-Cli\x86\Etcher", Arguments: "-d \.\PHYSICALDRIVE3 "Files\Core\Gpt.zip" --yes --no-unmount" }
2019-02-16 16:09:28.762 +01:00 [Verbose] Process started sucessfully
2019-02-16 16:10:25.295 +01:00 [Information] Validating flashed image...
2019-02-16 16:10:56.618 +01:00 [Information] GPT image flashed
2019-02-16 16:10:56.622 +01:00 [Verbose] Getting "EFIESP" volume
2019-02-16 16:10:56.901 +01:00 [Verbose] Couldn't find any partition in "Number: 3, Size: 28,97 GB, AllocatedSize: 230 MB". Updating Storage Cache...
2019-02-16 16:11:00.434 +01:00 [Verbose] Retrying Get Partitions...
2019-02-16 16:11:00.839 +01:00 [Error] An error has ocurred
System.NullReferenceException: La référence d'objet n'est pas définie à une instance d'un objet.

@cewbdex
Copy link
Member

cewbdex commented Feb 18, 2019

@cewbdex cewbdex closed this as completed Feb 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants