Page 2 of 2

Re: IFW fails writing image to removable drive with Bitlocke

Posted: Tue Jul 19, 2016 12:36 am
by Bob Coleman
"I searched for how to determine the build number. I used "WINVER" from the
command line. It pops up a dialog that says 10586.0. "

Yes, same procedure here, but 10586.0 is probably the original Windows 10 1511 build. It's certainly significantly earlier than 10586.494 which I have. Since Windows 10 updates automatically, I'm trying to figure out how you managed to stay at 10586.0.

This mostly a curiosity. I'm not suggesting that it probably has anything to do with the problem at hand.

Re: IFW fails writing image to removable drive with Bitlocke

Posted: Sun Jul 24, 2016 3:08 am
by TeraByte Support
that is a write error. look in the .log to see the windows error code
reported. Run chkdsk /f, run drive manufactures scan or spinrite on it.

you can also use the options for the smaller cache size or io sizes if you think the file system driver doesn't like the large writes.

"timg11" wrote in message news:11800@public.image...

I've been using IFW x64 2.99-00 with a removable drive.
I recently encrypted the removable drive with Bitlocker.
Now IFW gets 3% into writing the image, and fails with "Unable to write data
to file!"
Nothing has changed except for Bitlocker on the image storage drive.

I tried IFW with both VSS and PHYlock, and get the same failure.