Windows Terminal cannot open after install last update ("not designed to run on Windows", 0xc0000045)

[javlaks]

Windows Terminal version

Win11_1.14.2282.0

Windows build number

Microsoft Windows [Version 10.0.22000.856]

Other Software

No response

Steps to reproduce

Install the lastest version (Win11_1.14.2282.0) in a windows 11 machine

Expected Behavior

Install successfully the Microsoft.WindowsTerminal_Win11_1.14.2282.0_8wekyb3d8bbwe.msixbundle in a Windows 11 machine and open the Terminal

Actual Behavior

The installation completes well, but when I try to open the Terminal, I see the following error:

[zadjii-msft]

um what. @DHowett ‼️ I've never seen anything like this.

Is it cause we have a dependency on 2.7.3, but that's not rolled out yet? I literally have no idea.

[DHowett]

UH WHAT

MUX isn't linked by ordinal (or at all actually... it's all loaded at runtime)

[zadjii-msft]

OKAY WHAT DOES THIS MEAN

@javlaks I know this sounds stupid, but can you back up your settings and reinstall? Maybe it just botched the install?

[DHowett]

Do you happen to have any higher security features enabled?

[javlaks]

OKAY WHAT DOES THIS MEAN

@javlaks I know this sounds stupid, but can you back up your settings and reinstall? Maybe it just botched the install?

I did it but the issue is still present, same error. I had to rollback to Win11_1.14.1963.0

[javlaks]

Do you happen to have any higher security features enabled?

Yes, the computer have some security options enabled by the company, but the weird thing is that previous versions work fine in the same computer, only the latest gives me this error

[zadjii-msft]

Note: Presumably there are weird bits set on a page in the DLL giving it invalid permissions (like, write+execute), but what, that should never happen.

If we did ship a binary that got compiled wrong, I'm sure we'll hear a lot more about in this thread soon 😨

[DHowett]

No significant difference in DLL headers:

I wonder if it could be an error coming out of loading MUX.dll...

[DHowett]

@javlaks do you happen to know which settings they've enabled?

Would you be able to check this one in the Advanced System Properties?

[javlaks]

This is why I see, @DHowett

[DHowett]

Crap.

How about this, from PowerShell?

get-ciminstance win32_operatingsystem | fl DataExecution*

[javlaks]

Here is it

[zadjii-msft]

Huh, that's what I'd expect there. Any chance this just went away/? I don't know if we had any leads left, to be honest. And we haven't heard any other similar reports since. I legit have no idea what this could be other than cosmic bit flip.

[zadjii-msft]

Hey all, our bot's been acting up the last few weeks. This issue has been marked as requiring author feedback, but hasn't had any activity in the last week. We're gonna close it to tidy up. Feel free to continue the discssion in the comments - we can always reopen if new information comes to light. Thanks!