Windows PR Build doesnt start webui and links to ucrtbased.dll

[brutez]

• I confirm that this is an issue rather than a question.

Bug report

I downloaded the PR Build for PR 1856. i had to install Windows SDK to optain ucrtbased.dll (debug version) to make it run.

Dialog starts but no webui is loaded.

Steps to reproduce

• Download https://github.com/hyperion-project/hyperion.ng/actions/runs/14540504850
• install Windows SDK
• run hyperion

What is expected?

PR Build works without ucrtbased.dll but with ucrtbase.dll instead.

Hyperion will start the webui und opens a browser tab for localhost.

What is actually happening?

First Error Message that ucrtbased.dll is missing is displayed. After that fix hyperion starts but doesnt load the webui under usual port and Adresse.

System

cant do, no webui (windows 11)

[Lord-Grey]

Which Windows Version are you running?

[Paulchen-Panther]

I am aware of this problem (debug build). A fix (RelWithDebInfo Build) for this problem is coming later this week with other customizations.

[brutez]

Which Windows Version are you running?

Windows 11 on an x86 system

[Paulchen-Panther]

@brutez I hope with this PR the PR artifacts work for you again?
https://github.com/hyperion-project/hyperion.ng/actions/runs/15074510051

[brutez]

@Paulchen-Panther

ot6 and ot5 are not stable. Start dialog is coming up but both doesnt automaticly open the webui. i can manually start the webui but its not stable and loses connection after a time (timetemp appcrash) Windows is showing an error event with ot6core.dll/ot5core.dll and a missing app-id.

EventName APPCRASH

Fehlerhafter Anwendungsname: hyperiond.exe, Version: 2.0.17.0, Zeitstempel: 0x68277dbf
Fehlerhafter Modulname: Qt5Core.dll, Version: 5.15.2.0, Zeitstempel: 0x5fa4dd3b
Ausnahmecode: 0xc00000fd
Fehleroffset: 0x00000000002dc9a8
Fehlerhafte Prozess-ID: 0x11C0
Fehlerhafte Anwendungsstartzeit: 0x1DBC8940A28ED3A
Fehlerhafter Anwendungspfad: ......\Hyperion\bin\hyperiond.exe
Fehlerhafter Modulpfad: ........\Hyperion\bin\Qt5Core.dll
Berichts-ID: f2b9c339-aa77-4661-a0ca-b9a9247c6a9a
Vollständiger Name des fehlerhaften Pakets:
Fehlerhafte paketbezogene Anwendungs-ID:

Fehlerhafter Anwendungsname: hyperiond.exe, Version: 2.0.17.0, Zeitstempel: 0x68277e6b
Fehlerhafter Modulname: Qt6Core.dll, Version: 6.8.3.0, Zeitstempel: 0x67d82d3a
Ausnahmecode: 0xc00000fd
Fehleroffset: 0x0000000000393147
Fehlerhafte Prozess-ID: 0x4D18
Fehlerhafte Anwendungsstartzeit: 0x1DBC8923DCC3886
Fehlerhafter Anwendungspfad: ........\Hyperion\bin\hyperiond.exe
Fehlerhafter Modulpfad: .........\Hyperion\bin\Qt6Core.dll
Berichts-ID: 3b6533ff-ffa3-4082-b9bb-c14d665f9146
Vollständiger Name des fehlerhaften Pakets:
Fehlerhafte paketbezogene Anwendungs-ID:

[Lord-Grey]

@brutez Could you share your hyperion configuration, please?

Einther you export the configururation or share the configuration database under your user .hyperion directory

[brutez]

@Lord-Grey

hyperion db.zip this will carry over to 2.0.17

Hyperion-2.0.16-Backup (Keller) 2025.04.30.json this cant be import in 2.0.17 (not compatible)

[Lord-Grey]

@brutez Thank you for providing your configuration.
Unfortunately, UI was not able to reproduce a crash on my system (I had not the chance running WLED).

[brutez]

@Lord-Grey Thanks for testing my config. Its running good on 2.0.16 but will crash on 2.0.17 when streaming starts. So maybe the part with streaming to wled is needed.

[Lord-Grey]

Hi @brutez We did some updates to the Windows build.
Would you mind testing the latest version (https://github.com/hyperion-project/hyperion.ng/actions/runs/15475771940), please?

I installed on a fresh Windows 11 with your config and do not see any aborts...