When connecting a USB or ESATA drive to a windows 2008 server, windows pops up a message stating that a driver is needed. A usb drive has worked on this server in the past. It looks like Windows is pulling from the wrong volume.inf directory. The USB and ESATA drives work perfectly on another Windows 2008 server. Below is the info from the setupapi.dev text document. ndv: {Update Driver Software Wizard for STORAGE\VOLUME\1&19F7E59C&0&SIGNATURE12C2883OFFSET7E00LENGTH4A85AD8200} inf: Opened PNF: 'C:\Windows\INF\volume.inf' ([strings.0409] <src=drvstore>) inf: {SetupCopyOEMInf: C:\Windows\INF\volume.inf} 17:14:59.501 inf: Driver Store location: C:\Windows\System32\DriverStore\FileRepository\volume.inf_f6e0f9b0\volume.inf inf: Published Inf Path: C:\Windows\INF\volume.inf inf: Opened PNF: 'C:\Windows\INF\volume.inf' ([strings.0409] <src=drvstore>) inf: OEM source media location: C:\Windows\INF\ inf: {SetupCopyOEMInf exit (0x00000000)} 17:14:59.520 dvi: Searching for hardware ID(s): dvi: storage\volume inf: Opened PNF: 'C:\Windows\System32\DriverStore\FileRepository\volume.inf_f6e0f9b0\volume.inf' ([strings.0409] <src=drvstore>) dvi: Selected driver installs from section [volume_install] in 'c:\windows\system32\driverstore\filerepository\volume.inf_f6e0f9b0\volume.inf'. dvi: Class GUID of device changed to: {71a27cdd-812a-11d0-bec7-08002be2092f}. dvi: Set selected driver complete. dvi: {Plug and Play Service: Device Install for STORAGE\VOLUME\1&19F7E59C&0&SIGNATURE12C2883OFFSET7E00LENGTH4A85AD8200} ump: Creating Install Process: DrvInst.exe 17:14:59.529 ndv: Infpath=C:\Windows\INF\volume.inf ndv: DriverNodeName=volume.inf:MSFT.NTamd64:volume_install:6.0.6001.18000:storage\volume ndv: DriverStorepath=C:\Windows\System32\DriverStore\FileRepository\volume.inf_f6e0f9b0\volume.inf ndv: Building driver list from driver node strong name... dvi: Searching for hardware ID(s): dvi: storage\volume inf: Opened PNF: 'C:\Windows\System32\DriverStore\FileRepository\volume.inf_f6e0f9b0\volume.inf' ([strings.0409] <src=drvstore>) dvi: Selected driver installs from section [volume_install] in 'c:\windows\system32\driverstore\filerepository\volume.inf_f6e0f9b0\volume.inf'. dvi: Class GUID of device changed to: {71a27cdd-812a-11d0-bec7-08002be2092f}. dvi: Set selected driver complete. ndv: {Core Device Install} inf: Opened PNF: 'C:\Windows\INF\volume.inf' ([strings.0409] <src=drvstore>) pol: Device installation is subject to policy ndv: Class {71a27cdd-812a-11d0-bec7-08002be2092f} does not exist. dvi: {Installing Class} inf: Opened PNF: 'C:\Windows\System32\DriverStore\FileRepository\volume.inf_f6e0f9b0\volume.inf' ([strings.0409] <src=drvstore>) dvi: Installing device class: 'Volume' {71A27CDD-812A-11D0-BEC7-08002BE2092F}. !!! dvi: Could not locate section [ClassInstall32]. !!! dvi: Class: {71A27CDD-812A-11D0-BEC7-08002BE2092F}. Install failed. !!! dvi: Error 0xe0000101: The required section was not found in the INF. dvi: {Installing Class exit(0xe0000101)} ndv: Device install status=0xe0000101 ndv: Performing device install final cleanup... ! ndv: Queueing up error report since device installation failed... ndv: {Core Device Install - exit(0xe0000101)} ump: Server install process exited with code 0xe0000101 17:14:59.749 ump: {Plug and Play Service: Device Install exit(e0000101)} ndv: Device Install failed for new device...installing NULL driver. dvi: {Plug and Play Service: Device Install for STORAGE\VOLUME\1&19F7E59C&0&SIGNATURE12C2883OFFSET7E00LENGTH4A85AD8200} ump: Creating Install Process: DrvInst.exe 17:14:59.823 ! ndv: Installing NULL driver! dvi: Set selected driver complete. pol: Device installation is subject to policy dvi: {DIF_ALLOW_INSTALL} 17:14:59.833 dvi: No class installer for 'Unknown driver software package' dvi: No CoInstallers found dvi: Default installer: Enter 17:14:59.834 dvi: Default installer: Exit dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 17:14:59.834 dvi: {DIF_INSTALLDEVICE} 17:14:59.835 dvi: No class installer for 'Unknown driver software package' dvi: Default installer: Enter 17:14:59.835 ! dvi: Installing NULL driver! dvi: Writing common driver property settings. dvi: {Restarting Devices} 17:14:59.849 dvi: Restart: STORAGE\VOLUME\1&19F7E59C&0&SIGNATURE12C2883OFFSET7E00LENGTH4A85AD8200 dvi: Restart complete. dvi: {Restarting Devices exit} 17:14:59.899 dvi: Default installer: Exit dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 17:14:59.900 ump: Server install process exited with code 0x00000000 17:14:59.904 ump: {Plug and Play Service: Device Install exit(00000000)} ndv: {Update Driver Software Wizard exit(e0000101)} <<< Section end 2010/08/12 17:15:02.318 <<< [Exit status: FAILURE(0xe0000101)] Anyone seen this before and know of a fix. Thank you.

Hi, Have you tried to plug this problematic USB/eSaTa hard disk to another computer to see whether it works? Have you tried to plug other USB hard disk to this problem computer to see whether you get the same issue? How about to let it search the drivers if the system asked for drivers after you insert the USB/eSaTa hard disk to the problematic computer? Best Regards, Vincent Hu

Did you discover a fix to your problem. I am having a very similiar problem with my Windows 2008 Server. Every time I try to install a usb device that uses the windows generic volume driver it gives me an error. "The required section was not found in the INF." This happens for any usb storage device, such as a flash drive or external hard drive. Any Help would be appreciated Thanks

I'm having the same problem, after a p2v migration of windows server 2008 x64 without hyper-v. prior to the p2v conversion, I also had the same issue when plugging in a USB hard drive. I tried the external usb drive in other machines without a problem.Marcus Leone