We are unable to reproduce this problem here, but the customer is able to
reproduce the problem consistently and cannot ship (or even run) their
application on the latest builds because of it.

From a stack trace provided by the user, the application is deadlocked
in the Win32BlitLoops code.