• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Question MS media creation tool

dlerious

Platinum Member
I'm having trouble creating a bootable USB drive with the media creation tool. It gets about halfway and then I get a blue screen and reboot. I tried 2 different computers with the same results. Haven't tried creating a CD yet. One of my computers has Win 10 sitting on a 4TB 5400 RPM spinner and I used the drive for storage for a few years. There's too much data to copy to a 1TB SSD (probably over 3TB. I thought about moving the data to my external - probably next step. I don't have much installed, so I don't mind. It beats the 4 hours or so it took to upgrade from 1709 to 1809.

Anyone else hear about problems vreating bootable USB?
 
Anyone else hear about problems vreating bootable USB?
I think it failed on me one time over the 4 or so years Windows 10 has been out, but I've made quite a few of them without issue. It didn't blue screen though, it just told me the drive couldn't be created.

But for 2 different PCs to blue screen when trying to create the installation USB, I would guess maybe the USB drive is bad?
 
I just happened to have created one today for a new build, and it worked just fine on the first try.

Assuming you are using a large enough USB drive, I agree with UsandThem - you have a malfunctioning USB drive.
 
Something's not happy in hardware-land, to cause BSODs in two different PCs like that.

I might ordinarily suggest that there was a problem with high-stress RAM/CPU processing, as halfway through the process, it decompresses and verifies (hashes) the resultant ISO, before it starts writing it to the USB drive.

So it could be the USB drive malfunctioning, but ... I wonder. Are these both overclocked rigs? 2500K rigs that haven't been stress-tested, since being overclocked for the last 10 years? Maybe something's amiss.
 
Neither one overclocked (4790K/1800X). I used different USB drives as well. Burned a dvd no problem. I'll add an external and backup the drive later, then nuke the partitions and do a clean install to SSD using the DVD.

Something else always happens with the win10 computer - every time I (dual) boot my Win7 drive after running Win10. Win7 wants to run a chkdsk and ends up removing a couple hundred thousand extended file attributes on the Win10 drive. No problems running either afterwards (other than mentioned chkdsk). Probably why the Win10 drive wasn't booted for a few years.

Thanks
 
You should check your USB drives with a program like h2testw.

A workaround is to download the ISO file and then burn it to the USB drive using a program like rufus.
 
Rufus are good at doing that,what is more,as the free tools,you can do it without any cost.
Been decades since I used Rufus. Heard about something call etcher as well - I use imgburn for optical. Downloaded Win10 ISO, verified the download, burned a dvd with the media creation tool and verified again. Started the install, waled to the bathroom and it crashed before I came back. managed to backup everything on current HDD, deleted everything non-windows to get space below 1TB and migrateed my OS over. In the process of restoring everything else.
 
Never had issues with windows media creation tool. Me think your usb stick is the problem.
It's possible, but I've had no problems reading and writing to them before. I don't remember if they were USB2.0 or 3.0 off hand. One of the first things that came to mind was a fake drive with less than the claimed capacity, but 4GB should be enough (32GB/64GB drives). I'll try copying over lots of data next time to see if there's a problem.
 
It's possible, but I've had no problems reading and writing to them before. I don't remember if they were USB2.0 or 3.0 off hand. One of the first things that came to mind was a fake drive with less than the claimed capacity, but 4GB should be enough (32GB/64GB drives). I'll try copying over lots of data next time to see if there's a problem.

You mean your stick is 4gb or has 4gb left?
 
You don't need Media Crerator to do any of this. Download the ISO Image file. Create a bootable USB from the command prompt. Then extract the ISO files to the root directory of the USB Stick.


To create a bootable USB flash drive
  1. Insert a USB flash drive into a running computer.
  2. Open a Command Prompt window as an administrator.
  3. Type diskpart.
  4. In the new command line window that opens, to determine the USB flash drive number or drive letter, at the command prompt, type list disk, and then click ENTER. The list disk command displays all the disks on the computer. Note the drive number or drive letter of the USB flash drive.
  5. At the command prompt, type select disk <X>, where X is the drive number or drive letter of the USB flash drive, and then click ENTER.
  6. Type clean, and the click ENTER. This command deletes all data from the USB flash drive.
  7. To create a new primary partition on the USB flash drive, type create partition primary, and then click ENTER.
  8. To select the partition that you just created, type select partition 1, and then click ENTER.
  9. To format the partition, type format fs=ntfs quick, and then click ENTER.
    Important
    If your server platform supports Unified Extensible Firmware Interface (UEFI), you should format the USB flash drive as FAT32 rather than as NTFS. To format the partition as FAT32, type format fs=fat32 quick, and then click ENTER.
  10. Type active, and then click ENTER.
  11. Type exit, and then click ENTER.
  12. When you finish preparing your custom image, save it to the root of the USB flash drive. (Extract the ISO Image to the root of the USB Drive)
 
I got it working. I'm in the process of moving some programs over then I have about 6 or 7 photo programs to evaluate. It'll be a while before I do any re-testing.
 
Back
Top