XXHighEnd

Hi, can anyone help ?

My setup is with a Music PC and a Audio PC
When i try to start XX on the Audio PC i get the message to Check UAC and reboot over and over again (not possible to start XX)

UAC is off on both PC`s.
It is not possible to open "Change User Account Control Settings" on Audio PC (is in Min. OS?)

Tore

Tore, it is not easy for me because I am at a poor Internet connection at where I am, but manually (RegEdit) set this key to 0 :

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
EnableLUA

Regards,
Peter

Peter, i hope you are in a warmer country than norway  :wacko2:

I get this message: the service cannot be started, either because it is disablet or because it has no enabled devices associated with it


Tore

Ah ... For this all go to Normal OS first !

Please notice that this UAC thing could be a 2.06(a) bug. I only noticed it myself 3-4 days ago.
I hope it helps !

Best regards,
Peter

It is not posible to open xx so that i can go to normal OS

Tore

I recall the similar situation.
A bit difficult to sort out on my phone, but I recall now that I shifted UP the UAC slider (plus reboot) to overcome the situation. But I forgot the situation.

I will be out soon;
What actually is it you are trying to attempt ? It does not look like normal installing to me ...

Also, at what thing you do you are getting this service disabled message ?

Peter

I`m trying to play music with a Rega DAC

Also, at what thing you do you are getting this service disabled message ? Audio PC in Min. OS

It is not possible to open "Change User Account Control Settings" on Audio PC, is it because of min. OS?

Tore

the problem started with this message from 2.06 : Music root does not excist

I found out that the external HD in the Music PC was not shared with everyone. I think it was because a windows update on Music PC
This is OK now

I meant : What do you do to get that message ...
Just open user acc control ?
If yes ...


Yes, that is what I recall.

I meant : What do you do to get that message ...

I got that message when i tryed to open Regedit on Audio PC

Peter,

the Ram-OS HD went out and my normal HD went in.
I played one song and picked the Min. OS button (XX 2.04)

After the reboot i have exactly the same problem, not posible to open XX 2.02, 2.03 and 2.04. (just telling me to check UAC and to reboot)  :sad:

But now you can open Regedit ?

No way, i get the same message (min OS)

Misunderstanding : Regefit in Normal OS I meant. But maybe I make no sense...

Run - regefit = Windows can not find regefit

But i`m in Min. OS, is it posible to go to Normal OS when i can`t open XX?

Tore

As often I am lost now. But : Put the ram-os in whereever you use it normally and in there go to normos. Then put back in the other pc if there is another pc in the firtst place (difficult to understand the situation).

It is regedit. Not regefit.

OK, where do i find normos?

The RAM-OS is back in my Audio-PC. The Audio-PC have a SSD with the OS original

Normos = Normal OS.

one more time: But i`m in Min. OS, is it posible to go to Normal OS when i can`t open XX?

Nope. :nea:

Peter,

I am ignorant about the way the OS is minimized, so I hope you will forgive me if my suggestion does not make any sense...

Is it possible to have a script that could enable the needed processes to go "almost" back in normal OS mode ?

Sorry if this does not make any sense...

Alain

Hi Alain,

None of this should be necessary. It never happens to anybody, and it is my guess some strange kind of disk swapping has been going on. Now if you can get Tore to tell what this is with not too many language problems ;), we would be a few steps further.

My guess : somebody tried to copy XXHighEnd data from one disk or folder to another. That violates the Activation. Next it is the Windows 10 bug (?) which does not allow to start RegEdit (??).

Thanks,
Peter

Peter,
the only different now that i can remember is the REGA DAC and new DAC settings in XX 2.06.
I was playing some tracks and picked the Min. OS button. After that reboot XX started to telling me to check UAC and reboot. (not posible to open XX.

Then the RAM-OS went out and the SSD OS went in.
I started XX 2.04 and played one track. Then i picked the Min OS button and now i have the same problem with my SSD

Tore

I have an emergency this morning and since I am back at work (after 2 weeks of vacation) I am short on time... I will try to find the time to formulate some questions later this evening...

All I can say at this time is assuming that:
- The ram-os drive is the original hard drive.
- It is used and located on your one and only Audio PC (the one in your signature).
- The 2.06 XXHighEnd version (and the 2.06a patch) were installed on your Windows 10 build 10586.0 version (at least) and it has worked well with your NOS1a before.
- It is still activated (but this seem impossible to verify at the present time) with a RED title at the top of the XXHighEnd Window.

The questions that I think of for the moment are: is there something that you did apart from switching the NOS1a to the Rega dac and adjusting the settings to have it work ? I assume it was working before you went in Minimized OS ?

Regards,

Alain

Alain, all is correct (Windows 10 build 10586.11)

Everyting was working fine in Min. OS until the NOS1 usb failed

Tore

HI Tore,

I am about to leave for work, so I may only be able to check later in the day :)

You did not mention that USB fail (at least not in this topic)... I fail to see how this can be related to the UAC problem though... I can start XXHighEnd even it the NOS1a is disconnected or turned OFF.

But if that relates to the actual problem, maybe you could try another USB cable, another USB port, removing the Intona temporarily, deactivate the USB port that does not seem to work through Device Manager...

?

I was not aware that the build is 10586.11... Isn't it supposed to be 10586.0 ? Have you updated your Windows 10 version too ?

Alain

I forgot to suggest... Is it possible for you to copy the ".vhd" file that you normally have in copy over your actual ".vhd" file and restart from there ?

Don't forget that if you haven't changed Windows 10 build 10565 yet, you may need to change the date by putting it back a few months behind...

You may also need to connect a keyboard, mouse and monitor directly to your Audio PC to redo a few things...

I have to leave now... :)

Regards,

Alain

Alain,
usb problems: http://www.phasure.com/index.php?topic=3675.0

My NOS1 (+ ram-OS) is on the way to Peter now

Windows 10 build 10586.11 is because Windows automatic started a update :-(

About Windows 10565, do i have to do anything with it when i never use it?

Tore

Hi Tore,

Sorry it took me some time to understand :(

AS for build 10565, since it was suppose to end its life July 29th, you should normally go back in time. I changed the date in another Windows (from the ram-os drive), but be sure the date is changed before attempting to load build 10565...

Regards,

Alain

No ...

but


You would use it to boot from and copy back the "Copy" OS file which is in there, so you'd have the normally running 10586.0 back ...

Regards,
Peter

Maybe, very maybe, it is my conclusion that

- or you changed the UAC yourself for some reason
- or the upgrade process started and did it for you.

Both are "wrong" to do, so to speak. So the UAC should never be touched (although nobody told you :swoon:) and the upgrade should not have started, so possibly you did something with that too, and it could be explicit Windows Activation (I am not 100% sure, but I feel from other situations that Activation also triggers updating).

I am 99% sure you did something which should not have happened and I am 100% sure you don't tell about it; if I have my RAM-OS Disk or whatever disk with activated XXHighEnd and all I can put it in any PC I like, and it just will run as happily as it did before. Do notice that all of you with the RAM-OS Disk actually do exactly that (I create it over here and you use it over there).

One thing : I am almost sure that in 2.06(a) there's a bug about the UAC thing which occurs when an already installed XXHighEnd is "mangled with". This is not negatively meant, but say that you try to copy your XX folder from one place to the other from a MinOS situation to a Normal OS situation which is actually fresh and not UAC manipulated yet, then the UAC change by XXHighEnd does not work out.
In addition to that - or in combination with it - it looks like Windows 10 can be in the state of not allowing RegEdit to start because of some service not running, but which is about the UAC level again (at least that is how I interpret things). I don't know what it takes to incur for that, but I saw it too. And it was during "mangling".

Anyway ... Tore, I sent you a 2.06b so if you still have a disk/ssd with the situation, you can try whether it helps. For me it did (but I can not tell whether the situation is the same).

Peter

Peter, you think a have done something wrong. I too, but i don`t know what

Before the NOS1 usb problem i pulled out the usb card because i was using mobo usb. Maybe i did that without switchin off PC-power?

I think i was changing the UAC one time when i was told to check it


Tore

No no, you did not do anything wrong as such. But many things can be done which are not anticipated (by me). :)


Yes, this is typical that situation I referred to. But the damage has been done at that moment already. So :

1. Something changed the UAC (can be anything, like XXHighEnd does it too, although it will not be common practice (like XXHE is not common practice)).

2. Now that "rare" message of XXHighEnd pops up and it tells you don't run as Administrator and/or check your UAC.

See the rarity of the situation ? So :
Ad 2.
Since when do we need to run as administrator ? OK, since 9 years ago and maybe 7 years ago that disappeared (it even goes explicitly wrong whenm attempted). Thus anser : NEVER.
Since when do we need to adjust the UAC ourselves ? ... same story. Never since ages.
Still XXHighEnd runs into this (as it now appears to exist) very old code, and it is a strange situation to begin with. But I had it myself too ... (and coincidentally only 10 days or so ago).

To be hopefully clear about this :
The message appears when all has been installed nicely and runs already, and then the UAC is set back by whatever means. So this check for the UAC to be "off" is always there, at startup. Now when it is detected that this is suddenly wrong, this message appears and now there's a bug in XXHighEnd (2.06(a)) which does not set the UAC to where it should be. And there is your forever (boot) loop ...


I think the UAC thing is not related to that, but it will be the result of you trying to repair things (in software). So of course you tried everything to get it running again.
One thing about this happening itself : it could explain why your USB interface "broke". That is, if you indeed pulled the card with the PC powered on (which is of course not allowed).

Let's say : over and out. I will try the 2.06b on your RAM-OS Disk which is underway, so I can see whether the adjustment I made for myself, indeed helps your situation too.
Btw, the messagea about checking UAC and to run in Admin mode has now be removed (beyond 2.06a).

Peter

Peter, it is the same problem with my SSD OS and XX 2.04


Tore

Peter, it is the same problem with my SSD OS and XX 2.04

Interesting ... :scratching:

Well, this has been quite a sneaky one ...
The key is is this :


... which sadly got the emphasis on that TRIAL OS and its upgrade or not, while it is about the 10586.11 - which btw is 10586.122.
Who could have guessed that that (or its upgrading itself which completely failed) is now causing all the troubles.

So - also for everybody who tried to help Tore - just nothing runs any more. Not even TaskManager.
UAC was probably still right, but the internal (OS) programs to check it, could not run. Same like Regedit to change it could not start (see posts about that).

So the sad thing is that all was solved by copying back that "10586 Copy" version. 5 minutes of work (of waiting actually). But that did not happen and now the whole lot is over here at us, just to notice this ...

So this too, was all about the same problem : PC can`t find NOS1 (http://www.phasure.com/index.php?topic=3675.msg39209#msg39209).

Summarized what will have happened :
1. PC got hooked up to the Internet (Tore will no the Why of that, but it should not have happened);
2. W10 Updates were downloaded by the OS;
3. The OS got into the state of "OK, I am going to update myself";
4. ... which probably miserably failed because of the MinOS state (but this is just guessing).
5. The OS worked, but only for a little. Actually all started to fail.
6. The hint was clearly there to copy back the backup, but it was not done because it did not seem "the" subject. This relates to the thought of the DAC being broken, that needing to be send out for repair, the OS disk coming along with it for observation as a small side matter.

Sh*t happens.
Peter

Hi Peter!

How do i avoid Windows update?

I know there is i button in XX, but is there anything else to do?

Audio PC is connected to Music PC with networkcable


Tore

Hello there Tore,

Unless you applied an explicit "bridge" in the Music Server PC, the Audio PC will not be able to access the Internet.
(if you did not do anything about a bridge, it will not be there for sure)

Thus, at some stage you will have had your PC connected to the Internet. Btw, Activation could be such a reason AND it is known that that applies upgrades meanwhile.

So can you tell us what may have happened in your case ?

Regards,
Peter

Peter,

The only Windows update i have noticed is the one right after i got my Ram-OS. After that update everything has been working fine.

I was updating W10 on the Music-PC some days before this problems


Tore

Phew ...

The Windows 10 updates are organized such that when your "neighbour" has obtained an update, you will get it from him (although these days that "neighbour" can shut off that feature). Thus, this is how the updates are literally "distributed".
What I now start to think is that it can happen in your own network too. I mean, why not. It saves a lot of Internet traffic ...

Ouch

Oops! Windows 10 distribute updates :-(

My Music PC runs Windows 10

How to stop this: http://lifehacker.com/windows-10-uses-your-bandwidth-to-distribute-updates-d-1721091469


Tore

Ha !
Tore, very well done !

Regards,
Peter

Hi All,

The same now happened to myself. But this is not correct (sort of) :


What I did to get into this state, is this :
Moved up the UAC (User Account Control) slider with one step and rebooted.
By coincidence (I was testing something) the check in XXHighEnd for that UAC level was not active, but I don't think this is related. Well, I could start XXHighEnd because of it, but received unexpected errors anyway. And, after setting back the normal UAC checks, it appeared all the same as Tore experienced (and which I saw over here from his RAM-OS Disk).
Back then I was sorry that I did not sort it out (how to recover from this) but now, 60 minutes later, I can see that there's no solution to it. Too few things will run and what I get from it is that "Run as administrator" won't run any more. So all what requires Adinistrator (elevated) rights, just fails.

I also changed something with gpedit, but I can't imagine that this is the cause, just because Tore will not have done similar by far. Thus :

I think it is so that once you slide up the UAC by one step and boot into that, some inconsistent situation occurs with Rights and it can not be repaired because all what you do requires those rights. Next guess is that something like that happened with Tore, or by him changing the UAC slider, or because the Windows Update does that. That Windows Update does this, seems logic to me. But anyway the real culprit will be the slider position.

Now I am going to look for my own 14393.0 backup ...
Peter

Indeed it is that simple ...
Be in MinOS, slide up the UAC, Reboot by means of Windows itself (not by means of XXHighEnd when it is to be started first, because it will repair right away) and find yourself locked out.

I tried the same in Normal OS but there all keeps on working.

On a side note : in 14393.0 it will not be so easy to let this fail, because rebooting by means of the Start Button most probably won't work (because the Start Button does not work). So you really need to be "lucky" to run into this failure.
And as said, Windows Update probably will reset the UAC as well (for itself) so run into Windows Updates in MinOS and you're dead.

Regards,
Peter

PS: If you start XXHighEnd in this erroneous situation and it comes up with the dreaded UAC Reboot message and that a reboot is needed or else XXHighEnd will quit, the below shows when you click away the Reboot message, when the problem is a fact (the number in that Temp name will be different).

:fool: I felt into this pitfall again just now.

Btw, again I tried to let run XXHighEnd at normal UAC levels. That in itself I have working (I think) but I can't test it - at least not when in MinOS and W10.
When do I finally remember this, when working on XX without UAC down ?
grrr

Peter

Something to add or otherwise I might forget for the next time :

What actually seems to happen is that there's no internal "administrator right" possible any more. I think this can best be derived from the normal command prompt still working, but "run as administrator" already comes up with the error message (see screenshots in previous posts).

I just noticed that even deleting or renaming a file throws a "You need administrator rights to do this" (similar).

With this knowledge I tried to get it going again for an hour or so, but I gave up and in comes the copy of the OS again ....
Btw the worse part is the necessity to insert the video card again in order to boot into a "service OS". So FYI, XXHighEnd Boot Menu also can't work in this state. Nothing works what's required in such situation. At least nothing I can find.

Peter

I'm all too familiar with this procedure. Were you just trying to delete a file or did the OS stop working so you had to reinstall the OS copy? If the latter, what do you think caused the OS to stop working?

Hoping to shed more light on prior problems.  :)

Brian, as I told in the previous posts ... all it requires is setting the UAC up when in MinOS + Reboot.

But I just finished the procedure of XXHighEnd doing that for you, and which it disallows when in MinOS. Now all we need to learn is to stay out of the normal Windows functionality for that ...

Peter

Thanks Peter.