"Blame Microsoft". Who didn't see that coming? It's a valid assessment to be fair, but I'm sure there are people out there who are looking for a workaround rather than a place to direct their bug reports. For those people, just bear in mind that this issue is caused when a problematic control, maybe a DataGridView or a ToolStrip, is assigned a new parent