Adjusting severity now that we understand that this could make people crash as soon as they they type - so very impacting for the relatively few users who experiment this. There has been a lot of progress in bug 1777960.
Bug 1846512 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Adjusting severity now that we understand that this could make people crash as soon as they they type - so very impacting for the relatively few users who experiment this. There has been a lot of progress in bug 1777960, leading to the following conclusions: - Starting with Windows 11 22H2 (10.0.22621.*), `TF_Notify` from `msctf.dll` (also known as `CtfImmNotify` from `imm32.dll`) uses a new convention for its third argument. It takes a pointer to a structure where a scalar value was used before. - ESET presumably has an optional feature (perhaps an anti-keylogger feature here too?) that calls into this function but would still use the old convention. I will contact ESET to forward these details.
Adjusting severity now that we understand that this could make people crash as soon as they they type - so very impacting for the relatively few users who experiment this. There has been a lot of progress in bug 1777960, leading to the following conclusions: - Starting with Windows 11 22H2 (10.0.22621.*), `TF_Notify` from `msctf.dll` (also known as `CtfImmNotify` from `imm32.dll`) uses a new convention for its third argument. It takes a pointer to a structure where a scalar value was used before. - ESET presumably has an optional feature (perhaps an anti-keylogger feature here too?) that calls into this function but would still use the old convention. - ESET is responsible for ~14% of the volume on this crash signature. I will contact ESET to forward these details.
Adjusting severity now that we understand that this could make people crash as soon as they they type - so very impacting for the relatively few users who experiment this. There has been a lot of progress in bug 1777960, leading to the following conclusions: - Starting with Windows 11 22H2 (10.0.22621.*), `TF_Notify` from `msctf.dll` (also known as `CtfImmNotify` from `imm32.dll`) uses a new convention for its third argument. It takes a pointer to a structure where a scalar value was used before. - ESET is responsible for ~14% of the volume on this crash signature. - ESET presumably has an optional feature (perhaps an anti-keylogger feature here too?) that calls into this function but would still use the old convention. I will contact ESET to forward these details.
Adjusting severity now that we understand that this could make people crash as soon as they they type - so very impacting for the relatively few users who experiment this. There has been a lot of progress in bug 1777960, leading to the following conclusions: - Starting with Windows 11 22H2 (10.0.22621.*), `TF_Notify` from `msctf.dll` (also known as `CtfImmNotify` from `imm32.dll`) uses a new convention for its third argument. It takes a pointer to a structure where a scalar value was used before. - ESET is responsible for 1% of the volume on this crash signature. - ESET may have an optional feature (perhaps an anti-keylogger feature here too?) that calls into this function but would still use the old convention, or maybe they have already fixed this issue? I will contact ESET to forward these details.
Adjusting severity now that we understand that this could make people crash as soon as they they type - so very impacting for the relatively few users who experiment this. There has been a lot of progress in bug 1777960, leading to the following conclusions: - Starting with Windows 11 22H2 (10.0.22621.*), `TF_Notify` from `msctf.dll` (also known as `CtfImmNotify` from `imm32.dll`) uses a new convention for its third argument. It takes a pointer to a structure where a scalar value was used before. - ESET is responsible for ~1% of the volume on this crash signature. - ESET may have an optional feature (perhaps an anti-keylogger feature here too?) that calls into this function but would still use the old convention, or maybe they have already fixed this issue? I will contact ESET to forward these details.
Adjusting severity now that we understand that this could make people crash as soon as they they type - so very impacting for the relatively few users who experiment this. There has been a lot of progress in bug 1777960, leading to the following conclusions: - Starting with Windows 11 22H2 (10.0.22621.*), `TF_Notify` from `msctf.dll` (also known as `CtfImmNotify` from `imm32.dll`) uses a new convention for its third argument. It takes a pointer to a structure where a scalar value was used before. - ESET is responsible for ~1% of the volume on this crash signature. - ESET may have an optional feature (perhaps an anti-keylogger feature here too?) that calls into this function but would still use the old convention, or maybe they have already fixed this issue?