No official driver available > When windows version is not correct

[sushislicer]

Hello community forums,

EDIT: reformulated this minor issue.

I'm a junior developer and a power-user

I've found that an official HP driver downloaded from HP support performs a system check at opening.

As such it must be downloaded according to the windows version. last version is 1909.

Then because I'm a developer and Microsoft is what it is: I must have

* Docker

* WSL2

It was required to wipe the system because my country wide HP seller provided only W10 home.

Problem, if you want to install any HP driver it is no longer possible because one of these aforementioned features requires to run w10 insider 2004. Note that technically IT IS STILL THE SAME BUILD VERSION aka 19041. Only os version has changed.

I've solved my problem with a workaround to avoid relying on driver update.

Ok we can still install drivers manually if we really need to.

This windows version verification script is very annoying.

Besides: I cannot tell when running this W10 version who provides driver update... it might be MS that provides generic drivers. Or is it outdated drivers...

But then I've started to encounter weird issues that I didn't have on the OEM home installation of W10 180x

Perhaps Windows had installed the wrong drivers!

EDIT: side issues fixed due to external devices.

[WAWood]

@sushislicer 

Win10 2004 is an Insider Preview version -- and we do not support that.

[sushislicer]

Just to be clear: What do you mean by not supported?
What WE refers to?
HP or Community?

DO you have an idea of the driver status when it is not available like in my case.

I've installed W10 pro 1909 from scratch performed update and shortly after pushed for Insider for WSL2 feature.

Thanks