Well, that is the problem then. They assume it is setup correctly in Windows, while it isn't.
You MUST use the installation disk for Windows to enable SSD correctly. It does not come out of the box correctly. Besides, SSD with Windows have a number of issues as Windows has lots of functions that writes to the disk all the time, shortening the lifetime of the disk, unless you do a lot of manual optimization. I feel much safer using an SSD with GNU/Linux, even without trim, than I do using Windows on an SSD.
Besides, like I said, most disks don't need to use trim these days, modern SSD disks have these functions inbuilt in their firmware.
And, I never saw any option like the one you mention, in Windows. You can't simply tick "enable trim" in Windows, which means it will be far less transparent than in GNU/Linux when you enable SSD functions by installing a lot of software in Windows. I mean, as far as I know, Windows does not even have proper Sata Ahci support without driver CDs, while the Linux kernel support Sata Ahci SSD (& Raid) out of the box.
XP for example is not possible to install on Sata at all. While on Linux it has been possible for a very long time. I mean, I even remember back in the old days, say 10 years ago that Linux Kernel also supported Arm processors. At the time I had no idea what that was.
It's no point arguing about this. It is how it is.
http://superuser.com/questions/346606/i ... -etc-fstab