Scripted installation of Win 10 x64 version 1809 fails after the driver installation step. Error: Invalid Partition Table!

I have been successfully deploying Win 10 x64 version 1809 using my K2000 for several months with no issues. However, last week after doing a successful deployment on a Dell Optipex 3020 in the morning I attempted another deployment in the afternoon on a Dell Latitude E6440. After completing the driver installation step the system automatically reboots and when it attempts to come back up it goes to a black screen and says Invalid Partition Table! I have now tried to deploy on several different machines and each has the same result. 

2 Comments   [ + ] Show comments
  • Normally that is a hardware issue.

    Have you tried re-uploading the ISO again?

    Maybe you are bootig in Legacy Mode but Using UEFI partitioning scripts or vice-versa? - Channeler 2 years ago
  • You might also want to check in Bios if Secure Boot is enabled or disabled. - jboling 2 years ago

Answers (1)

Answer Summary:
Posted by: jmcfates 2 years ago
White Belt

Top Answer

Thanks to Channeler's comment about booting in Legacy or UEFI I was able to figure out the issue.  When i first initiated the imaging process I initiated a one time boot using f12 as i always do and chose UEFI IPV4 However i apparently failed to changed the default from legacy boot to UEFI in the bios. So when the system did the automatic reboot after loading the drivers it booted into legacy, therefore causing the issue. It was booting in legacy bios instead of UEFI.

So thank you Channeler for putting me on the trail

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ