Version .5 made my 4 GB Drive 1 GB

Bug #980751 reported by Brian on 2012-04-13
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Image Writer

Bug Description

The latest version reduced my 4 GB USB Drive down to 4 GB. It created a number of orphaned volumes. I tried to delete these, but this does not free them up to merge back into a valid (whole drive). I think this toasted my drive. Any ideas on how to salvage this drive. You might want to pull this version, as it seems others are having this same issues. Out on the net is seemed like this was a good solution for creating bootable drives from img files. You may want to keep that reputation.

Tobin Davis (gruemaster) wrote :

This utility is not designed to partition your device, it raw writes over the device. If you have an image that is 1G, then the drive will look like a 1G drive when done (regardless of true size). This is just what Windows sees when it looks at the partition table, which comes from the image being flashed.

Changed in win32-image-writer:
status: New → Invalid
Jeff B (skydiver38) wrote :

As Tobin said, ImageWriter doesn't partition - that comes from the image that you burn. See the FAQ about repartitioning for possible solutions to the problem (

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers