Segoe UI has always been problematic for text measurement. It returns all sorts of inconsistent results. So I wonder if what's happening here is that the AutoResize on the column is getting into some kind of loop where we are measuring the same text and getting different results.

I would have thought using GDI would get around that, though. I wonder if the UseGDIPlusTextRendering setting is being ignored because your application is setting the property elsewhere, or on the control or something like that. Are you seeing a visual difference in the way text is drawn when you switch that off? You can't actually switch it at run-time, so you might want to just take a screen shot with and without that setting and see if you can spot a difference. 

We tried different things like upgrading the the latest Infragistics version, UseGDIPlusTextRendering = false but neither helped.  We noticed the sample applications did not have the issue so looking at differences in our app and the sample app we stumbled on the fact that removing the code load our style .isl file seemed to avoid the issue. Then further review about what was in the file, we found changing this one line 

            <state name="Normal" fontName="Segoe UI" themedElementAlpha="Transparent" />

to

           <state name="Normal" fontName="" themedElementAlpha="Transparent" />

Seemed to avoid the issue and still maintain the significant part of the style.

We will continue to test this, but wanted to pass along what we found so far.

Using GDI is generally better and more reliable, anyway, So try using GDI instead instead of GDI Plus and see if that helps.

The GdipMeasureString is the underlying C method that gets called by Graphics.MeasureString.  It's the use of Graphics.measureString that triggers this.  Yes this was introduced by a change in Windows 10.  MS is working on a fix for this, but from what we are seeing with our customers that have been testing the fix it does not return performance completely back to previous levels.

Hm. That explanation is a bit confusing for a number of reasons. 
First, I'm not sure exactly what is meant by "GdipMeasureString". Is that just Graphics.MeasureString? Or are they specifically referring to using GDI Plus? Or is that "p" a typo and they meant to say GDI? 

Second, we haven't changed anything fundamental about how we measure strings or how often we measure them. So if the Windows Update caused the issue, then this is something Microsoft changed on their end. Are they saying they introduced a performance issue in Windows when measuring strings? If so, then hopefully, they will fix that in Windows. We can't go in and fundamentally restructure our entire suite of controls due to a temporary bug in Windows 10.

If this is, in fact, an issue with GDI Plus, then you could work around it by switching to GDI text rendering. You can do that for your entire application like so: 

Infragistics.Win.DrawUtility.UseGDIPlusTextRendering = false;

I would put that into your Main method or in the constructor of your main form.