Windows AMD64 MSI contains unsigned executables blocked by Smart App Control
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 44/100
Línea de trabajo
Start by checking the Windows AMD64 release packaging and signing workflow for the MSI and ZIP artifacts; the issue names sunshine.exe and sunshinesvc.exe as unsigned. Confirm whether executable signing is expected, then reproduce the Smart App Control block with the reported release and verify the Authenticode status of the packaged executables. Done means the release artifacts have the expected signatures and Sunshine starts under Smart App Control.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Is there an existing issue for this?
- I have searched the existing issues
Is your issue described in the documentation?
- I have read the documentation
Is your issue present in the latest beta/pre-release?
None
Describe the Bug
Issue: Sunshine v2026.914.233613 cannot start on Windows 11 with Smart App Control enabled because its executables are unsigned.
Steps to reproduce:
- Enable Windows 11 Smart App Control.
- Download the official
Sunshine-Windows-AMD64-installer.msifor v2026.914.233613. - Install Sunshine using the MSI installer.
- Attempt to start the Sunshine service or run
sunshine.exedirectly. - Windows blocks execution with Application Control error 4551.
Observed behavior:
- The MSI installer completes successfully.
SunshineServiceis installed but remains stopped.- Running
sc.exe start SunshineServicereturnsStartService FAILED 4551: Application Control policy blocked this file. - Running
sunshine.exedirectly is also blocked. - Windows Security displays a Smart App Control notification indicating that the application's publisher could not be verified.
Signature verification:
- Official MSI installer:
Valid C:\Program Files\Sunshine\sunshine.exe:NotSignedC:\Program Files\Sunshine\tools\sunshinesvc.exe:NotSignedsunshine.exeextracted directly from the MSI:NotSigned
I also compared the SHA-256 hashes of the installed executable and the executable extracted from the MSI. They are identical, confirming that the installed executable was not modified during installation.
The MSI itself has a valid digital signature, but the executable files checked above are unsigned.
Could the Windows AMD64 release artifacts be checked to confirm whether the executable files are expected to be digitally signed?
Expected Behavior
Sunshine should install and start successfully on Windows 11 with Smart App Control enabled, using appropriately signed and trusted executable files.
The Sunshine service should start without Application Control error 4551, and the web interface should become accessible.
Additional Context
Sunshine version: v2026.914.233613
Installation package: Sunshine-Windows-AMD64-installer.msi (official GitHub release)
Security configuration: Windows 11 Smart App Control enabled
SHA-256 of sunshine.exe (installed and extracted from MSI):
8E2C4627318432B67520A9DE7CFD8AC089068A2873CCF8443756733A1AF7D571
The executable was also tested from a separately extracted Sunshine ZIP package and was blocked by Windows Application Control.
Disabling Smart App Control has not been attempted, because I would prefer to keep this Windows security feature enabled.
Host Operating System
Windows
Operating System Version
Windows 11 Home
Architecture
amd64/x86_64
Package
Windows - msi installer (recommended)
GPU Type
NVIDIA
GPU Model
NVIDIA GeForce RTX 5070 Ti Laptop GPU
GPU Driver/Mesa Version
32.0.15.7290
Capture Method
None
Apps
Log output
Sunshine cannot start, so a current Sunshine web UI troubleshooting log is unavailable.
Windows Service Control Manager output:
[SC] StartService FAILED 4551:
Application Control policy blocked this file.
PowerShell service status:
Name Status StartType
SunshineService Stopped Automatic
Running `sunshine.exe` directly also produces an Application Control policy block.
Authenticode verification:
sunshine.exe NotSigned
sunshinesvc.exe NotSigned
MSI installer Valid
Online logs
No response
- Lenguaje dominante
- C++
- Estrellas
- 42k
- Forks
- 2.2k
- Merge medio
- 1 d 11 h
- PR fusionados (30 d)
- 124
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de LizardByte/Sunshine
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
LizardByte/Sunshine#5795 ·
Los mantenedores suelen responder en 1 día
-
PIN pairing fails with "Missing CSRF token" - web UI never fetches/attaches the tokenQuizá libre de nuevo Un pull request para esta issue se cerró sin fusionarse. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
LizardByte/Sunshine#5467 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
LizardByte/Sunshine#5919 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 22/100
LizardByte/Sunshine#5894 ·
Los mantenedores suelen responder en 1 día
-
[Windows 11 Insider] Black screen when capturing secondary monitor (negative coordinates / AMD GPU)Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 15/100
LizardByte/Sunshine#5884 ·
Los mantenedores suelen responder en 1 día
Todos los issues de LizardByte/Sunshine
Issues similares
-
`IO.FS.realPath` reports every failure as `noFileOrDirectory` instead of classifying by `errno`Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
leanprover/lean4#15683 ·
Los mantenedores suelen responder en 1 día
-
llvm.memcpy with destination align but no source align asserts "Missed Source alignment!"Posiblemente ocupada @pvelesko la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
KhronosGroup/SPIRV-LLVM-Translator#4093 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
Los mantenedores suelen responder en 1 día
-
SIMQ silently truncates multi-query batch search to the first queryPosiblemente ocupada @LHT129 la tomó hoy. Abiertokind/bug module/index needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
antgroup/vsag#3080 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 Medio día Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día