Hexnode Agent for Windows: supported .NET runtime version and troubleshooting e0434352 crashSolved

Hi @jaxon_r,

The Hexnode Agent installer for Windows includes the required runtime components during installation, so you do not usually need to manually download or pre-install a separate .NET runtime package for the agent to deploy successfully. For reference, the Hexnode Windows Agent generally requires .NET Framework 4.7.1 or later.

For the crash entry you mentioned, exception code “e0434352” usually indicates a .NET-related exception. The Application Error entry that lists “HexnodeAgent.exe”, “KERNELBASE.dll”, and the exception code is only part of the information. To troubleshoot further:

1. Run the Microsoft .NET Framework Repair Tool.
2. Restart the Windows device.
3. Open Event Viewer using eventvwr.msc.
4. Go to Windows Logs > Application.
5. Check for a .NET Runtime error at the exact same timestamp as the Application Error entry.

The .NET Runtime event usually contains the stack trace, which is what identifies the actual cause of the crash, such as a missing file, permission issue, or another runtime exception.

Regards,
Sienna Carter
Hexnode UEM

Thanks, so if I’m deploying the Windows agent, I don’t need to push .NET Framework separately first? I was assuming the crash meant the runtime version was missing or unsupported.

Hi @jaxon_r,

In normal installations, the Hexnode Agent installer handles the required .NET dependency. A crash with e0434352 does not always mean the supported .NET version is missing. It means a .NET exception occurred. If the Microsoft .NET Framework Repair Tool and reboot do not resolve it, the next useful place to check is the matching .NET Runtime event in Event Viewer. The stack trace from that entry is more specific than the generic KERNELBASE.dll Application Error entry.

Regards,
Sienna Carter
Hexnode UEM

That makes sense, I’ll check the Application log for the matching timestamp and use the stack trace to narrow it down.