If any of you fancy giving it a go let me know in the comments! Read more about it here: The second option is used to create a Windows To Go USB stick, from which you can boot Windows directly from the USB drive. We’ll use the 1st option: “Standard Windows installation”. For that press the button shown below:īrowse to the path where you saved the ISO image, select it and press “Open” (sorry for the Portuguese “Abrir”):Īs you can see the “Create a bootable disk using” changed from “FreeDos” to “ISO Image”, and all the previous options are automatically selected, label filled and two new options showed up: Let’s choose now the Windows Server 2016 2019 ISO image that has been previously downloaded. I believe the minimum USB size for creating the boot disk are 8GB, but nowadays, the best option is to get a 16GB or 32GB USB stick.ĭo not fill the rest of the options because Rufus will fill them automatically when we select the ISO image. I will not be responsible if you erase all your data if you select the wrong disk!įrom the application main screen select the drive you want to use. Rufus will clean your USB stick and delete all the data in it!! For this note, I’m using a Windows Server 2016 2019 ISO that I downloaded from Microsoft. Have your Windows ISO file ready as we’re going to need it later on, to “burn” it onto the USB stick. It’s a single file application, so no installation needed. Just a side note: with this app you can not only create Windows USB bootable thumb drives but you can also use it to create Linux bootable USB thumb drives.Ĭreate a Windows Server 2016 2019 Bootable USB Before startingĭownload Rufus latest version from the Rufus official website and save it to your computer. This time I will use a small application called Rufus that does all the hard work for you, though, from my experience, it’s a bit slower copying files to the USB stick. Opened \\.In a previous article, I created a Windows Server bootable USB using the command line. Will use 'Windows 10 Pro' (Build: 17134, Index 6) for Windows To Go xml)Įxtracting: C:\Users\skoushan\AppData\Local\Temp\Ruf5364.tmp (From. SHA256: f8f56e6387054573a1bcfe3028ffc6df28275c7252da951c2a9861bae823ec39ĭevice eliminated because it appears to contain no mediaįound USB 2.0 device 'Generic Flash Disk USB Device' (058F:6387)ĭisk type: Removable, Disk size: 16GB, Sector size: 512 bytesĬylinders: 1988, Tracks per cylinder: 255, Sectors per track: 63Įxtracting: C:\Users\skoushan\AppData\Local\Temp\Ruf1754.tmp (From. Opening: \\.\CDROM0\sources\install.wim: (API)Ĭould not access image: The data is invalid.įound USB 3.0 device 'TOSHIBA USB FLASH DRIVE USB Device' (0930:6545)Ĭomputing checksum for 'C:\Users\skoushan\Desktop\Win10_1803_English_圆4.iso'. WIM extraction method(s) supported: 7-Zip, wimgapi.dll Image does not have an x86 Master Boot Record What could be the problem here? Logĭisk type: Removable, Disk size: 32GB, Sector size: 512 bytesĬylinders: 3766, Tracks per cylinder: 255, Sectors per track: 63ĭrive has a Windows 2000/XP/2003 Master Boot Record My device is USB 3.0 (and Rufus recognized that). From the log, it's mostly taking time to extract small files like PNG's, though CPU usage from Rufus is below 1%. The "Applying Windows image" step is taking approximately 10 minutes per 0.1% (i.e. Trying to create a WIndows To GO USB for Windows 10 Pro. I confirmed, by performing an internet search, that these values match the ones from the official image. If using an image, I clicked on the (✓) button to compute the MD5, SHA1 and SHA256 checksums, which are therefore present in the log I copied.Plugging the USB into a different port.I also tried one or more of the following:.I ran a bad blocks check, by clicking Show advanced format options then Check device for bad blocks, and confirmed that my USB is not defective.The log I am copying is the FULL log, starting with the line Rufus version: x.y.z - I have NOT removed any part of it.I clicked the "Log" button in Rufus (last small blue button before START) and copy/pasted the log into the line that says below.I performed a search in the issue tracker for similar issues using keywords relevant to my problem, such as the error message I got from the log.I looked at to see if my question has already been answered.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |