For your understanding ...

The sheer fact that you shut off services in the Audio PC may mean that the other PC (the one communicating over RDC to the Audio PC) is not able to detect the properties of the screen (size) at the other end correctly. This is the only thing which comes to my mind because indeed, XXHighEnd is obviously not running on that controlling PC.

I am pretty sure (no guarantee) that if you don't shut off services (the more the better the chance) that all stays in-tact. But what to do with that.
I can't tell how this could be made more comfortable for you because I don't see / have the problem. So what it seems to come down to is that with the help of Google you start to recognize your situation and from there may "tweak". Regarding that in itself ... it probably won't bring a solution because what XXHighEnd does in the Audio PC is a kind of killing the communication. This is intentional (better SQ).

Not using RDC is a kind of solution, but in the end probably not because it requires an active video card. This is present in the Mach III but (I'd say) for most it is not present at all and then the other "remote connection" means won't work.

Peter

What do you mean ?

Paul, to be honest I has a similar experience the other day. But I thought it was coincidence (I actually still think it was).

Peter

(yes, I must upload the "solved" search issues with Tidal, but one nasty thing holds back (plus the lack of time).)

Fr a program which runs on an OTHER PC ?
hahaha
No.
This has to be some compatibility issue between Windows versions. You know, such screens which warn you that something is out-dated ... (but which we all accept).

Please Google the issue and try to solve it. I can't do that myself ... (as I don't have the problem). I know the question seems odd, but ...

Peter

Thank you, Paul.

Interesting. Do you perhaps have any idea yourself what could be the difference between this laptop and the other PC's not showing the issue ? W10 version ?

... Which brings me to the oddity of you telling about the issue as you did all right - even showing it per photograph ... but this is your remote ! So this is not where XXHighEnd plays at all - right ?
This makes it a sort of RDC issue of which I am not sure whether it is under your control in the first place. Anyway, now knowing this, can you think further a bit ?

Also ... referring to the topic Anthony linked to ... are you used to seeing Scrollbars ? I don't mean "today" per se, but always before ? If Yes, it is a good indication that your settings of the RDC client (the remote) have never been right. But today it starts to bother because of (for example !) a not-equal resolution between the client and the host(-capabilities).

Regards,
Peter

Anthony, I now see that that topic ended in you not understanding something. Hence it never was worked out.

Please notice (Paul too) : This can only be about the DPI setting of Windows, as I never have any problem with this whatsoever, BUT I also never set that DPI setting different than 100%. Still all should be able to cope ...

Peter

Hmm ... Still it has been made such that all should be able to cope. So maybe at some stage something sneaked in that undermines it now.

Paul, or Anthony, can you give me a DPI (Windows) setting on one hand, and the Scale Factor of XXHighEnd on the other ?
Also, at which native resolution of the display is this ?

Best regards,
Peter

Hi Ramesh - thank you for that feedback. Really !

Meanwhile I have another in the works. It is more to the extremes than the "disconnect the red wire" one.
Judging that one for weeks again already. Not sure yet when I will be sure about it. 
:-)
Peter

Yes, this seems the general consensus, and a reason for me to think you listen/observe (very) well to what happens when.

Unfortunately it doesn't seem as simple as highering Q1 x xQ1 as it seems to suck the life out of matters. Actually the opposite of settings them ultra-low, which makes all very spacious and lively, but also more harsh. So it is key to find the proper balance, and it now seems that Q3,4,5 are key to that. But it is a typical thing nobody played with really, unless they did not tell about it.
Let's remember that for me it started to become a "subject" when I went from the Blaxius^2 to the Blaxius^2.5 which are so much more explicitly showing less distortion that other "distortions" now submerge. And taming it is done with Q3,4,5, as it seems to me. Having them all at 0,0,0 is too much of it (smears too much) so it could be the combination.
Btw, I am waiting for the day that I or anyone else dares to dial one in at 2 or beyond. So yes, go figure about the 25,000 etc. ... it never stops.

Thank you, David,
Peter

David,

Thank you very much; I think you ate a very good listener.
With this Lush^3 config, my relevant settings are :

Q1=14
xQ1=4
Q3=0
Q4=0
Q5=1
SFS=10.13
ClockRes=10ms
Custom Filter = Low
Balanced Load=62.

This is the result of quite some weeks (months actually) of changing and trying. The above itself I now use for I think 3 weeks, to great satisfaction.
The importance of Q3, 4 and 5 is remarkable. As you see, I arrived at 0,0,1 which is quite explicit.

Kind regards,
Peter

Paul,

Then Delete the album from the Gallery like you see in the attachment.

Does that help ?
Peter

Hi Paul,

I think that selecting a new album to play, play that a bit, then quit XXHighEnd and restart, should solve it. But it depends a bit ...

Otherwise a couple of screenshots could be helpful.

Regards,
Peter

Almost.

1. There needs to be potential in the version. Could be something drastic like W11.

2. I need to install it. No big deal, but it should be a "native" version (not destroyed by bloatware).

3. I need to make it technically work. No Blue Screens at going to MinOS.

4. From there it should have SQ potential. If it has :

5. I will need to eliminate all the extra new services and processes. That is, usually there is support for many more things. It all needs to go out. This requires the 100+ boots, because use a wrong combination (too many) and all may never be booting again. -> Reinstall and after adjustments reiterate. Possibly one month further (throughput) :

6. I need to install it in the RAM-OS environment because this is my reference. Like MinOS, RAM-OS makes a serious SQ difference. This requires installing till you drop, and that from a ready guide (of 12 pages or so).

7. If the RAM-OS version does not sound well, I could try to tweak for the better with the virtual one million parameter possibilities, but it may lead to nothing. W8 is an example of that - it took a year to get right and that with the help of "all of you". Luckily this is an exception. But FYI, W7 SP1 also did not sound and was given up upon quickly. W8.1 ? too poor to continue with.

Now you know why it is still 14393.0 we are using. Actually it is simple : there is nothing wrong with it. Of course if you use the audio playing PC as office PC, then this can't work. But audio (when done well) requires a dedicated PC ...
Btw, we will only know whether there is nothing wrong with 14393.0 when W11 has been tried. See 1,2,3,4,5,6,7 above. Haha.

Peter