Administrator privileges in WPI

[polemos]

Greetings,

After the 23450,25th time of reinstalling XPs, I 've recently decided to make my own unattended version for it. My problem arised when WPI autostarted to install the Broadcom bluetooth drivers in my laptop. The wizard stopped working after complaining that it needs "administrative privileges" for completing the installation.

This happened in an administrative account.

Any info?

thanks.

p.s:And offcourse, I really googled the planet for an answer, no answers for the WPI though.

[zorphnog]

Have you tried installing the drivers silently without using WPI? It sounds like the problem is with your installer, not WPI.

[polemos]

Thank you for your response,

yes it is indeed a problem with the driver. It is not a problem with WPI. If I follow the regular path and I install manually the driver, after the system boots etc., the installation proceeds without flaws.

The problem arises when I try to install the bluetooth driver unattended with the help of WPI.

Even though the driver supports silent mode by itself, it fails to accomplish the installation since it asks for administrative privileges, (which it already has, since WPI starts the install process after it logs on in a chosen account, which in my case is an administrator account).

After I googled for a solution, I found out this not the only driver with this kind of problematic behaviour and that there are many more people with the same problem (drivers installers asking for administrative privileges).

There are many solutions for installing these drivers in an unattended setup (example RunOnceEX) but I haven't found any solution for using it with the WPI alone.

This is a hole in using the WPI, of which no answer has came yet. Even though many people are asking about it.

As I understand from watching WPI in action, it starts to function in a free of programs and processes enviroment. This makes me suspect that the above mentioned installers are searching for some certain processes or programs in memory, to validate if the account which they are being installed to, is an administrative account.

In short, how is it possible to make installers, asking for administative privileges when they are in an administration account and by fault identify the account as a not being an administrative one, to... install when they are executed from WPI?

Thank you.

Edited January 18, 2008 by polemos

[polemos]

Hey guys,

am I missing something? I searched a lot in the forum and I haven't found an answer to this. The answer is so obvious that nobody cares to take a look?

There are a lot of bright minds participating in this forum, I really can't believe they don't have an answer for this, I am starting to believe that I really miss something to obvious!!!

[Kelsenellenelvian]

Sorry I missed your post. However as a non-Vista user I can't help you one single bit.

Wait after looking you say this is XP??

Please tell me exact drivers and installation method you are using so I can try to recreate this issue...