Crash in conhost?

[vefatica]

Any ideas on why conhost might crash (Access violation - code c0000005 (!!! second chance !!!)), at ntdll!RtlCustomCPToUnicodeN+0xa9?

[DHowett]

This is a bug in conhostv1 (the “legacy” console) that resulted from changes to the PEB to accommodate per-process ACP. This should only occur on 22000+ (“Windows 11”).

Notes here: #15038

Fixed, but I can’t give a release timeline.

Viable workaround: stop using conhostv1; it’s 2023.

[vefatica]

Here's a link to the original report. It's from a JPSoft/TCC user who says he's using Win-10, version 22H2 (OS-build 19045.3324).

Are you saying it won't happen with the legacy console in Windows 10? If so, I reckon it's something else.

[zadjii-msft]

MSFT:42362468 points at MSFT:41399222 which points at KB5027303, which is OS Build 22621.1928.

I believe that regressed in OS!4161028, in Dec 2019... that might have made its way to Win10 builds. Hard to say...
The revert was in os.2020!8161820 in Dec 2022. Interesting.

[vefatica]

I guess that was it. The user has reported

Now after switching off Lecacy Mode, I've not seen the same crash again.

Thanks!