SYNACK Posted June 3, 2013 Posted June 3, 2013 I see that now, thanks, but hopefully this isn't the only thing to do here. With this I'd have to run it on all 300 machines before I tried to image them if I'm reading it correctly. Look through old drivers, intel has pulled this rubbish before and their first attempt at a fix was a driver that responded to the incorect pnp id even in windows pe, find out what the reported pnp id is before installing a driver that may mask the problem then do a text search in as many intel driver versions as you can find for that string. If the inf has it it should work. This depends on intel having taken the same shortcut when they screwed it up this time.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now