EwfApi.dll Doesn't Work Without Plug and play?

  • Thread starter Thread starter TerryW
  • Start date Start date
T

TerryW

We are trying to bypass a printer being found by plug and play.

We disable the plug and play service, to find that our ewfapi.dll
doesn't work anymore? Has anyone ran into this before??

TIA

Terry
 
Terry,

I could not get quite your question. What is the connection between EWF API and PnP Printer?
Could you describe exactly what you do on your image?
 
We create a custom shell that monitors the EWF. To do this we write a
dll that interfaces with the MS file ewfapi.dll. It reports the
current usage and the state of the ewf. We find that after we disable
the PNP service we can no longer use the dll. The ewf still works and
we can still enable/disable it but the dll misreports the condition.
 
Terry,

I got it. Sorry, I misread your original post.

I don't think the ewfapi.dll can work properly with PnP service disabled. The ewfapi.dll imports Setup APIs (SetupDiXxx) (to
enumerate devices, e.g.) and therefore has dependencies on PnP.
 
Is there a work around?? Thanks for the reply.
Trying to eliminate a printer being detected when system starts up...
 
Terry,

Have you tried to remove "Class Installer - Printers" component from the Configuration?
 
I don't know how to disable/remove class INstaller printer. And I do
need one printer installed. Can I disable/remove it post reseal, and
if so how?

Thanks a lot for the help.
 
Set TD Min visibility level to 200 (or 100) and you will see the "Class Installer - Printers" component in your Configuration.
Disable it or remove.
Uncheck "Auto-resolve dependencies" option in TD settings (Tools-->Options-->Dependency Check page).
Re-build your image and ignore all the errors/tasks about the missing "Class Installer - Printers" component.
Deploy the new image and see if it helps.

In post-FBA image... Try to remove [HKLM\SYSTEM\ControlSet001\Control\Class\{4D36E979-E325-11CE-BFC1-08002BE10318}] key with all
subkeys and see if it helps (I haven't tried such, though).
 
Hey,KM's right that the ewfapi has got the dependencies with the PNP
..It happened in my case however :( not sure .I see that probably
reaching the resource of PNP that in common is tied up with the ewf
might help * requires a test *.If its a static kind of resource then u
can include only that for ewf purpose.

Kesavan


KM said:
Set TD Min visibility level to 200 (or 100) and you will see the "Class Installer - Printers" component in your Configuration.
Disable it or remove.
Uncheck "Auto-resolve dependencies" option in TD settings (Tools-->Options-->Dependency Check page).
Re-build your image and ignore all the errors/tasks about the missing "Class Installer - Printers" component.
Deploy the new image and see if it helps.

In post-FBA image... Try to remove [HKLM\SYSTEM\ControlSet001\Control\Class\{4D36E979-E325-11CE-BFC1-08002BE10318}] key with all
subkeys and see if it helps (I haven't tried such, though).

--
KM,
BSquare Corporation
I don't know how to disable/remove class INstaller printer. And I do
need one printer installed. Can I disable/remove it post reseal, and
if so how?

Thanks a lot for the help.
Click to expand...
Click to expand...
 
Back
Top