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.
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.
Statistics: Posted by incognitum — Sat Jul 27, 2024 9:04 am
