[Developer Question] Windows 11 upgrade failed with Portuguese government application

I'm a member of the development team for a software for Portuguese eID mechanisms (Web page in Portuguese: https://www.autenticacao.gov.pt/web/guest/cc-aplicacao)

This application is developed and distributed by an agency of the Portuguese government: Agência para a Modernização Administrativa (https://www.ama.gov.pt)

We received feedback from some of our users who are Windows Insiders about crashes in Windows 11 upgrades since the beginning of August and by means of trial-and-error they managed to attribute the cause to our software being installed on their computers.

The error reported was very difficult to understand SYSTEM_THREAD_EXCEPTION_NOT_HANDLED in module tcpip.sys

Here you can find the initial user report: https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/tcpipsys-error-windows-insider-program/3ab79955-9128-40f2-b7f7-d4a2a626a54a


After intensive testing on our side we think that we isolated our component that is causing the issue. 

We believe that a registration of a custom Key Storage Provider that our installer program performs leads to this failed Windows 11 upgrade.

Specifically because it's using a non-ASCII string as the Provider name in the BCryptRegisterProvider() call (pszProvider parameter). All our software is open source so you can analyze the KSP registration program here:

https://github.com/amagovpt/autenticacao.gov/blob/master/pteid-mw-pt/_src/eidmw/cmd-ksp/Config/KSPConfig.c

The Unicode string provided as pszProvider parameter to BCryptRegisterProvider()  is defined in a header file as “Chave Móvel Digital Key Storage Provider”


We then removed the single non-ASCII character from the name of the associated registry key naming it

“HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Cryptography\Providers\Chave Movel Digital Key Storage Provider”

and then repeated the upgrade process which worked correctly this time.

Build version that was used in our tests: Windows 11 build 22000.176

In conclusion we believe that something is wrong in the Windows 11 upgrade process with respect to handling these Key Storage Provider registry entries and it will cause considerable trouble for many Portuguese Windows users who will upgrade to Windows 11 in the near future.

|

Thank you for the update. I've raised this with some former colleagues at Microsoft to get more "eyes" on it, and here on Twitter, as a follow up on a thread I had previously started: https://twitter.com/pedrolamas/status/1436343098041376770

As you can see the Windows Insider account is asking to open a Windows Feedback ticket (the standard procedure) to get this tracked, has you opened such a ticket?

If so, please provide the link so we can reply directly; if not, I can open it with the above information if needed be.

Pedro Lamas

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

OK, I initially thought about posting it on Feedback Hub but my report exceeds the character limit :(

I'll try to cut it down to the essential details without the initial context part.

Thank you Pedro

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

This is the Feedback ticket link submitted, I circumvented the chars limitation with an attached .txt file:

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thank you, I've now replied to the Twitter thread with the link, so hopefully someone will prioritize it.

Pedro Lamas

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Is not true I have install windows 11 without any problem like this.

At least I have install 6 times and no any problem.

And I have the app also.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I'm a member of the development team for a software for Portuguese eID mechanisms (Web page in Portuguese: https://www.autenticacao.gov.pt/web/guest/cc-aplicacao)

This application is developed and distributed by an agency of the Portuguese government: Agência para a Modernização Administrativa (https://www.ama.gov.pt)

We received feedback from some of our users who are Windows Insiders about crashes in Windows 11 upgrades since the beginning of August and by means of trial-and-error they managed to attribute the cause to our software being installed on their computers.

The error reported was very difficult to understand SYSTEM_THREAD_EXCEPTION_NOT_HANDLED in module tcpip.sys

Here you can find the initial user report: https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/tcpipsys-error-windows-insider-program/3ab79955-9128-40f2-b7f7-d4a2a626a54a


After intensive testing on our side we think that we isolated our component that is causing the issue. 

We believe that a registration of a custom Key Storage Provider that our installer program performs leads to this failed Windows 11 upgrade.

Specifically because it's using a non-ASCII string as the Provider name in the BCryptRegisterProvider() call (pszProvider parameter). All our software is open source so you can analyze the KSP registration program here:

https://github.com/amagovpt/autenticacao.gov/blob/master/pteid-mw-pt/_src/eidmw/cmd-ksp/Config/KSPConfig.c

The Unicode string provided as pszProvider parameter to BCryptRegisterProvider()  is defined in a header file as “Chave Móvel Digital Key Storage Provider”


We then removed the single non-ASCII character from the name of the associated registry key naming it

“HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Cryptography\Providers\Chave Movel Digital Key Storage Provider”

and then repeated the upgrade process which worked correctly this time.

Build version that was used in our tests: Windows 11 build 22000.176

In conclusion we believe that something is wrong in the Windows 11 upgrade process with respect to handling these Key Storage Provider registry entries and it will cause considerable trouble for many Portuguese Windows users who will upgrade to Windows 11 in the near future.

@AndreGuerreiro85, maybe this would be prevented by submitting the Win32 app to the Microsoft Store. At least, this app would be processed for verification and raised an alarm at Microsoft. I had an issue like this some years ago. André, talk to your team to consider this. Thanks.

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info


Last updated November 14, 2021 Views 558 Applies to: