yes and no. long ago, someone had the stupid idea of mix everything into the same script, like happens in the .net script. the same thing was done with the other ones. the problem: certain things can't be installed in all OS's and certain users can choose an free anti-virus (that most of the times, doesn't have an spyware scanner). for those cases, an alternate version should be present. in this case, windows defender. for .net, it's even worst. an user running 2k (that requires about 30MB of that package) must download the whole thing, that is about 478MB and will increase in about 170MB in a few days. an similar issue happens with those that are running windows 7, vista and xp. there's no reason for someone running an x86 OS download the updates for x64, but since at the time that this was done the releaser was the same one for all of those, then the user has no choice. with more people handling the updates, that mistake could be fixed. my idea was do an script for xp, another one for seven and another one for 2k, but free time to do that is an problem. yesterday, to prepare an vm to take certain detections for vista x64, i was working a little bit below 32F (in fact, 30.2). right now, i'm with one core handling an vm with an vista x86 sp1 that is being updated to sp2 and then i will take certain detections to finish one of the scripts that are broken. for the .net updates, will take a few more days. then, i will be back to xp to fix a few things. but really, to fix all that fast, someone else should be doing this. could be an easy thing, like extras or something else, i don't know, but anyone else working could be great, like you are doing. alone, we just don't have time enough do to every single thing that has to be done
[]s