Part-1 OK finally figured out how that limit of > 2TB HDD support actually works and what can be done and what can not be done to overcome limitations. Everything mentioned here was implemented by myself in practice. Practical experience includes using 2, 3, 4, 5, 6 and 8 TB drives. After reading this tutorial you will see that HDD > 2TB is supported both as Internal HDD and as USB attached HDD. There are however conditions to this and formats under both conditions in fact are (mostly) conflictive with each other. I am afraid this is a bit technical, but as many of us including support staff was often confused about things, I will try to make it clear(er). If you are only interested in the do's and don'ts to make it work you may jump straight to Part-2. As a start one needs to understand the difference between "HDD Initiation" and "HDD Formatting". Often this is done in one step by a program, but the technical functions are different. - The "HDD Initiation" tells the interface driver where and how to Boot, how the HDD can physically be addressed and where the physical partitions can be found on the disc. Here Microsoft Windows MBR or GPT initiations will be used to be compatibel with various Media Players - "HDD Formatting" puts on the filesystem. This defines how and where files are put on the disk using as specific filesystem. Here the filesystem is assumed always to be Microsoft Windows NTFS to remain compatible with most Media Players, FAT32 works functionally but has a 4 GByte individual file size upper limit. That won't do for bigger MKV files and above all ISO images of DVD and BD. BD in fact will hardly ever work. Some technical background for the interested - First there are the Hard Drive manufacturers which make HDD drives traditonally read by sectors of 512 bytes each. With modern discs in Terabytes that is a lot of sectors which is not very efficient any more. Filesystems like FAT32 and NTFS therefore always read/write bigger blocks of data called clusters. A cluster is by default 4 KBytes (=8 sectors) and is configurable. - Sectors are referenced to using 32-bit registers. If one calculates right one learns that a maximum 2.2 TByte can be addressed with a 32- bit counter adressing 512 byte sectors. Changing that is far from simple as this resides deep in the OS and Drivers. Partioning does not help here as still the whole disc space needs to be accessed at the physical level. This was up till recent done via the Master Boot Record (MBR) and Logical Block Addressing (LBA) using 32-bit. Windows changed to GPT (GUID Partion Table) with Windows-7 using 64-bit addressing solving this limitation structurally. - But even with GPT the read/write overhead remains the same. So Hardware manufactures did a trick and intruduced Physical and Logical sectors. The newer 2 Tera Byte and bigger discs all work with Physical Sectors of 4K Bytes presented to the software as 8 Logical sectors of 512 bytes. This technology is called "Advanced Format 4K" which reduces the disc internal overhead but not the total CPU processing chain for I/O. The drives should be labeled 512e which stands for 512 byte logical sector emulation. To make a 512e HDD efficient sectors must be aligned at 4K boundaries. See the matching AF logo for a 512e HDD. - The next step is Native 4K support. See attached logo for these 4Kn HDD. With 4Kn drives Logical Sectors, Physical Sectors and Clusters are all identical 4K Bytes streamlining throughput that way. This requires drivers dealing with 4K Logical sectors and obviously bolts on support of GPT for Initiation. Windows supports Native 4K HDD starting with Windows 8.1 OS. This paves the road for hazzlefree support of > 2 TB and even > 16 TB HDD combined with improved performance. Starting begin 2016 the first Native 4K HDD's made by WD appeared on the market. These are sold as HDD or build-in into their USB3 Enclosures. Drives can easily be identified as both Logical Sectors and Physical Sectors are always 4K. You can display all mentioned HDD format details using fsutil fsinfo ntfsinfo x: under Windows. This is a CMD to be executed with Admin rights! (Note x: replaces the actual drive being used) You may also use "MiniTool Partition Wizard Free" (see bottom for more details). Back to most media players around Access can run via Internal HDD, USB HDD Docking Bay, USB HDD enclosure or a NAS. - A NAS setup hides the total physical drive access plus format (RAID) used and as such supports > 2TB drives without the Media Player even being aware of it. - Internal discs are SATA attached (like internal drives in your PC). Drivers for SATA are easier to adapt and most media players upgraded to GPT support. They can address > 2TB discs using Advanced Format 4K support. All external drives for mounting into a PC purchased in shops are formatted that way. There is always a buffering/memory limitation somewhere but there is not a hard limitation for the maximum disc size. We know that 6 TB and 8 TB drives do work, but I do expect drives far above 16 TB to work too. - USB attached drives is a complete different ballgame. Drivers are in all places and often very old. Also 64-bit addressing support may be jeopardized by a structural HW limitation. So GPT support is often not yet available and worse not being planned for many products. Under the condition that GPT is handled by products on both ends then USB standards do not impose limitations. In practice only some recent USB3 Docking Bay implementations do include such support. As a temporary fix hardware manufactures came up with a trick. They started to ship USB-enclosures (= Casing, USB/ATA bridge and a HDD as one unit) with native 4K Logical sector enabled. The USB/ATA bridge firmware presents these to the USB-side. Result MBR can now work with 32-bit adressing of 4K Logical sectors. The physical disk access is not a problem as this is done by the USB/ATA bridge here. This trick will obviously only work up to a limit of just above 16 TB capacity.