• Windows Live is FUCKED
    9 replies, posted
This has been an issue I have had for as long as I can remember and I only had to really care about it after I got back to using my PC again instead of my laptop. For starters, I'm running XP Pro, SP3. Anyways, after you login, windows gives "this program has encountered an error and will have to close" bullshit and clicking OK merely logs you out. Generaly I can ignore it by just hiding the error window off the screen. What really grinds my gears though is that it's not handling my friends right. For some it will see them, for others it says they do not exist. You can still talk to your nonexistant friends if they talk to you first but you can't do shit like transfer files...or even add them to your friends list. If I login to Live from my laptop (again, XP pro SP3), everything works and I can see everyone. Even if I'm logged in from both systems at the exact same time, the laptop sees everyone, the PC does not. Okay, so I asume that this was a corrupt install so I uninstall Live and reinstall and THE PROBLEMS ARE STILL THERE. I'm assuming that the installer from Microsoft is not fucked so what gives? If bad comes to worse, I can use an alternate messenger but it needs to support a decent numbers of features (including display pictures, video chat, multiple login locations, file transferring, etc.)
I tried to get windows live to work on fallout 3 for fucking hours, gave up after a while.
Downloaded a skill pack for dead rising 2. Still hasn't showed up.
I prefer Steam though Windows Live supports chatting to XBL users (which is most of my friends)
The majority of the people I know don't have an XBL account, let alone a 360.
If all else fails, you can always use a program like aMSN to chat to your friends. Microsoft programs can be very buggy, unfortunately
Open your Event log:[url]http://support.microsoft.com/kb/308427[/url] Look in the "Application section", post anything relating to Live.
Try using pidgin.
I tried pidgin. It's garbage. Anyways, I checked the logs, low and behold: [code]Faulting application wlcomm.exe, version 14.0.8117.416, faulting module kernel32.dll, version 5.1.2600.5781, fault address 0x00009eda. [/code] ...thi is no more helpful that the old Windows bluescreens.
[QUOTE=MIPS;25588783]I tried pidgin. It's garbage. Anyways, I checked the logs, low and behold: [code]Faulting application wlcomm.exe, version 14.0.8117.416, faulting module kernel32.dll, version 5.1.2600.5781, fault address 0x00009eda. [/code] ...thi is no more helpful that the old Windows bluescreens.[/QUOTE] Google is your friend, use it.
Sorry, you need to Log In to post a reply to this thread.