AppExecutionAlias directory missing

Question

Hello

I noticed errors in Event Logs of my msix packaged apps, I think because of space in directory and file names, didn't find a tip online, AI didn't help either, here's the log and part of my AppxManifest.xml, any help is appreciated.

DateTime:	12/7/2025 12:11:46 PM
Level:	Error
Source:	Microsoft-Windows-AppXDeploymentServer/Operational
ErrorCode:	0x8007010B
Opcode:	Info
User:	NT AUTHORITY\SYSTEM
Message:	AppExecutionAlias directory missing, error code is 0x8007010B.
Troubleshooting info: The directory name is invalid. | The directory name is invalid.



  <Applications>
    <Application Id="App" Executable="VFS\ProgramFilesX64\ACME\My App\My App.exe" EntryPoint="Windows.FullTrustApplication">
      <uap:VisualElements DisplayName="My App" Description="Enterprise grade My and storage viewer, parser and converter." Square150x150Logo="Assets\MedTile.png" Square44x44Logo="Assets\AppList.png" BackgroundColor="transparent">
        <uap:DefaultTile ShortName="My App" Square71x71Logo="Assets\SmallTile.png">
          <uap:ShowNameOnTiles>
            <uap:ShowOn Tile="square150x150Logo" />
          </uap:ShowNameOnTiles>
        </uap:DefaultTile>
      </uap:VisualElements>

      <Extensions>
        <uap3:Extension Category="windows.appExecutionAlias">
          <uap3:AppExecutionAlias>
            <desktop:ExecutionAlias Alias="MyApp.exe" />
          </uap3:AppExecutionAlias>
        </uap3:Extension>

Answer 1

Hello Halifax Crosby, 

I spent a bit of time looking around after seeing your error. I think I’ve found a plausible explanation for what’s happening and a few things worth trying to fix it. 

It seems the error code 0x8007010B stands for “directory name is invalid.” In the context of using an AppExecutionAlias inside an MSIX package, that likely means the alias-registration process tried to register a path to your executable  but the path it got was considered invalid.  

A few things I suggest you try: 

• Rename the folder(s) and executable so there are no spaces or special characters, for example MyApp\MyApp.exe instead of My App\My App.exe. Then update the manifest accordingly, rebuild, and reinstall. 
• If you want to test whether the alias registration is the issue, you can temporarily remove the <AppExecutionAlias> extension from the manifest, the app should still install and run normally, just without the alias. 
• After installation, check whether the alias was actually registered: on Windows aliases are typically stored under …\Users<YourUser>\AppData\Local\Microsoft\WindowsApps. If it’s missing, alias creation failed.  
• If renaming doesn’t help, there might be other causes, for example, permission issues, profile corruption, or restrictions on alias creation. 

Hope this helps !