Sounds like the case. I'm guessing it was on an expanding virtual machine disk image, in which case the problem is user error rather than Windows.