Windows Client TechCenter >
Windows 7 Forums
>
Windows 7 Hardware Compatibility
>
Alps touchpad in Vostro 1520
Alps touchpad in Vostro 1520
- Recently insstalled Windows 7 RC 1 on a brand new Vostro 1520, and the Alps touchpad works intermittent. The device manager shows the message This device cannot start. (Code 10). And I'm using the last Apls device driver I found. Ver. 7.2.303.107 Date 7.2.303.107. Some times it starts perfectly some times not. Any idea?
Answers
Hi,
Thanks for posting in Microsoft TechNet Forum.
While encountering error code 10, we usually update the device driver to narrow down this issue. Based on my research, you can download updated version v7.4.102.102,A02 from Dell's Site.
Note: we provide this link for downloading drivers, Microsoft doesn't control and guarantee any change in this website.
Best Regards.
Dale Qiao
- Marked As Answer byRonnie VernonMVP, ModeratorMonday, August 10, 2009 8:32 AM
All Replies
Hi,
Thanks for posting in Microsoft TechNet Forum.
While encountering error code 10, we usually update the device driver to narrow down this issue. Based on my research, you can download updated version v7.4.102.102,A02 from Dell's Site.
Note: we provide this link for downloading drivers, Microsoft doesn't control and guarantee any change in this website.
Best Regards.
Dale Qiao
- Marked As Answer byRonnie VernonMVP, ModeratorMonday, August 10, 2009 8:32 AM
- I have the exact same problem.
I am running driver version 7.104.102.102 which is dated 3/6/09 (according to the driver properties in windows)
The driver installed is listed on Dell's site as 7.4.102.102 and dated 4/27/09
I am running 64bit Windows 7 - I'm experiencing this as well. I'm running the driver linked to on Dell's site, 32bit. This is quite frustrating...
- What exactly is the problem you guys are facing?
The driver package says that it's good for 32-bit or 64-bit.
I wouldn't worry about the dates not matching up if the version information does. The date displayed in device manager is the date used in the installer file. The date on the website is probably the date the package was posted for download.
Want to know if your hardware will work on Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Microsoft Logo'd Hardware List** - This is what shows up in "Device Status" when I run properties in Device Manager.
"This device cannot start. (Code 10)"
The touchpad doesn't respond. - Please run that installer package.
After you've run it, open this file: c:\Windows\inf\setupapi.dev.log. Please let me know if you got any error messages when you ran it.
Scroll down to the bottom and look for something that has a section start time close to when you tried to install this driver package.
Copy everything from that point to the end of the file, and paste it in a reply here. Hopefully that info will help me understand what's happening on your machine.
Another thing you can try: Next to the clock at the bottom of the screen, there's a flag. This is the Action Center in Windows 7. Please click on that and see if it provides you with a link to a different driver package for this device.
Thanks,
Mark
Want to know if your hardware will work on Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Microsoft Logo'd Hardware List** - Action center doesn't give me anything. Here's what the log shows:
[Boot Session: 2009/08/25 02:31:50.375] >>> [Device Install (UpdateDriverForPlugAndPlayDevices) - ACPI\SYN070B] >>> Section start 2009/08/25 02:38:20.221 cmd: C:\dell\drivers\R213942\\Vi32\\DPInst.exe dvi: Set selected driver complete. dvi: {Build Driver List} 02:38:20.267 dvi: Searching for hardware ID(s): dvi: acpi\syn070b dvi: *syn070b dvi: Searching for compatible ID(s): dvi: *syn0700 dvi: *syn0002 dvi: *pnp0f13 cpy: Policy is set to make all digital signatures equal. dvi: Processing a single INF: 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' inf: Opened PNF: 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' ([strings]) dvi: Created Driver Node: dvi: HardwareID - *PNP0F13 dvi: InfName - c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf dvi: DevDesc - Dell Touchpad dvi: DrvDesc - Dell Touchpad dvi: Provider - Alps dvi: Mfg - Alps Electric dvi: ModelsSec - CompanyMfg dvi: InstallSec - MouFilter_Inst dvi: ActualSec - MouFilter_Inst.NTx86 dvi: Rank - 0x00ff2002 dvi: Signer - Microsoft Windows Hardware Compatibility Publisher dvi: Signer Score - WHQL dvi: DrvDate - 03/06/2009 dvi: Version - 7.4.102.102 dvi: {Build Driver List - exit(0x00000000)} 02:38:20.283 dvi: {DIF_SELECTBESTCOMPATDRV} 02:38:20.283 dvi: Using exported function 'MouseClassInstaller' in module 'C:\Windows\system32\SysClass.Dll'. dvi: Class installer == SysClass.Dll,MouseClassInstaller dvi: Using exported function 'CriticalDeviceCoInstaller' in module 'C:\Windows\system32\SysClass.Dll'. dvi: CoInstaller 1 == SysClass.Dll,CriticalDeviceCoInstaller dvi: Using exported function 'WdfCoInstaller' in module 'C:\Windows\system32\WdfCoInstaller01005.dll'. dvi: CoInstaller 2 == WdfCoInstaller01005.dll,WdfCoInstaller dvi: CoInstaller 1: Enter 02:38:20.423 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 02:38:20.439 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 02:38:20.439 dvi: Class installer: Exit dvi: Default installer: Enter 02:38:20.439 dvi: {Select Best Driver} dvi: Selected driver installs from section [MouFilter_Inst] in 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf'. dvi: Class GUID of device remains: {4d36e96f-e325-11ce-bfc1-08002be10318}. dvi: Set selected driver complete. dvi: Selected: dvi: Description - [Dell Touchpad] dvi: InfFile - [c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf] dvi: Section - [MouFilter_Inst] dvi: Signer - [Microsoft Windows Hardware Compatibility Publisher] dvi: Rank - [0x00ff2002] dvi: {Select Best Driver - exit(0x00000000)} dvi: Default installer: Exit dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 02:38:20.439 inf: {SetupCopyOEMInf: C:\Windows\INF\oem1.inf} 02:38:20.455 inf: Driver Store location: C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf inf: Published Inf Path: C:\Windows\INF\oem1.inf inf: Opened PNF: 'C:\Windows\INF\oem1.inf' ([strings]) inf: Installing catalog Apfiltr.cat as: oem1.CAT ! inf: Failed to install catalog - error ignored ! inf: Error 2: The system cannot find the file specified. inf: OEM source media location: C:\Windows\INF\ inf: {SetupCopyOEMInf exit (0x00000000)} 02:38:20.642 dvi: Searching for hardware ID(s): dvi: acpi\syn070b dvi: *syn070b dvi: Searching for compatible ID(s): dvi: *syn0700 dvi: *syn0002 dvi: *pnp0f13 inf: Opened PNF: 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' ([strings]) dvi: Selected driver installs from section [MouFilter_Inst] in 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf'. dvi: Class GUID of device remains: {4d36e96f-e325-11ce-bfc1-08002be10318}. dvi: Set selected driver complete. dvi: {Plug and Play Service: Device Install for ACPI\SYN070B\4&34E3DF88&0} ump: Creating Install Process: DrvInst.exe 02:38:20.673 ndv: Infpath=C:\Windows\INF\oem1.inf ndv: DriverNodeName=apfiltr.inf:CompanyMfg:MouFilter_Inst:7.4.102.102:*pnp0f13:*pnp0f03:*pnp0f0e:*pnp0f0b:*pnp0f12 ndv: DriverStorepath=C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf ndv: Building driver list from driver node strong name... dvi: Searching for hardware ID(s): dvi: acpi\syn070b dvi: *syn070b dvi: Searching for compatible ID(s): dvi: *syn0700 dvi: *syn0002 dvi: *pnp0f13 inf: Opened PNF: 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' ([strings]) dvi: Selected driver installs from section [MouFilter_Inst] in 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf'. dvi: Class GUID of device remains: {4d36e96f-e325-11ce-bfc1-08002be10318}. dvi: Set selected driver complete. ndv: {Core Device Install} inf: Opened PNF: 'C:\Windows\INF\oem1.inf' ([strings]) dvi: {DIF_ALLOW_INSTALL} 02:38:21.063 dvi: Using exported function 'MouseClassInstaller' in module 'C:\Windows\system32\SysClass.Dll'. dvi: Class installer == SysClass.Dll,MouseClassInstaller dvi: Using exported function 'CriticalDeviceCoInstaller' in module 'C:\Windows\system32\SysClass.Dll'. dvi: CoInstaller 1 == SysClass.Dll,CriticalDeviceCoInstaller dvi: Using exported function 'WdfCoInstaller' in module 'C:\Windows\system32\WdfCoInstaller01005.dll'. dvi: CoInstaller 2 == WdfCoInstaller01005.dll,WdfCoInstaller dvi: CoInstaller 1: Enter 02:38:21.079 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 02:38:21.079 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 02:38:21.079 inf: Opened PNF: 'C:\Windows\INF\oem1.inf' ([strings]) inf: Opened PNF: 'C:\Windows\INF\oem1.inf' ([strings]) dvi: Class installer: Exit dvi: {DIF_ALLOW_INSTALL - exit(0x00000000)} 02:38:21.079 ndv: Installing files... dvi: {DIF_INSTALLDEVICEFILES} 02:38:21.110 dvi: CoInstaller 1: Enter 02:38:21.110 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 02:38:21.110 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 02:38:21.110 dvi: Class installer: Exit dvi: Default installer: Enter 02:38:21.110 dvi: {Install FILES} inf: Opened PNF: 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' ([strings]) inf: Opened PNF: 'C:\Windows\INF\msmouse.inf' ([strings.0409]) inf: {Install Inf Section [MouFilter_Inst.NTx86]} inf: CopyFiles=MouFilter_CopyFiles,MouFilter_CopyFilesDll,MouFilter_CopyFilesHome (apfiltr.inf line 42) cpy: Open PnpLockdownPolicy: Err=2. This is OK. Use LockDownPolicyDefault flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceSection: [sourcedisksfiles] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: SourceFilename - 'Apfiltr.sys' flq: TargetDirectory- 'C:\Windows\system32\DRIVERS' flq: TargetFilename - 'Apfiltr.sys' flq: SourceDesc - 'Alps Touch Pad Filter Driver for Windows 2000/XP/Vista Setup Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceSection: [sourcedisksfiles] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: SourceFilename - 'Vxdif.dll' flq: TargetDirectory- 'C:\Windows\system32' flq: TargetFilename - 'Vxdif.dll' flq: SourceDesc - 'Alps Touch Pad Filter Driver for Windows 2000/XP/Vista Setup Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceSection: [sourcedisksfiles] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: SourceFilename - 'Apoint.exe' flq: TargetDirectory- 'C:\Program Files\DellTPad' flq: TargetFilename - 'Apoint.exe' flq: SourceDesc - 'Alps Touch Pad Filter Driver for Windows 2000/XP/Vista Setup Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceSection: [sourcedisksfiles] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: SourceFilename - 'ApntEx.exe' flq: TargetDirectory- 'C:\Program Files\DellTPad' flq: TargetFilename - 'ApntEx.exe' flq: SourceDesc - 'Alps Touch Pad Filter Driver for Windows 2000/XP/Vista Setup Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceSection: [sourcedisksfiles] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: SourceFilename - 'Apoint.dll' flq: TargetDirectory- 'C:\Program Files\DellTPad' flq: TargetFilename - 'Apoint.dll' flq: SourceDesc - 'Alps Touch Pad Filter Driver for Windows 2000/XP/Vista Setup Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceSection: [sourcedisksfiles] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: SourceFilename - 'Elprop.dll' flq: TargetDirectory- 'C:\Program Files\DellTPad' flq: TargetFilename - 'Elprop.dll' flq: SourceDesc - 'Alps Touch Pad Filter Driver for Windows 2000/XP/Vista Setup Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceSection: [sourcedisksfiles] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: SourceFilename - 'EzAuto.dll' flq: TargetDirectory- 'C:\Program Files\DellTPad' flq: TargetFilename - 'EzAuto.dll' flq: SourceDesc - 'Alps Touch Pad Filter Driver for Windows 2000/XP/Vista Setup Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceSection: [sourcedisksfiles] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: SourceFilename - 'Uninstap.exe' flq: TargetDirectory- 'C:\Program Files\DellTPad' flq: TargetFilename - 'Uninstap.exe' flq: SourceDesc - 'Alps Touch Pad Filter Driver for Windows 2000/XP/Vista Setup Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceSection: [sourcedisksfiles] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: SourceFilename - 'ApInst.dll' flq: TargetDirectory- 'C:\Program Files\DellTPad' flq: TargetFilename - 'ApInst.dll' flq: SourceDesc - 'Alps Touch Pad Filter Driver for Windows 2000/XP/Vista Setup Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceSection: [sourcedisksfiles] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: SourceFilename - 'hidfind.exe' flq: TargetDirectory- 'C:\Program Files\DellTPad' flq: TargetFilename - 'hidfind.exe' flq: SourceDesc - 'Alps Touch Pad Filter Driver for Windows 2000/XP/Vista Setup Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceSection: [sourcedisksfiles] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: SourceFilename - 'ApMsgFwd.exe' flq: TargetDirectory- 'C:\Program Files\DellTPad' flq: TargetFilename - 'ApMsgFwd.exe' flq: SourceDesc - 'Alps Touch Pad Filter Driver for Windows 2000/XP/Vista Setup Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceSection: [sourcedisksfiles] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: SourceFilename - 'ApMouCpl.dll' flq: TargetDirectory- 'C:\Program Files\DellTPad' flq: TargetFilename - 'ApMouCpl.dll' flq: SourceDesc - 'Alps Touch Pad Filter Driver for Windows 2000/XP/Vista Setup Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceSection: [sourcedisksfiles] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: SourceFilename - 'DellTPad.exe' flq: TargetDirectory- 'C:\Program Files\DellTPad' flq: TargetFilename - 'DellTPad.exe' flq: SourceDesc - 'Alps Touch Pad Filter Driver for Windows 2000/XP/Vista Setup Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: {FILE_QUEUE_COPY exit(0x00000000)} inf: {Install Inf Section [MouFilter_Inst.NTx86] exit (0x00000000)} inf: {Install Inf Section [PS2_Inst]} inf: CopyFiles=PS2_CopyFiles,mouclass_CopyFiles (msmouse.inf line 315) flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceInf: 'C:\Windows\INF\msmouse.inf' flq: SourceSection: [sourcedisksfiles] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\msmouse.inf_x86_neutral_b65ef379c8c62294' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x01000000 flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x01000000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\msmouse.inf_x86_neutral_b65ef379c8c62294' flq: SourceFilename - 'i8042prt.sys' flq: TargetDirectory- 'C:\Windows\system32\DRIVERS' flq: TargetFilename - 'i8042prt.sys' flq: SourceDesc - 'windows cd' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceInf: 'C:\Windows\INF\msmouse.inf' flq: SourceSection: [sourcedisksfiles] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\msmouse.inf_x86_neutral_b65ef379c8c62294' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x01000000 flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x01000000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\msmouse.inf_x86_neutral_b65ef379c8c62294' flq: SourceFilename - 'mouclass.sys' flq: TargetDirectory- 'C:\Windows\system32\DRIVERS' flq: TargetFilename - 'mouclass.sys' flq: SourceDesc - 'windows cd' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: {FILE_QUEUE_COPY exit(0x00000000)} inf: {Install Inf Section [PS2_Inst] exit (0x00000000)} dvi: Processing co-installer registration section [MouFilter_Inst.NTx86.CoInstallers]. inf: {Install Inf Section [MouFilter_Inst.NTx86.CoInstallers]} inf: CopyFiles=MouFilter_CopyFiles_CoInstaller (apfiltr.inf line 60) flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' flq: SourceSection: [sourcedisksfiles] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756' flq: SourceFilename - 'WdfCoInstaller01005.dll' flq: TargetDirectory- 'C:\Windows\system32' flq: TargetFilename - 'WdfCoInstaller01005.dll' flq: SourceDesc - 'Alps Touch Pad Filter Driver for Windows 2000/XP/Vista Setup Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: {FILE_QUEUE_COPY exit(0x00000000)} inf: {Install Inf Section [MouFilter_Inst.NTx86.CoInstallers] exit (0x00000000)} dvi: Co-installers registered. dvi: {Install INTERFACES} dvi: Installing section [MouFilter_Inst.NTx86.Interfaces] dvi: {Install INTERFACES exit 00000000} dvi: {Install FILES exit (0x00000000)} dvi: Default installer: Exit dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 02:38:21.203 ndv: Pruning file queue... dvi: {_SCAN_FILE_QUEUE} flq: ScanQ flags=620 flq: SPQ_SCAN_PRUNE_COPY_QUEUE flq: SPQ_SCAN_FILE_COMPARISON flq: SPQ_SCAN_ACTIVATE_DRP flq: ScanQ number of copy nodes=16 flq: File 'C:\Windows\system32\DRIVERS\Apfiltr.sys' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT'. cpy: DrpSetRegFileProt 'C:\Windows\system32\DRIVERS\Apfiltr.sys' Status=0 Class=OEM Legacy flq: File 'C:\Windows\system32\Vxdif.dll' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT'. cpy: DrpSetRegFileProt 'C:\Windows\system32\Vxdif.dll' Status=0 Class=OEM Legacy flq: File 'C:\Program Files\DellTPad\Apoint.exe' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT'. cpy: DrpSetRegFileProt 'C:\Program Files\DellTPad\Apoint.exe' Status=0 Class=OEM Legacy flq: File 'C:\Program Files\DellTPad\ApntEx.exe' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT'. cpy: DrpSetRegFileProt 'C:\Program Files\DellTPad\ApntEx.exe' Status=0 Class=OEM Legacy flq: File 'C:\Program Files\DellTPad\Apoint.dll' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT'. cpy: DrpSetRegFileProt 'C:\Program Files\DellTPad\Apoint.dll' Status=0 Class=OEM Legacy flq: File 'C:\Program Files\DellTPad\Elprop.dll' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT'. cpy: DrpSetRegFileProt 'C:\Program Files\DellTPad\Elprop.dll' Status=0 Class=OEM Legacy flq: File 'C:\Program Files\DellTPad\EzAuto.dll' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT'. cpy: DrpSetRegFileProt 'C:\Program Files\DellTPad\EzAuto.dll' Status=0 Class=OEM Legacy flq: File 'C:\Program Files\DellTPad\Uninstap.exe' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT'. cpy: DrpSetRegFileProt 'C:\Program Files\DellTPad\Uninstap.exe' Status=0 Class=OEM Legacy flq: File 'C:\Program Files\DellTPad\ApInst.dll' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT'. cpy: DrpSetRegFileProt 'C:\Program Files\DellTPad\ApInst.dll' Status=0 Class=OEM Legacy flq: File 'C:\Program Files\DellTPad\hidfind.exe' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT'. cpy: DrpSetRegFileProt 'C:\Program Files\DellTPad\hidfind.exe' Status=0 Class=OEM Legacy flq: File 'C:\Program Files\DellTPad\ApMsgFwd.exe' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT'. cpy: DrpSetRegFileProt 'C:\Program Files\DellTPad\ApMsgFwd.exe' Status=0 Class=OEM Legacy flq: File 'C:\Program Files\DellTPad\ApMouCpl.dll' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT'. cpy: DrpSetRegFileProt 'C:\Program Files\DellTPad\ApMouCpl.dll' Status=0 Class=OEM Legacy flq: File 'C:\Program Files\DellTPad\DellTPad.exe' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT'. cpy: DrpSetRegFileProt 'C:\Program Files\DellTPad\DellTPad.exe' Status=0 Class=OEM Legacy flq: File 'C:\Windows\system32\DRIVERS\i8042prt.sys' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-Common-Drivers-Package~31bf3856ad364e35~x86~~6.1.7100.0.cat'. cpy: DrpSetRegFileProt 'C:\Windows\system32\DRIVERS\i8042prt.sys' Status=0 Class=Inbox Windows protected flq: File 'C:\Windows\system32\DRIVERS\mouclass.sys' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-Common-Drivers-Package~31bf3856ad364e35~x86~~6.1.7100.0.cat'. cpy: DrpSetRegFileProt 'C:\Windows\system32\DRIVERS\mouclass.sys' Status=0 Class=Inbox Windows protected flq: File 'C:\Windows\system32\WdfCoInstaller01005.dll' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem7.CAT'. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT'. cpy: DrpSetRegFileProt 'C:\Windows\system32\WdfCoInstaller01005.dll' Status=0 Class=OEM Legacy flq: ScanQ action=200 DoPruning=32 flq: ScanQ end Validity flags=620 CopyNodes=0 dvi: {_SCAN_FILE_QUEUE exit(0, 0x00000000)} ndv: Committing file queue... flq: {_commit_file_queue} flq: CommitQ DelNodes=0 RenNodes=0 CopyNodes=0 flq: CommitQ early exit: No nodes are queued flq: {_commit_file_queue exit OK} ndv: Registering CoInstallers... dvi: {DIF_REGISTER_COINSTALLERS} 02:38:25.649 dvi: CoInstaller 1: Enter 02:38:25.649 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 02:38:25.649 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 02:38:25.649 dvi: Class installer: Exit dvi: Default installer: Enter 02:38:25.649 inf: Opened PNF: 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' ([strings]) inf: {Install Inf Section [MouFilter_Inst.NTx86.CoInstallers]} inf: AddReg=MouFilter_CoInstaller_AddReg (apfiltr.inf line 59) inf: {Install Inf Section [MouFilter_Inst.NTx86.CoInstallers] exit (0x00000000)} dvi: {DIF_DESTROYPRIVATEDATA} 02:38:25.649 dvi: CoInstaller 1: Enter 02:38:25.649 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 02:38:25.649 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 02:38:25.649 dvi: Class installer: Exit dvi: Default installer: Enter 02:38:25.649 dvi: Default installer: Exit dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 02:38:25.649 dvi: Co-installers registered. dvi: Default installer: Exit dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 02:38:25.649 ndv: Installing interfaces... dvi: {DIF_INSTALLINTERFACES} 02:38:25.649 dvi: Using exported function 'CriticalDeviceCoInstaller' in module 'C:\Windows\system32\SysClass.Dll'. dvi: CoInstaller 1 == SysClass.Dll,CriticalDeviceCoInstaller dvi: Using exported function 'WdfCoInstaller' in module 'C:\Windows\system32\WdfCoInstaller01005.dll'. dvi: CoInstaller 2 == WdfCoInstaller01005.dll,WdfCoInstaller dvi: CoInstaller 1: Enter 02:38:25.665 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 02:38:25.665 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 02:38:25.665 dvi: Class installer: Exit dvi: Default installer: Enter 02:38:25.665 dvi: {Install INTERFACES} inf: Opened PNF: 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' ([strings]) dvi: Installing section [MouFilter_Inst.NTx86.Interfaces] dvi: {Install INTERFACES exit 00000000} dvi: Default installer: Exit dvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 02:38:25.665 ndv: Installing device... dvi: {DIF_INSTALLDEVICE} 02:38:25.665 dvi: CoInstaller 1: Enter 02:38:25.665 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 02:38:25.665 inf: Opened PNF: 'C:\Windows\INF\oem1.inf' ([strings]) dvi: CoInstaller 2: Exit dvi: Class installer: Enter 02:38:25.899 dvi: {Install DEVICE} inf: Opened PNF: 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf' ([strings]) inf: Opened PNF: 'C:\Windows\INF\msmouse.inf' ([strings.0409]) dvi: Processing Registry/Property directives... inf: {Install Inf Section [MouFilter_Inst.NTx86]} inf: AddReg=MouFilter_Inst.AddReg,DriverInfoAddReg (apfiltr.inf line 43) inf: {Install Inf Section [MouFilter_Inst.NTx86] exit (0x00000000)} inf: {Install Inf Section [PS2_Inst]} inf: AddReg=PS2_Inst.AddReg (msmouse.inf line 316) inf: {Install Inf Section [PS2_Inst] exit (0x00000000)} inf: {Install Inf Section [MouFilter_Inst.NTx86.Hw]} inf: AddReg=MouFilter_Inst.HW.AddReg,MouFilter_Inst.AddReg (apfiltr.inf line 51) inf: AddReg=PS2_Inst.HW.AddReg (msmouse.inf line 325) inf: {Install Inf Section [MouFilter_Inst.NTx86.Hw] exit (0x00000000)} dvi: {Writing Device Properties} dvi: Provider name=Alps dvi: DriverDate 03/06/2009 dvi: DriverVersion=7.4.102.102 dvi: Class name=Mouse dvi: Manufacturer=Alps Electric dvi: Matching DeviceID=*pnp0f13 dvi: Strong Name=oem1.inf:CompanyMfg:MouFilter_Inst:7.4.102.102:*pnp0f13:*pnp0f03:*pnp0f0e:*pnp0f0b:*pnp0f12 dvi: {Writing Device Properties - Complete} inf: {Install Inf Section [MouFilter_Inst.NTx86.Services]} inf: AddService=ApfiltrService,,filter_Service_Inst (apfiltr.inf line 46) inf: ServiceType=1 (apfiltr.inf line 407) inf: StartType=3 (apfiltr.inf line 408) inf: ErrorControl=0 (apfiltr.inf line 409) inf: ServiceBinary=C:\Windows\system32\DRIVERS\Apfiltr.sys (apfiltr.inf line 411) inf: DisplayName="Alps Touch Pad Filter Driver for Windows 2000/XP/Vista" (apfiltr.inf line 406) inf: LoadOrderGroup="Pointer Port" (apfiltr.inf line 410) dvi: Add Service: Modified existing service 'ApfiltrService'. inf: {Install Inf Section [MouFilter_Inst.NTx86.Services] exit(0x00000000)} inf: {Install Inf Section [PS2_Inst.Services]} inf: AddService=i8042prt,0x00000002,i8042prt_Service_Inst,i8042prt_EventLog_Inst (msmouse.inf line 347) inf: ServiceType=1 (msmouse.inf line 365) inf: StartType=3 (msmouse.inf line 366) inf: ErrorControl=1 (msmouse.inf line 367) inf: ServiceBinary=C:\Windows\system32\DRIVERS\i8042prt.sys (msmouse.inf line 368) inf: DisplayName="i8042 Keyboard and PS/2 Mouse Port Driver" (msmouse.inf line 364) inf: LoadOrderGroup="Keyboard Port" (msmouse.inf line 369) dvi: Add Service: Modified existing service 'i8042prt'. inf: AddReg=i8042prt_EventLog_AddReg (msmouse.inf line 372) inf: AddService=mouclass,,mouclass_Service_Inst,mouclass_EventLog_Inst (msmouse.inf line 348) inf: ServiceType=1 (msmouse.inf line 260) inf: StartType=3 (msmouse.inf line 261) inf: ErrorControl=1 (msmouse.inf line 262) inf: ServiceBinary=C:\Windows\system32\DRIVERS\mouclass.sys (msmouse.inf line 263) inf: DisplayName="Mouse Class Driver" (msmouse.inf line 259) inf: LoadOrderGroup="Pointer Class" (msmouse.inf line 264) dvi: Add Service: Modified existing service 'mouclass'. inf: AddReg=mouclass_EventLog_AddReg (msmouse.inf line 267) inf: {Install Inf Section [PS2_Inst.Services] exit(0x00000000)} dvi: Updated reflected section names for: oem1.inf dvi: {Install DEVICE exit (0x00000000)} dvi: Writing common driver property settings. dvi: DriverDescription=Dell Touchpad dvi: DeviceDisplayName=Dell Touchpad dvi: Install Device: Restarting device. 02:38:26.851 dvi: Install Device: Restarting device completed. 02:38:27.053 !!! dvi: Device not started: Device has problem: 0x0a: CM_PROB_FAILED_START. inf: Opened PNF: 'C:\Windows\INF\oem1.inf' ([strings]) dvi: Class installer: Exit dvi: CoInstaller 2: Enter (Post Processing) 02:38:27.069 dvi: CoInstaller 2: Exit (Post Processing) dvi: CoInstaller 1: Enter (Post Processing) 02:38:27.724 dvi: CoInstaller 1: Exit (Post Processing) dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 02:38:27.724 dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 02:38:27.724 dvi: CoInstaller 1: Enter 02:38:27.724 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 02:38:27.724 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 02:38:27.724 dvi: Class installer: Exit dvi: Default installer: Enter 02:38:27.724 dvi: Default installer: Exit dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 02:38:27.724 ndv: Device install status=0x00000000 ndv: Performing device install final cleanup... ! ndv: Queueing up error report since device has a PnP problem... ndv: {Core Device Install - exit(0x00000000)} dvi: {DIF_DESTROYPRIVATEDATA} 02:38:27.740 dvi: CoInstaller 1: Enter 02:38:27.740 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 02:38:27.740 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 02:38:27.740 dvi: Class installer: Exit dvi: Default installer: Enter 02:38:27.740 dvi: Default installer: Exit dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 02:38:27.740 ump: Server install process exited with code 0x00000000 02:38:27.740 ump: {Plug and Play Service: Device Install exit(00000000)} dvi: {DIF_DESTROYPRIVATEDATA} 02:38:27.740 dvi: CoInstaller 1: Enter 02:38:27.740 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 02:38:27.740 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 02:38:27.740 dvi: Class installer: Exit dvi: Default installer: Enter 02:38:27.740 dvi: Default installer: Exit dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 02:38:27.755 dvi: {Build Driver List} 02:38:27.755 ! dvi: Driver list already built dvi: {Build Driver List - exit(0x00000000)} 02:38:27.755 dvi: {DIF_SELECTBESTCOMPATDRV} 02:38:27.755 dvi: Using exported function 'MouseClassInstaller' in module 'C:\Windows\system32\SysClass.Dll'. dvi: Class installer == SysClass.Dll,MouseClassInstaller dvi: Using exported function 'CriticalDeviceCoInstaller' in module 'C:\Windows\system32\SysClass.Dll'. dvi: CoInstaller 1 == SysClass.Dll,CriticalDeviceCoInstaller dvi: Using exported function 'WdfCoInstaller' in module 'C:\Windows\system32\WdfCoInstaller01005.dll'. dvi: CoInstaller 2 == WdfCoInstaller01005.dll,WdfCoInstaller dvi: CoInstaller 1: Enter 02:38:27.755 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 02:38:27.755 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 02:38:27.755 dvi: {Build Driver List} 02:38:27.755 ! dvi: Driver list already built dvi: {Build Driver List - exit(0x00000000)} 02:38:27.755 dvi: {Select Best Driver} dvi: Selected driver installs from section [MouFilter_Inst] in 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf'. dvi: Class GUID of device remains: {4d36e96f-e325-11ce-bfc1-08002be10318}. dvi: Set selected driver complete. dvi: Selected: dvi: Description - [Dell Touchpad] dvi: InfFile - [c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf] dvi: Section - [MouFilter_Inst] dvi: Signer - [Microsoft Windows Hardware Compatibility Publisher] dvi: Rank - [0x00ff2002] dvi: {Select Best Driver - exit(0x00000000)} inf: Opened PNF: 'C:\Windows\INF\oem1.inf' ([strings]) dvi: Class installer: Exit dvi: Default installer: Enter 02:38:27.771 dvi: {Select Best Driver} dvi: Selected driver installs from section [MouFilter_Inst] in 'c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf'. dvi: Class GUID of device remains: {4d36e96f-e325-11ce-bfc1-08002be10318}. dvi: Set selected driver complete. dvi: Selected: dvi: Description - [Dell Touchpad] dvi: InfFile - [c:\windows\system32\driverstore\filerepository\apfiltr.inf_x86_neutral_35c3992d3b3f1756\apfiltr.inf] dvi: Section - [MouFilter_Inst] dvi: Signer - [Microsoft Windows Hardware Compatibility Publisher] dvi: Rank - [0x00ff2002] dvi: {Select Best Driver - exit(0x00000000)} dvi: Default installer: Exit dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 02:38:27.771 dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 02:38:27.771 dvi: CoInstaller 1: Enter 02:38:27.771 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 02:38:27.771 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 02:38:27.771 dvi: Class installer: Exit dvi: Default installer: Enter 02:38:27.771 dvi: Default installer: Exit dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 02:38:27.771 dvi: {DIF_DESTROYPRIVATEDATA} 02:38:27.787 dvi: CoInstaller 1: Enter 02:38:27.787 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 02:38:27.787 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 02:38:27.787 dvi: Class installer: Exit dvi: Default installer: Enter 02:38:27.787 dvi: Default installer: Exit dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 02:38:27.787 <<< Section end 2009/08/25 02:38:27.787 <<< [Exit status: SUCCESS]
- Thanks jewbles. I'll post here if I can figure anything out from that log info.
Want to know if your hardware will work on Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Microsoft Logo'd Hardware List** - having any luck?
- Nothing yet, sorry.
Want to know if your hardware will work on Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Microsoft Logo'd Hardware List** - Maybe this will help. Something went wacky with my video driver (Nvidia 9300M GS) and the computer restarted at 640x480 resolution. I reinstalled the driver package from Nvidia. This fixed both the video issue and the touchpad. Some sort of conflict between the two?
Thanks for the update jewbles. Do you have a Dell Vostro 1520, or a different laptop?
Want to know if your hardware will work on Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Microsoft Logo'd Hardware List**- I am having the same issue as the above. I'm dual booting Vista home basic 32bit with win 7 RC build 7100 32 bit on a Dell Vostro 1520 with Intel GMA X3100 with latest windows 7 drivers (but issue was still present with older drivers.) Almost every time I boot into windows 7 the screen is either black or the default graphics driver is loaded and device manager shows error code 37. Along with this, my touchpad with latest ALPS driver 7.4.102.102 gives me error code 10 and won't start. The 2 seem to always happen together. Either they both work, or they both won't start. To fix this I either have to use a restore point, or sometimes booting into safemode or vista will work but I might have to restart up to 5 or 6 times before win7 will load properly.
- yes, it's the vostro 1520
- I have win 7 pro installed on a new vostro 1320 and ran into something similar with the alps touchpad: windows update wants you to update to a "synaptics" driver. If you update to this EVEN ONCE it will eternally mess up everything- not even uninstalling the driver will help (BSOD every other startup). Downloading dell's alps driver under the win7 drivers works though- as long as you have not installed the synaptics driver. Remember never install the synaptics driver period. Why it's even in windows update I have no idea...
- I am pretty sure I installed the synaptics driver at one point and all it did was take away my scrolling ability. I believe I successfully went back to ALPS. This MIGHT have been in vista though so better safe than sorry if what cococo says is true.
- Did anyone try this on the RTM version. I don't want to reinstall if I am going to have the same problem with that version as well.
- Tried this on Vostro 1320 (GM45 graphics, Bios A03) with 7 RTM and got this problem also. Then I reformatted and reinstalled 7 32-bit and disabled Windows Update to avoid incompatible drivers from being installed and I'm getting this problem yet again. No idea why this is happening- I guess it's time to go back to Windows XP/Vista
- I think Jewbles might be on to something here. I also have a Vostro 1520, but I also have an NVIDIA GeForce 9300M GS with the same touchpad.
My video card says: "Windows has stopped this device because it has reported problems. (Code 43)"
touchpad says: "This device cannot start. (Code 10)
Reinstalling the video card driver does seem to fix the problem, but it comes back. I am running Win7 Ultimate 64bit Version 6.1 (build 7600)
Here is a link to the requested portion of logs:
http://nuclearcrayon.net/~greg/setupapi.dev.log.snippet.txt- I am experiencing the same issue. Currently have the Vostro 1520. Every other time I boot into windows, the video driver (Intel 4 series graphics driver version 8.15.10.1808) stops working and the Alps Touchpad driver version 7.4.102.102 also stops working. Only fix I have been able to find is to reinstall the Intel video driver. This will seem to fix the issue temporary.
It seems that this problem did not start until after an automatic update installed a compatibility issue with Internet Explorer 8. I have tried uninstalling the update, but that did not resolve the problem. Tried restoring the system to a date prior to that update and it did not resolve the issue. Any ideas?? I am running Win7 Ultimate 64bit Version 6.1 (build 7600)
Here is a link to the requested portion of logs:
http://nuclearcrayon.net/~greg/setupapi.dev.log.snippet.txt
Is the the RC version or the RTM?- Any developments or have we decided that 7 is incompatible with the new Vostros for the time being? I'm annoyed because I thought 7 was supposed to be fully backwards compatible with hardware that worked on Vista.
- This is not a solution to the problem. Please do not mark it as such. Vostros cannot be used with Windows 7 as yet!
- This did not solve the problem.
For a while the touchpad would work every other time I started up the computer, but it no longer does. I didn't notice this before since I rebooted when the mouse didn't work, but now I see that when the mouse isn't working the video performance is abysmal. I have a USB mouse plugged in, but the computer isn't usable for much other than MS Office.
I'm switching back to WinXP today. Win7 has been just as much of a failure as Vista was for me with drivers, except in this case where Vista actually worked, but Win7 does not.- Agreed, musicgreg. It seems like this thread is dead. Anyone from Microsoft have any ideas? Link to my post on the Dell support forum: http://en.community.dell.com/forums/p/19295227/19555240.aspx#19555240 Please post here as well. Perhaps someone from Dell has a solution
Agreed, musicgreg. It seems like this thread is dead. Anyone from Microsoft have any ideas? Link to my post on the Dell support forum: http://en.community.dell.com/forums/p/19295227/19555240.aspx#19555240 Please post here as well. Perhaps someone from Dell has a solution
Sorry that you guys are hitting this, and that I have been a slacker following up on it. I was trying to get some answers internally, then went on vacation for about a week, and I didn't come back and update this thread.
Unfortunately, I wasn't able to get any additional suggestions internally (other than following up with Dell).
Sorry.
Want to know if your hardware will work on Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Microsoft Logo'd Hardware List**- Hmm, I haven't noticed any video performance issue except for the couple of times the video driver died. After reinstalling it, that worked fine.
I've thought about switching back to XP but I'm in the middle of a semester and it's just too much trouble. If it helps you, check out <http://www.aerosnap.de/>. It replicates the aero-snap of Windows7 in XP. For me, at least, that's the one feature of 7 i couldn't live without. I wish they had come up with it years ago. - So Windows 7 RTM worked perfectly out of the box for me. Then in about a week, the touchpad and video driver started to fail. So, something was installed or modified in that one week. I tried reinstalling 7 and set updates to manual. But I don't think I did this correctly; windows updated some components regardless (is there a way to turn it off completely, Mark?) and then the problems happened again. We should isolate exactly what is causing the failure and blacklist that update/modification. Windows upgrade advisor says my system is fully compatible, btw.I also got a strange error message about Windows not being able to preserve the memory map while trying to hibernate:""Your system's firmware did not preserve the system memory map across the hibernation transition. If you proceed with resume, your system could behave in an unexpected manner after resume completes. It is recommended that you save all your data and reboot after system resume finishes. Kindly check for a firmware update with your system vender as it may fix this problem."I have never seen this error before and I never got it again. Upon starting windows after getting this pre-boot error, the problems arose. Anyone with this problem too? I believe I had just updated the BIOS to A03 prior to getting this error and I thought the error because of the BIOS update. However, I cannot explain why the touchpad and video problems occurred upon rebooting.
So Windows 7 RTM worked perfectly out of the box for me. Then in about a week, the touchpad and video driver started to fail. So, something was installed or modified in that one week. I tried reinstalling 7 and set updates to manual. But I don't think I did this correctly; windows updated some components regardless (is there a way to turn it off completely, Mark?) and then the problems happened again. We should isolate exactly what is causing the failure and blacklist that update/modification. Windows upgrade advisor says my system is fully compatible, btw.
You said that you disabled Windows Update after installing, yet you still hit this after some time. Another poster above said they uninstalled the update that they thought was related to this, and it didn't change the behavior. So I don't think there's enough info here to say if it's related to an update on WU or not.I also got a strange error message about Windows not being able to preserve the memory map while trying to hibernate:""Your system's firmware did not preserve the system memory map across the hibernation transition. If you proceed with resume, your system could behave in an unexpected manner after resume completes. It is recommended that you save all your data and reboot after system resume finishes. Kindly check for a firmware update with your system vender as it may fix this problem."I have never seen this error before and I never got it again. Upon starting windows after getting this pre-boot error, the problems arose. Anyone with this problem too? I believe I had just updated the BIOS to A03 prior to getting this error and I thought the error because of the BIOS update. However, I cannot explain why the touchpad and video problems occurred upon rebooting.
My understanding is that if you disable Windows Update in the Windows Update UI, you won't get anything automatically pushed to you. That's not a recommended setting though.
If you think that's not working, a guaranteed solution is to disconnect it from the network :)
So 2 out of 2 times you've done an install, and you don't have this problem initially. When does the problem start happening for you? After the first reboot? After installing some other drivers/software?
The Upgrade Advisor alerts you to any known incompatible software. It does not guarantee compatibility. Small yet important difference :) Dell mentions that they support Win7 on this machine though, so hopefully a solution can be found here.
As for the hibernation thing, I've never seen that error before. I'll see what I can find out about it.
Want to know if your hardware will work on Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Microsoft Logo'd Hardware List**- Hi,
I've just experience a similar issue on my Vostro 1720. Up until two days ago, the Microsoft provided Synaptics drivers were working fine. Then, after a reboot the touchpad stopped working - Device Manager shows "The device could not start. (code 10)".
I spent a few hours last night, and with the aid of System Restore was able to narrow it down to the Windows Update KB915597 which is the weekly Windows Defender definition update. I rolled back using System Restore several times to before the most recent install of that update, and each time, after installing KB915597 and restarting the laptop, the touchpad would stop.
Hope this provides some leads,
Cheers,
Greg - Hey gplwhite,That's exactly what I was looking for! I'll try to install 7 and skip this update and keep everyone posted.drdayal
- http://editorsdesktop.com/KB915597.htmlGreg,It seems like that is a standard number for many updates. Could get more details about the update (date, version number?)
- I had the ALPS driver installed as the default Synaptics driver from Windows Update disabled scrolling from the side of the touchpad. I recently have gotten so fed up with the ALPS mouse driver not loading that I finally decided to suck it up and switch to the Synaptics one. To my dismay I have found that the Synaptics driver is having the same issue with Error Code 10. So drdayal, you are saying you are having this problem with the RTM version as well? I was hoping it was just a quirk with the RC version.
I even sent in a support ticket to a free tch support board and this was their response:
Thank you for contacting protonic.com. My name is David and I will be assisting you with your question.
I am afraid that Windows 7 is still in Release Candidate (RC) and as such is not supported by Microsoft until it is final release in late October/early November.
This also means that vendors such as Dell have not yet released official W7 drivers that are Windows 7 tested.
If you install Windows 7 RC you do so at your own risk and the same applies to drivers, so until the final release is out and Dell has released official W7 tested drivers there is very little that can be done. All this is stated when you signed up for the W7 RC on the Microsoft web site.
I am sorry this does not help, but it is Microsoft's officially stated position.
If you wish to contact me regarding this question, please feel free to reply to this e-mail. - I have a Vostro 1520 and installed Win7 pro x64 (official release from the MSDN / MAPS release for MS-Partners).
I have the same issue with the Alps Touchpad driver (version 7.104.102 from Dell) working for a while and now it doesn't anymore, error code 10.
Small extra contribution to this thread: I have tried the Alps Touchpad drivers v7.105.2015.101 but the error remains. I found those drivers on the Acer website, an Aspire 5736G uses the same touchpad and they posted newer drivers for Win7 x64.
So far I have not found any drivers newer than the v7.105 and I guess we all have to wait for Alps to release some descent drivers for Win7 ...
Best Regards, Raymond Lardenoije - OK, I am stuck here because the XP install bluescreens every time. I hope we can find a solution here soon.
It seems that everyone that has the touchpad stop working also sees that the video card driver is disabled. Reinstalling the video card driver solves the problem for one reboot.
Does everyone here have an nvidia 9300M? Or at least all nvidia?
Has anyone tried going the extreme route and switching video cards?
Is there another touchpad that will fit in this laptop?
Has anyone tried a different/older driver for the video card or touchpad? I have tried the driver from nvidia's site as well as Dell's, but both have the same result.
Mark [MSFT] what do you need from us to diagnose this problem?
Killerz298 I have tried using RC1 and RTM and both have the same problem. Mark [MSFT] what do you need from us to diagnose this problem?
Thanks for asking :)
It would help if we got some clarification for these points for everyone:
Is this happening on the RC build or the RTM build?
What version of the Alps driver are you using, and where did you get it from?
What version of the video driver are you using, and where did you get it from?
Are you ever able to get the touchpad working? If yes, is there any pattern to when it stops working (like after the next reboot), or does it just happen randomly?
No, not all instances reported are on systems with the Nvidia video adapter. AFAIK, there's no way you can switch video cards on your own.
Switching to a different touchpad is also an extreme step. As a temporary measure, you might want to consider a USB mouse. (Not ideal, but cheaper and easier than ripping apart your laptop)
Thanks,
Mark
Want to know if your hardware will work on Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Microsoft Logo'd Hardware List**For Mark (and others) - More details as requested:
I started out with:
- Dell Vostro 1520 with GeForce 9300M GS and Alps TouchPad
- Windows 7 pro x64 RTM (from Microsoft Action Pack Subscription)
- Dell BIOS A03 and Win7 drivers up-to-date from Dell website
including the Dell Touchpad driver 7.104.102 download from DellAfter I got the code 10 error I tried:
- nVidia driver 8.16.11.8681 (19-8-2009) download from nVidia
- Alps Pointing-device driver 7.105.2015.101 (24-2-2009) download from AcerSo far, both these updates did not the problem!
And now, to make it really interesting:
As a part of my Win7 testing I made a backup using Ghost 11.5 (corporate editon, started from WinPE boot-CD). After that I formatted the harddisk and restored the image, because I wanted to make sure that Ghost can create a reliable backup.
The backup and restore work just fine, and after rebooting to Win7 my touchpad als worked fine again ??!! During the first start of Win7 after the restore I have NOT noticed any hardware-detection or any other change ?!I will keep you up-to-date if my touchpad stops working or if I figure out something else ...
Best Regards, Raymond Lardenoije
- Hi DrDayal,
As far as I can tell it is definitely related to Windows Defender. Windows Update lists it as "Definition Update for Windows Defender KB915597 (Definition 1.65.957.0) Published 21/9/2009".
NOTE: I suspect this update has been updated, as I first saw the issue on about 20/09/2009. When I get time I'll check if this version of the update still causes problems.
Another thought - I haven't tried it, and its a bit of a long shot, but you could try disabling Windows Defender and see if your touchpad is resurrected... http://www.simplehelp.net/2009/03/11/how-to-disable-windows-defender-in-windows-7/
Cheers,
Greg - Hi Mark,
- This is occuring for me on Windows 7 x64 RTM (via MSDN).
- I'm using the Synaptics driver installed automatically from Microsoft v11.1.18.0
- I haven't noticed any correlation with the video driver. I have the Intel GMA X4500MHD adapter running Intel Express drivers v8.15.10.1808 (probably also from Microsoft)
As I mentioned earlier in the thread, I have been able to consistently get the touchpad working again after rolling back (using System Restore) prior to the install of a recent Windows Defender update from Microsoft Update.
My touchpad has been working without issue for the last couple of days since removing the Windows Defender update.
Hope this helps,
Cheers,
Greg - Hmm, maybe you want to reply to the response and tell David that Windows 7 is technically released in its final form (RTM, which is the version we are having problems with)
- Hey Greg,I disabled Windows Defender altogether along with Microsoft update and so far everything is working well! I'm glad we have narrowed down the source of the problem.Cheers,AD
- Dear Mark,That's correct. Everytime I install 7 Professional (RTM 32bit) it works fine initially and after a couple of days it glitches up on me. I reinstalled it again and disabled Update and Win Defender and so far it is working great! I did not install any drivers (besides those that Windows installed by default). The drivers Windows 7 is currently using are:PS/2 compatible mouse 6/21/2006 version: 6.1.7600.16385 by MicrosoftMobile Intel(R) 45 express Chipset family (Microsoft Corporation- WDDM 1.1) 5/6/2009 Version: 8.15.10.1749I hope 7 continues to work and I hope I don't catch a nasty virus because of Windows Updates and Defender being disabled!AD
- I have windows update enabled however I disabled win defender almost immediately as I have Avira anti virus running. I am still updating windows though. Can the update itself in some way be causing this problem even if windows defender isn't running?
- Killerz298,You want to disable the Defender updates. If you can keep defender running but disable the updates then in theory everything should be fine.
- Would I have to reinstall now to do that? I have already installed several updates I'm sure.
- No, you don't have to reinstall just go into Windows Defender and disable automatic updating. I am not running 7 on this machine otherwise I'd give more detailed instructions, sorry
- I've asked some folks to look into this, but I don't have any updates yet.
I definitely do not suggest disabling defender just to work around this problem.
Want to know if your hardware will work on Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Microsoft Logo'd Hardware List** - Hi,
I have a vostro 1520 and for the moment this is the working solution:
S.O. Win7 Enterprise RTM (msdn license)
Driver video: Intel gm45 (express chipset series 4 ) ver. 8.15.10.1872 --> get it here: http://downloadmirror.intel.com/17801/a08/win7_15154.zip
Mouse Driver: Ps/2 compatible automatic installed with Windows7 ( you loose scroll function )
This is the combination that seems to work for me right now. the most important driver is the VIDEO one :-)
Let me know if this help!
bye,
MickPeck Hi,
:-( nevermind...the issue with the mouse started again :-(
I have a vostro 1520 and for the moment this is the working solution:
S.O. Win7 Enterprise RTM (msdn license)
Driver video: Intel gm45 (express chipset series 4 ) ver. 8.15.10.1872 --> get it here: http://downloadmirror.intel.com/17801/a08/win7_15154.zip
Mouse Driver: Ps/2 compatible automatic installed with Windows7 ( you loose scroll function )
This is the combination that seems to work for me right now. the most important driver is the VIDEO one :-)
Let me know if this help!
bye,
MickPeck
The Device Cannot Start!
hope someone else find a solution as soon as possible :-(
bye,
MickPeck- I see that this isn't a new problem:Mark, maybe your team should google (err. Bing) "Windows defender and touchpad" and see the myriad of related problems on Windows vista. Maybe there is a fix available for 7 also.
I have a Vostro 1520 with Windows 7 RC installed, and have had the exact same problem. This happened a couple months ago, and unable to solve it I formatted and re-installed completely and it's been fine since. Tonight it did it again. After finding this thread I checked, and sure enough the Windows Defender updated last time I shut down.
I couldn't find how to uninstall the updates, but instead checked for any more updates. None were found, so I went here http://www.microsoft.com/security/portal/Definitions/ADL.aspx and downloaded the latest definitions, which may or may not have really been newer.
Either way, after installing them and rebooting, the touchpad is fine again.
Since I've had the problem twice, months apart, with Defender updates being installed at various times in between, maybe the problem is with the install routine rather than the update itself.
Bill Greganti
Innovation Squared- Ok... I am going to disable the auto update of defender updates and see if that helps. If it does, I will see if installing them manually makes the issue come back.
- So as it turns out I already had defender disabled and haven't been downloading definitions since I first installed Win7. Since the definitions aren't downloading for me I don't see what can be causing my problem on reboots etc... Sometimes it works, sometimes it doesn't so I don't see how that is related to defender. Oh well, back to the drawing board for me I guess.
Sometimes it works, sometimes it doesn't so I don't see how that is related to defender.
Yeah, that's a good summary of the issue. This is an intermittent problem.
Still working on getting some updates for you guys. Sorry for the pain here.
Want to know if your hardware will work on Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Microsoft Logo'd Hardware List**- Ok, I have/had the same same problem.
After installing W7 the touch-path is working fine but after a couple of days it stopped working.
I have a Vostro 1320 with a 9300M video card.
I Uninstalled the WDDM 1.1 video card driver and at the same time uninstalled/deleted the touch-pad drivers.
After a reboot it started working again. Don't know for how long but maybe its a quick fix for someone.
- I have the same issue.
I've tried disabling defender, doesn't work. Rolled back driver on my GeForce 9300, didn't do a thing.
Tried every version of both Synaptics and Alps drivers, no success.
I have a Vostro 1320 with a GeForce 9300 and I'm running Windows 7 64Bit Pro RTM.
I'm glad to see I'm not alone in this.
Dell has to solve this, the computer is unusable in Win7 and that sucks, I really don't wanna go back to Vista! :/ - I don't know if I mentioned this previously but when I finally do get win7 up and running (sometimes after several restarts) if I shut down the computer using hibernate instead of a full shutdown the computer ALWAYS starts back up working. This isn't feasible for me as I am dual booting and sharing the laptop but this might work for some of you as a temporary measure (unless you MUST restart for some reason.)
Perhaps this will help figure out the issue... - That doesn't work for me, the touchpad is still dead after resuming Win from hibernation. :/
- Sorry if my post was unclear or if I am misunderstanding you. I wasn't saying that if I start up windows and the touchpad isn't working I put it into hibernation to get it working. What I was saying in my post was that after restarting however many times, and I finally boot into windows with the touchpad and display driver working correctly, if I hibernate the computer instead of completely shutting it down it will always come back from hibernation working.
- I updated to Dell's drivers on the website and it messed up the touchpad. I'm gonna try restoring to before the installation. For now I think running 7 with all updates (Windows and Defender) off is the only way to ensure a stable system - still not a fix Microsoft and Dell!
- As mentioned above, this is an intermittent problem. The things that happen to get it working on your machine may simply be a coincidence, and might not always work for you.
I don't think it's a good idea to run with Windows Update & Windows Defender turned off on your system.
I don't have any updates for you on the status of a possible fix for this right now. Sorry.
Want to know if your hardware will work on Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Microsoft Logo'd Hardware List** - Dell is selling this computer with 7 starting Oct 22nd. Hopefully they will have a fix for it before then.
- I sure hope so!
I got mine working again yesterday and i haven't got a single clue why, and today after a reboot it's fucked up again. - Zippo, the next time you get it working don't shut it down (if you don't have to.) Enable hibernation mode and hibernate instead of a complete shutdown. See if that works for you.
- Yeah, I did that a couple of times and it works, but it's kinda logical since you have the whole session saved. But from time to time I do have to reboot since I use my comp at school doing stuff so it's not a solution for me.
- I have the same problem with version 7.4.102.102 (the latest one I found on the Dell support page). Did you find a working solution? All help appreciated.
- Is there an official word from dell on this issue? Launch is less than a month away. Is this only an issue with the Vostro models?
- just was on dell support chat. The representative said she will forward the issue to technicians/supervisors. I told her to show them this forum so keep posting guys!
- I have the exact same problem with my vostro, i realised it started doing this yesterday so i thought maybe i installed something wrong and screwed up my vostro 1320. Did a complete format today and came across this thread. Hopefully dell does something....or else this laptop would be useless.
EDIT: im new to this place, i thnk i accidentaly proposed as an answer when its not, sorry my bad.- Proposed As Answer bychinesedevil Thursday, October 08, 2009 8:41 PM
- Ive got the same problem on a 1320,
Im wondering if it could be the A03 bios update? Anybody rule that out?
Anyway, got the intel g4500mhd grafix running Dell's drivers and WIN7 x64 RTM
Never had a video issue until I tried to fix the mouse pad by installing a synaptic driver from their website, that screwed up both video and mouse pad, so i rolled back to a previous restore and that corrected the problem.
I thought it could be the Symantic antivirus i was running, so i uninstalled that, and had no problems since... cant remember if defender was on or not, I recall that symantic turned off defender during install. So anyway, everything was working with the dell mouse pad driver installed.
Then I installed the new M$ free antivirus they got offered now. It installed fine and updated fine and everything scanned as safe....
I recall then later that day there were updates being installed in windows... fare enough..... then this morning I see... updates will be installed when you shut down windows.... OK, good.....
I go to work, then my wife calls me screaming about this G.D! lemon computer we got from dell.... the mouse pad didn't work. So she does a hard reboot, still didn't solve the problem. I try to talk her through over the phone. I say "I think it might be a problem with antivirus" so I get her to uninstall M$ antivirus thats a day old. She reboots and everything works again.
Dunno if I turned ON defender when I installed the new AV software of if it was already ON.
But let it be know, that through this whole process, the laptop only ever gets turned off for new installs or updates.... most other times im seeding!!! ha. So in terms of reboots, the laptop don't get alot. - It is quite possible that the Bios A03 update could be the cause of this, because I can't recall I had this issue before updating!
Maybe I should try reverting back to A02 if it's possible? - I don't believe the problem is due to the A03 BIOS update. My understanding is also that this has nothing to do with Defender.
Sometimes the touchpad isn't working. Sometimes it is. I'm not aware of any workarounds for you guys to get it working 100% of the time.
The right people are investigating this problem. As soon as I have news on how to resolve this, I'll post something here.
Want to know if your hardware will work on Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Microsoft Logo'd Hardware List** - Shouldn't be the bios update, I have A02 on my dell, same problem, graphics drivers would fail to load along with ALPS touchpad drivers, right now i use the hibernate function instead of shut down. This seems to be the only way to ensure that i get working drivers everytime i start my laptop. Btw its a Vostro 1320 that i own w/ 4500MHD.
- Thanks for looking into it Mark, hopefully it'll be resolved soon, this really blows!
So we've ruled out the bios anyway, that's good, and it seems to happen on configurations with both Nvidia 9300 and Intel 4500. - I have a Vostro 1520 from dell that I bought on 8/31/09. About 1 week after I got it my touchpad stopped working. My tech guy put a new motherboard in it (not the Problem) Tried several different drivers etc. nada. But an external mouse will work. So far I found that system restore works to fix it. Than if I let it hibernate I have no problems. Problem is I can't take it anywhere for very long with it doing this. I was so pissed off for the first month. but I refuse to dual boot Xp or install vista. I like Win 7 alot. One problem I did notice was when I did shut it off not only would the touchpad not work but my display options would change.
It has nothing to do with Bios A03 update cause the problem happened before.
I did switch from auto update to manual updates.
talked to Dell they said they can't help me until Oct.22.
Somebody needs to fix it. or Dell needs to furnish me with a Vostro 1520 that IS compatible with Win 7. - Please post this on the dell forum as well. It is half their fault as well and they will only listen if we voice our concerns:
Same problems here too.
More often than not the touchpad will not work showing code 10 in device manager (USB mouse works fine)
Sometimes the display will not work at all (black screen) but the system seems to boot to the login screen (have to power down and restart)
Some times the display reverts to low resolution with code 37 in device manager.
Display problems usually clear up after re-boot but touchpad rarely works.
Vostro 1520, GM45, Alps Touchpad, BIOS A03 & Windows 7 RTM
- Same here..I have a Vostro 1320 with the latest drivers. I have already tried DELL drivers as well as Synaptics and Intel drivers. I have tried turning off windows update, after fresh windows 7 installation: didn't work.
They got to solve this problem as fast as possible! It is a shame, I was telling everyone around me how wonderful windows 7 is and now this!
Please, please guys from DELL or MS, go on and find a solution! - This just got weirder! When i rebooted my machine (been hibernating it for a while now) 3 devices wouldn't load their drivers.
Dell touchpad, Nvidia GeForce 9300 AND my Intel 5300 WiFi. I tried rebooting again and suddenly the touchpad was ok, but the other two still dead.
After yet another reboot all three devices wouldn't work.
What the ____ is going on?!
- Exactly the same problem
Vostro 1520 - Nvidia GeForce 9300M GS - Alps touchpad - Bios A02
When I reboot, sometimes the touchpad doesn't work, sometimes the keyboard doesn't work, sometime the graphic card doesn't work.
Despite of many tests, I have not been able to establish a cause in that problem. For example, I tried to boot and reboot whithout doing anything else on the computer, and sometimes I get the problem, sometime not.
As user, this problem is just understandable. My laptop is unsuable with Windows 7.
Dell and MS, please debug this problem. I'm really desapointed by new Vostro 1520 with Windows 7 RTM. - Alright, so I just installed maybe 10 updates from WU and after the reboot everything works!!
I tried rebooting 3 more times and it's still good.
I have no idea if the updates fixed anything or if things will be broken in a couple of days again but so far it looks good! Alright, so I just installed maybe 10 updates from WU and after the reboot everything works!!
I tried rebooting 3 more times and it's still good.
I have no idea if the updates fixed anything or if things will be broken in a couple of days again but so far it looks good!
I don't want to bum you out, but I think that's just a coincidence. I'm not aware of any updates that have been pushed out for this issue yet.
Want to know if your hardware will work on Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Microsoft Logo'd Hardware List**- Installed all those updates- one of them was an Intel GM45 graphics update actually and everything started working upon reboot. And then I shut down the machine and turned it on again; this time the windows desktop never loaded (looks like graphics driver completely failed to load). Ooof great. 6 more days until release.... Dell is so screwed for these Vostros.
- Mark, any idea as to what is atleast causing the problem? Remember, a clean install of 7 works perfectly initially and later it gets messed up. So something is being installed or modified that is screwing the machine up. Anyone at MSFT have any idea what this could be? Anyone use process of elimination? As soon as my computer got messed up I checked the installed updates. There was only 1 (I have updates disabled) and that was the Windows Defender update.
- I am not quite sure if this is 100% correct, but it seems to me that as long as I plug in my external usb mouse and start, it works! Just leave the mouse inside until you completely turned off the laptop, then you can plug it off. This way I was able to have 10 reboots without any problems. I am using Win7 pro x86 (MSDN-AA), latest intel graphics drivers(4500HD or what?) over MS Update and DELL Touchpad Drivers from Dell website.
May be you would also like to try this up! - I don't know if this helps but I am running the win 7 ultimate 64 bit os on the vostro 1520. i have been plagued with the touchpad problem for so long and I thought about sending it back to dell. My touchpad only worked for a week. We found a toshiba driver that somewhat worked but if I turned off my laptop then when It started up well nothing happened with my touch pad(yay for the external mouse) which helped me to do systems restore. That worked but I could never turn off the computer and had to let it hibernate. I keep my updates in manual and just recently updated and restored . no problems. That is with the toshiba driver. Well I checked the synaptics.com/support/drivers this morning and they finally have a driver set for win 7 32bit and 64bit. Downloaded and installed restarted and again no problems. also I think you really need the BIOS A03 update from dell drivers and downloads In A02 I had more problems than just the touchpad. I had issues with graphics and the screen going black or changes in my desktop settings after each startup. So far everything is working again as it should. And someday I might just feel confident enough to take this damn thing with me somewhere and use it for what I got it for.
- I dont think the mouse trick works.... I have a logitech VX nano plugged into my laptop at all times, and it would still fail to load ALPS and GMA4500 drivers. Right now i leave it on hibernate and its doing OKAY so far.
Mark, any idea as to what is atleast causing the problem? Remember, a clean install of 7 works perfectly initially and later it gets messed up. So something is being installed or modified that is screwing the machine up. Anyone at MSFT have any idea what this could be? Anyone use process of elimination? As soon as my computer got messed up I checked the installed updates. There was only 1 (I have updates disabled) and that was the Windows Defender update.
As I've stated a few times here, the problem is described as intermittent. Maybe you'll find something that happens to work for a while, but I do not believe that there is any set of steps that can be provided right now that will reliably allow you to work around this issue.
I do know that it has been communicated to the correct people, but there aren't any updates to share at this time. Sorry :(
Want to know if your hardware will work on Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Microsoft Logo'd Hardware List**- nope, my bad, touchpad stopped working again...
- Ya wanna hear something weird... I actually was having good success with the touchpad, it would go a few times but it was working for awhile..... Then I made an image of the HD with acronis true image, I copied the contents from a 160gb hd to an external hd and then to a new 250gb hd. When I placed the new image on the new HD, the mouse pad would not work, wierd. I rebooted a few times, and still nnothing. So I rolled back the driver to the MS one, still nothing, then I uninstalled the dell touchpad program from the uninstall application. This did not work..... so I tried to do a restore from an older point, it tried and said there was a bad system file on the HD, So I ran disk error check, after that the pad worked. I have since turned on defender, DL'd MS virus program and dells alps driver program and rebooted, and the mouse pad worked fine. I updated win7 and rebooted, still works.... WEIRD. There is no rhyme or reason for this that I can see.
- Dell is saying that you can purchase Vostros with Win7 preinstalled as of October 20th. I guess we will see what they have come up with shortly after that point in the drivers section.
- I too have experienced this exact same issue on Win 7 RTM. I stopped the forefront services, changed the startup type to manual, rebooted the laptop and the touchpad started working. I have then configured forefront to exclude drivers and services and all is working.
- BenKemp,What is forefront? What exactly did you exclude? Please give us more details- maybe this will work for all of us.
- i think he's talking about microsoft forefront ... but i haven't installed forefront (and i think most of us) and i'm experiencing this issue ... anyway tell us what you've done, thanks!
- I have no forefront yet I still have the same issues. Tomorrow is the big day, DELL is supposed to be bringing some new drivers addressing the issue..we'll see!
- Yes I'm talking about Microsoft ForeFront. It's the client software we use on our Windows 7 laptops. Anyway I went into Tools > Options and under the real-time protection settings I unchecked Services and Drivers from the Choose which security agents you want to run. So far so good and not had any complaints from the laptop user.
What client security software are you running? Was the touchpad working during the Windows 7 build phase? Try booting from your Windows 7 disk and I bet the touchpad starts working.- Proposed As Answer byErmannoST Monday, October 19, 2009 4:02 PM
- your suggestion maybe helped us .... i deactivated windows defender (from gui and then from services.msc) ... the problem for me happened from the last windows defender update (and you can't uninstall win defender updates) ... and then at the first reboot touchpad WORKS!I think that something in win defender doesn't allow legacy touchpad (and maybe display) driver ... just try it if you have this issue and let us know if work for you
- In Windows Defender try going into Tools > Options and under the real-time protection settings I uncheck Services and Drivers from the Choose which security agents you want to run. It may work in the same way it worked for me with ForeFront.
Yes I'm talking about Microsoft ForeFront. It's the client software we use on our Windows 7 laptops. Anyway I went into Tools > Options and under the real-time protection settings I unchecked Services and Drivers from the Choose which security agents you want to run. So far so good and not had any complaints from the laptop user.
Ben - This issue has nothing to do with Forefront or any other security software as far as I can tell. The defender suggestion has been posted before, but please review the thread. Other folks have tried various things. So far, nobody has a 100% reliable way of getting the device to work.
I don't think disabling security software is really a good idea here. I understand that the issue is frustrating. I hope to have more info to share with you soon regarding a fix for this problem.
Thanks,
Mark
Want to know if your hardware will work on Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Microsoft Logo'd Hardware List**- Proposed As Answer byMark [MSFT]MSFTWednesday, October 21, 2009 4:10 AM
I am yet another person experiencing this intermittent and extremely frustrating problem...
dell Vostro 1520 with GeForce9300M, Win 7 Ultimate 32bit RTM
I am def going to be putting in a call to Dell on 22 Oct!- Fair enough Mark. I find it strange that the touchpad was working fine when installing and configuring Windows 7 and the problem for me only occured after installing the following apps: Office 2007, Project 2007, Visio 2007, Adobe Reader, ForeFront.
I'll look out for future postings in this thread but in the mean time I shall continue to run ForeFront with Services and Drivers excluded. Please note I have not disabled ForeFront. - I wanted to mention that I'm also having this problem. I'm running whatever 32 bit version of Windows 7 Ultimate that Microsoft gave out at the "The New Efficiency" events. I'm using a Dell Vostro 1520 with an NVidia GeForce 9300M GS. I currently have this error on my Dell Touchpad, causing it to not work:
This device cannot start. (Code 10)
With Alps driver 7.4.102.102 dated 3/6/2009
I also have this error on my NVidia card:
Windows has stopped this device because it has reported problems. (Code 43)
With NVidia driver 8.16.11.9107, dated 9/27/2009
I have Microsoft Security Essentials installed. However, it is currently listed as disabled. If I open it and click "Turn On", the "Turn On" button disables, but Security Essentials still says my computer is at risk; it doesn't appear that it actually turns on. Action Center mentions that Windows Defender and Microsoft Security Essentials both report that they are off.
I'm sometimes able to get the Touchpad and NVidia display adapter working again, but I couldn't tell you the steps I use to do it. It may be intermittent as suggested above. I typically try and uninstall the touchpad device, checking the "uninstall the driver software" option. Then I go to Uninstall Programs and uninstall the Alps driver software from there as well. Finally I reinstall the drivers from the extracted driver zip off of Dell's support site.
I'm looking forward to this being resolved. - I think Mark's head is going to explode if 1 more person suggests disabling windows defender :-)
I think Mark's head is going to explode if 1 more person suggests disabling windows defender :-)
:-P
I understand the thread is long, and it's easy to miss the earlier responses on this topic. I just don't want people to leave their PC's in an unprotected state while waiting for a solution for this problem. I hate to propose my own post as an answer, but I've flagged it so hopefully people see it when they're looking through this thread.
Want to know if your current hardware & software will work with Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Windows 7 Compatibility Center**Update: Per posts below, this doesn't resolve the problem. :(
BIOS revision A04 has been posted for Vostro laptops.
I've been told that this update should resolve this problem. Please let me know if it works for you.
Thanks,
Mark
Want to know if your current hardware & software will work with Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Windows 7 Compatibility Center**- Edited byMark [MSFT]MSFTThursday, October 22, 2009 2:25 AMremoving "solution" tag
- "Systems: Dell Vostro 1320 Series
Version: A04
Build Date: 09/10/2009
UMA VBIOS Version: Intel GM45 Graphics Video BIOS version 1706
VGA VBIOS Version: Nvidia 62.98.67.00.0E
Fixes/Enhancements
------------------
1. Fix sometimes touch pad lockup when enter windows 7 OS.
2. Update nVidia VBIOS to 62.98.67.00.0E.
3. Fix: System will hang up while using 1394 Device."Woohoo! - Spoke too soon...Video card works 100% of the time but touchpad is still nonfunctional. After the BIOS update I reinstalled the ALPS drivers from the dell website and rebooted (did these steps multiple times) and it's still not functioning.
- Is it still code 10, or does it show some other error condition?
Can you please look in c:\windows\setupapi.dev.log and copy the install section from today's driver install attempt and paste it here?
Thanks,
Mark
Want to know if your current hardware & software will work with Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Windows 7 Compatibility Center** - Okay, this is what I did to get mine working. By the way, I'm running Windows 7 Ultimate 64-Bit Retail.
First, I uninstalled the ALPS drivers. Then, I uninstalled the NVidia Physx Drivers. Then, I uninstalled the NVidia graphics drivers. Then, I installed the BIOS update. Then, I restarted.
When Windows started, Windows automatically installed some NVidia drivers. After it was finished, I installed the ALPS driver and restarted.
Upon, restart, the touchpad still didn't work and both the touchpad and graphics card had the usual errors reported in the device manager.
Next, I installed the lasted NVidia drivers. When the computer restarted, both the touchpad and graphics card were working fine :-) - Mark, see my post above.
- @Mark:Here is the install section from the driver install attempt:>>> [Device Install (Hardware initiated) - HID\VID_047D&PID_2030&MI_01&Col04\7&31194a56&0&0003]>>> Section start 2009/10/21 12:35:32.449ump: Creating Install Process: DrvInst.exe 12:35:32.459ndv: Retrieving device info...ndv: Setting device parameters...ndv: Searching Driver Store and Device Path...dvi: {Build Driver List} 12:35:32.479dvi: Searching for hardware ID(s):dvi: hid\vid_047d&pid_2030&rev_0200&mi_01&col04dvi: hid\vid_047d&pid_2030&mi_01&col04dvi: hid_device_system_mousedvi: hid_device_up:0001_u:0001dvi: hid_devicecpy: Policy is set to make all digital signatures equal.dvi: Enumerating INFs from path list 'X:\Windows\inf'inf: Opened PNF: 'X:\Windows\System32\DriverStore\FileRepository\msmouse.inf_x86_neutral_7a9084e0177406eb\msmouse.inf' ([strings.0409])dvi: Created Driver Node:dvi: HardwareID - HID_DEVICE_SYSTEM_MOUSEdvi: InfName - X:\Windows\System32\DriverStore\FileRepository\msmouse.inf_x86_neutral_7a9084e0177406eb\msmouse.infdvi: DevDesc - HID-compliant mousedvi: DrvDesc - HID-compliant mousedvi: Provider - Microsoftdvi: Mfg - Microsoftdvi: ModelsSec - MSMfg.NTx86dvi: InstallSec - HID_Mouse_Instdvi: ActualSec - HID_Mouse_Inst.NTdvi: Rank - 0x00ff1002dvi: Signer - Microsoft Windowsdvi: Signer Score - INBOXdvi: DrvDate - 06/21/2006dvi: Version - 6.1.7600.16385inf: Opened PNF: 'X:\Windows\System32\DriverStore\FileRepository\input.inf_x86_neutral_5a80b94d3045438a\input.inf' ([strings.0409])dvi: Created Driver Node:dvi: HardwareID - HID_DEVICEdvi: InfName - X:\Windows\System32\DriverStore\FileRepository\input.inf_x86_neutral_5a80b94d3045438a\input.infdvi: DevDesc - HID-compliant devicedvi: DrvDesc - HID-compliant devicedvi: Provider - Microsoftdvi: Mfg - (Standard system devices)dvi: ModelsSec - Standard.NTx86dvi: InstallSec - HID_Raw_Instdvi: ActualSec - HID_Raw_Inst.NTdvi: Rank - 0x00ff1004dvi: Signer - Microsoft Windowsdvi: Signer Score - INBOXdvi: DrvDate - 06/21/2006dvi: Version - 6.1.7600.16385inf: Searched 2 potential matches in published INF directoryinf: Searched 35 INFs in directory: 'X:\Windows\inf'dvi: {Build Driver List - exit(0x00000000)} 12:35:32.629ndv: Selecting best match from Driver Store (including Device Path)...dvi: {DIF_SELECTBESTCOMPATDRV} 12:35:32.629dvi: Using exported function 'MouseClassInstaller' in module 'X:\Windows\system32\SysClass.Dll'.dvi: Class installer == SysClass.Dll,MouseClassInstallerdvi: Using exported function 'CriticalDeviceCoInstaller' in module 'X:\Windows\system32\SysClass.Dll'.dvi: CoInstaller 1 == SysClass.Dll,CriticalDeviceCoInstallerdvi: CoInstaller 1: Enter 12:35:32.634dvi: CoInstaller 1: Exitdvi: Class installer: Enter 12:35:32.636dvi: Class installer: Exitdvi: Default installer: Enter 12:35:32.636dvi: {Select Best Driver}dvi: Selected driver installs from section [HID_Mouse_Inst] in 'x:\windows\system32\driverstore\filerepository\msmouse.inf_x86_neutral_7a9084e0177406eb\msmouse.inf'.dvi: Class GUID of device changed to: {4d36e96f-e325-11ce-bfc1-08002be10318}.dvi: {DIF_DESTROYPRIVATEDATA} 12:35:32.638dvi: CoInstaller 1: Enter 12:35:32.638dvi: CoInstaller 1: Exitdvi: Class installer: Enter 12:35:32.639dvi: Class installer: Exitdvi: Default installer: Enter 12:35:32.639dvi: Default installer: Exitdvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 12:35:32.640dvi: Set selected driver complete.dvi: Selected:dvi: Description - [HID-compliant mouse]dvi: InfFile - [x:\windows\system32\driverstore\filerepository\msmouse.inf_x86_neutral_7a9084e0177406eb\msmouse.inf]dvi: Section - [HID_Mouse_Inst]dvi: Signer - [Microsoft Windows]dvi: Rank - [0x00ff1002]dvi: {Select Best Driver - exit(0x00000000)}dvi: Default installer: Exitdvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 12:35:32.643inf: {SetupCopyOEMInf: X:\Windows\INF\msmouse.inf} 12:35:32.644inf: Driver Store location: X:\Windows\System32\DriverStore\FileRepository\msmouse.inf_x86_neutral_7a9084e0177406eb\msmouse.infinf: Published Inf Path: X:\Windows\INF\msmouse.infinf: {SetupCopyOEMInf exit (0x00000050)} 12:35:32.646dvi: Searching for hardware ID(s):dvi: hid\vid_047d&pid_2030&rev_0200&mi_01&col04dvi: hid\vid_047d&pid_2030&mi_01&col04dvi: hid_device_system_mousedvi: hid_device_up:0001_u:0001dvi: hid_deviceinf: Opened PNF: 'X:\Windows\System32\DriverStore\FileRepository\msmouse.inf_x86_neutral_7a9084e0177406eb\msmouse.inf' ([strings.0409])dvi: Selected driver installs from section [HID_Mouse_Inst] in 'x:\windows\system32\driverstore\filerepository\msmouse.inf_x86_neutral_7a9084e0177406eb\msmouse.inf'.dvi: Class GUID of device changed to: {4d36e96f-e325-11ce-bfc1-08002be10318}.dvi: Set selected driver complete.ndv: Driver selected, now performing install...ndv: {Core Device Install} 12:35:32.653inf: Opened PNF: 'X:\Windows\INF\msmouse.inf' ([strings.0409])! pol: Selected driver node does not match this device (force-install)inf: Opened PNF: 'X:\Windows\INF\msmouse.inf' ([strings.0409])dvi: {DIF_ALLOW_INSTALL} 12:35:32.761dvi: Using exported function 'MouseClassInstaller' in module 'X:\Windows\system32\SysClass.Dll'.dvi: Class installer == SysClass.Dll,MouseClassInstallerdvi: Using exported function 'CriticalDeviceCoInstaller' in module 'X:\Windows\system32\SysClass.Dll'.dvi: CoInstaller 1 == SysClass.Dll,CriticalDeviceCoInstallerdvi: CoInstaller 1: Enter 12:35:32.761dvi: CoInstaller 1: Exitdvi: Class installer: Enter 12:35:32.761inf: Opened PNF: 'X:\Windows\INF\msmouse.inf' ([strings.0409])inf: Opened PNF: 'X:\Windows\INF\msmouse.inf' ([strings.0409])dvi: Class installer: Exitdvi: {DIF_ALLOW_INSTALL - exit(0x00000000)} 12:35:32.761ndv: Installing files...dvi: {DIF_INSTALLDEVICEFILES} 12:35:32.771dvi: CoInstaller 1: Enter 12:35:32.771dvi: CoInstaller 1: Exitdvi: Class installer: Enter 12:35:32.771dvi: Class installer: Exitdvi: Default installer: Enter 12:35:32.771dvi: {Install FILES}inf: Opened PNF: 'x:\windows\system32\driverstore\filerepository\msmouse.inf_x86_neutral_7a9084e0177406eb\msmouse.inf' ([strings.0409])inf: {Install Inf Section [HID_Mouse_Inst.NT]}inf: Copyfiles=HID_Mouse_Inst.CopyFiles.NT (msmouse.inf line 403)flq: CopyFiles from an inbox inf.cpy: Open PnpLockdownPolicy: Err=2. This is OK. Use LockDownPolicyDefaultflq: QueueSingleCopy...flq: Inf : 'x:\windows\system32\driverstore\filerepository\msmouse.inf_x86_neutral_7a9084e0177406eb\msmouse.inf'flq: SourceInf: 'x:\windows\system32\driverstore\filerepository\msmouse.inf_x86_neutral_7a9084e0177406eb\msmouse.inf'flq: SourceSection: [sourcedisksfiles]flq: Source root path based on SourceInfflq: SourceRootPath: 'X:\Windows\System32\DriverStore\FileRepository\msmouse.inf_x86_neutral_7a9084e0177406eb'flq: {FILE_QUEUE_COPY}flq: CopyStyle - 0x09000000flq: {FILE_QUEUE_COPY}flq: CopyStyle - 0x09000000flq: SourceRootPath - 'X:\Windows\System32\DriverStore\FileRepository\msmouse.inf_x86_neutral_7a9084e0177406eb'flq: SourceFilename - 'mouhid.sys'flq: TargetDirectory- 'X:\Windows\system32\DRIVERS'flq: TargetFilename - 'mouhid.sys'flq: SourceDesc - 'windows cd'flq: {FILE_QUEUE_COPY exit(0x00000000)}flq: {FILE_QUEUE_COPY exit(0x00000000)}flq: QueueSingleCopy...flq: Inf : 'x:\windows\system32\driverstore\filerepository\msmouse.inf_x86_neutral_7a9084e0177406eb\msmouse.inf'flq: SourceInf: 'x:\windows\system32\driverstore\filerepository\msmouse.inf_x86_neutral_7a9084e0177406eb\msmouse.inf'flq: SourceSection: [sourcedisksfiles]flq: Source root path based on SourceInfflq: SourceRootPath: 'X:\Windows\System32\DriverStore\FileRepository\msmouse.inf_x86_neutral_7a9084e0177406eb'flq: {FILE_QUEUE_COPY}flq: CopyStyle - 0x09000000flq: {FILE_QUEUE_COPY}flq: CopyStyle - 0x09000000flq: SourceRootPath - 'X:\Windows\System32\DriverStore\FileRepository\msmouse.inf_x86_neutral_7a9084e0177406eb'flq: SourceFilename - 'mouclass.sys'flq: TargetDirectory- 'X:\Windows\system32\DRIVERS'flq: TargetFilename - 'mouclass.sys'flq: SourceDesc - 'windows cd'flq: {FILE_QUEUE_COPY exit(0x00000000)}flq: {FILE_QUEUE_COPY exit(0x00000000)}inf: {Install Inf Section [HID_Mouse_Inst.NT] exit (0x00000000)}dvi: Processing co-installer registration section [HID_Mouse_Inst.NT.CoInstallers].inf: {Install Inf Section [HID_Mouse_Inst.NT.CoInstallers]}inf: {Install Inf Section [HID_Mouse_Inst.NT.CoInstallers] exit (0x00000000)}dvi: Co-installers registered.dvi: {Install INTERFACES}dvi: Installing section [HID_Mouse_Inst.NT.Interfaces]dvi: {Install INTERFACES exit 00000000}dvi: {Install FILES exit (0x00000000)}dvi: Default installer: Exitdvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 12:35:32.781ndv: Pruning file queue...dvi: {_SCAN_FILE_QUEUE}flq: ScanQ flags=620flq: SPQ_SCAN_PRUNE_COPY_QUEUEflq: SPQ_SCAN_FILE_COMPARISONflq: SPQ_SCAN_ACTIVATE_DRPflq: ScanQ number of copy nodes=2flq: File 'X:\Windows\system32\DRIVERS\mouhid.sys' pruned from copy.sig: Using catalog 'X:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-Common-Drivers-Package~31bf3856ad364e35~x86~~6.1.7600.16385.cat'.cpy: DrpSetRegFileProt 'X:\Windows\system32\DRIVERS\mouhid.sys' Status=0 Class=Inbox Windows protectedflq: File 'X:\Windows\system32\DRIVERS\mouclass.sys' pruned from copy.sig: Using catalog 'X:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-Common-Drivers-Package~31bf3856ad364e35~x86~~6.1.7600.16385.cat'.cpy: DrpSetRegFileProt 'X:\Windows\system32\DRIVERS\mouclass.sys' Status=0 Class=Inbox Windows protectedflq: ScanQ action=200 DoPruning=32flq: ScanQ end Validity flags=620 CopyNodes=0dvi: {_SCAN_FILE_QUEUE exit(0, 0x00000000)}ndv: Committing file queue...flq: {_commit_file_queue}flq: CommitQ DelNodes=0 RenNodes=0 CopyNodes=0flq: CommitQ early exit: No nodes are queuedflq: {_commit_file_queue exit OK}ndv: Registering CoInstallers...dvi: {DIF_REGISTER_COINSTALLERS} 12:35:32.831dvi: CoInstaller 1: Enter 12:35:32.831dvi: CoInstaller 1: Exitdvi: Class installer: Enter 12:35:32.831dvi: Class installer: Exitdvi: Default installer: Enter 12:35:32.831inf: Opened PNF: 'x:\windows\system32\driverstore\filerepository\msmouse.inf_x86_neutral_7a9084e0177406eb\msmouse.inf' ([strings.0409])inf: {Install Inf Section [HID_Mouse_Inst.NT.CoInstallers]}inf: {Install Inf Section [HID_Mouse_Inst.NT.CoInstallers] exit (0x00000000)}dvi: {DIF_DESTROYPRIVATEDATA} 12:35:32.841dvi: CoInstaller 1: Enter 12:35:32.841dvi: CoInstaller 1: Exitdvi: Class installer: Enter 12:35:32.841dvi: Class installer: Exitdvi: Default installer: Enter 12:35:32.841dvi: Default installer: Exitdvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 12:35:32.841dvi: Co-installers registered.dvi: Default installer: Exitdvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 12:35:32.841ndv: Installing interfaces...dvi: {DIF_INSTALLINTERFACES} 12:35:32.841dvi: Using exported function 'CriticalDeviceCoInstaller' in module 'X:\Windows\system32\SysClass.Dll'.dvi: CoInstaller 1 == SysClass.Dll,CriticalDeviceCoInstallerdvi: CoInstaller 1: Enter 12:35:32.841dvi: CoInstaller 1: Exitdvi: Class installer: Enter 12:35:32.841dvi: Class installer: Exitdvi: Default installer: Enter 12:35:32.841dvi: {Install INTERFACES}inf: Opened PNF: 'x:\windows\system32\driverstore\filerepository\msmouse.inf_x86_neutral_7a9084e0177406eb\msmouse.inf' ([strings.0409])dvi: Installing section [HID_Mouse_Inst.NT.Interfaces]dvi: {Install INTERFACES exit 00000000}dvi: Default installer: Exitdvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 12:35:32.841ndv: Installing device...dvi: {DIF_INSTALLDEVICE} 12:35:32.851dvi: CoInstaller 1: Enter 12:35:32.851dvi: CoInstaller 1: Exitdvi: Class installer: Enter 12:35:32.851inf: Opened PNF: 'X:\Windows\INF\msmouse.inf' ([strings.0409])dvi: {Install DEVICE}inf: Opened PNF: 'x:\windows\system32\driverstore\filerepository\msmouse.inf_x86_neutral_7a9084e0177406eb\msmouse.inf' ([strings.0409])dvi: Processing Registry/Property directives...inf: {Install Inf Section [HID_Mouse_Inst.NT]}inf: {Install Inf Section [HID_Mouse_Inst.NT] exit (0x00000000)}inf: {Install Inf Section [HID_Mouse_Inst.NT.Hw]}inf: DelReg=HID_Mouse_Inst.DelReg.NT (msmouse.inf line 407)inf: AddReg=HID_Mouse_Inst.AddReg.NT (msmouse.inf line 406)inf: {Install Inf Section [HID_Mouse_Inst.NT.Hw] exit (0x00000000)}dvi: {Writing Device Properties}dvi: Provider name=Microsoftdvi: DriverDate 06/21/2006dvi: DriverVersion=6.1.7600.16385dvi: Class name=Mousedvi: Manufacturer=Microsoftdvi: Matching DeviceID=hid_device_system_mousedvi: Strong Name=msmouse.inf:MSMfg.NTx86:HID_Mouse_Inst:6.1.7600.16385::hid_device_system_mousedvi: {Writing Device Properties - Complete}inf: {Install Inf Section [HID_Mouse_Inst.NT.Services]}inf: AddService=mouhid,0x00000002,MouHid_Service_Inst,MouHid_EventLog_Inst (msmouse.inf line 428)inf: ServiceType=1 (msmouse.inf line 503)inf: StartType=3 (msmouse.inf line 504)inf: ErrorControl=0 (msmouse.inf line 505)inf: ServiceBinary=X:\Windows\system32\DRIVERS\mouhid.sys (msmouse.inf line 506)inf: DisplayName="Mouse HID Driver" (msmouse.inf line 502)inf: LoadOrderGroup="Pointer Port" (msmouse.inf line 507)dvi: Add Service: Modified existing service 'mouhid'.inf: AddReg=MouHid_Service_Inst_AddReg (msmouse.inf line 508)inf: AddReg=MouHid_EventLog_AddReg (msmouse.inf line 432)inf: AddService=mouclass,,mouclass_Service_Inst,mouclass_EventLog_Inst (msmouse.inf line 429)inf: ServiceType=1 (msmouse.inf line 260)inf: StartType=3 (msmouse.inf line 261)inf: ErrorControl=1 (msmouse.inf line 262)inf: ServiceBinary=X:\Windows\system32\DRIVERS\mouclass.sys (msmouse.inf line 263)inf: DisplayName="Mouse Class Driver" (msmouse.inf line 259)inf: LoadOrderGroup="Pointer Class" (msmouse.inf line 264)dvi: Add Service: Modified existing service 'mouclass'.inf: AddReg=mouclass_EventLog_AddReg (msmouse.inf line 267)inf: {Install Inf Section [HID_Mouse_Inst.NT.Services] exit(0x00000000)}dvi: Updated reflected section names for: msmouse.infdvi: {Install DEVICE exit (0x00000000)}dvi: Writing common driver property settings.dvi: DriverDescription=HID-compliant mousedvi: DeviceDisplayName=HID-compliant mousedvi: Install Device: Restarting device. 12:35:33.481dvi: Install Device: Restarting device completed. 12:35:33.641dvi: Class installer: Exitdvi: CoInstaller 1: Enter (Post Processing) 12:35:33.688dvi: CoInstaller 1: Exit (Post Processing)dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 12:35:33.688dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 12:35:33.688dvi: CoInstaller 1: Enter 12:35:33.688dvi: CoInstaller 1: Exitdvi: Class installer: Enter 12:35:33.688dvi: Class installer: Exitdvi: Default installer: Enter 12:35:33.688dvi: Default installer: Exitdvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 12:35:33.688ndv: Device install status=0x00000000ndv: Performing device install final cleanup...ndv: {Core Device Install - exit(0x00000000)} 12:35:33.688dvi: {DIF_DESTROYPRIVATEDATA} 12:35:33.688dvi: CoInstaller 1: Enter 12:35:33.688dvi: CoInstaller 1: Exitdvi: Class installer: Enter 12:35:33.688dvi: Class installer: Exitdvi: Default installer: Enter 12:35:33.688dvi: Default installer: Exitdvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 12:35:33.688ump: Server install process exited with code 0x00000000 12:35:33.704<<< Section end 2009/10/21 12:35:33.704<<< [Exit status: SUCCESS]
- Oh and it's still Error code 10
- Okay, did another restart, had the same problem again.
Already running BIOS revision A04 here.
- Okay, this is just crazy. I went into the Device Manager and completely uninstalled the touchpad. Then, I uninstalled the ALPS driver. Then, I uninstalled all of the NVidia Physx and device drivers. Upon restart, the computer automatically installed an NVidia driver. When I restarted, both the touchpad and the graphics card were working. The driver was listed as 185.xx, as opposed to the more current 186 driver. Upon restarting, the graphics card is no longer working, but the touchpad works fine. The error in the Device Manager is Code 37. I still have yet to install the ALPS driver.
Very frustrating. - After my last post, I installed the latest NVidia drivers and restarted. Upon restart, the graphics drivers were behaving fine, as was the touchpad. I restarted again, and once again, both were working fine.
Next, I installed the ALPS driver. Upon restarting the computer, both the touchpad and graphics drivers were working fine. I customized the ALPS program (no touch-to-click, faster cursor speed, etc.) and restarted the computer. I restarted again, both the touchpad and graphics drivers were working fine again. I restarted one last time, and once again, both the touchpad and graphics drivers were working fine.
So, to reiterate, for me, this sequence worked:
Dell Vostro 1320
NVIDIA 9300m
Installed BIOS A04
Restart
Uninstalled NVidia drivers
Restart
Uninstalled Touchpad under Device Manager
Uninstalled ALPS software
Restart (Touchpad works fine - No ALPS software)
Installed latest NVidia drivers
Restart (Graphics working fine)
Installed ALPS drivers
Restart (Graphics and touchpad working fine)
Restart (Graphics and touchpad working fine)
Restart (Graphics and touchpad working fine)
I've got my fingers crossed, but as I said, three restarts since the ALPS drivers and both are working fine.
Keep in mind, though, I have NOT refreshed the Windows Experience Index, but my score is still showing as a 4.3 and everything is working fine (i.e. Aero Peak, color settings, etc.). I just don't want to temp fate at this point. - Update, after a few more restarts, the problem began again. Obviously, Dell has a lot more work to do...
- TJ... welcome to our world of trying everything you can think of and having nothing work. I think we tried every driver in every sequence but the problem ALWAYS comes back. We will have to hang in there a little longer. Has anyone tried a CLEAN install with bios updated to A04? Maybe we need to start from scratch to get it working with the new bios?
Also, Dell just sent me an email and this was the subject:
Windows 7. Worries 0. Dell Systems Now with Windows 7
Lol Are people who aren't using Windows 7 in a dual boot configuration having this issue? I'm running Windows XP on the C: partition and Windows 7 on the D: partition. Of course, when Windows 7 is running it identifies itself as being on the C: partition. Strangely enough, though, at one point I did have an issue where Windows XP's touchpad stopped working as well. However, upon reinstalling the driver, it never became an issue again.
To be honest, I love Windows 7. But, the whole reason I've been running XP throughout Vista's life-cycle is because I couldn't get it to work on my main system in the beginning, with similar problems to this Windows 7 installation. Still, XP is 8 years old now and I'm ready for the switch. Is there any way to push Dell to get another update going? And do you think installing Windows 7 on the C: drive versus the D: drive might make any difference?- Sorry but, until now (for 3 days and maybe 10 restart) since i disabled drivers control from windows defender all is working, Vostro 1720 with Win 7 Ultimate and shipped (with win 7) intel gma drivers & touchpad drivers. Maybe i'm wrong, but if the issue come in with defender, forefront or ms security essential installed and updated and disabling the driver control resolve the issue, isn't all clear?I don't say it'ìs microsoft fault (because gma & touchpad drivers are not officially compatible with windows 7, so microsoft's behaviour it's ok) but for me the solution until now it's pretty simple ...hope this helps ;-)
- T.J., I'm not running in a dual boot configuration but I'm still having this problem. My Windows 7 Ultimate install was an upgrade from Vista Business, but not dual booting.
- Well, at least that's good to know.
By the way, I have disabled Windows Defender. I disabled it before I installed A04. It has absolutely zero effect. - What kind of testing was done by Dell? They rewrite the freaking BIOS to fix a certain problem and their update still doesn't address the issue fully? Are you kidding me?
- Sorry everyone :( I've let the folks that were investigating this know that the problem is not resolved.
Want to know if your current hardware & software will work with Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Windows 7 Compatibility Center** - I agree. As of tomorrow, Dell is selling laptops to consumers that do not work, or are at least severely crippled functionality-wise. A normal person would have no idea how to attempt all of the troubleshooting we've just gone through...
- Received my Vostro 1720(Windows 7 Ultimate 64-bit RTM - 9600M GT), 8 days ago, and my touchpad stoppede working an hour ago. I updated today - Danish Language Pack(KB967828), Realtek PCIe GBE Family Controller - Broadcom Driver Dell Wireless 1397.
Have been trying all the resolutions mentioned in the thread. All drivers updated to newest version from Dell official (and they were before it stopped working) but it is still not working. My graphic driver is still working by the way. - Heard about the A04 Bios update and the information on the DL said it was to address this problem that we are all having. So I got two identical machines, one running Win7 RTM pro x64 and one with WinXP. I tried to flash the bios with win 7, and it froze up halfway through the program erase mode.... so i had to haul out the battery and power plug to reboot, it luckely rebooted with A03 bios. So I tried it 3 more times, each time with a freezup at different stages of the bios rebuild. So I gave up on it.
I moved onto the WinXP machine, it flashed first time no problem. So I swapped Hard Drives and was able to flash the win7 vostro no problem with the xp hard drive in it. Another problem with Windows 7 for me. But I do not have the touchpad problem now for the last few weeks. I did at times though. - Anna did you get your machine shipped from Dell with Windows 7 on it or did you put it on it?
- I installed it myself :) . It was shipped with Vista ( thumbs down) Still got the original drive with Vista on, though.
- It seems the process "RPCnetp.exe" have something to do with this problem.
Try to delete it from Task Manager, and also delete "icpnetp.exe" and/or "icpnetp.dll" from C:\Windows\system32\
These files may respawn after reboot, but will not cause trouble if I use A04 BIOS. - I executed RPCnetp.exe - no effect :) (And there's no files named icpnetp.dll in my \system32)
- The Mac fanboys are going to have a picnic if they read this stuff...
- I think my problem is solved! I have done 20 cold starts mixed with restarts with and without an external mouse plugged in: No touchpad or graphic issues!
Here are the details:
I have installed A04 Bios. Restarted. Had touchpad issue. Tried couple of other ALPS drivers from DELL and Toshiba. none worked without issues with touchpad...So in the end I uninstalled Dell touchpad driver and program. Restarted. MS Update loaded a standard mouse driver. And since then everything is fine.
Windows 7 Pro x86 with latest updates
Vostro 1320
Intel GMA 4500M graphics with the driver "Mobile Intel(r) 4 series express chipset family" driver date: 13.08.09 Version:8.15.10.1872
as for mouse I have this listed in device manager: "PS/2-compatible mouse" Driver is from MS, Date:21.06.2006 Version:6.1.7600.16385
Now, only thing what is missing is the horizontal and vertical scroll function of the touchpad. Well, thats better than this annoyance...
I hope I could help a little.
- Same problem with synaptics device... code 10 this device cannot start, this only happens on Windows 7, the mouse never hangs up on vista or xp configuration (I have triple boot) this is for Inspiron 1501... Win7 has a serious problem with synaptics pointing devices that needs to be fixed ASAP.
- A little of topic but..
Does anyone else agree with me when I say that the touchpad isn't very accurate in terms of sensitivity? I was at my parents house yesterday and they have an 17" HP (don't know the model) and that touchpad was much smoother and more responsive.
I've tried both the synaptics and alps driver.
I hope this is driver related and not that they used cheap hardware.
Edit: after thoroughly reading the review at http://www.studentbuyingguide.com/2009/06/dell-vostro-1320-review/ it looks like the used cheap touchpad hardware, that sux! Guess you can't have everything :) - Update: Still no problems with the touchpad or graphics with the settings I posted above... My laptop is working 100%.
- Has anyone tried installing the new bios and THEN doing a clean windows 7 install? Perhaps that will work for some reason.
- That might do okay as a workaround, but Dell needs to come up with an actual solution. Anyone at Microsoft know the status?
- Someone on the Dell forums said that ALPS 7.5.2015.101 worked for him. He downloaded it from:
http://alps-touch-pad-driver.software.informer.com/
- I am now able to use the full functionality of the touchpad without any crashes or problems! I installed ALPS driver version 7.5.303.117 release date:24.07.2009, and now everything is working perfect. I can scroll horizontal and vertical, and adjust many other stuff in the touchpad software. How bad that many users won't see a difference after A04 cause they won't change their drivers. DELL must come up with a driver update to resolve the issue for all users..
- Where did you get that driver?
- Well, honestly, I forgot where I found it :-( I have the driver saved on the disk, but have no idea how I can upload it to a free server for other users...
I googled a bit and found two interesting other drivers. I am posting the links but bare in mind that I did not download these files before and I can not guarantee if they are what they say they are! So use at your own risk:
this one says it is version 7.5.505.309 : http://notebook.driversdown.com/notebook-drivers/Sony-VPCX111KD-notebook-Alps-Pointing-Device_127467.shtml
this one says it is version 7.5.303.105 : http://www.x-drivers.com/catalog/drivers/mice/companies/alps/models/alps_touchpad_driver/13978.html
good luck!
- Hey good news I just found the link where I got that driver.
It's from Toshiba and here is the link: http://support1.toshiba-tro.de/tedd-files2/0/tpdrv-20091015152335.zip
:-) - Thats the one that my tech guy found. Its been working fine for 2 weeks now. No problems. I am still running Bios A03. Not sure I want to update toA04. I can shut off and restart no problem. have full functionality of my ALPS touchpad.
- I am still having driver issues on my Vostro 1320 with Windows 7 32-bit. My video/graphics driver (Mobile Intel 4 Series Express Chipset) only works intermittently.
I also downloaded the new Alps driver from: http://alps-touch-pad-driver.software.informer.com/. It's version 7.5.303.117. Doesn't fix the touchpad problem.
Edit: I could not upgrade my BIOS either. I am on A03 but the A04 installer failed. It posted an error code: -144 saying that my BIOS is not flashable. No luck for me at all. - Still didn't fix my problem for me either. This is getting ridiculous. As mentioned, Dell advertised zero problems with their hardware and Windows 7. My brother is a lawyer and if a lawsuit is what's needed to finally get Dell in gear then so be it.
- I got that same issue for upgrading the BIOS on battery power. It worked fine once I plugged in, but I don't know if that's really the issue or not. I also ran the upgrade from my XP partition.
I've also tried the Alps 7.5.303.117. The only difference is that the device manager gives me error code 10 for an "Alps Pointing-device" instead of a "Dell Touchpad."
I think the funniest (at least *sad* funny) is that this hardware works beautifully in Linux but not Windows 7. I've never seen that before... - You're never supposed to attempt to do a BIOS upgrade on battery power, probably because messing it up can brick a system.
I got the same problem installing 7.5.303.117, just changing the name of the hardware with the error code.
As far as the touchpad is concerned, the hardware works fine in Windows XP and Vista, just not in Windows 7. Hahaha. Oh wow. On Dell's forum, first they replaced the word "lawsuit" with astericks. Then, they sent me an e-mail telling me that my post contained profanity and was deleted. Hahahaha!
Don't get me wrong, I love Dell, I really do. I've probably purchased about 50 PC's from them over the past two years. Any company I do consulting work for, I always insist that they use Dell because of the cost-savings associated with the Vostro line. Out of all of those PC's, the only time I ever had an issue was when one arrived with a DOA motherboard and another had a hard drive lock up after about three months. In both instances, I offered to do the replacements myself to save myself the time and Dell the expense of having to send out a technician to fix such minor issues (well, minor to me).
This isn't a question of quality, really. It's an issue involving a driver conflict with a new OS. It's a question of principles. Dell assured us that there were zero issues with their systems and Windows 7. I purchased systems for myself, a friend, and a client based on this claim. Now, I look foolish for assuring everyone that it was safe to use Windows 7 without fear of having an issue. True, I may have been overly optimistic, especially considering the issues I had with Vista when it first came out, but in in the case of Vista, I knew there was an issue when I couldn't get Adobe Reader to install. A minor issue. In the case of Windows 7, we have laptop users with touchpads that don't work and video hardware that is either disabling Aero functionality or, even worse, causing blank screens. This is a major issue. I appreciate Dell's initiative in getting a BIOS update out almost immediately, but it appears that the update was never even tested. Just as bad, it was released without insructions. Should we uninstall all touchpad and video drivers and then uninstall? Should we install the BIOS and then uninstall the touchpad and video drivers? We have no communication from Dell, and so we go through, wasting our time trying various options to try to get it to work.
And that's the real issue. How many times does a company have to go through this sort of situation before it realizes that all it needs to do is stay in communication with its customers? I mean seriously, this line has been developed specifically for small business owners. These are not the kind of people who have extensive IT staff on hand to help them figure out workarounds for these sorts of problems. This problem has been reported in brand new 15, 13, and 17 inch Vostros. At the very least, Dell needs to give us some sort of communication as to where they stand on solving this issue...
- I'm telling those who didn't get their laptops work again: Come on guys, I mean don't get me wrong but, just read the instructions and use some common sense! It says in instructions "plug the damn laptop in while updating BIOS". And furthermore, doesn't it make sense to uninstall the previous driver before installing the new one? Come on guys! Of course DELL needs to learn a lot if they want to keep their customers happy. But I mean it is the same hardware and same software: Nothing but user failure can explain why my laptop is working now and some others don't! I hope you don't get me wrong...
- OK, trying to run a BIOS update on battery was a simple oversight that was immediately corrected with no ill effects. I uninstalled the appropriate before re-installation and still have no use of the touchpad. Can you tell me anything else I did wrong? Perhaps my teeth were clenched improperly...
- That would make sense, except for the fact that there are no new drivers (aside from the BIOS update), so how exactly is asking whether we should uninstall and reinstall the exact same drivers a stupid question? Since it made no mention of doing so, then installing A04 should have fixed the problem with no further guesswork, period. I mean come on, the combination that you got to work uses a Toshiba driver! Doesn't that tell you that Dell has to get in gear with this issue if we're having to resort to look to another company for an answer to a Dell issue?
Regarding my installation question, I'm not an idiot. If you read my post you'll see that I wasn't asking whether or not to uninstall the drivers, I said that if we needed to do it, Dell should have indicated whether to do it before the installation of the new BIOS or after.
And yes, since we've tried your combination and it doesn't work, we realize that none of us know what we're doing and we all bow down to your almighty genius that allowed you to figure out the exact way to tap your feet and spin in x-amount of circles before hitting the install button. We've tried it, it doesn't work, end of story. Obviously, since it worked for you but didn't work for us, we must not know what we're doing. We'll just ignore the fact that not all systems are set up the same, such as some using integrated graphics and some using NVIDIA graphics, some using 32-bits and some using 64-bits.
You hope we don't get you wrong? Give me a break... - This problem seems to be caused by a conflict with the video driver installed as a Microsoft update. If you boot in safe mode, the Alps touchpad works every time. Boot normally, and the touchpad driver fails to load. I've been able to get my 1520 to work again by booting into safe mode and uninstalling the MS update video driver (sometimes it's listed twice). I then installed, in safe mode, the Mobile Intel 4 Series Chipset Family driver (date 12/2/2008, version 7.15.10.1608) and it works fine even after repeated reboots. Dell needs to get this confict resolved now that Windows 7 is shipping with the Vostro 1520 notebooks. The average user is not going to be satisfied with my solution.
Before I figured it out, I had a chat session with a Dell tech regarding the Vostro 1520 touchpad issue. Get this, he told me, "Currently we do not yet support hardware issues after installing Windows 7.". I told him that it's shipping with Windows 7. His reply, "For assistance with Windows 7 at this time please call our Customer care or our Pay as you need(PAYN) service at 866-507-3355". I then told him he was, "useless", and closed the chat session. What a dope. - hi, i had the same problem with my vostro 1320 using windows 7 ultimate RTM 32bit. After reading about windows defender i deactivated it, and now after 10 or more reboots i had no touchpad or vga problems. that worked for me, at least try it and if it doesn't work you can just activate it again.
- Well...I deactivated my Windows Defender and I am still receiving touchpad/graphics driver issues...
hi, i had the same problem with my vostro 1320 using windows 7 ultimate RTM 32bit. After reading about windows defender i deactivated it, and now after 10 or more reboots i had no touchpad or vga problems. that worked for me, at least try it and if it doesn't work you can just activate it again.
Been having the VGA issue on the 1520, just deactivated real time on Window Security and seems to work, touchpad and no blank screen. Dell do need to sort these issues out! Running on A04 bios.Well...I deactivated my Windows Defender and I am still receiving touchpad/graphics driver issues...
try upgrading to A04 bios- Upgrading to A04 did not work for me. After I installed it, I deleted the drivers for the video and touchpad and allowed windows to reinstall them. Still no change here.
Well...I deactivated my Windows Defender and I am still receiving touchpad/graphics driver issues...
try upgrading to A04 bios
I already said my BIOS update fails to work.- i had the same error while upgrading from A02 to A04, the problem was that i was using the notebook without the AC adapter
- I am also running on AC power.
- Proposed As Answer byBuddyg1965 Monday, November 02, 2009 2:44 PM
- I have the same issue. Just purchased a new Vostro 1520. Installed Windows7 Pro and it worked fine through all updates and software loading. After a reboot, the touchpad stopped. Thought it was related to the app install. Ultimately, I discovered this thread. In further searching, I found that Alps needs to update the driver for the touchpad. I have done all of the suggested fixes of updating the driver for the touchpad from the Dell support site (dated 4/27/09), updating the BIOS A04 (dated 10/21/09), I did system restores to a time when the touchpad did work successfully but after the reboot the touchpad did not work. I have reinstalled the touchpad driver over and over. I have found in my case, after the reboot, if the touchpad utility shows in the system tray, the touchpad will work. If it does not show, the touchpad will not work. An external usb wired or wireless mouse works all of the time regardless. I dont think there is anything wrong with the laptop at all. It appears to be an incompatable driver issue and I am firmly believing no amount of reboots, system restores, or holding the notebook upside down while standing on one foot singing the start spangled banner is going to fix this issue. Who will step up to the plate, take ownership of the issue, and resolve the problem? Dell? Microsoft? Alps? There are many frustrated people in the same situation and all are looking for an answer.