I figured it out. The HDD i was ussing for B drive was on SATA 0, so it was disk 0 on Windows, and C drive was disk 4 (yes, I have several HDD hehe). I changed the cables so now B is disk 4 and C is disk 0 and now it boots correctly, I mean, WF is no longer up, ESET takes the place.
What I fail to understand is the relation between firewalls and C not being the first physical disk, or maybe the problem was having a B drive on disk 0.
Is Windows that weird sometimes??