Windows 11

[yannickA]

Dear Peter,

There is this new insider version of Windows 11 avaliable and I could not resist to test how it sounds.
Everything went fine but...
It seems that xxHighEnd consider this new OS as Windows XP.
Of course this new version of Windows 11 did not exist when XXH was released last year.

As a matter of fact :
- in the Services and OSD section, the Stop W10 Services box is black,
- in the XTweaks section, nothing happens when clicking on Refresh
- and when trying Minimize OS, a small window "Check OS : Not allowed for XP" pops up.

Is there some trick that would allow to bypass the "misinterpreted XP status" or should I ease my mind, enjoy xxH as it is working fine on W10 and wait for the next version of xxH to be released ?

Thank you for your work !
Best regards,
Yannick

[PeterSt]

Hi there Yannick,

XXHighEnd must explicitly anticipate on W11. And it does not. Then indeed it falls back to XP mode and nothing will work.
When W11 is more definitive I will dive into it and make it work (if possible).

Kind regards !
Peter

[yannickA]

Dear Peter,

As a matter of fact I installed the Windows 11 for Workstation version which was tested to be good for the SQ, as being said by a fellow in another forum.
May be this Workstation version breaks the way xxH "senses" the Windows version.
I will test the more conventional Windows 11 Pro version this afternoon.
I'll keep you informed !

Best regards,
Yannick

[PeterSt]

May be this Workstation version breaks the way xxH "senses" the Windows version.

Yannick, nah ... Each Windows version is explicitly dealt with. If the version is newer than what is supported, it just falls out (to not supported, hence XP).

At this moment, the latest versions supported are WS2019 for Server and 14393 for normal W10. Within that we have guidelines line "only use the .0 version". For this latter we have the 14393.0 version and any 14393 version beyond that, will sound worse (it is loaded with more stuff not dealt with and obviously I can't make new XXHighEnd versions each day or week or even month. This is also not necessary as no 14393.x will have better SQ versions than the most native one (the .0).

You will (hopefully soon) see that for W11 there will be a supported "base" version. Next, XXHighEnd will not allow updates to that supported version because it may break things (this is similar to current W10 versions not being able to boot into MinOS unless you got that working yourself). There is (or could be) too much in the way.

Each newly supported OS version (and e.g. 14393 vs 00074 are formally supported versions with 4 or so in between) takes many weeks to get there. And 100s of boot attempts.

Peter

[yannickA]

So in a nutshell, if a version of Windows sounds nice, you spend time to fine tune xxH to it. With a lot of stuff happening behind the scenes (services to be switched off and so on).
And at the end, you deliver a xxH version that sounds nicely.

It makes sense and it means that I should keep on listening to xHH on the 1607 windows 10, with joy and happiness ;o)

Did I get it right ?

Best regards,
Yannick

[PeterSt]

Did I get it right ?

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