Hey @Bennard_van_Diermen,
Absolutely! You have access to the same exact files, here is more information on how to obtain your Roon Server logs:
Hope this helps and let us know if you have any additional questions along the way! 
Have enabled setting under HKEY_LOCAL_MACHINE LANMAN-WORKSTATION > CHECK FOR UNSAFE GUEST AUTHENTICATION (default N/C (enabled)) to disabled. And SMB enabled…
Unable to access Rock folders. Have done this in the past with a previous version of windows. My Windows 10 laptop works for doing this. Logs of 02-06-2026 are gone.
Based on your description, it looks like Windows is blocking access to the ROCK internal storage due to its security settings regarding “Guest” access.
This is a common behavior in recent Windows updates (10/11), where the system automatically blocks network shares that don’t require a password. Since Nucleus is designed to be accessible without a password for convenience, Windows essentially puts up a barrier.
We have a step-by-step guide on how to adjust this setting in Windows so you can copy your music files:
Please give those steps a try and let me know if you are able to connect afterwards!
Have changed the registrysettings according to the document. All is working fine afterwards.
Roon Server Machine
Roon Rock (Latest version 2.57 build 1598) Hiby R6PRO Max Firmware Latest 1.50_20251208-2312
Networking Gear & Setup Details
Roon Rock (Latest version 2.57 build 1598) Hiby R6PRO Max Firmware Latest 1.50_20251208-2312 Wifi ASUS AX XT8 5 nodes Mesh Network. Music stored on Synology NAS DS1817+ Also have a FiiO M11 Plus that doesn’t has this issue.
Connected Audio Devices
Hiby R6PROMAX, FiiO M11 Plus, Cambridge Audio 851n
Number of Tracks in Library
Description of Issue
The Hiby R6PROMAX is supposed to be Roon Ready and working fine but it really isn"t at all. Several issues with this device. Client crashing, just disconnects by the roon server. I think it would be be good decision to remove this device from the list of certified devices. Cause this device is not in a good working state for Roon at this time. Preventing users to buy this product assuming this will be a legit choice. (Have allready reported the issue but this issue is closed.)
I have merged your post with the original technical support request, and reopened.
In future, simply flag the thread as “Something Else” and the moderators will assist. Moreover, please do not post directly in Support, but follow the steps used in the original thread. Thank you.
We need to clarify what is perhaps a fundamental misunderstanding in this thread:
Roon Ready does not refer to a device’s capacity to reliably install and run the Roon client itself (the GUI, Roon Remote).
When a Partner device is Roon Ready, it means that RAAT has been fundamentally integrated into the manufacturer’s own firmware. This guarantees the following:
- Network auto-discovery of the device within Roon as an endpoint
- 32-bit/768khz PCM playback
- DSD playback
- Multi-channel playback
- DAC as its own clock master
- Two-way communication (for volume, mute, convenience switching, metadata displays, standby controls, and other commands)
- Multi-room synchronization of devices from different manufacturers using Roon Ready
- Integrated device and manufacturer branding within Roon
Have you tried using Roon ARC instead on this DAP?
As an aside, we noticed your Roon Server instance hasn’t been updated in some time and is running an outdated Roon build. This might be influencing symptoms of poor connectivity you’ve had on this and other Roon Remotes. Please navigate to Settings within Roon and update your server as soon as possible.
We’ll watch for your response and we’re happy to clarify any details.
Hello &Connor
I surely think that my roon core is running the last available build. Dated: 2-7-2026.
If things are this bad, you do not feel the responsibility to inform and protect Roon clients? I think most people rely on the certification list. It’s their reference guide for buying gear concerning roon. This is simply not good. Not for Roon clients and in the end also not for Roon itself.
Using ARC works. But all downsampled to 24/48 is maybe not what you had in mind with buying a DAP. A Phone with a good USB DAC would have been sufficient in that case.
And there is a problem with de reliability of the Hiby roon-ready client. Issues that most likely appears within 15-30 minutes. There is nothing wrong with the Roon Remote for android that’s installed on the Hiby. That is working like a charm.
Whist the HiBy is Roon Ready, this means that it is a discoverable zone (endpoint), not that the Roon client runs on the device. The app is designed to work on stock android only.
Have you tried removing the android app to see if the issue is resolved?
The Roon Ready Client is a development of HiBy. (this piece of software has been tested and got certified by Roon.) i’m not talking about Roon Remote or Roon ARC here. The Roon Ready Client can not be removed as it’s part of the Operating System provided by Hiby.
My closing comment was that the Roon app may be interfering with the Roon Ready client. That is, remove it to see if the issue persists.
Hey @Bennard_van_Diermen,
Thanks for the clarification, that’s a fair point, and we want to make sure we’re all on the same page.
You’re right: the Roon Ready certification covers the RAAT implementation that HiBy has built into the R6 Pro Max’s firmware itself, the piece that makes it discoverable as an endpoint and handles playback, clocking, and control. That’s baked into the OS and isn’t something that can be uninstalled. The separate Roon Remote app (the GUI you use to browse and control Roon) is a different, removable piece of software that just happens to also be available on the device.
What we’re actually trying to isolate with the “remove the app” suggestion is whether having that Remote GUI running alongside the built-in RAAT client is contributing to the dropouts, for example, if both are competing for the WiFi radio or CPU in a way that causes the RAAT client to miss its keepalive window. That’s a different question from whether HiBy’s core Roon Ready implementation itself is at fault, which is what we flagged back on June 4th with the no data received for >10000ms timeout in your logs.
So, if you’re willing, here’s what would help us narrow this down:
- Uninstall or force-stop the Roon Remote app on the R6 Pro Max (leaving the device connected to your network as normal), then reproduce playback for 20–30 minutes as before. If the dropouts still happen with the Remote app gone, that rules out app contention and points us squarely back at the RAAT client itself.
- Let us know whether you were able to try the WiFi-related steps we suggested on June 4th, specifically disabling WiFi power saving / battery optimization for network services, disabling adaptive WiFi switching, locking the device to a single band on your ASUS mesh, and assigning it a static IP. Even partial testing helps us rule things in or out.
- If you've heard anything back from HiBy support after sharing the log details we gave you, we'd like to know what they found on their end too, it may help us push this forward together with them.