[Thông báo bảo mật quan trọng] Phát hiện các trang web giả mạo Qfinder Pro. Tìm hiểu thêm >

QuTS hero h6.0.1.3550 build 20260709

2026-07-14

Applicable Models

  • TS-h2490FU/TS-h1090FU
  • TS-h1290FX
  • TDS-h2489FU/ TDS-h2489FU R2
  • TS-h3088XU-RP
  • TVS-h1288X/TVS-h1688X
  • TS-h987XU-RP/TS-h1887XU-RP/TS-h2287XU-RP/TS-h3087XU-RP
  • TS-h1886XU-RP/TS-1886XU-RP/TS-h1886XU-RP R2
  • TS-h686/TS-h886
  • TNS-h1083X
  • TS-883XU/TS-883XU-RP/TS-983XU/TS-983XU-RP/TS-1283XU/TS-1283XU-RP/TS-1683XU/TS-1683XU-RP/TS-2483XU/TS-2483XU-RP/TS-h1283XU-RP/TS-h1683XU-RP/TS-h2483XU-RP
  • TS-h977XU-RP/TS-h1277XU-RP/TS-h1677XU-RP/TS-h2477XU-RP
  • TS-h1277AXU-RP/TS-h1677AXU-RP/TS-h2477AXU-RP/TS-h3077AFU
  • TVS-h1675U-RP/TVS-h1275U-RP/TVS-h875U-RP/TVS-h875U
  • TVS-675
  • TVS-h474/TVS-h674/TVS-h874/TVS-h874X/TVS-h674T/TVS-h874T
  • TBS-h574TX
  • TS-873AU/TS-873AU-RP/TS-1273AU-RP/TS-1673AU-RP/TS-873AeU/TS-873AeU-RP
  • TS-h973AX/TS-473A/TS-673A/TS-873A
  • TVS-672X/TVS-872X/TVS-672N/TVS-872N/TVS-472XT/TVS-672XT/TVS-872XT
  • TS-1655/TS-855X
  • TS-855eU/TS-855eU-RP/TS-h1655XeU-RP
  • TS-253E/TS-453E
  • HS-264/TBS-464/TS-364/TS-464/TS-664/TS-264/TS-464C2
  • TS-466C
  • TS-464U/TS-464U-RP/TS-1264U-RP/TS-464eU/TS-864eU/TS-864eU-RP
  • TS-i410X/TS-410E
  • TS-h765eU
  • TS-h1277AFX
  • TVS-AIh1688ATX
  • Qu805/Qu605/Qu405

Important Notes

  • The following expansion card models have reached the end of product support, starting from QuTS hero h6.0.0: Mustang-200-C-8G-R10, Mustang-200-i5-1T-32G-R10, Mustang-200-i7-1T-32G-R10, Mustang-F100, Mustang-V100, QM2-2P10G1T, QM2-2S10G1T.
  • Starting from QuTS hero h6.0.0, the following applications will no longer be supported: CAYIN CMS-WS Lite and CAYIN MediaSign Player (replaced by CAYIN Media Viewer), IDrive, JRE, Mustang Card Manager, Mustang Card User Driver, Python, Python3, QButton, Qmiix Agent, QVR Elite (replaced by QVR Surveillance), Skype.
  • To ensure system security, starting from h6.0.0 release candidate, QuTS hero no longer allows firmware downgrade.
  • For the best experience and optimal system performance, we recommend updating all available applications in the App Center after updating the firmware.

Security Updates

  • Applied multiple security updates to further enhance system security.

Fixed Issues

  • Fixed an issue where a console message incorrectly hinted the default admin password during setup when users connected the NAS via HDMI. (The default password should be the Cloud Key instead of the MAC address.)
  • Fixed an issue where Storage & Snapshots incorrectly displayed the firmware version of the TL-R6020Sep-RP SAS JBOD expansion enclosure as 0.0.0.
  • Fixed an issue where Storage & Snapshots incorrectly displayed the error status icon for TL-R6020Sep-RP SAS JBOD expansion enclosure even though the device was functioning normally.
  • Fixed an issue where large-capacity storage pools would go offline after users updated QuTS hero version from h5.1.14 to h6.0.0.3500.
  • Fixed an issue where the "Resize Shared Folder" button would become grayed-out and unclickable after users expanded a shared folder capacity to 5 PB (upper limit).
  • Fixed an issue where the progress of applying individual ACL permission changes would be occasionally stuck at 0% if the folder structure was deep and complex.
  • Fixed an issue where Storage Manager would display RAID 60 as RAID 6 when adding a new RAID group.
  • Fixed an issue where the "Expand Pool" wizard could allow users to exceed the upper limit of 16 disks when creating a RAID 60 group.
  • Fixed an issue where the snapshots taken on the temporary takeover node would not appear in the SMB Previous Versions after an automatic failback to the original active node.
  • Fixed an issue where wired 802.1X authentication would fail after a firmware update from QuTS hero h5.x.x to h6.0.0.
  • Fixed an issue where encrypted shared folders still allowed unsupported characters in passwords, which would lead to unlock failures after firmware update to QuTS hero h6.0.0.
  • Fixed an issue where DNS resolution would fail if the DNS server IP address was not in the list of allowed connections defined by users.
  • Fixed an issue where improper API handling would cause abnormal log writing and lead to ramdisk errors.
Was this article helpful?
Thank you for your feedback.

Chọn thông số kỹ thuật

      Xem thêm Thu gọn
      Chọn quốc gia hoặc khu vực của bạn
      open menu
      back to top