[Package Issue]: Microsoft.DotNet.SDK.9

### Please confirm these before moving forward

- [x] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
- [x] I have not been informed if the issue is resolved in a preview version of the winget client.

### Category of the issue

Installation issue.

### Brief description of your issue

From https://github.com/microsoft/winget-pkgs/pull/338349:

> The .NET SDK 9.0.311 burn installer completed successfully — all 30 MSI packages installed with result: 0x0 and the burn log shows Exit code: 0x0. However, WinGet reported the installation as failed with 0x80004004 (E_ABORT) from ShellExecuteInstallerHandler.cpp:122.
>

### Steps to reproduce

Install Microsoft.DotNet.SDK.9 version 9.0.311

### Actual behavior

> Key log evidence:
>
> x64-Scope_Undefined-Locale_Undefined-Microsoft.DotNet.SDK.9.9.0.311-26-02-10-11-16-28.log (line 299): Apply complete, result: 0x0, restart: None
x64-Scope_Undefined-Locale_Undefined-WinGet-2026-02-10-11-16-08.581.log (last line): Terminating context: 0x80004004 at ...ShellExecuteInstallerHandler.cpp:122
x64-Scope_Undefined-Locale_Undefined-Log_InstallationClient_202602101914.txt (line 28): Installation failed with exit code -2147467260
This is a false failure — the SDK installed correctly but WinGet's post-execution handler raised E_ABORT despite the installer's successful exit code.

### Expected behavior

Exit code 0, install completes successfully with no errors.

### Environment

```raw
I don't have the user data.
```

### Screenshots and Logs

_No response_

Start by reviewing PR 338349 and the cited logs, especially ShellExecuteInstallerHandler.cpp:122, to compare the successful Burn installer result with WinGet's post-execution failure. Reproduce installation of Microsoft.DotNet.SDK.9 version 9.0.311 if the required environment and logs are available. Done means WinGet reports exit code 0 when the installer completes successfully.

Written by the indexing model from the issue text.