Found the issue to this problem. The script fails on Windows 7, even with updated PowerShell with latest .NET framework: $PSVersionTable Name Value ---- ----- PSVersion 5.1.14409.1005 PSEdition Desktop Tried this script/program in Windows 10 VM and download script works, no CURL -H missing argument error. I think the CURL -H problem only on Windows 7.
Okay I think something is wrong with the .253 consumer iso... When I make usb install drive using rufus and select the partition scheme to GPT the file system set to NTFS not FAT32 like usual... but I try it anyway... when try booting on Asus notebook it gave warning "Secure boot violation"... but trying on alienware it boot okay to the windows setup AFAIK the GPT must be use FAT32 and MBR using NTFS, so what when wrong with my .253 consumer iso... is anyone had this same experience?
You're right. If your partition scheme is GPT/UEFI you format the USB disk to FAT32. If your partition scheme is MBR/BIOS you format the USB disk to NTFS.
The problem is there's no option on rufus to change it to FAT32.. so whether I choose GPT or MBR the file system is still NTFS for that ISO. I checked with LTSC ISO to make sure there's no problem with Rufus and everything is normal. So there must be something wrong with the 17763.253 ISO. Here's my x64 Consumer ISO SHA : E955971E3BF398B9859332B484CF868EC27BDB8E is it the correct ones?
But you can still use NTFS with GPT UEFI, Rufus creates a partition on your USB stick so you can boot from NTFS. Also you can download abbodi's ESD<>WIM converter (Found here on this forum), and it will compress the wim into a smaller sized esd.
Oow I see it now... so it is normal to have GPT install usb on NTFS formatted? Or will it be problem when I actually using it to install the windows... I haven't try it yet to install the windows since when I try it on asus it shows me an error
Okay sorry s1ave77... I only found it strange ISO created by the tools on this topic is creating the problem that I got. don't know if its already offtopic.
ISOs created are original MVS/VLSC ones, unlikely the problems are related to the way they were created.