pbatard
commented
6 years ago It doesn't matter if your device is USB 3.0 if the flash memory inside is slow. Alas, it's not at all uncommon for cheap USB 3.0 device to use flash that can only write at 10 MB/s, in which case you are going to find that applying a Windows image can be excruciatingly slow.
Unless your device can sustain 60 MB/s write speed (be mindful that a USB 3.0 device might be rated 100MB/s read speed, but still have a 10 MB/s write speed or less), you should consider using a different device for Windows To Go, as you will only be disappointed by both the speed at which you can create the Windows To Go drive, and the speed at which it operates.
Also, because Windows is basically using the Windows APIs to apply an image, which means that it's a complete black box, there's literally nothing we can do to speed up things, as Microsoft are the only ones who control what's going on behind the scenes here.
For the record, with a USB 3.0 flash drive that has a 70 MB/s write speed, creating a Windows To Go drive takes less than 15 mins.
skoushan
Ibuprophen
lock[bot]
Checklist
<FULL LOG>below.Rufus version: x.y.z- I have NOT removed any part of it.Additionally (if applicable):
(✓)button to compute the MD5, SHA1 and SHA256 checksums, which are therefore present in the log I copied. I confirmed, by performing an internet search, that these values match the ones from the official image.Issue description
Trying to create a WIndows To GO USB for Windows 10 Pro. The "Applying Windows image" step is taking approximately 10 minutes per 0.1% (i.e. it's going to take a week at this rate). From the log, it's mostly taking time to extract small files like PNG's, though CPU usage from Rufus is below 1%. My device is USB 3.0 (and Rufus recognized that). What could be the problem here?
Log