The Opposite Problem

[Jud]

Everyone is wondering how to go back or keep from upgrading W10 builds, but being a foolish kid of 60+, I have the opposite problem: I have 10586.0, and have been on the "fast track" to receive new W10 builds.  Since Peter put out 2.03 I have installed it and have been listening to the welcome sounds of XXHE again for a week or so now.  (Thanks, Peter!)

However, last time I looked to see whether an updated W10 build was ready, I got an error from Windows Update (not at home, so will get the exact message later if it is helpful).  I wondered: Is this an intentional or accidental effect of installing XXHE?  If so, is there a way, without uninstalling XXHE, that I can switch on and off W10's searching for updates?  I do like playing around with the new builds, though I realize the implications for sound quality.  (On the other hand this is for a desktop system with a $200 DAC and $79 speakers - the pair, not each - so we are not talking about ultimate sound quality in any case; though the difference made by XXHE is more than evident even on such a system.)

[PeterSt]

Hey Jud,

Everyone is wondering how to go back or keep from upgrading W10 builds,

If so, is there a way, without uninstalling XXHE, that I can switch on and off W10's searching for updates?

Maybe I put it a tad too much out of context, but I see you posing two times the same thing : Prevent from Windows updating
If this is in the end your question then I'd say that you can RightClick on XXHighEnd's Stop button and choose for switching off the updates (do that in Normal OS).

Otherwise I have read that once in a "slow ring build" (like 10586) one can opt out of the insider program, hence updates stop (??).

I have 10586.0, and have been on the "fast track" to receive new W10 builds.

If that is so, you should have a higher number instead of that .0 ?
Well over a week ago it already was at .11 ?

However, last time I looked to see whether an updated W10 build was ready, I got an error from Windows Update (not at home, so will get the exact message later if it is helpful).  I wondered: Is this an intentional or accidental effect of installing XXHE?

Phew, difficult to answer;
If you are in MinOS BUT connected to the Internet and (thus) did not switch off the Updating in the first place (see above) then I guess anything can happen. I just can't tell.
Notice though that you will be about 100% unique in having the Audio PC connected to the Internet (and use W10).
And ... when not connected to the Internet, the encouragement for "errors" could even be larger, because it could nag about the Internet connection (though with an indirect message) ?
So yes, the message itself could be helpful.

Something else is : If you by now survived all the updates then this is prize worthy. I mean, sooner or later one will fail. That could just have happened to you. And if XXHighEnd was in Normal OS ... nothing special anywhere in that situation.

Sorry for the long answer !
Peter

[Jud]

Hi Peter.  Sorry for being confusing, but I really do have the "opposite problem" - I *want* W10 to update, but it gives me an error message when I try! 

(Isn't that just how the universe works: all the rest of you want to turn off updates and are having problems keeping them from happening, while I want updates and am having trouble getting them to happen.)

[PeterSt]

Jud,

I think that's implied in my responses just the same. So what remains is you confirming that "of course" you are in Normal OS etc.
And when you do so then I will say "then of course it can't be XXHighEnd related".

Or you say : "Obviously I did not switch off Updates via XXHighEnd". Then I will respond back "then obviously that can't be the issue either".

All 'n al, I don't know. Yeah, that W10 is wacky as hell.
Of course XXHighEnd could be the cause, but then I don't recognize any of it, apart from what I've written.

Any more ideas yourself ?

Peter

[Jud]

Of course XXHighEnd could be the cause, but then I don't recognize any of it, apart from what I've written.

Any more ideas yourself ?

Peter

That makes sense.  I don't have any ideas at the moment (a Google search a couple of days ago on my error message didn't turn up any similar problems, but perhaps there is something by now), but will try to have a look tonight or tomorrow.

[PeterSt]

Did you get hold of the error message ? I can try to find it too ...

[Jud]

At the same time as I had the update problem, I also had an irritating bug where many apps would not run, saying I couldn't do so with the "built-in administrator account."  I Googled complaints about this and wound up doing something more than the answers said to do after their suggestions proved ineffective.

I had to adjust a couple of settings in local security policy; at this point I don't want to say exactly what, since security is involved, but I can confirm:

- The same thing that fixed the bug where apps would not run also fixed the build update problem;

- XXHE was not at fault (I switched the XXHE W10 updates setting back and forth a couple of times and confirmed I still could not update prior to my security policy fix);

- 10586.0 is still the latest, even for those on the Fast Ring for Insider Program updates.

[Jud]

OK, so actually I was wrong about XXHE being "at fault" (in quotes because I mean XXHE install results in the problem, not that there is any sort of blame attached).

If anyone wants to do the same crazy thing I'm doing, allow W10 to update while having XXHE installed, here is what to do if you want to update and can't due to some cryptic error code (or you have the bug that you can't seem to run half the apps on the machine):

- In the Cortana/Search/Run field, type "secpol.msc" (no quotes).

- Under Local Security Policy/Security Settings/Local Policies/Security Options, for the policy "User Account Control: Run all administrators in Admin Approval Mode," change the security setting to Enabled.

That's it, you should be able to update or run the apps you want to.  Next time you run XXHE it will change the security setting back, so you'll have to repeat the process above whenever you next want to update or run certain apps.

[PeterSt]

Jud,

OK, so actually I was wrong about XXHE being "at fault"

... being NOT at fault, correct ?

That assumed, but of course and as logical as can be.
As a matter of fact I am (was already) thinking about some kind of (UAC) tweak back, because with W10 it doesn't really work without. I have no idea yet whether I can manage that though, although you just sort of prooved it (if I understand correctly).

Thanks ...
Peter

[Jud]

Jud,

OK, so actually I was wrong about XXHE being "at fault"

... being NOT at fault, correct ?

That assumed, but of course and as logical as can be.
As a matter of fact I am (was already) thinking about some kind of (UAC) tweak back, because with W10 it doesn't really work without. I have no idea yet whether I can manage that though, although you just sort of prooved it (if I understand correctly).

Thanks ...
Peter

Yes, all correct Peter.