I got the same error just now when I started my M18. Was working fin yesterday.

Same here. Working last night, failed on startup this AM

I have an M17x R4 and this is the error I am getting on every boot.  Any solutions?     System.Runtime.InteropServices.COMException (0x80010002): Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))    at System.Management.ThreadDispatch.Start()    at System.Management.ManagementScope.Initialize()    at System.Management.ManagementEventWatcher.Initialize()    at System.Management.ManagementEventWatcher.Start()    at AlienLabs.AlienFX.DeviceDiscovery.Classes.DeviceWatcherClass.StartHidDeviceInsertedWatcher()    at AlienLabs.AlienFX.DeviceDiscovery.Classes.DeviceWatcherClass.Start()    at AlienLabs.AlienFX.DeviceDiscovery.Classes.AlienFXDeviceDiscoveryService.RegisterForDevicesEvents()    at AlienLabs.AlienFX.DeviceDiscovery.ObjectFactory.NewAlienFXDeviceDiscovery()    at AlienLabs.AlienFX.Tools.Classes.ObjectFactory.get_DiscoveryService()    at AlienLabs.AlienFX.Tools.Classes.ObjectFactory.NewAlienFXDeviceRepository()    at AlienLabs.AlienFX.Tools.Classes.ObjectFactory.get_AlienFXDeviceRepository()    at AlienLabs.AlienFX.Controller.LightsZoneController..ctor()    at AlienLabs.AlienFX.Controller.ControllerMainForm.initializeLightController()    at AlienLabs.AlienFX.Controller.ControllerMainForm..ctor()    at AlienLabs.AlienFX.Controller.Program.Main(String[] args)

Same here. Working last night. Failed on startup this AM.

Went to Safe Mode. Restored to 9/14 Critical update. Problem wenaway.  Microsoft strikes again?

I experienced the exact same issue yesterday.  I called Dell Support and they did a system restore to the Critical update on 9/15.  I worked all night (since I had lost a day trying to correct the issue) and shut down.  When I booted up this morning, the issue resumed.  Dell Support thought that it was a Bios issue, but I think it has more to do with Command Center; at least that's what my research has revealed.

Hello!

I will recommend you to uninstall the command center, do a BIOS up date and then reinstalled the command center again, that might help you.  

I'm on bios version: Voyager MLK (M17R4) BIOS A12

Is that the latest version?  I also reintalled command center yesterday and it didn't help.

Got the same problem on my M14 R2 this morning, was working fine when i went to bed. When i started up i was unable to open the Alienware Command Center, MSE, Google Chrome, my start menu or anything so uninstalling wasn't an option. I started up in safe mode and did a system restore to a few days ago and it's working fine now, curious as to why this is happening though.

Yes you can try doing a system restore or doing an Alienrespawn 

This post is just speculation on my part, but I'm not getting any answers from Dell. They have always been very secretive about the embedded Alienware hardware/software tech ... so I can only guess.

It seems that Command Center (as it loads and initializes on startup) is stepping on some Microsoft Process and/or Service. It could also be a Dell pre-loaded Process/Service. Might even have something to do with poor coding in CC being revealed in .Net platform layer (due to recent update).

It's similar to this problem:

http://en.community.dell.com/owners-club/alienware/f/3746/t/19497146.aspx

There are also bundled drivers in CC. Whether it's a laptop (MIO circuit) or desktop (MIO Board) there are drivers that silently load into OS (in a strange, fairly unconventional way). These drivers seem to sneak into OS under this WHQL compatibility testing procedure (and allow it to load without alert or error)

http://msdn.microsoft.com/en-us/library/windows/hardware/ff553976(v=vs.85).aspx

Due to the behaviors described here:

http://en.community.dell.com/owners-club/alienware/f/3746/t/19497146.aspx

Microsoft would never approve it.

Shocking I have this exact same problem from last night working fine to this morning not working at all.  Must be something like a virus or something but I have the same exact issues as everyone else