Windows Mobile Remote Adapter Failed
- Windows Mobile Remote Adapter Failed Update
- Windows Mobile Remote Adapter Failed Windows 10
- Windows Mobile Remote Adapter Failed Windows 7
- Windows Mobile Remote Desktop
- Windows Mobile Remote Adapter
- Windows Mobile Remote Adapter Failed Download
- Windows Mobile Remote Adapter Failed Windows 10
One of your computer's NetBIOS names is already registered on the remote network. !Note Deprecated in Windows Vista and later versions of Windows. ERRORSERVERGENERALNETFAILURE 643: A network adapter at the server failed. !Note Deprecated in Windows Vista and later versions of Windows. WARNINGMSGALIASNOTADDED 644.
-->The following Routing and Remote Access (RRAS) API error codes are defined in raserror.h. All error codes are supported in Windows 2000 or later versions of Windows unless specified otherwise.
Android 4 4 2 download. Android 4.4.2 free download - Fortnite, Android 6.0 Marshmallow, Android 5.0 Lollipop, and many more programs.
Apr 21, 2012 As a windows mobile programmer I have to fight with ActiveSync aka Windows Mobile Device Center. The newer WM devices come with enhanced network function via USB ActiveSync/WMDC and then each time a new device is connected, you will get a new Mobile Remote Adapter with a new number at the end. Capsule Cloud Connector fails with Reason 'Failed to load virtual network adapter'. The Cloud Connector VNA(Virtual Network Adapter) is missing from the adapter list on Windows. This is due to the fact that even though the 'Windows Mobile-based device' fails to install, I still end up with a 'Microsoft Windows Mobile Remote Adapter #x' in the network adapters list with a 169.254.2.2 IP address. Koyote soft free mp3 wma converter. On Windows 10, Microsoft introduced a new Remote Desktop app, which you can download from the Windows Store, and it aims to make it easier for anyone to connect to another computer over a local.
| Return code/value | Description |
|---|---|
| An operation is pending. |
| The port handle supplied is not valid. |
| The specified port is already open. |
| The buffer supplied is too small. |
| The port information specified is incorrect. |
| The port information specified cannot be set.[!Note] |
| The port specified is not connected. |
| An event that is not valid was detected.[!Note] |
| The specified device does not exist. |
| The specified device type does not exist. |
| The buffer supplied is not valid. |
| A route was specified that is not available.[!Note] |
| The specified route is not allocated. |
| The specified compression is not valid.[!Note] |
| There were insufficient buffers available. |
| The specified port was not found. |
| An asynchronous request is pending. |
| The specified port or device is already disconnecting. |
| The specified port is not open. |
| The specified port is disconnected. |
| No endpoints could be determined.[!Note] |
| Cannot open the specified phone book file. |
| Cannot load the specified phone book file. |
| Cannot find the specified phone book entry. |
| Cannot write to the specified phone book file. |
| Information found in the specified phone book is not valid. |
| A string could not be loaded.[!Note] |
| Cannot find the specified key. |
| The specified port was disconnected. |
| The specified port was disconnected by the remote computer. |
| The specified port was disconnected due to hardware failure. |
| The specified port was disconnected by the user. |
| Incorrect structure size. |
| The specified port is already in use or is not configured for remote access dial-out. |
| Your computer could not be registered on the remote network.[!Note] |
| An unknown error has occurred. |
| The wrong device is attached to the specified port. |
| A string was detected that could not be converted.[!Note] |
| The request has timed out. |
| No asynchronous net is available.[!Note] |
| An error has occurred involving NetBIOS.[!Note] |
| he server cannot allocate NetBIOS resources needed to support the client.[!Note] |
| One of your computer's NetBIOS names is already registered on the remote network.[!Note] |
| A network adapter at the server failed.[!Note] |
| You will not receive network message popups.[!Note] |
| An internal authentication error has occurred. |
| The specified account is not permitted to log in at this time of day. |
| The specified account is disabled. |
| The specified password has expired. |
| The specified account does not have remote access permissions. |
| The remote access server is not responding.[!Note] |
| Your modem or other connection device has reported an error. |
| An unrecognized response was returned by the device. |
| A macro required by the device was not found in the device .INF file section. |
| A command or response in the device .INF file section refers to an undefined macro. |
| The |
| The |
| The device .INF file could not be opened. |
| The device name in the device .INF or media .INI file is too long. |
| The media .INI file refers to an unknown device name. |
| The device .INF file contains no responses for the command. |
| The device .INF file is missing a command. |
| Attempted to set a macro not listed in device .INF file section. |
| The media .INI file refers to an unknown device type. |
| Cannot allocate memory. |
| The port is not configured for remote access. |
| Your modem or other connection device is not functioning. |
| Cannot read the media .INI file. |
| The connection was dropped. |
| The usage parameter in the media .ini file is not valid. |
| Cannot read the section name from the media .INI file. |
| Cannot read the device type from the media .INI file. |
| Cannot read the device name from the media .INI file. |
| Cannot read the usage from the media .INI file. |
| The system was unable to read the maximum carrier connection speed from the media .INI file.[!Note] |
| Cannot read the usage from the media .INI file. |
| The line is busy. |
| A person answered instead of a modem. |
| There is no answer. |
| Cannot detect a carrier signal. |
| There is no dial tone. |
| The modem (or other connecting device) reported a general error.[!Note] |
| There was an error in writing the section name. |
| There was an error in writing the device type. |
| There was an error in writing the device name. |
| There was an error in writing the maximum connection speed. |
| There was an error in writing the maximum carrier speed. |
| There was an error in writing the usage. |
| There was an error in writing the default-off. |
| |
| The media .INI file is empty. |
| Access denied because the user name, password, or both is not valid on the domain. |
| A hardware failure has occurred in the port or attached device |
| The macro is not a binary macro. |
| DCB not found. |
| State machines are not started. |
| State machines are already started. |
| Partial response looping. |
| A response key name in the device .INF file is not in the expected format. |
| The device response caused a buffer overflow. |
| The expanded command in the device .INF file is too long. |
| The device moved to a connection speed that is not supported by the COM driver. |
| Device response received when none expected. |
| An error occurred because the interactive mode is enabled. |
| A bad callback number was specified. |
| The specified authentication state is not valid. |
| An error occurred when writing the initial connection speed.[!Note] |
| An X.25 diagnostic indication was received. |
| The specified account has expired. |
| An error occurred while attempting to change the password on the domain. |
| Serial overrun errors were detected while communicating with your modem. |
| RasMan initialization failure. Check the event log. |
| The two-way port is initializing. Wait a few seconds and redial.[!Note] |
| No active ISDN lines are available. |
| No ISDN channels are available to make the call.[!Note] |
| Too many errors occurred because of poor phone line quality.[!Note] |
| The remote access IP configuration is unusable. |
| No IP addresses are available in the static pool of remote access IP addresses. |
| A PPP timeout occurred. |
| The connection was terminated by the remote computer.[!Note] |
| No PPP control protocols are configured. |
| The remote PPP peer is not responding. |
| The PPP packet is not valid. |
| The phone number, including the prefix and suffix, is too long. |
| The IPX protocol cannot dial out on the modem (or other connecting device) because this computer is not configured for dialing out (it is an IPX router).[!Note] |
| The IPX protocol cannot dial in on the modem (or other connecting device) because this computer is not configured for dialing in (the IPX router is not installed).[!Note] |
| The IPX protocol cannot be used for dial-out on more than one port at a time. |
| Cannot access TCPCFG.DLL.[!Note] |
| Cannot find an IP adapter bound to remote access. |
| SLIP cannot be used unless the IP protocol is installed. |
| Computer registration is not complete.[!Note] |
| The specified protocol is not configured. |
| The PPP negotiation is not converging. |
| the PPP control protocol for the specified network protocol is not available on the server. |
| The PPP link control protocol was terminated. |
| The requested address was rejected by the server. |
| The remote computer terminated the control protocol. |
| Loopback detected. |
| The server did not assign an address. |
| The remote server cannot use the Windows NT encrypted password. |
| The TAPI devices configured for remote access failed to initialize or were not installed correctly. |
| The local computer does not support encryption. |
| The remote server does not support encryption. |
| The remote computer requires data encryption.[!Note] |
| The system cannot use the IPX network number assigned by the remote computer. Additional information is provided in the event log.[!Note] |
| The Session Management Module (SMM) is not valid.[!Note] |
| The SMM is uninitialized.[!Note] |
| No MAC for port.[!Note] |
| The SMM timed out.[!Note] |
| A bad phone number was specified. |
| The wrong SMM was specified.[!Note] |
| The callback number contains a character that is not valid. Only the following 18 characters are allowed: 0 to 9, T, P, W, (, ), -, @, and space.[!Note] |
| A syntax error was encountered while processing a script. |
| The connection could not be disconnected because it was created by the multi-protocol router. |
| The system could not find the multi-link bundle. |
| The system cannot perform automated dial because this connection has a custom dialer specified. |
| This connection is already being dialed. |
| RAS could not be started automatically. Additional information is provided in the event log. |
| Internet Connection Sharing (ICS) is already enabled on the connection.[!Note] |
| An error occurred while the existing Internet Connection Sharing settings were being changed.[!Note] |
| An error occurred while routing capabilities were being enabled.[!Note] |
| An error occurred while Internet Connection Sharing was being enabled for the connection.[!Note] |
| An error occurred while the local network was being configured for sharing.[!Note] |
| Internet Connection Sharing cannot be enabled. There is more than one LAN connection other than the connection to be shared.[!Note] |
| No smart card reader is installed. |
| Internet Connection Sharing cannot be enabled. A LAN connection is already configured with the IP address that is required for automatic IP addressing. |
| A certificate could not be found. Connections that use the L2TP protocol over IPSec require the installation of a machine certificate, also known as a computer certificate. |
| Internet Connection Sharing cannot be enabled. The LAN connection selected as the private network has more than one IP address configured. Please reconfigure the LAN connection with a single IP address before enabling Internet Connection Sharing. |
| The connection attempt failed because of failure to encrypt data. |
| The specified destination is not reachable. |
| The remote computer rejected the connection attempt. |
| The connection attempt failed because the network is busy. |
| The remote computer's network hardware is incompatible with the type of call requested. |
| The connection attempt failed because the destination number has changed. |
| The connection attempt failed because of a temporary failure. Try connecting again. |
| The call was blocked by the remote computer. |
| The call could not be connected because the remote computer has invoked the Do Not Disturb feature. |
| The connection attempt failed because the modem or other connection device on the remote computer is out of order. |
| It was not possible to verify the identity of the server. |
| To dial out using this connection you must use a smart card.[!Note] |
| An attempted function is not valid for this connection. |
| The encryption attempt failed because no valid certificate was found.[!Note] |
| Connection Sharing (NAT) is currently installed as a routing protocol, and must be removed before enabling Internet Connection Sharing. |
| Internet Connection Sharing cannot be enabled. The LAN connection selected as the private network is either not present, or is disconnected from the network. Please ensure that the LAN adapter is connected before enabling Internet Connection Sharing. |
| You cannot dial using this connection at login time because it is configured to use a user name different than the one on the smart card. If you want to use this connection at login time, you must configure it to use the user name on the smart card. |
| You cannot dial using this connection at login time because it is not configured to use a smart card. If you want to use it at login time, you must edit the properties of this connection so that it uses a smart card. |
| The L2TP connection attempt failed because there is no valid machine certificate on your computer for security authentication. |
| The L2TP connection attempt failed because the security layer could not authenticate the remote computer. |
| The L2TP connection attempt failed because the security layer could not negotiate compatible parameters with the remote computer. |
| The L2TP connection attempt failed because the security layer encountered a processing error during initial negotiations with the remote computer. |
| The L2TP connection attempt failed because certificate validation on the remote computer failed. |
| The L2TP connection attempt failed because security policy for the connection was not found. |
| The L2TP connection attempt failed because security negotiation timed out. |
| The L2TP connection attempt failed because an error occurred while negotiating security. |
| The Framed Protocol RADIUS attribute for this user is not PPP. |
| The Tunnel Type RADIUS attribute for this user is not correct. |
| The Service Type RADIUS attribute for this user is neither Framed nor Callback Framed. |
| A connection to the remote computer could not be established because the modem was not found or was busy. |
| A certificate could not be found that can be used with the Extensible Authentication Protocol (EAP). |
| Internet Connection Sharing (ICS) cannot be enabled due to an IP address conflict on the network. ICS requires the host be configured to use 192.168.0.1. Ensure that no other client on the network is configured to use 192.168.0.1.[!Note] [!Note] |
| Unable to establish the VPN connection. The VPN server may be unreachable, or security parameters may not be configured properly for this connection. [!Note] |
| This connection is configured to validate the identity of the access server, but Windows cannot verify the digital certificate sent by the server.[!Note] |
| The card supplied was not recognized. Please check that the card is inserted correctly, and fits securely.[!Note] |
| The PEAP configuration stored in the session cookie does not match the current session configuration.[!Note] |
| The PEAP identity stored in the session cookie does not match the current identity.[!Note] |
| You cannot dial using this connection at login time because it is configured to use the currently-logged-in user's credentials.[!Note] |
| A connection between your computer and the VPN server has been started, but the VPN connection cannot be completed. The most common cause for this is that at least one Internet device (for example, a firewall or a router) between your computer and the VPN server is not configured to allow Generic Routing Encapsulation (GRE) protocol packets.[!Note] |
| The network connection between your computer and the VPN server was interrupted. This can be caused by a problem in the VPN transmission and is commonly the result of internet latency or simply that your VPN server has reached capacity. Try to reconnect to the VPN server.[!Note] |
| The network connection between your computer and the VPN server could not be established because the remote server refused the connection. This is typically caused by a mismatch between the server's configuration and your connection settings.[!Note] |
| The network connection between your computer and the VPN server could not be established because the remote server is not responding. This could be because one of the network devices (for example, firewalls, NAT, routers) between your computer and the remote server is not configured to allow VPN connections.[!Note] |
| A network connection between your computer and the VPN server was started, but the VPN connection was not completed. This is typically caused by the use of an incorrect or expired certificate for authentication between the client and the server.[!Note] |
| The network connection between your computer and the VPN server could not be established because the remote server is not responding. This is typically caused by a pre-shared key problem between the client and server. A pre-shared key is used to guarantee you are who you say you are in an IP Security (IPSec) communication cycle.[!Note] |
| The connection was prevented because of a policy configured on your RAS/VPN server. Specifically, the authentication method used by the server to verify your username and password may not match the authentication method configured in your connection profile.[!Note] |
| You have attempted to establish a second broadband connection while a previous broadband connection is already established using the same device or port.[!Note] |
| The underlying Ethernet connectivity required for the broadband connection was not found.[!Note] |
| The broadband network connection could not be established on your computer because the remote server is not responding. This could be caused by a value that is not valid for the 'Service Name' field for this connection.[!Note] |
| A feature or setting you have tried to enable is no longer supported by the remote access service.[!Note] |
| Cannot delete a connection while it is connected.[!Note] |
| The Network Access Protection (NAP) enforcement client could not create system resources for remote access connections. Some network services or resources might not be available.[!Note] |
| The Network Access Protection Agent (NAP Agent) service has been disabled or is not installed on this computer. Some network services or resources might not be available.[!Note] |
| The Network Access Protection (NAP) enforcement client failed to register with the Network Access Protection Agent (NAP Agent) service. Some network services or resources might not be available.[!Note] |
| The Network Access Protection (NAP) enforcement client was unable to process the request because the remote access connection does not exist.[!Note] |
| The Network Access Protection (NAP) enforcement client did not respond. Some network services or resources might not be available.[!Note] |
| The Crypto-Binding type-length-value (TLV) received is not valid.[!Note] |
| Crypto-Binding TLV was not received.[!Note] |
| Point-to-Point Tunneling Protocol (PPTP) is incompatible with IPv6. Change the type of virtual private network to Layer Two Tunneling Protocol (L2TP).[!Note] |
| EAPTLS validation of the cached credentials failed. Discard cached credentials.[!Note] |
| The L2TP/IPsec connection cannot be completed because the IKE and AuthIP IPSec Keying Modules service and/or the Base Filtering Engine service is not running. These services are required to establish an L2TP/IPSec connection.[!Note] |
| The connection was terminated because of idle timeout.[!Note] |
| The modem (or other connecting device) was disconnected due to link failure.[!Note] |
| The connection was terminated because user logged off.[!Note] |
| The connection was terminated because user switch happened.[!Note] |
| The connection was terminated because of hibernation.[!Note] |
| The connection was terminated because the system got suspended.[!Note] |
| The connection was terminated because Remote Access Connection manager stopped.[!Note] |
| The L2TP connection attempt failed because the security layer could not authenticate the remote computer. This could be because one or more fields of the certificate presented by the remote server could not be validated as belonging to the target destination.[!Note] |
| The machine is not NAP capable.[!Note] |
| Invalid Tunnel ID.[!Note] |
| Another update connection request is in progress. RAS allows only one update connection request at a time.[!Note] |
| Negotiating using configured protocol is disable. Edit connection properties and select different protocol for negotiation and try again.[!Note] |
| Internal address negotiation failed.[!Note] |
| Client has to request an Internal IPv4 or IPv6 address.[!Note] |
| Traffic Selectors negotiation failed.[!Note] |
| Mobility is disabled for this connection.[!Note] |
| The VPN Connection is still connecting or re-authenticating because of Quarantine state change. Initiate mobile update only when connection state is 'Connected'.[!Note] |
| Server rejected client authentication, due to unexpected TLV or value mismatch for a TLV.[!Note] |
| Either VPN destination preference is not selected by the user or it is no longer valid.[!Note] |
| Cached smart card credential is invalid.[!Note] |
| VPN connection attempt failed due to internal error occurred while adding cookies to the Secure Socket Tunneling Protocol (SSTP). Please see the System Event Log for the detailed information. |
| The PEAP inner method attribute(s) stored in the cookie is/are invalid. |
| The Extensible Authentication Protocol type required for authentication of the remote access connection is not installed on your computer. |
| The Extensible Authentication Protocol type configured on the remote access connection does not support single sign-on. |
| The Extensible Authentication Protocol type configured on the remote access connection does not support the requested operation. |
| The remote access connection completed, but authentication failed because the certificate that authenticates the client to the server is not valid. Ensure that the certificate used for authentication is valid. |
| The remote access connection completed, but authentication failed because the certificate that authenticates the client to the server is expired. Renew the certificate. |
| The remote access connection completed, but authentication failed because the certificate that authenticates the client to the server is revoked. Use a certificate that has not been revoked. |
| The remote access connection completed, but authentication failed because of an error in the certificate that authenticates the client to the server. |
| The remote access connection completed, but authentication failed because the certificate that the client uses to authenticate the server is not valid. |
| The remote access connection completed, but authentication failed because the certificate that the client uses to authenticate the server is expired. |
| The remote access connection completed, but authentication failed because the certificate that the client uses to authenticate the server is revoked. |
| The remote access connection completed, but authentication failed because of an error in the certificate that the client uses to authenticate the server. |
| The remote access connection completed, but authentication failed because a trusted root certificate that validates the user certificate was not found in the Trusted Root Certification Authorities certificate store. |
| The remote access connection completed, but authentication failed because the trusted root certificate that is used to validate the user certificate is not valid. |
| The remote access connection completed, but authentication failed because the certificate in the Trusted Root Certification Authorities certificate store that authenticates the user certificate is expired. Renew the certificate. |
| The remote access connection completed, but authentication failed because a certificate that validates the server certificate was not found in the Trusted Root Certification Authorities certificate store. |
| The remote access connection completed, but authentication failed because the certificate in the Trusted Root Certification Authorities certificate store that validates the server certificate is not valid. |
| The remote access connection completed, but authentication failed because the certificate on the server computer does not have a server name specified. |
| The PEAP outer identity is not same as the inner identity when identity privacy is turned OFF. |
| The remote connection was not made because the name of the remote access server did not resolve. |
| The password provided for the certificate is not valid. |
| The interface could not be enabled because more than one interface with the same destination has been created with the pre-shared key authentication method. Change the destination/auth method and enable the interface. |
The following Routing and Remote Access (RRAS) API error codes are defined in mprerror.h. All error codes are supported in Windows 2000 or later versions of Windows unless specified otherwise.
| Return code/value | Description |
|---|---|
| The router is not running. |
| The interface is already connected. |
| The specified protocol identifier is not known to the router. |
| The Demand-dial Interface Manager (DDM) is not running. |
| An interface with this name is already registered with the router. |
| An interface with this name is not registered with the router. |
| The interface is not connected. |
| The specified protocol is stopping. |
| The interface is connected and hence cannot be deleted. |
| The interface credentials have not been set. |
| This interface is already in the process of connecting. |
| An update of routing information on this interface is already in progress. |
| The interface configration is not valid. There is already another interface that is connected to the same interface on the remote router. |
| A Remote Access Client attempted to connect over a port that was reserved for routers only. |
| A Demand Dial Router attempted to connect over a port that was reserved for Remote Access Clients only. |
| The client interface with this name already exists and is currently connected. |
| The interface is in a disabled state. |
| The authentication protocol was rejected by the remote peer. |
| There are no authentication protocols available for use. |
| The connection could not be established because the authentication protocol used by the RAS/VPN server to verify your username and password could not be matched with the settings in your connection profile. |
| The remote account does not have Remote Access permission. |
| The remote account has expired. |
| The remote account is disabled. |
| The remote account is not permitted to logon at this time of day. |
| Access was denied to the remote peer because the user name, password, or both is not valid on the domain. |
| There are no routing enabled ports available for use by this demand dial interface. |
| The port has been disconnected due to inactivity. |
| The interface is not reachable at this time. |
| The Demand Dial service is in a paused state. |
| The interface has been disconnected by the administrator. |
| The authentication server did not respond to authentication requests in a timely fashion. |
| The maximum number of ports allowed for use in the multi-linked connection has been reached. |
| The connection time limit for the user has been reached. |
| The maximum limit on the number of LAN interfaces supported has been reached. |
| The maximum limit on the number of Demand Dial interfaces supported has been reached. |
| The maximum limit on the number of Remote Access Clients supported has been reached. |
| The port has been disconnected due to the Bandwidth Allocation Protocol (BAP) policy. |
| Because another connection of your type is in use, the incoming connection cannot accept your connection request. |
| No RADIUS servers were located on the network. |
| The response received from the RADIUS authentication server was not valid. Make sure that the case sensitive secret password for the RADIUS server is set correctly. |
| You do not have permission to connect at this time. |
| You do not have permission to connect using the current device type. |
| The connection could not be established because the authentication method used by your connection profile is not permitted for use by an access policy configured on the RAS/VPN server. Specifically, this could be due to configuration differences between the authentication method selected on the RAS/VPN server and the access policy configured for it. |
| BAP is required for this user. |
| The interface is not allowed to connect at this time. |
| The saved router configuration is incompatible with the current router. |
| Remote Access has detected older format user accounts that will not be migrated automatically. |
| The transport is already installed with the router. |
| The signature length received in a packet from RADIUS server is not valid.[!Note] |
| The signature received in a packet from RADIUS server is not valid.[!Note] |
| Did not receive signature along with EAPMessage from RADIUS server.[!Note] |
| The length or Id received in a packet from RADIUS server is not valid.[!Note] |
| The length received in a packet with attribute from RADIUS server is not valid.[!Note] |
| The packet received from RADIUS server in not valid.[!Note] |
| Authenticator does not match in packet from RADIUS server.[!Note] |
| Routing and Remote access server is either not configured or not running.[!Note] |
Requirements
| Minimum supported client | Windows 2000 Professional [desktop apps only] |
| Minimum supported server | Windows 2000 Server [desktop apps only] |
Hello,
My Windows 7 x64 laptop (Win 7x64 Pro) fails to install the 'Windows Mobile-based device driver' component of WMDC.
I have installed WMDC , uninstalled, reinstalled, uninstalled, reinstalled. Unplugged, re-plugged, un-plugged, Many times.
I have been a mobile applications developer for many years, and I have a dozen or so Windows-CE-based devices (CE5, CE6, WM5, and WM6.1, and WM6.5) from various mobile device manufacturers. NONE of them will connect to this PC, yet ALL of them will readily connect to my other Win7x64 PC that is setup the same as this one.
I have been using this PC since 2009, and previously have had no problems syncing mobile devices to it. I started experiencing the problem a few months ago. I have been struggling with this, continuously searching for answers for months.
As far as updates, KBs and SPs,
- I have Windows Update turned on and I use it frequently,
- SP1 is installed,
- all updates to-date have been installed.
Windows Mobile Remote Adapter Failed Update
I have followed instructions from numerous discussion groups suggesting such things as
- deleting INFCACHE.1 and letting it get recreated,
- uninstalling the problem device from device manager, waiting, reinserting,
- tried uninstalling the 'Root USB Hub' and letting it reinstall.
- verified 'TrustedInstaller' is owner of registry keys
- tried checking and un-checking the 'enhanced' ActiveSync checkbox,
- tried USB RNDIS mode, USB Serial mode, and Bluetooth.
- tried to no avail a total of 10 different mobile devices ranging from CE5, CE6, PPC2003, WM5, WM6.1, and WM6.5 with a whole slew of USB cables and cradles
- Tried all 3 USB ports on the laptop, AND tried 2 different USB HUBs
- I am NOT running an Antivirus program, although I regularly scan with the latest MalwareBytes scanner
- Firewall is OFF
- Installed, uninstalled, repaired the WMDC install countless times
- rebooted, powered off and re-tried all of the above countless times.
- read every WMDC troubleshooting guide I can find on the Internet
I have checked and verified that the following services start and are running (I have started and stopped them countless times)
- COM+ Event System
- DCOM Server Process Launcher
- DHCP Client
- Remote Procedure Call (RPC)
- UPnP Device Host
- Windows Mobile 2003-baased device connectivity
- Windows Mobile based device connectivity
I have also tried to sync/connect from both USB and Bluetooth.
USB (both RNDIS and Serial) and Bluetooth get very far into the driver install process, and each connection method installs other devices except the device called 'Windows-mobile-based device'
Even though WMDC fails to connect and sync, If I connect using the USB RNDIS driver or Bluetooth (but not the USB Serial driver), enough of the driver subsystem is installed so that I can still use Visual Studio Remote Tools (Remote Process Viewer, Remote Registry Editor, etc).
Even SOTI Pocket Controller Pro is able to connect to the device while it is in this state using its 'ActiveSync' connection path.
Visual Studio 2008 device manager is able to connect, and my project executables can deploy, and I can even debug them. Platform Manager seems to be working fine.
This is due to the fact that even though the 'Windows Mobile-based device' fails to install, I still end up with a 'Microsoft Windows Mobile Remote Adapter #x' in the network adapters list with a 169.254.2.2 IP address.
The ONLY thing that cannot connect to any device is WMDC itself.
I have included a snippet of (what I hope to be) the relevant section of setupapi.devices.log from this evening's session of futile attempts to solve this on my own.
There must be a solution to this that does not involve wiping and reinstalling Windows. I will not even consider that as a last resort.
Please HELP!
Thank you,
Mike
setupapi.devices.log
ndv: Installing device..
dvi: {DIF_INSTALLDEVICE} 21:31:45.204
dvi: CoInstaller 1: Enter 21:31:45.204
inf: Opened PNF: 'C:WindowsINFoem31.inf' ([strings])
dvi: CoInstaller 1: Exit
dvi: Class installer: Enter 21:31:46.475
dvi: {Install DEVICE}
inf: Opened PNF: 'c:windowssystem32driverstorefilerepositorywpdrapi.inf_amd64_neutral_a093053dd72737ebwpdrapi.inf' ([strings])
dvi: Processing Registry/Property directives..
inf: {Install Inf Section [WINDOWSMOBILE_WPD_DEVICE.NT]}
inf: 12,UMDF,wpdrapi2.dll,1 (wpdrapi.inf line 68)
inf: Processing REGISTERDLLS section [WPDRAPIDRIVER_COMMON.RegisterComServers]. Module: '%12%UMDFwpdrapi2.dll', flags: 0x0001, timeout: 300s, Arguments: '(null)'.
inf: Calling 'DllRegisterServer' in OLE Control 'C:Windowssystem32DRIVERSUMDFwpdrapi2.dll' succeeded.
inf: {Install Inf Section [WINDOWSMOBILE_WPD_DEVICE.NT] exit (0x00000000)}
inf: {Install Inf Section [WINDOWSMOBILE_WPD_DEVICE.NT.Hw]}
inf: AddReg=WPDRAPIDRIVER_COMMON.AutoPlayRegistration (wpdrapi.inf line 45)
inf: {Install Inf Section [WINDOWSMOBILE_WPD_DEVICE.NT.Hw] exit (0x00000000)}
dvi: {Writing Device Properties}
dvi: Provider name=Microsoft Corporation
dvi: DriverDate 05/31/2007
dvi: DriverVersion=6.1.6965.0
dvi: Class name=WPD
dvi: Manufacturer=(Standard Windows Mobile devices)
dvi: Matching DeviceID=tcpipwindows_mobile_device
dvi: Strong Name=oem31.inf:Microsoft.NTamd64:WINDOWSMOBILE_WPD_DEVICE:6.1.6965.0:tcpipwindows_mobile_device
dvi: {Writing Device Properties - Complete}
inf: {Install Inf Section [WINDOWSMOBILE_WPD_DEVICE.NT.Services]}
inf: AddService=WUDFRd,0x000001fa,WUDFRD_ServiceInstall (wpdrapi.inf line 48)
inf: ServiceType=1 (wpdrapi.inf line 79)
inf: StartType=3 (wpdrapi.inf line 80)
inf: ErrorControl=1 (wpdrapi.inf line 81)
inf: ServiceBinary=C:Windowssystem32DRIVERSWUDFRd.sys (wpdrapi.inf line 82)
dvi: Add Service: Modified existing service 'WUDFRd'.
inf: {Install Inf Section [WINDOWSMOBILE_WPD_DEVICE.NT.Services] exit(0x00000000)}
dvi: Updated reflected section names for: oem31.inf
dvi: {Install DEVICE exit (0x00000000)}
dvi: Writing common driver property settings.
dvi: DriverDescription=Windows Mobile-based device
Windows Mobile Remote Adapter Failed Windows 10
dvi: DeviceDisplayName=Windows Mobile-based devicedvi: Install Device: Restarting device. 21:31:46.745
dvi: Install Device: Restarting device completed. 21:31:47.035
!!! dvi: Device not started: Device has problem: 0x1f: CM_PROB_FAILED_ADD.
dvi: Class installer: Exit
dvi: CoInstaller 1: Enter (Post Processing) 21:31:47.061
dvi: CoInstaller 1: Exit (Post Processing)
Windows Mobile Remote Adapter Failed Windows 7
dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 21:31:47.137
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 21:31:47.137
dvi: CoInstaller 1: Enter 21:31:47.138
dvi: CoInstaller 1: Exit
dvi: Class installer: Enter 21:31:47.139
Windows Mobile Remote Desktop
dvi: Class installer: Exitdvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0x00000000)} 21:31:47.149
Windows Mobile Remote Adapter
Windows Mobile Remote Adapter Failed Download
ndv: Device install status=0x00000000ndv: Performing device install final cleanup..
! ndv: Queueing up error report since device has a PnP problem..