This problem was brought up before by others (with the same subject)
but no solution was found:

simonc wrote:
> This problem occurs on a laptop, running Windows XP Pro, SP2 with latest
> updates:
>
> when a limited user tries to run a programme as Administrator, using RunAs
> from a desktop shortcut, the programme window opens, but the contents of the
> window are white, and no operations are possible except closing the window.
>
> In another post on this subject it was suggested it was a Group Policy issue
> - but when I posted this question in the Group Policy group this cause was
> not thought probable. The issue was resolved for another user by stopping a
> process called topsis.exe but this is not running on my system.
>
> I have checked that the secondary logon service is definitely running. I
> also use a desktop with Windows XP SP2 and on this machine Runas works with
> no problem. As yet I haven't been able to find any differences in the setup
> between the two machines.
>
> Very grateful for any suggestions.

Now, I have the very same symptoms on my new laptop. Anyone knows where
to look? Of course this problem also prevents running any diagnostic
tools which require admin privileges (regmon, filemon) so it's hard to
track down what causes it.

Regards,
John

Does make mich sense that a Limited User could run an Administrator
program/file!!
Doesn't the Run As ask for Administrator password?
So the limited user knows the Admin password?

Why should any program designed to run as/under Administrator, run when
logged in under Limited account?

"John" wrote:

> This problem was brought up before by others (with the same subject)
> but no solution was found:
>
> simonc wrote:
> > This problem occurs on a laptop, running Windows XP Pro, SP2 with latest
> > updates:
> >
> > when a limited user tries to run a programme as Administrator, using RunAs
> > from a desktop shortcut, the programme window opens, but the contents of the
> > window are white, and no operations are possible except closing the window.
> >
> > In another post on this subject it was suggested it was a Group Policy issue
> > - but when I posted this question in the Group Policy group this cause was
> > not thought probable. The issue was resolved for another user by stopping a
> > process called topsis.exe but this is not running on my system.
> >
> > I have checked that the secondary logon service is definitely running. I
> > also use a desktop with Windows XP SP2 and on this machine Runas works with
> > no problem. As yet I haven't been able to find any differences in the setup
> > between the two machines.
> >
> > Very grateful for any suggestions.
>
> Now, I have the very same symptoms on my new laptop. Anyone knows where
> to look? Of course this problem also prevents running any diagnostic
> tools which require admin privileges (regmon, filemon) so it's hard to
> track down what causes it.
>
> Regards,
> John
>
>

http://blogs.msdn.com/aaron_margosis...ory/10085.aspx

Dixonian69 wrote:
> Does make mich sense that a Limited User could run an Administrator
> program/file!!
> Doesn't the Run As ask for Administrator password?
> So the limited user knows the Admin password?
>
> Why should any program designed to run as/under Administrator, run when
> logged in under Limited account?

I've found other posts with the same issue. The common thing seems to
be that it always occures on laptops.

http://groups.google.com/group/micro...71c18377acc7ed
http://groups.google.com/group/micro...08e2d8c7cd873b
http://groups.google.com/group/micro...e4da29247e08ac

The Secondary Logon Service is running under Local Services?

RUNAS Command in Windows XP
http://search.microsoft.com/results....-US&FORM=QBME1

"John" wrote:

> I've found other posts with the same issue. The common thing seems to
> be that it always occures on laptops.
>
> http://groups.google.com/group/micro...71c18377acc7ed
> http://groups.google.com/group/micro...08e2d8c7cd873b
> http://groups.google.com/group/micro...e4da29247e08ac
>
>

KB322906
Program Windows Are Blank When You Use the RUNAS /USER:ADMINISTRATOR
Command in Windows XP
To work around this problem, keep the first Command Prompt window open.
To do so:
1. Click Start, and then click Run.
2. In the Open box, type cmd, and then click OK.
3. At the command prompt, type the following command, and then press ENTER.
runas.exe /user:administrator "cmd /k runas /user:user_domain\user_name
/netonly cmd"
After you perform this procedure, start the program that you want to use
from that command prompt. For example, type notepad at the command prompt,
and then press ENTER

"John" wrote:

> I've found other posts with the same issue. The common thing seems to
> be that it always occures on laptops.
>
> http://groups.google.com/group/micro...71c18377acc7ed
> http://groups.google.com/group/micro...08e2d8c7cd873b
> http://groups.google.com/group/micro...e4da29247e08ac
>
>

Start>Help and Support
Search>Runas

"John" wrote:

> I've found other posts with the same issue. The common thing seems to
> be that it always occures on laptops.
>
> http://groups.google.com/group/micro...71c18377acc7ed
> http://groups.google.com/group/micro...08e2d8c7cd873b
> http://groups.google.com/group/micro...e4da29247e08ac
>
>

Dixonian69 wrote:
> The Secondary Logon Service is running under Local Services?

No, it's running under Local System what is the system default on XP.

John

Dixonian69 wrote:
> KB322906
> Program Windows Are Blank When You Use the RUNAS /USER:ADMINISTRATOR
> Command in Windows XP
> To work around this problem, keep the first Command Prompt window open.
[...]

I tried this before because the symptoms are the same but it did not
help.

John