Install it through device manager via "disc install"
I confirm that 18.104.22.16834 fixes the leak. But...
..we need to be able to run our app also if the MSDK installed has the leak, we can do that - we have a fallback - but we need to detect the faulty driver.
I see a user above told about 22.214.171.12439, at the beginning someone is talking about a 4530, I know that the 126.96.36.19905 is leaking too. Instead the 4463 is good, not sure about the 4501 cited in the first message...any suggestion on how to detect the leak at startup? something like a sample code? some parameter to check in the MSDK? maybe a subversion number? the availability of a function introduced (or removed)?