XXHighEnd

Hi, Peter,

After enjoying the Great-W10 sound I wanted to go one step further and enjoy Great-Great W10 sound via Minimised Mode. However, here I got stuck.

A restore point is created but after rebooting I get an HARD error popup (which I can ignore as I understand from somewhere on the forum).
Then, when starting XX, I get a "Check UAC" popup saying:

"After this a Reboot is required to put through changed User Account Control Settings; Not allowing for this will quit XXHighEnd. Reboot?".

Yes, ofcourse, go ahead, reboot.
But nothing happens. I tried manual reboots but same popups appear.
I then tried to manually check and set UAC: Explorer -> This PC -> Properties -> Control Panel -> User Accounts -> Change User Account Control Settings. I can click on the option 'till I weigh an ounce', so to say, but nothing happens. I do not get to this slider screen. Others settings are also not accessible anymore, such as the Taskmanager via Taskmgr.exe ("The service cannot be started, either because it is disabled or because it has no devices associated with it".
So, i'm lost and cannot make this last final step to ultimate sound...

Any idea how this can be solved?
(Btw, can a restore point somehow be manually be restored?)

Bert

Hi Bert,

Something ain't right here (ah, that's what you thought ;)) and this is that to me it seems impossible that this is related to MinOS. So first things first now :

Does it all work in Normal OS ? hard to believe, but please let me know.

Hint : That message occurs when you set something else than Mixed Memory (opposed to Mixed Contigous Memory / Straight Contiguous Memory) in XXHE Settings. Also in normal OS.

The message should not reoccur at all of course (after a first reboot) and actually I see no reason that it *can* in the first place, unless you used this W10 for upgrading another OS instead of for a fresh install. So did you (the former) ? and what is the OS reporting for version (lower right corner) ?

Regards,
Peter

Peter,

All worked fine and sounded great in Normal OS, unattended mode.
I'm running W10-Build 10074 showing as follows on my screen in the right hand corner.
"Test mode". Below that: "Windows Pro Insider Preview" and below that: "Evaluation copy. Build 10074". Seems OK?

My sig shows "Mixed contiguous" and that is what it is.

I can't go back to Normal mode anymore to check things, or whatever. That is the problem. If I click on the XX symbol in the taskbar, or double click the .exe, then the only thing that happens is the "Check UAC" popup appearing displaying this "After this a Reboot is required...." message. Selecting Cancel vanishes the popup; clicking OK too and no reboot takes place. I waited a few minutes to check this.

I seem to locked into this (please don't tell me that I have to reinstall all...)

Bert

Hi,

read in the news today, that the W10 previews are all locked now. (no update etc. possible) You can try to change the actual date via the BIOS back to "lets say 2015-01-10 or so"
Would be interesting to see if W10 starts again.

Joachim

EDIT: The other bad news with W10: we can’t avoid „automatic updates” except with the Enterprise edition.

Bert,

Today I slept better than yesterday and I now see that I have been on the wrong track with my Contiguous stuff. Instead, something is definitely wrong. I mean, if you can't even start Task Manager ...

Can it be that you had other "optimization" means running/applied in Normal OS ? Otherwise I see no reason how your OS can start to behave like this, while for others all is fine.

You have two options, and the first one will be the most decent :

1.
Go back to an earlier restore point. How ?
Get your install DVD, boot from it, and choose "repair" or whatever it is called and then somewhere Advanced and from there Go back to a Restore point (all "something like that", but you will find it). This should work.

2.
Try to apply the change the program is attempting, with possibly no chance because the program can't do it either (somehow). Also, after this, things will still be all over wrong. However, you might be able to do back to Normal OS and see further from there :
Start an elevated Command Prompt IF you can still get there (notice the advice to have a command prompt icon on your desktop, so I hope it is there. Elevated : Run as Administrator (cmd.exe). Start RegEdit.exe.
(maybe if you start RegEdit directly (not via the Command Prompt) it works just the same)
Give this key a value of 0 :
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System : EnableLUA (= 0)
If you can put this through, Reboot and XXHighEnd will start.
And if not, check that Registry key again and see whether it reverted to 1 (which is what I suppose it's at to begin with).

Let me know what happens.
Peter

Hi, Peter,

Light in the darkness!
I started with the second option, the registry key setting. However, I didn't have the admin rights to start regedit. Lots of shields symbols everywhere blocked me from doing things.

Then I continued with the repair option via the W10-DVD. First I tried to restore a restore point, however the file seemed to be corrupted. No way to restore it. There is a 'Refreshing your PC" option that I tried and some how this worked in the sense that I was able to start programs again.
When I clicked on the XX icon in the task bar it came up with the wellknown "Check UAC" popup. When I choose Reboot it executed the reboot  :veryhappy:!
After the reboot XX was back again and working! However it returned not in minimised OS, but in Normal mode. But, OK, so far so good. The sound card driver was gone but I could reactivate that (partly). The XX-license was not gone, luckally, and I could start XX and got it playing.

Currently I'm still struggling with the soundcard driver but that is another issue. Once that is working the next step will be going to Minimised OS again.

I hesitate doing that, as you probably understand :smirk:. So, any good suggestions before doing that?

Thanks anyway for the suggestions and i'm glad that things start working again.

regards,
Bert

So Bert, I would do it the oter way around; get everything going for MinOS, and after that work on the further stuff like the soundcard driver. This, with the notice that all should just work, so I expect it will, but it may stop working when you yourself apply further things (like that driver).
Not need to be afraid to waste some additional time either (might MinOS again not work out) because you have to go through it anyway, right ? and that's why my proposed sequence, which in the end should save you time ...

During the process of booting into MinOS, try to watch for strangenessess. I have no clue what to watch for but it should just boot without any anomalies. Two thing perhaps :
- Take care that you have an Account + Password;
- Yes that "Hard Error" is normal (not of course, but everybody has it, and it is harmless).

Good luck !
Peter

Hi Bert,
Is there a reason for to stay in mixed contiguous?

Regards, Johan

Joachim,
You'll be able to turn off updates in Windows 10, just a few more magical clicks -
http://www.tenforums.com/tutorials/8013-windows-update-automatic-updates-enable-disable-windows-10-a.html
Dave

Hi Dave,

thank you, that are good news!

Joachim

Hi, Peter,

Was in the UK this week, so therefore this late response.
I got it all running now, a licensed 2.02 XX, the sound card and XX in min OS and the sound is great!
It first didn't want to create a restore point but I got that fixed after finding a help for that on the forum.
I was a bit stubborn, actually  ;), as re-installing sound drivers could, that is what I thought, easily give problems in Min OS, cause of missing/stopped services. Therefore I solved this first before going into min OS. And this time going into min OS worked OK.

Thanks for your help.

@Johan.
Johan, as I understand from the manuals it is a kind of 'best of both worlds' (at least for me) being in the middle between being Mixed and Straight Contiguous. Mixed mode provides the least SQ of the three and SC requires starting whatever track immediately after starting XX to be sure that memory is reserved exclusively for XX, which I personally find a bit 'unpleasant' to be so hasty right after starting XX (knowing that SC gives best SQ).

Regards,
Bert

Hi Bert,

Thank you for the feed back.


Accidentally your SFS value isn't listed in your sig, but what you claim here is only true when you are way low on memory to begin with which is only with a combination of

a. 8GB or less of memory
b. an SFS of over 400.

When either is not in order (not a. *or* not b.) you can take an hour if not a day for starting playback.
Of course it is not allowed for the PC to do other things explicitly (like using MS Word and opening a 100 large documents etc.).

Best regards,
Peter

Hi Dave,

I missed this post at first. Anyway :
Forget about that or let's have a bet that this soon won't work any more (July 29 for the final ("RTM") version). For the 10074 version it will I suppose, but I didn't test it.

Peter

Hi, Peter (and Johan, thanks for notifying upon this setting :)),

I set XX to Straight Contiguous, but got no reboot message. I set it while in Min OS mode. Was this allowed? I had no idea if XX picked up the new setting so got back into normal mode and checked Control Panel->System->Administrative Tools->Local Security Policy. My username was in there so, so far so good, however I still don't have a clou if XX has picked up the new setting (it should have asked to reboot isn't it?)

Is there a way to check it?

regards,

Bert

Bert,

No, only at the very first time using one of the "Contiguous" settings, the system needs to set something and reboot for it. This probably happened "months" ago for you and you forgot.

There's no need to check it; when it is set in the settings and it works, it really works internally as well.

Regards,
Peter

Hi, Peter,

Perhaps a good idea to add to the manuals that only going from mixed mode to one of the two contiguous modes requires a reboot. And switching between the two contiguous modes doesn't.

My question came from my understanding from the manuals that also switching from mixed contiguous to straight contiguous required a reboot (which I wasn't asked for by XX, therefore my doubts), but apparently that is not the case if you are already in mixed contiguous.

Bert