Unable to get any compatible drivers for Windows 10 Enterprise LTSC

[faXcooL]

Hi,

I bought brand new HP 15-eh1021nm notebook, but it came without Windows so I installed Windows 10 Enterprise x64 LTSC edition, the one I used on my 7 year old HP. Anyways, this model it has some serious issues with drivers and I am not able to get them via "software and drivers" download page because this model isn't in the list. When I put SN I'm getting redirected to the page "15-eh1000 (2K4Y7AV)" which is not my model. The model I am using is "15-eh1021nm (5cd120sn12)". Maybe that's the reason I'm getting the drivers which aren't compatible. I tried all available drivers for three versions of Windows 10 x64, none of them work.

Please, help.

[Paul_Tikkanen]

Hi:

According to the product specs for your notebook...

HP Pavilion Laptop 15-eh1021nm Product Specifications | HP® Customer Support

You need this wifi driver...

https://ftp.hp.com/pub/softpaq/sp121001-121500/sp121426.exe

The rest of the drivers would be found under the 15-eh1000 support page.

I don't know anything about W10 Enterprise (how the build updates work), but if you are trying to install the drivers on an old version of W10 Ent from 2015- 2019, the drivers are too new to work on that old a build.

The drivers are designed to work on the newer builds of W10 Home and Pro (2004, 20H2).

[faXcooL · Accepted solution]

Unfortunately, it didn't work. But I managed to get it fixed in the meantime.

One of a few drivers that were successfully installed was bluetooth driver. I managed to establish a network connection via bluetooth between my phone and laptop by creating a hotspot (bluetooth tethering) and finally I was able to use Windows Update which helped me update all missing drivers, including wifi adapter. Now I'll create a backup with all installed drivers, it will be helpful in the future.

One interested thing though - HP assistant didn't detect any missing driver, even though there were more than 20 exclamation points in the device manager. My laptop was false detected as eh1000nm insted of eh1020nm, so that could have been an issue.

Thanks anyway, I appreciate your help.

[Paul_Tikkanen]

You're very welcome.