Scripting Question

Registering a DLL after reboot

09/10/2014 3729 views

            I have an application which requires to register a DLL, but after disabling DEP (Data Execution Prevention) and reboot. I wrote a vbscript to install application, then disable DEP and reboot. I included an Active Setup to register dll and enable DEP. Active setup is running after reboot but not registering the DLL or enabling the DEP. I get to know that Activesetup runs in User mode so it cant do admin tasks like registering dll and enabling DEP. Can anyone suggest me is there any other options to do it. 

Thank you. 
1 Comment   [ + ] Show comment


  • The most common package authoring tools will capture the addition of a DLL and automatically extract the COM information and add the relevant entries to the appropriate tables in the MSI.

Community Chosen Answer

Registering a dll using active setup is not a good idea.. Active Setup will try to register that particular dll for every users during their first logon after installing your application.
if you want to register that dll after reboot then try registering it through RunOnce registry key.
Answered 09/14/2014 by: jagadeish
Red Belt

  • Hello Jagadeesh,

    I tried with runonce and run keys they also running in user context not system.
    • ..

All Answers

Limited user will not have permission to register that DLL. There is one way that you can get around with that scenario by doing these:

1. Install your application.
2. Disable that DEP.
3. Reboot the machine.
4. Gather a lightweight capturing tool like Installrite and install.
5. Run the pre snapshot.
6. Register the DLL
7. Run the post snapshot
8. Capture the registries
9. Add to your package.
10. Test and grab a coffee.
Answered 09/10/2014 by: dj_xest
5th Degree Black Belt

  • Hello dj_xest. I agree with your point, but client want to do the registration manually only after reboot not by capturing.
    • How the clients sees the over-all installation is very different on how the actual and for us packagers sees how it works. The manual steps cannot be compared with how you can automate it. How we do the steps does not matter but the results. Customers will always put in install guide how they made it. We don't do what they do, otherwise cannot do it.
I would agree with this approach. Capture the registry settings created by DLL registration and then install them as part of your package while is it running with admin or system rights.
Answered 09/10/2014 by: EdT
Red Belt

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ