Keeping things in perspective, this was never a Games for Windows -- LIVE issue, it was a problem that was addressed like several other products by the Windows development team.
If you are seeing errors with Halo 2 for Windows Vista, such as 'Failed to Initialize LIVE', then this kb below should be your next step in resolving your issue. However, if the error still persist, for whatever reason, then you should contact Windows Support for assistance as this update is supported by them.
http://support.microsoft.com/KB/976264
As for the manul steps below, they were a spin off from the exact same issue occuring wtih folks running dedicated servers on Windows Server 2003, they have also been proven to work with Vista and Win 7; However, its a last resort approach and should be avoided unless the above patch fails to resolve your Halo 2 for Windows Vista problems.
http://support.microsoft.com/kb/941208
If you continue to expereince problems with this error and Halo 2, then you should contact the support number provided in the manual specific to your country.
----------------------------------------------------------------------------------------------------------------------------------------------------
Here is the following troubleshooting steps I have done and so far have worked for me and a few friends
try the following:
Run Command Prompt (run as Administrator):
Type: net stop cryptsvc and hit enter
You will receive a message stating that the service was stopped.
Navigate to your LocalDrive:/Windows/System32 and rename the "catroot2" folder to "cr2old"
Once it is renamed, go back to command prompt and run this command: net start cryptsvc which will restart the Cryptographic Services:
The above steps may work, however I have noticed that if it does when you exit to the desktop then try to relaunch or reboot the PC the error may come back. If this is true then the steps below have been so far successful.
1. Delete all the tmp*.cat files in the following folders (use the search option on the top right corner of the screen to find and delete the files):
%systemroot%\system32\CatRoot\{127D0A1D-4EF2-11D1-8608-00C04FC295EE} (there may be no files in this folder if that’s the case then only worry about the next folder)
%systemroot%\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} (if no items are found then go to the next step)
2. Delete all the kb*.cat files in the following folders (use the search option on the top right corner of the screen to find and delete the files):
%systemroot%\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} ( A pop up will ask that you need admin rights to delete, accept and delete, you may notice that they were deleted however still appear, if you refresh the screen they will be gone)
%systemroot%\System32\CatRoot\{127D0A1D-4EF2-11D1-8608-00C04FC295EE} (again skip if there is no files in the folders)
3. Delete all the oem*.* files from the %systemroot%\inf folder. (again use the search option on the top right hand corner of the screen to find and delete the files)
4. At the command prompt (Run as Administrator), type the following commands. Press ENTER after each command.
A) net stop cryptsvc
B) Next, Navigate to your LocalDrive:/Windows/System32 and delete the renamed Catroot2 folder we made previously and keep the “Catroot2” file
C) ren %systemroot%\System32\Catroot2 oldcatroot2
D) net start cryptsvc
Exit Command Prompt
5. Run halo 2
This should run successfully, even after exiting and re-launching halo 2 as well as after a reboot. Hopefully this helps and Please post back with results, as i'm sure the Mods would like to know the outcome
Your Greatest Strength is
Your Greatest Weakness
Check out Fraggs.net for the lastest news in gaming (podcast and store included)
Deadblow's suggestion works. I done all the steps and now I can play Halo 2 again with no errors.
My post rating rules....
If you 1 star me you love me, if you 5 star me you still love me and anything between, you just like me.
AMAZING! ive been with this thread from the start and this finaly works :D
Thanks Allot man!!!
A much needed solution for people. Thank you Deadb0w you can take pride in your work
even tho you found the answer, its still a issue with in windows 7 and GFW's software, and it needs to be adress. I do thank you for finding a walk around but this is a temp and shouldn't be taken as a perm-fix.
but thanks again.
Thank you very much. I did follow youradvice with the second part. I did not find any of the files that you mentioned. I guess thats good for me. Maybe when I deleted the "cr2old" file that did the trick because it would not work before that. Again a big thank you.
Stickied and split due to popular demand. Again I want to thank everyone for their patience and help in the work around.
GFWLMod:Again I want to thank everyone for their patience and help in the work around.
Hey Mod, don't you think Deadblow deserves direct credit as he spent weeks looking for a solution to this issue! Let's here it for deadblow!
3 cheers and all that, what?
eastmanblues:Deadb0w
You mean Deadblow right? Yeah I knew you did.....
Additional confirmation: I reread Deadblow's post and followed the instructions. I screwed up and deleted *.cat in the first catroot folder instead of just tmp*.cat and kb*.cat and it still worked. The game can be a bit choppy when strafing and turning at the same time, but otherwise perfect.
what do you mean by the:
tmp*
kb*
oem*
sorry if you get mad
all the files look like this:
$RXQB41E
how do i know if it is a kd* or a tmp* or a oem*?
Please help, i want to play halo 2.
Kabs195: what do you mean by the: tmp* kb* oem* sorry if you get mad
The * symbol in relation to a filename, for those that aren't as schooled on computing lingo as those in the know are, serves as a wildcard match for... well, practically anyting. It could stand for one or more numers or letters or any other symbol (so long as it doesn't cross paths with specifically reserved characters so a slash, backslash, vertical bar or double quote symbol would be against the rules as they are used only in specific command console operations much like the * symbol itself). Examples which could theoretically appear in this particular instace include kb459884918, tmp84564a848e and oem2285accdsre.
As a further example, *.* is much like calling everyone out of the pool in that it can provide an exact match to everything that falls within the boundaries of it's use. For the example in question it could mean oem111111111111111.aaa, oem999999999999999.zzz, and everything in between. In fact, when *.* is used by itself, it literally means everything (as in aaaaaaaaaaaaaaaaaaaaaaaaaa.aaa to 99999999999999999999999999.999 or similar).
well all the files look similar to this:
$R1XGLXX
what is this?