I’ll tag @support for you, however, running on an unsupported beta OS version is at the user’s risk.
Moving reports about unsupported setups to tinkering is standard practice but that does not mean Roon will ignore it. However, it will have a lower priority to those from supported environments … hence it may be a while before they comment.
See, there is an issue that i see in your logic. Just because I am running an unsupported OS does not mean that is the cause of my issue. There are other threads of the same issue being reported by windows 10 users. In my eyes, as a former quality manager and QA/QC lead, having data from all reports - both supported and unsupported OS regarded, would be valuable in debugging the issue as a whole.
I know you are probably used to snobby people expecting support to be a fix-everything button, but what I view it as is a collaborative environment wherein the consumer and producer can work together towards better understanding and improving the product both of them work hard to ensure the other enjoys.
I was able to fix my own problem with Roon, because of my background in troubleshooting and knowledge of the platform internals to a novel degree. I can only hope that posting my debugs, logs, and results of fixing my own issue would help the support department understand the issue better.
If my thread about all that is moved to tinkering , it gets buried. It’s still valuable information, that’s just my two cents.
people make many stupid decisions in life such as
- tugging on Superman’s cape
- spitting into the wind
- trying to pull the mask off of the Lone Ranger
- messing around with Jim
- upgrading to a beta version of Windows
Of course you are having problems, it is a beta version so who cares?
Frankly, reporting to the masses that any software has an issue with a beta version of an operating system is of interest only to operating system developers and the others who decided to “upgrade” to it. It is a complete waste of time for any sensible person who waits until the bugs are worked out…
Who cares? I do, anyone else running windows 11, and the people who are running into the same problem with windows 10, a supported OS.
How do you think bugs & issues get sorted out? There is some magical member of microsoft who uses roon and will integrate a fix into the final version of windows 11? It takes users like me to test and report issues for all parties, microsoft and roon, to understand and fix issues.
Hi all, we’ll make sure to test with Windows 11 before it’s officially released to the public, but right now it’s just too early.
Problems with Roon on beta versions of operating systems are typically resolved before the public release without us changing a thing (we learned this lesson the hard way!). So until it’s out of public beta, it’s not officially supported by Roon.
Roon and Windows 11.
I have Windows 11 on three different machines two of them are end points and one is the Roon Server Core. It operates as before without issue. One of the end points is hardwired in my network and the other is my laptop which is wireless. Just thought I would throw this out there.
I have a Windows 11 PC and Roon Server Core works like a charm.
||Windows 11 Enterprise
||Windows Feature Experience Pack 1000.22000.176.0
Installed the core and remote on the official version of Windows 11. It seems to me all right apart from some disconnections and reconnections that however I do not know if they depend on the operating system or not, perhaps some RAM problem with windows 11.
Who is using Roon on Windows 11?
The installation went smoothly, I was able to find the Linux server (Manjaro) located on the network, it connected, played and did not cause any problems with the devices.
Only Remote rather than Core (as I use ROCK on a NUC) but it seems fine here.
I am. Both core and server, and everything is fine.
No problem at all.
My (OLD) system
Intel Core i7-2600 CPU 3.40 GHz OC@4.3GHz 16GB RAM
Nvidia GeForce 2X GTX500 SLI Configuration
Windows 11 Pro
Anybody having ROON core on WINDOWS11? Any issues?
I was wondering the same. My headless computer where I run the core does not have a TPM so unless I use one of the workarounds that are circulating I can’t upgrade. Was wondering it it’d be worth it to push the issue and do the upgrade anyway.
The Windows client seems to run fine on W11 - I’ve been using it for a few weeks now with no issues.
I had it running with Win 11 without any problems. But Rock is still unbeatable.
It’s much faster with my DAC, and I have full MQA support that I didn’t have before. A real improvement in terms of sound too.
There shouldn’t be any difference in MQA support between different versions of Roon core presuming you know how to make it work. ROCK is my personal preference too but not everyone wants to dedicate a machine exclusively to Roon.