Comment 1 by ppatel on 2013-03-09 17:00
The full executable also had the same error twice; but appeared to update once the OK button was hit each time. Just to be certain, I restarted the machine and ran the update. The error did not occur after restarting Windows.

Comment 2 by mdcurran on 2013-03-10 23:19
I'm pretty sure this is simply just a limitation of Windows. Either you'd been running without a reboot for quite some time (weeks?) or perhaps you started/restarted one or more ATs 100s of times. But in short, Windows ran out of resources to register for MSAA events.
If you see the issue again, please reopen.

Changes:
Added labels: cantfix
State: closed

Comment 3 by ppatel (in reply to comment 2) on 2013-03-10 23:39
I wonder if there is a graceful way to let the user know about this issue not affecting the update. Based on this explanation, the error showing up is a usability issue. The explanation helps me understand what might have happened. How does the user interacting with the update in the moment know what to do?

Replying to mdcurran:

I'm pretty sure this is simply just a limitation of Windows. Either you'd been running without a reboot for quite some time (weeks?) or perhaps you started/restarted one or more ATs 100s of times. But in short, Windows ran out of resources to register for MSAA events.

If you see the issue again, please reopen.