Normally this should not be possible but ewfmgr and fbwfmgr told me
exactly this a few minutes ago. It's not the first time this has happened.
Actions preceding this phenomen were to enable/disable fbwf a few times
with reboots between.
I did a "fbwfmgr /disable" followed by a "ewfmgr c: /disable" and
performed a reboot. No change: still both of them active.
I did just a "ewfmgr c: /disable" and after reboot, both, ewf and fbwf,
were disabled.

Is this a known bug? Did anyone have similar experiences? Is there a
solution /workaround? Problem is that switching on/off of fbwf is done
in the field and should be very reliable.

Juergen

EWF and FBWF cannot be used to protect the same drive. They can be in the
same image, but they need to protect different drives.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com

"Juergen Striegel" wrote in
message news:OSCB8Gt$IHA.2072@TK2MSFTNGP02.phx.gbl...

In deed, I did the impossible... We use a self-written program to set
the ewf/fbwf state. I think that there's a situation where the program
disables fbwf and enables ewf at nearly the same time.
Normally (in my opinion) the windows API should lock ewf against fbwf
but the lock seems to be a little holey.

The first device I told of (below) could be recovered by the described
actions. Another device cannot be pulled out from "dual write filter
mode": ewfmgr and fbwfmgr and the corresponding API functions tell us
that both write filters are ON.

Sean Liming (MVP) schrieb: