Switching to Windows Hello Causes Unrecoverable Issue

[mjmatthiesen]

1. Describe the bug

after enabling / switching to windows hello the extension can no longer auth with bc saas systems.

2. To Reproduce
Steps to reproduce the behavior:

1. use the extension to auth with a bc saas system.
2. enable windows hello, restart you machine, etc.
3. start vs code, try and auth with the same bc system, get an error
4. it's possible it'll error with any saas system, but I didn't have a new one available to test with.

[2026-07-21 13:24:54.38] Starting a debug session using launch configuration 'Attach: Microsoft cloud sandbox' .
[2026-07-21 13:24:54.55] Error: Key not valid for use in specified state
[2026-07-21 13:24:54.55] Error: An internal error has occurred

3. Expected behaviour
I am not expecting to have the credentials cache available, however I would expect it to be able to make a new cache, if that makes sense. The same way git recognizes it needs me to login, copilot, signal, etc.
to work around this I had to

1. uninstall the extension
2. close vs code
3. delete the extension folder
4. start vs code
5. re-install the extension

if you can tell me which file in that folder is the actual guilty party I will be happy to note that internally.

4. Actual behaviour
Hard error that cannot be resolved.

5. Versions:

• AL Language:17.0.2273547
• Visual Studio Code:1.129.1 (system setup)
• Business Central:saas 28

Final Checklist

Please remember to do the following:

• Search the issue repository to ensure you are reporting a new issue

• Reproduce the issue after disabling all extensions except the AL Language extension

• Simplify your code around the issue to better isolate the problem

[thloke]

There's the Clear Credentials Cache command specifically for this. You'll need to do Ctrl + Shift + P to bring up the command palette, and you can search for it in there. Please reopen if that doesn't fix it.

[mjmatthiesen]

There's the Clear Credentials Cache command specifically for this. You'll need to do Ctrl + Shift + P to bring up the command palette, and you can search for it in there. Please reopen if that doesn't fix it.

Yeah, that doesn't fix this issue. I'm also not able to reopen this issue. GitHub won't let me

[thloke]

That's super weird if credential clearing didn't work. Can you run it with verbose logging? Then that should generate some log files in your extension install directory that might have more information about the underlying error.

In your settings.json: "al.editorServicesLogLevel": "Verbose"

And then it should produce two files in the extension folder. In this case, I think the debuggerservices.log might be the more useful one, but there's also the editorservices.log file.

[mjmatthiesen]

The debuggerservices.log isn't being updated during the process.

What we are doing is using the download symbols command (1) and then we tried to clear credentials with a vs code restart in between (2).

IT has almost completed the transition, so I may not be able to collect more logs.

1-EditorServices.log
2-EditorServices.log

[mjmatthiesen]

I did the process with another developer, and they received an error different from myself or the previous one. They received basically nothing, even with the verbose turned on. You can just see that it instantly disconnects. Clearing credentials cache did nothing, not even any logging.

I have another developer I will be doing this with early next week. I will see if they get something more descriptive out.

DebuggerServices.log