jhi_service.exe
Also called jhi_service, jhi, intel dal, dal host interface
Intel Dynamic Application Loader Host Interface (DAL / JHI) service. It lets host apps talk to Intel DAL applets. It is not a Microsoft OS host.
What you need to know
Intel DAL/JHI service, not a Microsoft OS host.
jhi_service.exe is Intel Dynamic Application Loader Host Interface Service. It is JHI, the host side of Intel DAL. It lives under Intel Management Engine Components, not System32 as a Windows inbox image. Ending it does not stop lsass or services.exe.
- Safe?
- Yes, under Intel ME / DAL
- Is it Windows?
- No. Intel DAL/JHI, not a Microsoft host
- Can I uninstall it?
- Only with the Intel ME package
What is jhi_service.exe?
jhi_service.exe is Intel DAL/JHI, not a Microsoft OS host. JHI is the Dynamic Application Loader Host Interface. Microsoft does not ship this filename as a Windows inbox binary.
What does it do?
It brokers sessions between Windows apps and Intel DAL applets in firmware. It does not host WMI providers. Intel ME WMI registration is a different helper.
Why is it running?
Intel ME / TXE / DAL components are installed, usually by the PC vendor. A machine without that package should not show a Microsoft-signed jhi_service in System32.
Is it safe?
Usually safe when Intel signed
An Intel-signed jhi_service under Management Engine Components\DAL is JHI. jhi_service.exe in Temp is not. This is still not a Windows inbox host.
A legitimate copy normally runs from:
C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL\jhi_service.exe
- TXE builds can use Intel\TXE Components\DAL
- Service: Intel Dynamic Application Loader Host Interface Service
- Not System32 Microsoft inbox
Can I end it?
DAL applet sessions can fail
Ending jhi_service.exe drops Host Interface sessions. Windows core processes keep running. Intel IPT or ME tools may complain until the service starts again.
Can I remove it?
Only with Intel ME software
Do not delete jhi_service.exe. Repair or uninstall Intel Management Engine / DAL from the PC vendor. Do not delete System32 files to "remove JHI."
Should it start with Windows?
The Intel DAL Host Interface service starts it. That is vendor install, not a Windows Startup Apps default.
Normal resource behavior
These are contextual labels, not universal averages.
- CPU
- Idle unless an app talks to a DAL applet
- Memory
- Small
- Disk
- Low
- Network
- None required for local JHI
File information
| Executable name | jhi_service.exe |
|---|---|
| Common legitimate path | C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL\jhi_service.exe |
| Publisher | Intel Corporation |
| Signature expectation | Signed by Intel Corporation |
Common problems
Filename mills call any Intel ME string malware
Path and Intel signature decide this one. A Microsoft System32 host will not be named jhi_service.exe.
ME tools fail after someone deleted DAL
Repair the Intel ME package from the OEM. A Windows component-store repair does not put JHI back.
Troubleshooting
Diagnose before you change anything destructive.
Repair Intel ME / DAL from the PC vendor
That is the supported path. Do not copy jhi_service.exe into System32. This is not a Microsoft inbox file.
Confirm the service name in services.msc
Intel Dynamic Application Loader Host Interface Service. If the image path is not under Intel\...\DAL, treat it as a different file.
Technical details
Technical details
| Image name | jhi_service.exe |
|---|---|
| Role | Intel DAL Host Interface (JHI) |
| Service | jhi_service |
Sources and verification
Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. How we research.
- Intel: DAL Host Interface Service · JHI is the DAL host interface, not a Microsoft process
- Intel: Management Engine · ME software packages include DAL components
- Foxhole process map · First-party samples on Windows PCs. Not a lab benchmark.
Was this article useful?
A yes or no is enough. Pick a reason if you want, or add a short note.
Thanks. That helps us improve this page.