Welcome to OStack Knowledge Sharing Community for programmer and developer-Open, Learning and Share
Welcome To Ask or Share your Answers For Others

Categories

0 votes
595 views
in Technique[技术] by (71.8m points)

wix - CustomAction DriverPackageInstall failing with 0x80030005

I am having WDF driver installing using WiX installer via custom action using API DriverPackageInstall. but its failing with error "0x80030005" STG_E_ACCESSDENIED. I am running as admin (assuming no priviledge issues) created test "c" console application that is able to install driver successfully.

<InstallExecuteSequence>
     <Custom Action='UninstallDriver'
             After='InstallInitialize'>
                    REMOVE~="ALL" OR REINSTALL</Custom>
 </InstallExecuteSequence>      
  <CustomAction Id='UninstallDriver'
                BinaryKey='install_lib'
                DllEntry='InstallDriver'
                Execute='deferred'
                Impersonate="no"
                Return='check'/>

Not able to figure why is it failing enabled full logs and checked.

MSI (s) (E8:50) [11:56:09:296]: Invoking remote custom action. DLL: C:WindowsInstallerXXXXXX.tmp, Entrypoint: InstallMyDriver
CustomAction InstallMY.XXXXX_9XX_XXXX_XXXX_XXXXXXXX returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 11:56:10: InstallFinalize. Return value 3.
MSI (s) (E8:38) [11:56:10:144]: Note: 1: 2265 2:  3: -2147287035 
MSI (s) (E8:38) [11:56:10:144]: User policy value 'DisableRollback' is 0
MSI (s) (E8:38) [11:56:10:144]: Machine policy value 'DisableRollback' is 0

Checked INF file is present at expected input location.

Any help appreciated.

See Question&Answers more detail:os

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome To Ask or Share your Answers For Others

1 Answer

0 votes
by (71.8m points)

Similar Answer: WiX silent install unable to launch built in .EXE: WiX v3


Driver element: Why do you not use WiX's built-in difx:Driver element / construct? I am wondering if you have a system context / impersonation problem? By using the built-in driver element you get more "auto-magic" in the sense that you can avoid certain common problems that occur when you do things "manually".

Blast From The Past: Here is a previous answer which tersely describes this element. I have unfortunately not been able to test it properly myself: How do I use WiX to deploy an INF-based USB driver Plus all the start menu shortcuts and desktop icons

Testing: I would definitely give this element a try, just comment out your existing custom actions and give it a try.

<Component>
   <File ... /> 
   <difx:Driver ... />
</Component>


与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome to OStack Knowledge Sharing Community for programmer and developer-Open, Learning and Share
Click Here to Ask a Question

...