none
Unable to deploy and test x86 printer driver on Win8 x64 with VS2012 RRS feed

  • Question

  • Hello,

    I created a V4 printer driver using the new Wizard in VS2012 + WDK 8. I followed the directions in related documentation "Developing v4 Printer Drivers v1.2" to setup the debug target, signing and deployment options.

    Since I only have one Windows 8 machine, I set up the Remote test machine to be my own local machine (Win8 x64).

    The build got fine until it reached the deployment phase where it fails with the following error:

    "The driver processor architecture does not match the processor architecture of the target computer.  The processor architecture of the driver and the computer must match."

    I tried also by duplicating the Win32 solution configuration to create an x64 version of the driver but then it fails again with the following error:

    "Driver Deployment Task Failed: Default Printer Driver Package Installation Task (possible reboot)"

    I don't where to go from here.

    Any help appreciated.

    Monday, September 24, 2012 3:09 PM

Answers

  • Sorry I was finally able to correct this issue. I simply forgot to include lines for the -PipelineConfig.xml and related library files in the main .INF file.

    I don't have anymore error messages.

    Now I'm stuck on next step: When I start remote debugging, the driver is recompiled, deployment starts, no error messages, but then it never ends. It seems to hang.

    Just to make sure, I tried to manually install a printer with the Add Printer Wizard and was able to select my driver and succesfully finished the installation.

    Have I done the steps in the correct order? Is there a different way to start debugging into the XPS rendering filter?

    Tuesday, September 25, 2012 9:36 AM

All replies

  • Are you able to see a cmd window pop up and execute the "Default Printer Driver package Installation Task"? Can you check if there is any log file generated in "C:\DriverTest\Logs" that is related to that task?

    Why were you duplicating the Win32 configuration, cant you pick the x64 configuration from VS dropdown menu (or a projects configuration props) and  try to deploy and see. You do have to set the driver install properties again.


    Thanks PVR

    Monday, September 24, 2012 10:05 PM
  • Following your indications, I selected the x64 configuration, re-entered the driver debbuger, signing and install properties again, and tried to deploy.

    It failed just like previously (+ an extra error message "Driver Deployment Task Failed: Driver Removal (x64) (possible reboot)").

    I do have cmd windows that pop up during deployment but it's too quick to read anything useful (besides the fact that there are some red lines - errors I guess).

    I got .wtl files DriverTest\Logs folder, each related to one step of the deployment process. In the file "Default_Printer_Driver_Package_Installation_Task_(possible_reboot)_00010.wtl", I have the following error stated:

    <EndTest 
    	Title="WDTF_TEST                 : Import  Driver Package" 
    	TUID="" 
    	Result="Pass" 
    	Repro="" CA="6206572" LA="6206871" >
    <Data>
    <WexTraceInfo ThreadId="248" ProcessId="1972" TimeStamp="4816474684"/>
    </Data>	<rti id="3428231467" />
    	<ctx id="2189700239" />
    </EndTest>
    <Error 
    	File="" 
    	Line="-1" 
    	ErrCode="0x0" 
    	ErrType="" 
    	ErrorText="Error 0x00000000" 
    	UserText="System.Runtime.InteropServices.COMException (0x80004005): Une erreur HRESULT E_FAIL a été retournée à partir d&apos;un appel à un composant COM.
       à Microsoft.DriverKit.DefaultPrinterDriverPackageInstallationClass.InstallPrinterDriverFromPackage(String server, String infPath, String driverName, String environment, UInt32 flags)
       à Microsoft.DriverKit.DefaultPrinterDriverPackageInstallationClass.PerformDefaultPrinterDriverPackageInstallation()" CA="6614946" LA="6615159" >
    <Data>
    <WexTraceInfo ThreadId="248" ProcessId="1972" TimeStamp="4816884972"/>
    </Data>	<rti id="3428231467" />
    	<ctx id="320002455" />
    </Error>
    <Error 
    	File="" 
    	Line="-1" 
    	ErrCode="0x0" 
    	ErrType="" 
    	ErrorText="Error 0x00000000" 
    	UserText="[HRESULT: 0x80131604]. Test operation failed: &apos;Microsoft.DriverKit.DefaultPrinterDriverPackageInstallationClass.PerformDefaultPrinterDriverPackageInstallation&apos;." CA="6668317" LA="6668487" >
    <Data>
    <WexTraceInfo ThreadId="2156" ProcessId="1200" TimeStamp="4816891892"/>
    </Data>	<rti id="3613907475" />
    	<ctx id="320002455" />
    </Error>
    <EndTest 
    	Title="Microsoft.DriverKit.DefaultPrinterDriverPackageInstallationClass.PerformDefaultPrinterDriverPackageInstallation" 
    	TUID="" 
    	Result="Fail" 
    	Repro="" CA="6716993" LA="6717238" >
    <Data>
    <WexTraceInfo ThreadId="2156" ProcessId="1200" TimeStamp="4816940506"/>
    </Data>	<rti id="3613907475" />
    	<ctx id="320002455" />
    </EndTest>
    <Msg 
    	UserText="WDTF_DRIVER_SETUP_SYSTEM  :  - SnapTriageLogs()" CA="6764523" LA="6764768" >
    <Data>
    <WexTraceInfo ThreadId="248" ProcessId="1972" TimeStamp="4816992941"/>
    </Data>	<rti id="3428231467" />
    	<ctx id="384048256" />
    </Msg>
    <Msg 
    	UserText="WDTF_DRIVER_SETUP_SYSTEM  :          Target: BCRAPOULET" CA="6814453" LA="6814725" >
    <Data>
    <WexTraceInfo ThreadId="248" ProcessId="1972" TimeStamp="4817037238"/>
    </Data>	<rti id="3428231467" />
    	<ctx id="384048256" />
    </Msg>
    <PFRollup 
    	Total="3" 
    	Passed="2" 
    	Failed="1" 
    	Blocked="0" 
    	Warned="0" 
    	Skipped="0" CA="7169592" LA="7169707" >
    	<rti id="2870898666" />
    	<ctx id="384048256" />
    </PFRollup>

    It seems I have a COM error when the driver is installed on the machine. Is there any way to have more information about it?

    Tuesday, September 25, 2012 7:22 AM
  • Sorry I was finally able to correct this issue. I simply forgot to include lines for the -PipelineConfig.xml and related library files in the main .INF file.

    I don't have anymore error messages.

    Now I'm stuck on next step: When I start remote debugging, the driver is recompiled, deployment starts, no error messages, but then it never ends. It seems to hang.

    Just to make sure, I tried to manually install a printer with the Add Printer Wizard and was able to select my driver and succesfully finished the installation.

    Have I done the steps in the correct order? Is there a different way to start debugging into the XPS rendering filter?

    Tuesday, September 25, 2012 9:36 AM
  • And what did you add to fix it exactly? Just wondering because I'm facing the same error.
    Monday, October 23, 2017 12:51 PM