I found the article beneath concerning the VS 2010 error message. Maybe update 11 has nothing to do with it and it is the issue with the .NET 4 conflict coming with windows update. Have you installed SP1 for VS 2010?
Edit: If I had read the blog before I wrote, I had seen, that the SP1 would not help but that a check of the PATH variable should be done. PATH can get corrupted somehow. Steve had written something in an other thread on the matter.
I've installed update 11 without any problems so far. VS 2010 starts and compiling works. My path system32 entry is not corrupted or gone. No restart was necessary. Maybe this is because I am local administrator on my machine?
We have seen that Windows sometimes corrupts the path when an installation adds text to the path. No error is given during the install but the contents of PATH is lost. We haven't been able to figure out a pattern to this. You may find a reboot or logout/login helps.
The IVF Update 11 "caused" the problem, because the installer extended my path > 2048 characters. When your path is longer than 2048 characters, it wont work any more. But not only PATH is screwed, some vital environment variables like %windir% as well.
Now I cleaned my path and removed some entries, now all works fine again... Until I extend my path again ;-)
you have installed update 9, 10 and 11 parallel on your computer. I have installed only the newest update and the other uninstalled (automatically by installer). This is the reason, why I am not affected so far and my %PATH% has still some amount of free characters.
Do you really need the fallback to older updates? I know it costs a lot of time, if it is obvious the new update produces errors and older versions work, so, installing/ uninstalling is necessary. I take this risk.
We recognize that we are adding a lot to PATH. In the next release, we will add less. As I mentioned above, Windows does not handle well attempts to extend PATH a lot, and different versions of Windows seem to have different limits here.
It is a good idea to remove redundant folders from PATH - you need only the latest of any of the Intel products there as folders later in PATH simply won't get used (DLLs will get resolved earlier.)
Markus, yes, leave only the latest version in PATH (this should be a single set of entries under Common Files for Composer). For Fortran, you might have update-specific settings for MKL. But the way Windows searches PATH, it will load the first DLL of the right name (and architecture) it sees, so having same-named DLLs later in PATH is pointless. For the compiler, we offer upward compatibility so you can run older EXEs with newer library DLLs. MKL is supposed to be the same.