I fixed the problem problems I was experiancing with WMDC 6.1 and am now
running with WMDC Version 6.0, which runs flawlessly.

Since I installed the the Windows Mobile Device Centre 6.1 update the well
functioning connectivity with my Dell Axim X51 (with WM5) was destroyed and I
got two error messages - one that svchost.exe has closed down and one that
the Windows mobile 2003 based devices service had closed down. These events
occurred when I tried to connect the device in its USB cradle.

When the upgrade ran, the first thing it did was to install an unknown
device (at first this took ages but after various tries this goes faster now
in
the preconfigured folders.)

On a Vista Blog I read a suggestion that it might be an idea to try
uninstalling the upgrade (WMDC) and the boot and re-install the package. I
tried this many times and there was No change. I tried then uninstalling and
then installing each of two previous upgrades I still had - one from December
and one from February. No change.

I had been using my Dell Axim on XP and on Vista since the betas and RCs and
now have the commercial Ultimate Vista. There have been issues along the way
with various versions of the OS – mainly that there was never an automatic
upgrade when these were available and needed ( you had to hunt for them or
find references to them on blogs and newsgroups).

Several months went by......

I was getting very frustrated by these lengthy problems and tried:


1. every possible combination of uninstalling and reinstalling either the
6.1 Driver Update or the Device Center etc. etc. and have tried going back to
version 6.0, which had worked fine, to no avail.

2. I tried establishing a new Administrator account and tried installing the
version 6.1 updates there - to no avail.

3. I observe that the C:\Windows\WindowsMobile folder is populated with a
number of files and one folder ([en-US]) that I cannot remove. These are all
owned by Windows Trusted Installer. I try finding a way of taking ownership
of these files/folders to remove them - to no avail.

4. After backing up my PIM data to the SD card, a hard boot of my Dell Axim
Device and a re-install of WM5. While it was time
consuming to re-establish my settings, it had no influence on my ability to
sync. I attempted a re-install of WMDC Version 6.1 without luck.

5. I uninstalled my Belkin Bluetooth F8T009 dongle as that seemed to be
having problems as the PDA started with Bluetooth running ( I
don't use the Bluetooth). I suddenly could delete some of the locked files
in the Windows Mobil folder. I attempted a re-install of WMDC
Version 6.1 without luck.


But, this is what worked:

I found a program named Unlocker 1.8.5 at

UNLOCKER 1.8.5 BY CEDRICK 'NITCH' COLLOMB
which gave me the ability to unlock

and delete the locked files in the Windows Mobil folder. After doing
so I now attempted to re-install the WMDC Version 6.0, still available on
the Microsoft website, which had worked fine. After the usual legthy delay it
installed the "unknown device" UMBus enumerator ( why isn't this just
included?) and found Pocket PC at Windows Update and we were in business
again! [If anyone has the Belkin Bluetooth F8T009 dongle I suggest
uninstalling and reinstalling it before doing the above.]


What a relief!!!


I think I will keep using Version 6.0 for the foreseeable future! I don't
want to experience this sort of heartache again!

Axim X51 [520mhz]

I've had a similar problem using an Ipaq 4150 that worked flawless under WMDC 6.0
Did more or less the same you did...nothing worked. I was about to go back to 6.0 when I found this file ceappmgr.exe under c:/Windows/mobile.
Starting it resulted in an error message 'device not connected' even so the Ipaq was hooked up all the time. I turned off the Ipaw off and on again....and wouldn't u believe it....the WMDC pops up, find the Ipaq and everything is just fine.
I can't explain it - and frankly I'm too scared to mess it up again trying to confirm this. I'm however pretty sure that this is in some way related to the ceappmgr as i tried everything in the book, connected and disconnected the device numerouse times without luck.