HP 3300 no USB after applying w10 image

[tinca492]

Hi

 

Not sure if this is right forum but....

 

I have been deploying custom W10 image via MDT to our PCs.

 

All works well apart from some 5 yr old HP dc-3300 desktop PCs. The USB connected keyboard and mouse work during the Win PE part of the deployment, but once the image is loaded they cease to work.

 

If I boot from USB based "vanilla" windows 10 installation media all is well

 

I actually used this machine as our reference image creator from a clean install of windows 10, after loading the applications etc I did the usual sysprep generalize OOBE which completed with no errors. captured the image and imported it into MDT as a custom image.

 

when I then started what was the reference pc the usual select region screen appears but USB connected keyboard and mouse not responsive.

 

I have subsequently loaded the image onto a number of other PCs including Lenovo and Dell without issues.

 

Any clues gratefully received.

[Steve21]

Have you checked between the image and PE drivers as to what's applying to that model? Normally it's when you're pushing another driver down that things like that happen as during install its using the PE ones, then defaults back to the "broke" ones etc.

 

Or aren't you deploying drivers at part of the install via MDT etc? (Just via the capture?)

 

Steve

[tinca492]

Many thanks for your prompt response

 

initially no drivers injected via MDT.... usb didnt work

 

Then imported model specific drivers from the hp website and injected them into image. MDT dialogue appears to confirm that they are being injected ... usb stil not working

 

Ran the pc up on usb install media for vanilla win10, installed fine and mouse etc still working. Accessed Device Manager to note the driver it was using..Intel 6 series/c200

 

Went to Intel site to download, found relevant driver but Intel were very clear stating that it didnot include USB drivers so wouldnt cure any usb related issues.

 

have just sysprepped it after a fresh install of win 10, erebooted it and everything fine!

 

I am wondering if one of the routine MS Updates that I applied has caused the issue

 

As the current customised image works on all other machines so far, I think I will leave these desktops til after the summer