UnhandledException

[bilibili9331770]

UnhandledException

Oops, gInk crashed! Please include the following information if you plan to contact the developers:

未能加载文件或程序集“Microsoft.Ink, Version=6.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35”或它的某一个依赖项。生成此程序集的运行时比当前加载的运行时新，无法加载此程序集。

Stack Trace:
在 gInk.Root..ctor()
在 gInk.Program.Main() 位置 H:\Codes\gInk\src\Program.cs:行号 32

[lyk82468246]

我也是这样，之前还能用的，猜测是系统更新导致的

[yogi-playground]

I am also facing same issue

[pubpub-zz]

I'm experiencing also some troubles with my fork https://github.com/pubpub-zz/ppInk
This seems to be linked with a windows update that affects the old microso ft.ink.dll ( pubpub-zz#346 )

[famansengul]

I have the same problem too

[csss7732-hub]

Faced the same problem. Its been like that for the past couple of days. gInk stopped suddenly working. This happened after the new windows update

[TonyNRT]

I am experiencing the same issue:
gink wont launch after Windows Updates KB5064081 and KB5064401.

[1Am0]

This is confirmed, after uninstalling the updates, the program works as expected.

[SirClickALot]

Same for me.

[TonyNRT]

I wanted to share a confirmed issue affecting both ppInk and gInk following the recent Windows and .NET updates—specifically KB5064401 (.NET Framework) and KB5064081 (Windows).
After installing these updates, both ppInk and gInk fail to launch. The crash appears to stem from a change in how the .NET Framework handles native calls within the Microsoft.Ink namespace. I’ve isolated the issue using a minimal C# test harness that reproduces the failure:
InkOverlay inkOverlay = new InkOverlay();
DrawingAttributes da = new DrawingAttributes();
da.Color = Color.Red; // This line triggers the crash
inkOverlay.DefaultDrawingAttributes = da;

The error returned is:
Attempt by security transparent method 'Microsoft.Ink.InkOverlay..ctor()' to call native code through method 'Microsoft.Ink.IInkOverlay.get_DefaultDrawingAttributes()' failed. Methods must be security critical or security safe-critical to call native code.

This suggests that the InkOverlay constructor is now considered security-transparent, and native calls like get_DefaultDrawingAttributes() are blocked unless marked as security-critical. This behavior was not present prior to KB5064401.
I’ve verified:

• gInk v1.1.1 launches fine before the update, but fails after.
• ppInk exhibits the same crash behavior.
• The issue is reproducible with a standalone test app using Microsoft.Ink.dll.
  If anyone has insight into a workaround—such as alternate drawing APIs, compatibility flags, or isolating InkOverlay in a separate process—I’d love to collaborate. Otherwise, this may warrant a refactor away from Microsoft.Ink if Microsoft has deprecated or hardened access to these unmanaged calls.
  Thanks for all your work on these tools—they’re incredibly valuable, and I’d be happy to assist in testing or documenting a path forward.

[Shubham-vish]

Waiting for a fix on this. Please provide fix or suggest how I can contribute

[yodaphone]

any update to this?

[Kingfd157]

同样的问题，没有更新解决吗