Problem loading apache driver on Vista

[latemasterd]

Problem: Error in loading "Microsoft Windows Mobile Remote Adapter" states that "The required device registry key does not exist."

Device: xv6700 with WM6.1 from PPCkitchen.org
Computer: Vista Business with WMDC 6.1

Things that I have tried:
-uninstalled driver in Device manager, plugged back in, same error
-uninstalled and reinstalled windows mobile device center 6.1; same error
-tried reverting to windows mobile device center 6.0; same error
-uninstalled wmdc, ended all mobile program in task manager, stopped the two mobile device services, plugged in phone and still failed.
-unchecked "enable advanced network connections" on phone under Settings/System/USB-to-PC, plugged back in, and it loaded "Microsoft USB Sync" as the driver. This did not interface with WMDC or allow me to sync at all, despite the driver loading successfully.
-turned off firewall, still error
-hard reset device; same error
-tried on other vista pc, and it worked just fine. problem therefore lies in the pc.

Any ideas as to what could be causing this? This computer was just fine before, now all of a sudden the driver wont load. I REALLY dont feel like reformatting my PC (especially since it still might not eliminate the problem). From researching online, it appears to be an issue for other phones as well.

[gambatte]

I've been following that same thread in Windows Mobile Forum. So you have never been able to make a WMDC connection? I've got a similar setup, e.g. Vista Business SP1 and XV6700 but I'm running WM6, and it works fine. I wonder if you ran a reg cleaner? Let me know if you want me to compare a reg key or something...

[cbarret1]

How do you run a reg cleaner, I have my 6700 stuck in bootloader mode in vista business too

[gambatte]

That wouldn't help you. If ur stuck in bootloader, read through this post:
http://forum.ppcgeeks.com/showthread.php?t=33471

It is not a reg problem but a ROM flashing problem.

[latemasterd]

I just tried a registry cleaner - didn't fix it. I might be on to something - if you open C:/Windows/inf/setupapi.dev.log it has a record of the installations... I don't know if it means anything to anyone in this forum but here is the record of the latest failed installation.

>>> [Finish Install Wizard - USB\VID_0BB4&PID_0B02\35373633-3831-4131-3800-0050BF3F5173]
>>> Section start 2008/08/02 17:04:31.518
dvi: {Build Driver List} 17:04:31.518
! dvi: Driver list already built
dvi: {Build Driver List - exit(0x00000000)} 17:04:31.519
dvi: {DIF_SELECTBESTCOMPATDRV} 17:04:31.519
dvi: CoInstaller 1: Enter 17:04:31.519
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 17:04:31.520
dvi: CoInstaller 2: Exit
dvi: CoInstaller 3: Enter 17:04:31.520
dvi: CoInstaller 3: Exit
dvi: Class installer: Enter 17:04:31.521
dvi: Class installer: Exit
dvi: Default installer: Enter 17:04:31.522
dvi: {Select Best Driver}
dvi: Selected driver installs from section [WINMOBIL] in 'c:\windows\system32\driverstore\filerepository\wc erndis.inf_d847fb09\wcerndis.inf'.
dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
dvi: {DIF_DESTROYPRIVATEDATA} 17:04:31.524
dvi: CoInstaller 1: Enter 17:04:31.524
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 17:04:31.525
dvi: CoInstaller 2: Exit
dvi: CoInstaller 3: Enter 17:04:31.525
dvi: CoInstaller 3: Exit
dvi: Class installer: Enter 17:04:31.526
dvi: Class installer: Exit
dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 17:04:31.527
dvi: Set selected driver complete.
dvi: Selected:
dvi: Description - [Microsoft Windows Mobile Remote Adapter]
dvi: InfFile - [c:\windows\system32\driverstore\filerepository\wce rndis.inf_d847fb09\wcerndis.inf]
dvi: Section - [WINMOBIL]
dvi: Signer - [microsoft windows hardware compatibility publisher]
dvi: Rank - [0x0dff2000]
dvi: {Select Best Driver - exit(0x00000000)}
dvi: Default installer: Exit
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 17:04:31.530
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 17:04:31.566
dvi: Using exported function 'NetClassInstaller' in module 'C:\Windows\system32\NetCfgx.dll'.
dvi: Class installer == NetCfgx.dll,NetClassInstaller
dvi: Using exported function 'NciDeviceInstall' in module 'C:\Windows\system32\nci.dll'.
dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
dvi: Using exported function 'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'.
dvi: CoInstaller 2 == wlaninst.dll,WlanDeviceClassCoInstaller
dvi: CoInstaller 1: Enter 17:04:31.575
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 17:04:31.576
dvi: CoInstaller 2: Exit
dvi: Class installer: Enter 17:04:31.576
!!! dvi: Class installer: failed(0xe0000204)!
!!! dvi: Error 0xe0000204: The requested device registry key does not exist.
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe0000204)} 17:04:31.577
<<< Section end 2008/08/02 17:07:00.335
<<< [Exit status: FAILURE(0xe0000204)]


If you open C:/Windows/inf/setupapi.dev.log it says the following for the same installation:

>>> [DIF_SELECTBESTCOMPATDRV - USB\VID_0BB4&PID_0B02\35373633-3831-4131-3800-0050BF3F5173]
>>> Section start 2008/08/02 17:04:13.869
cmd: rundll32.exe C:\Windows\system32\newdev.dll,pDiDeviceInstallAct ion \\.\pipe\PNP_Device_Install_Pipe_1.{7109723e-c050-4944-ae02-8ce5c716ac1d} "USB\VID_0BB4&PID_0B02\35373633-3831-4131-3800-0050bf3f5173"
dvi: CoInstaller 1: Enter 17:04:13.869
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 17:04:13.870
dvi: CoInstaller 2: Exit
dvi: CoInstaller 3: Enter 17:04:13.870
dvi: CoInstaller 3: Exit
dvi: Class installer: Enter 17:04:13.871
dvi: Class installer: Exit
dvi: Default installer: Enter 17:04:13.871
dvi: {Select Best Driver}
dvi: Selected driver installs from section [WINMOBIL] in 'c:\windows\system32\driverstore\filerepository\wc erndis.inf_d847fb09\wcerndis.inf'.
dvi: Class GUID of device remains: {4d36e972-e325-11ce-bfc1-08002be10318}.
dvi: Set selected driver complete.
dvi: Selected:
dvi: Description - [Microsoft Windows Mobile Remote Adapter]
dvi: InfFile - [c:\windows\system32\driverstore\filerepository\wce rndis.inf_d847fb09\wcerndis.inf]
dvi: Section - [WINMOBIL]
dvi: Signer - [microsoft windows hardware compatibility publisher]
dvi: Rank - [0x0dff2000]
dvi: {Select Best Driver - exit(0x00000000)}
dvi: Default installer: Exit
<<< Section end 2008/08/02 17:04:13.875
<<< [Exit status: SUCCESS]

ndv: Device Install failed for new device...installing NULL driver.

>>> [DIF_DESTROYPRIVATEDATA - USB\VID_0BB4&PID_0B02\35373633-3831-4131-3800-0050BF3F5173]
>>> Section start 2008/08/02 17:07:00.336
cmd: rundll32.exe C:\Windows\system32\newdev.dll,pDiDeviceInstallAct ion \\.\pipe\PNP_Device_Install_Pipe_1.{7109723e-c050-4944-ae02-8ce5c716ac1d} "USB\VID_0BB4&PID_0B02\35373633-3831-4131-3800-0050bf3f5173"
dvi: CoInstaller 1: Enter 17:07:00.336
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 17:07:00.337
dvi: CoInstaller 2: Exit
dvi: Class installer: Enter 17:07:00.338
dvi: Class installer: Exit
<<< Section end 2008/08/02 17:07:00.338
<<< [Exit status: SUCCESS]

You can see where it decides to load the standard "Unknown Device" driver at the end...that driver is successful.

[gambatte]

Don't know if the text was copied faithfully but there is a difference in this one directory line:

dvi: Selected driver installs from section [WINMOBIL] in 'c:\windows\system32\driverstore\filerepository\wc erndis.inf_d847fb09\wcerndis.inf'.

and


dvi: InfFile - [c:\windows\system32\driverstore\filerepository\wce rndis.inf_d847fb09\wcerndis.inf]

\wce rndis.inf_d847fb09\ and \wc erndis.inf_d847fb09

Looked on my Vista Business but it is a different number at the end and no space. IDK if it means anything....

Looked through my device log and there is a CoInstaller 3 that you have to go through. You only seem to get 2 to finish.

[latemasterd]

Could you post or message to me the correct log file? Also, any chance i could get C:\Windows\system32\wlaninst.dll from you? I have a guess that mine might have become corrupted...who knows. It's worth a shot.

[gambatte]

OK. PM me you email addy. It's too big to post here. Also, remember I have SP1.

[latemasterd]

New development today - I turn on my computer and there is suddenly a "Recommended update" from vista for the Mobile Remote Adapter...it says it was released 9/14/07, so I should have already had this...nonetheless it was there this morning.

It fails on installation with error code 800F0204, which of course has no corresponding help page or explanation anywhere on microsoft's website. Even if there was, it would probably say "error code 800F0204: update could not be installed" or something equally pointless.

[gambatte]

I think I read that when the driver fails to install, you either have it already or a "better" version is installed. So your driver must be really messed up, e.g. it is acting like it isn't there (hence the driver update is offered to you) but it is there (e.g. the installer fails). LOL.