cannot run as administrator anymore

[Flecko]

I think maybe there went something wrong in your .NET framework update, if this was updated.
Maybe this helps a bit !?

Thank you Roy. I unsinstalled the named updates and uninstalled .net framework. After that, I used .net cleaner and restarted. It had no effect on xxhe. It still doesn't start as administrator

[PeterSt]

Do things change if you uninstall Phasure, and next run "As Administrator" the setup.exe (which is for that same Phasure) from your xx folder ?

[Flecko]

No change. Setup runs as administrator and installs successful but xxhe still don't start as administrator.

[PeterSt]

Well, maybe you can Google for it. That is, assuming that this is caused by some MS update (what we don't know for sure), while *you* know the best how exactly things changed for you (meaning : I won't do the Googling).

Notice that with W7 several (new) levels of UAC exist (compared to Vista), including a few registry hacks. At the time I looked at it I didn't understand a f*ck of it all, and ended up with the same settings as I had in Vista. But it is clear to me that it easily can happen that you ended up in one of those vague compination of UAC settings, wheter it was you who did it, or an upgrade of something.

When you start changing things in there, always reboot after a change, with the notice of W7 *not* always telling you to dom while it really is necessary !

[Flecko]

That is, assuming that this is caused by some MS update (what we don't know for sure), while *you* know the best how exactly things changed for you (meaning : I won't do the Googling).

I uninstalled all updates to 20.06.10. This is a long time befor this error happend. I rebooted after uninstalling but it didn't helped. But you never know what stays in the system after uninstalling. I can not make a clear connection to changes on windows and the point where xxhe stopped working. That is not a good situation to solve this, I know.

I googled but there are a lot of different posts respective to this error. A complete reinstall might "solve" the problem but that involves, that the error happens again and all the work was in vain. All other programms work without problems. So, this can not be a generall problem. And as I said, I tried different versions to get a clue. This happens since version z. "Every" older xxhe works fine.

It surprises me nobody else has this problem, except the one guy(the one you gave me the link to). I have the same problem on a very different PC (notebook of a friend) with Vista32 home.

Do you use autoupdate or do you have the newest updates?

[PeterSt]

Thank you Adrian.

I don't like this at all;

I have the same problem on a very different PC (notebook of a friend) with Vista32 home.

So, I don't like this, because if one person immediately has a friend with the same, he might coincidentally telling about it, while 100 others who try XX for the first time don't say anything, but pass on.

The problem with the other guy (rediazvh) is not solved. Not even after a 100 emails back and forth, and I actually had to give up. He has Vista Basic though, and possibly nobody is using that, and *that* may be the "cause" somehow. But his friend has W7.

Please notice that the problems of you both only look related, but possibly are not the same at all.

Ok, in your case disabling UAC just helps and you have no problems. Correct ?
Thank you very much for your help.
Peter

[PeterSt]

Adrian, allow me to continue with this a bit ...

Here is a debug version : http://www.stordiau.nl/downloads/XXHighEnd-09-z2b-01.zip
(this contains a XXHighEnd.exe to paste over a 0.9z version; save your current XXHighEnd version).

When all is right, small messages will appear with 001, 002, a, b, c etc. etc.
Just keep on clicking away those messages until it dies. I want to know the last number etc. which was on the screen.
The first time, just do it rather quickly, so you will have an idea where it dies. Next do it again so you can go quickly through the first bunch, but start concentrating and slow down when you are close to where it dies. There may be dozens of these messages.

I hope this is going to help ...
Peter

[PeterSt]

So, now a better clue. xx9y4 and 9y8 start as administrator. The problems comes with 9z. So it might be not the setup. Maybe the new gui?

I looked closer to this one, and found a change from 0.9y-8 to 0.9z which may be related. Of course this can't be the real cause for something which "just stopped working" at your side, but it may solve it.

Please try this one and let me know (paste it over your 0.9z-2 install, but keep the old one; this 0.9z-2b-06 is not a properly working version) :

[Flecko]

Please try this one and let me know

I tried the version 9z-2b-06 on the notebook and on my pc. It didn't helped. If I shut down UAC on the notebook it also helps to start as admin. I will try the debug version and tell you. I am short of time time at the moment but I will help to solve this as good as it is possible.
Greatings and thx for your support!

[Flecko]

There may be dozens of these messages.

This was a quick one... after 002 it dies.

[PeterSt]

Then most probably this one may just work :

[Flecko]

The error is different now. "Das angegebene Modul wurde nicht gefunden. (Ausnahme HRESULT:0x8007007E)".
Translation: "The indicated module was not found. (Exception HRESULT:0x8007007E).
If I start not as administrator it works.

[PeterSt]

Crazy ...
Today's administrators are allowed less as it seems.

Oh boy.

Isn't there more info at this message somehow (often there's a "detail" button) ?
And nowhere an indication of "what module" ?

[Flecko]

The box is named " initialize component" but there is not more information. I am sorry.

[PeterSt]

In the 0.9z version, there are two .OCX files;
What happens if you put these in your current XX folder ?

Possibly nothing much ...

But if you have found these two files anyway, please try to recall what your XX folder was named when you installed 0.9z for the first time, and perform this (in this sequence !) :

- Uninstall Phasure
- Create that folder I was talking about again, and put those .OCX files in it.
- Next register them with regsvr32 [name].ocx
- Now Unregister them with regsvr32/u [name].ocx
- Start XX again (the version you downloaded from this topic)

It is a kind of long shot, but at least we tried ...