Windows 7 Disk Management utility doesn't show disk with ext3 (type 83) partition

I have a 2 TB disk in an external SATA dock, formatted with a single ext3 (Linux) partition, which doesn't show up in the Windows 7 Computer Management->Disk Management utility, even as a raw/blank disk. I've verified that there's nothing wrong with the disk by connecting it to my Linux machine and mounting it, and I've verified that the dock is functioning properly by connecting a different FAT32-formatted disk, which mounts flawlessly as expected.

I realize that I can't actually read the ext3 partition without additional software (e.g., Ext3IFS), but why doesn't the disk show up at all? Is there some sort of stupid anti-Linux filter built in? Is there any way to force Windows to recognize the disk, so that I can at the very least use direct block access with it?

Background: I want to clone an identical 2 TB disk onto this one. Due to my hardware layout, it's much easier to have the source disk attached to one machine and the destination disk connected to another, and do the clone over the network (the network is not a bottleneck with switched gigabit ethernet), than it is to hook them both up to one machine.(1) I did this once before when both machines were running Linux, but I've since upgraded the destination machine and decided to switch back to Windows for regular desktop use. I've got Cygwin installed, and have verified that the same basic method (dd + nc) will work, but I can't do anything if Windows doesn't even consider the destination disk to exist.

(1) I only have one eSATA port on each machine. Opening them up just to do this clone is a rather large annoyance. Also, since this is my backup disk, I'd like to eventually automate the cloning from the active disk to another one that I regularly swap with a third disk that I store off-site.

Solution 1:

After further experimentation and head-banging, it turns out that Microsoft's SATA AHCI driver just sucks. After booting to a Linux livecd, I verified that there's nothing wrong with the hardware, and hotplug works exactly as expected in Linux on this machine. Then, just for fun, I decided to see what would happen with the drive plugged in at boot: Windows recognized it as expected. (I didn't try this before because I didn't want to reboot, and other drives worked just fine when hotplugged.)

I then decided to update my BIOS to the latest revision (which I didn't really expect to fix anything, and which didn't, but who knows with Windows) and finally to double-check for updated drivers. I thought I'd downloaded the latest of everything when I built this machine 2 months ago, but it turned out that I needed to install the sounds-like-a-useless-GUI-app "Intel Matrix Storage Manager" which also happens to mention deep in the manual that it includes the Intel SATA AHCI driver. With the non-generic AHCI driver installed, hotplug now works with this drive as well.

Oh, Windows driver, how I didn't miss you even a little.