This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(198.4, 21%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMH%3C/text%3E%3C/svg%3E)
When creating a Gdiplus Pen for a hair line we have always used 0.0 as witdh argument for the Pen constructor. With the KB5006670 this no longer works - the constructor changes the width from 0.0 to 1.0 (the default) and the width scales with various transformations - which is not what a hair line should do.
Explicitly setting the width (post construction) to 0 still works.
Is this a bug that will be fixed?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(60.8, 78%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFX%3C/text%3E%3C/svg%3E)
@Martin Husemann , This issue should already be fixed, please update Windows to the latest version and let me know whether it works.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 80%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAF%3C/text%3E%3C/svg%3E)
We noticed that the latest Windows update has fixed the issue and, we have already informed our customers to update their computers.
Thank you for taking prompt actions; it was a life saver!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 34%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EXY%3C/text%3E%3C/svg%3E)
KB5006670 release health does have a Microsoft Graphics Component update but It‘s probably not a bug. And It’s preferred to specify constructor parameter(s) directly instead of depending on default behavior.
No, you misunderstood.
We have lots of code that does:
Gdiplus::Pen myPen(Color::Black, 0.0f);
and then uses myPen in a context where transformations apply.
Previously you could ask that pen for its width and get 0 back:
ASSERT(myPen.GetWidth()==0.0f);
but now this fails (GetWidth() returns 1.0f) and you have to explicitly call SetWidth(0.0f) to make it work like it did the last 10 or so years.
This breaks all our applications out in the wild and we only can recommend customers to back out the KB5006670 update for now.
So what I tried to say:
Gdiplus::Pen myPen(col, 0.0f) now behaves exactly like Gdiplus::Pen myPen(col) - ignoring its explicit width argument.
Breaking existing applications is not good. I guess not many apps rely on tiny lines or use pens in scaling contexts, or this would have shown up in textng upfront before rollout.
OK, you should issue a bug. And can you find any problem in gdipluspen.h? I have no environment to verify.
I can not see any problem in gdipluspen.h (has there been an update to that recently?)
How do I issue a bug? Can you escalate it to a bug?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(307.2, 15%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EST%3C/text%3E%3C/svg%3E)
Workaround could be:
var pen = new Pen(color, width);
if (width==0)
pen.Width = 0;
Yes, I will. Sorry, I didn't make it clear. You can issue a bug through Windows feedback hub.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 45%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
This is definitely a bug! We have 15 year old applications and when Microsoft change their "preferences", we can not recompile those.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(272, 42%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAO%3C/text%3E%3C/svg%3E)
The same thing for our software! Please solve this bug asap. We are getting assistance request from dozens of customers!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(134.4, 67%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMH%3C/text%3E%3C/svg%3E)
This is a serious problem for us because our desktop mapping-application produces totally wrong graphics-output since installing this update.
I reported a bug here: https://developercommunity.visualstudio.com/t/wrong-gdiplus-graphics-output-after-installing-kb5/1553998
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 49%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDR%3C/text%3E%3C/svg%3E)
Looks like they closed your defect report.
@Martin Husemann You should issue a bug through Windows Feedback Hub instantly. With the Feedback Hub link given, anyone who encounters the bug may vote it up and then we can process easily.
I did already, https://aka.ms/AAe41ts
Unfortunately, My IT Department has disabled our ability to use the feedback hub so I can vote on it.