difx leads to INACCESSIBLE_BOOT_DEVICE

NTDEV
1

I have a boot start filter driver inside an MSI using difxapp.msm from the WDK RTM. If I install, uninstall, then install declining each prompts to restart the system up to this point (it asked 3 times), then system will blue screen when it is restarted with INACCESSIBLE_BOOT_DEVICE.

I believe it may be because the uninstall operation set the DeleteFlag in the service, but it wasn’t cleared by the second install.

Since this scenario will be common on product upgrade situations where customers may opt not to restart between upgrade steps it seems a disastrous situation. Has anyone else run into this and is there any way around this?

eof

2

argh. I am starting to feel like a guinea pig. A lot of queries about huge problems with difx I see are going unanswered. I get the feeling people are avoiding it. I made the mistake of trusting the docs that recommended using them. It seems at this stage proprietary is probably the best bet where you have control over fixing problems versus being stuck like this.

eof