I had been running MCE 2005 using a single (original) XBOX as a wireless
extender and it worked fine.
I just purchased an XBOX 360 to use as a second wireless extender.
I went to WWW.XBOX.COM/PCSETUP to obtain the latest MCE 2005 software to
support the XBOX 360.
The download page performed some detection and displayed the following
This computer is running Update Rollup 2 for Windows XP Media Center
You can enjoy all of the Media Center experiences through your Xbox
I proceeded to download XboxMCELite-ENU.exe and then ran it to install
the software. All appeared to be going well and, in fact, both the original
XBOX and the new XBOX 360 worked great as MCE extenders.
However, the initiation of either an XBOX or an XBOX 360 extender session
always spawns a new process which the Task Manager shows is a serious
At initialization the task performs about 2 or 3 minutes of intensive
hard disk Reads after which it stops all of it's IO activity. It then
immediately proceeds to enter an infinite CPU loop.
The process image name is WMCCDS.EXE which is part of WMC2 (Windows
Media Connect V2.0).
The version of the WMCCDS.EXE executable is 5.1.2600.2771 and was
apparently compiled on October 06, 2005.
The process is part of service WMConnectCDS, the Windows Media Connect
It appears that WMC2 was installed earlier this year on my copy of MCE
2005 and so is presumably not new software that was somehow introduced as
part of the new XBOX 360 PCSETUP process mentioned above. Perhaps WMCCDS.EXE
is encountering some incompatibility issue with the software that got
installed via XboxMCELite-ENU.exe.
My understanding is that Windows Media Connect is involved in streaming
media files to household media devices such as extenders. It IO scanning
at initialization is probably part of it's effort to detect, collect
information on and then share media folders. I have no problem with that but
the 100% CPU saturation has got to go.
I've performed some experiments and my extender functionality does not
seem to be adversely affected when I explicitly SUSPEND CPU dispatching for
the process using Process Explorer. Cancelling the process is fruitless
since the extender startup process unrelentlessly forces it's restart.
My questions are:
1. Has anyone else had this problem?
2. Does anyone know of a way to get a more recent version of WMCCDS.EXE
that might address the CPU loop issue?
3. Can I disable or delete WMCCDS.EXE? What are the extender related
consequences of doing so?