MattyUSA

Forgive me if this is less than 'technical' response. I think you have your technical answers already. I use a virtual machine for customer supplied suspect files. not been burned yet. My initial thought response to reading the thread was "Sod the safety aspect, it's illegal, it's theft. Steal her stuff (some things that are noticeable) from around the house and ask what the fundamental difference in behavior is before handing it back." Would it be ok to steal these games off a store shelf?

I had the same issue and after some reading I noted that the versions of mstscax.dll and mstsc.exe were different. It looks like the exe was not updated alongside the dll. So the two file versions were different and the upgrade of RDPClient from 6.0 to 6.1 was failing since this was a requisit. belivakov: nailed one method for a solution. Uninstall 956744 (rolls back RDP to previous version so no mismatch?? I think). Worked for me. If you don't have the update folders then I wonder if you can get that update again and use a command line switch to uninstall rather install. There was obviously a (usually low) risk in deleting the update folders, its a shame this KB update catches it. I found this page that explained a lot and offered other methods forward: http://www.mskbarticles.com/index.php?kb=2481109 Essentially it only effects those that installed updates without using windows updates site. So for me it effected all those machines I slipstreamed updates into a custom build dvd.. I'm guessing that is what a lot of readers here are facing. Hope this help some. Matt