Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Sign in to follow this  
bingloverld

WinPE automated wim deployment

Recommended Posts

So I can simply make:

select disk 0
clean
convert gpt
create partition primary size=350
format quick fs=ntfs label="System"
assign letter="S"
create partition primary
format quick fs=ntfs label="Windows"
assign letter="W"
exit

??

Share this post


Link to post
Share on other sites

Yes, that's the idea.

And I believe also what happens if you install "normally" from a DVD.

BUT you need to correct the script, the Boot partition (the one MS calls "System") MUST be FAT32 (thanks to the UEFI "standard") as most motherboards won't have a NTFS EFI driver and it should be of the EFI type:

Quote


select disk 0
clean
convert gpt
create partition efi size=350
format quick fs=ntfs label="System"
assign letter="S"
create partition primary
format quick fs=ntfs label="Windows"
assign letter="W"
exit


 


 

If you make it 350 Mb you won't have issues with 512 bytes vs. 4096 bytes disk sectors, though I am not too sure why the size of that partition is so large, and why exactly there is the recommendation (in the given page):

https://msdn.microsoft.com/en-us/library/windows/hardware/dn621890.aspx

create partition efi size=100
rem ** NOTE: For Advanced Format 4Kn drives,
rem          change this value to size = 260 **
format quick fs=fat32 label="System"
assign letter="S"

jaclaz


 
 

Share this post


Link to post
Share on other sites
On Saturday, September 10, 2016 at 9:58 AM, bingloverld said:

Yes I tooked gpt recommendations directly from Microsoft, gpt.txt is 100% copy/paste. 

It is for Windows 8 OS.

1. I have never seen stock Windows 7 recovery work on GPT disk.
2. Windows 10 does not have a recovery image.

I can post you my EFI diskpart scripts for Win7 and Win10 on monday if you want.

Share this post


Link to post
Share on other sites
On 11.9.2016 at 4:31 PM, Tripredacus said:

It is for Windows 8 OS.

1. I have never seen stock Windows 7 recovery work on GPT disk.
2. Windows 10 does not have a recovery image.

I can post you my EFI diskpart scripts for Win7 and Win10 on monday if you want.

That would be great! Thank you. 

I think this 4Kn and size 260MB are specials hdd, we don't use them anyway.

on 13.09.2016 added:

PS USB SSD did not wanted to run in UEFI mode because the BOOTX64.EFI file was damaged. I have simply copied this file from DVD with Windows 10 LTSB and it works!

Edited by bingloverld

Share this post


Link to post
Share on other sites

We apparently had a rollback and lost some posts. If you didn't see the two scripts I posted yesterday, I can post them again.

Share this post


Link to post
Share on other sites

For Windows 7/Server 2012/R2 (presumably 2016 also)

sel disk 0
clean
convert gpt

create part efi size=100
format quick fs=fat32 label="System"
assign letter=s

create part msr size=128

create part pri
format quick fs=ntfs label="Windows"
assign letter=w

exit

For Windows 10

sel disk 0
clean
convert gpt

create part efi size=260
format quick fs=fat32 label="System"
assign letter="s"

create part msr size=16

create part pri
shrink minimum=500
format quick fs=ntfs label="Windows"
assign letter="w"

create part pri
format quick fs=ntfs label="Recovery"
assign letter="r"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001

exit

Some things to note. These are designed for diskpart from Windows 10 ADK. Some older versions of diskpart would not auto-select a newly created partition. In case you are using an older diskpart, you would need to add "sel part x" between the "create" and "format" commands. So in the Win10 script, it would be sel part 1, 3, 4.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×