Unattended driver installation xp

Don Johe Don Johe 2 2 gold badges 11 11 silver badges 23 23 bronze badges. Ganesh R. Dan Gifford Dan Gifford 8 8 silver badges 31 31 bronze badges. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually.

Related But it wants to know where the driver is. The new hardware wizard should just go to where the driver is and install it - unattended like. I really want a plug and play solution - even if a reboot is required.

They are on a dedicated network. Software, including application and the driver I wish to install can be downloaded via the network. With this arrangement, I am soooo close to having an unattended install. Plugging in the device causes the new hardware wizard to find the INF file but it does not know where to find the actual driver.

I have to manually install the driver by telling the dumb wizard where it is. The driver came with an install disk. On a normal PC the driver can be installed by running an installer. Nothing much appears to happen. But when the device gets plugged in, as if by magic, the install happens without further human imntervention. It appears that the new hardware wizard has been educated. And this is the only problem that we still have ATM. Well Said Erik! We have spent a LONG time with this. INF post install.

WHat do you think Erik? Might it work? In my case, my embedded device has no shell explorer ain't there at all and no systray! The non-techical user still has to answere a few prompts, sees that the darned embedded device is running Windows, and finally - viola - installed!

I did try Microsoft's DPinst. Version 1. It makes little difference but means that I have to download KB extra to my devices baud. Windows is a user-centric operating system. They were designed to fill a niche that Microsoft missed. They did not consider THIS problem because for all intents and purposes, their embedded systems are still user-centric. They need human operators to make them work with PNP devices. Commandline is out of the question.

This is a dedicated DirectX application embedded windows xp box that is broadly distributed. Now I have snapshots of before ans after. I'm pretty sure that's were everything is.

So comparing for differences should give me what I need to change. The registry part is easy. Put the differences in a script file and download them. Scenario: we have a device that's going to be given out to about or so users. I have hardware driver files, INF's etc. If the device isn't connected to the machine and you right click install on the inf or use a command like devcon, nothing gets installed I would like to have the drivers pre-installed or staged on the machine so that when the user plugs in the device it just automagically finds the correct driver without the user being presented with prompts to go to windows update or browsing to the driver files.

Has anybody done something like this? Thanks in advance. Asked 11 years ago views. Posted by: mchild 6 years ago. Comments: pnputil. Posted by: pramodp 11 years ago. HI, you can use DPinst. Posted by: aogilmor 11 years ago. I didn't see anything useful. I still get the same stupid prompts when I plug in the device. Suppresses the Device Installation Wizard and any dialogs popped-up by the operating system.

Accepts unsigned driver packages and packages with missing files. These packages won't install on the latest version of Windows. Only valid for Plug and Play drivers. Useful for l ocalization tests. Suppressing Wizard and OS pop ups. INFO: Driver package 'okiccdwdm. INFO: Installation did not occur because the hardware isn't currently present. INFO: No drivers installed.

Driver will be installed when p lugged in. OK i copied to same dir.