Veeam service do not start after Windows 11 update

[azpets]

Case ID #08060467
After installing on Windows 11 KB5082417, KB5083769, ASP.NET core 8.0.26 Veeam service does not start at startup and does not get running if started.

[Mildur]

Hi A.Z. SRL,

I checked the latest support cases and couldn’t find any similar to yours, so I wouldn’t say at this point that the issue must be connected to ASP.NET Core 8.0.26. We’ll need to wait for the investigation by our Customer Support specialists.
Keep in mind that the Free Agent offering is supported on a best-effort basis.

In the meantime, please make sure:
- You’re running the most recent version of Veeam Agent (KB2683)
- If you’re using antivirus, all required exclusions are in place (KB2034)

Best regards,
Fabian

[azpets]

Thanks for your answer, Fabian, I am aware of the limited support to free product users.

Veeam Agente is 13.0.2.1102, AFAIK the latest available.
The installed antivirus is Windows Defender, no custom configuration has been done on this.

IMVHO this might be something not totally related to my install, and it was quite similar to what happened with Norton 360 in my previous topic (which is a completely different history and installation), therefore I considered to share data and create a support case.
Maybe I'm encountering this issue due to my "install style", but I hope that this could help to... at least enhance any KB already available for troubleshooting.

[SeanHoyt]

Hi A.Z. SRL,

I checked the latest support cases and couldn’t find any similar to yours, so I wouldn’t say at this point that the issue must be connected to ASP.NET Core 8.0.26. We’ll need to wait for the investigation by our Customer Support specialists.
Keep in mind that the Free Agent offering is supported on a best-effort basis.

In the meantime, please make sure:
- You’re running the most recent version of Veeam Agent (KB2683)
- If you’re using antivirus, all required exclusions are in place (KB2034)

Best regards,
Fabian

I had the same issue this morning. When I uninstalled 8.0.26 and reinstalled 8.0.25, the service started working again. You may be right that it's not the only cause, but I would suspect that the 8.0.26 update has a lot to do with it.

[azpets]

I had other installations with ASP.NET core 8.0.26 and Veeam 13 still works.

While I'm glad that you solved your issue rolling back to 8.0.25 its hard to tell that is the main part of the issue.

[Mildur]

@SeanHoyt

Can you please share your case number?

Thank you,
Fabian

[SeanHoyt]

I don't have a case number, just sharing my experience. The only antivirus I have is Windows Defender. The only variable that changed for me that I can tell was the ASP.NET runtime update. I'm going to stick with .25 for now. I'm using Veeam Agent for Microsoft Windows 13.0.2.1102 on Windows 11 Pro 25H2 (fully updated other than the ASP.NET runtime).

[Dima P.]

Thank you for your reports folks. We will investigate it with RnD team!

[azpets]

Sharing more experiences: just updated a Windows 10 + ESU with some other softwares.
KB5082200, KB5084068, ASP.NET Core 8.0.26 and more stuff; this have much more software installed than the other i provided the CaseID.

Guess what? No service running.

Makes sense to collect logs?

[Dima P.]

Thank you for the details. Based on our analysis, the issue is related to a runtime version mismatch. Here’s what’s happening:

1. aspnetcore-runtime was updated on the system, but windowsdesktop-runtime was not.
2. These two runtimes share a common component. When either runtime is updated, this shared component is also updated.
3. If the other runtime remains on an older version, it becomes incompatible with the updated shared component and may stop working entirely.

To resolve the issue, both runtimes must be installed with matching versions. In your case, updating windowsdesktop-runtime to version 8.0.26 will fix the problem.

Going forward, please avoid updating only one of these runtimes independently. aspnetcore-runtime and windowsdesktop-runtime should always be kept in sync to prevent compatibility issues like this.

Hope it helps!