Presumably, the FlushFileBuffers call would fail if any removable drive had been removed sometime in the past without being properly ejected.At the end, it asks the operating system to make sure all memory buffers are flushed to storage.
In the case of Windows Imager uses FlushFileBuffers() for that, and waits for that call to return.
Not sure if Etcher does that.
So if a broken driver or something else on the system causes the call to block it may show with Imager, but not with the competition.
Is there a way to flush only the writes pending for the SD card being imaged? That would avoid the software getting hung trying to perform unrelated writes for a different device removed earlier.
After rebooting Windows does imager work?
Statistics: Posted by ejolson — Sat Jul 27, 2024 4:06 pm