Could not load 'AL Explorer'

[SynPaul]

When trying to open AL Explorer via the command palette or the keyboard shortcut, the tab briefly opens with no content, then closes again. This error message appears at the bottom of the screen:

I can temporarily fix it by uninstalling VS Code, deleting the %appdata%\code and %userprofile%.vscode directories, then reinstalling VS Code. However, after some time, perhaps a few days, the issue happens again.

I'm currently using version 15.0.1433841 of the AL Language extension, dated 22nd May 2025, and this version of Visual Studio Code:

I have no other extensions installed.

My OS is Windows 11 24H2 build 26100.4202.

Some colleagues are also having the same issue.

[NKarolak]

FYI using the very same AL Language and VS Code versions, I cannot reproduce the issue on my Windows machine:

Windows 11 Enterprise, 24H2, build 26100.3983

[SynPaul]

Hi Natalie

I've been getting the issue for a couple of months now. If I reinstall VS Code as above, it works fine for a while, then stops. I've just tried to open it now and got this:

I get this about 90% of the time and it's quite frustrating. I'm happy for you that you don't get it, but how can I fix it for me?

[NKarolak]

"FYI" = just additional information, rather for Microsoft (I'm not a MSFT employee) than for you ;-) It is on Microsoft to gain the right conclusions from it.

Btw, was something logged in the Event Viewer > Windows Logs > Aplication? Or directly in the "OUTPUT" tab of VS Code?

[SynPaul]

Thanks Natalie, I didn't realise you're not with Microsoft.

There's nothing in either of those logs unfortunately, nor in %appdata%\Code\logs, or in the Developer Tools window.

[nndobrev]

Unfortunately, I can't repro the issue. Can you try to provide more info?

[SynPaul]

Yes sure, what additional information would you like? I raised this as a support ticket and they sent me here.

[nndobrev]

Hey @SynPaul sorry for not noticing your reply. Can you please enable Verbose logging to your editor service log by setting "al.editorServicesLogLevel": "Verbose" in your settings.json file. For your convenience you can also set editorServicesPath so you can find the log file easily. Then reproduce the issue and send me the file over to [email protected].

Don't forget afterwards to change the Level back to Normal as these logs can get very chatty and slow down vscode and degrade your experience with our extension.