XHN SCRAPY Posted April 16, 2012 Report Share Posted April 16, 2012 http://forums.xbox.c...95/t/13827.aspx THIS IS A REFERENCE FROM GAMES FOR WINDOWS FORUMS*** Possibly Sticky this??? DEADBL0W: 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 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 Second: Guardian Hope: Halo 2 PC Windows 7 Fix Many users have faced the "LIVE Gaming for Windows failed to initialize" error message in Halo 2 PC and/or Shadowrun . The solution offered to fix it in this thread http://forums.gamesforwindows.com/t/8958.aspx (see above) helped for some users but buried within the thread are several key posts which are evidentially the solution to resolve the issue for Halo 2 on Windows 7 and why the far more complicated fix in the previously mentioned thread works in the first place. It can also be noted that the solution offered by Microsoft in a compatibility update for Windows 7 doesn't fully address the issue either. Below is exactly how to resolve this issue, copied from the previously mentioned thread which is now cluttered with 17 pages and in its depths, the solution as well. Applies To Windows 7 x64 Systems Windows 7 x86 Systems (Possibly, haven't heard of an x86 user with problems) Symptoms When starting Halo 2 PC (and Shadowrun), users receive the error "LIVE Gaming for Windows failed to initialize..." and are unable to start Halo 2 or Shadowrun. Cause The cause is one or more OEM files located in the C:\Windows\INF directory. The OEM file that causes the problem to arise is different on every computer and as a result, one user's OEM file that caused the problem may not be the same on another user's. Solution You will need to narrow down the file that is causing the problem on your PC as this is user specific. The recommended procedure is to move half of the OEM files to another directory to see if Halo 2 starts. If it does, you need to start moving some of the OEM files back until you get the error, then narrow it down to the one or multiple OEM files that are causing the problem. Delete the problematic OEM file(s) causing your problem once located. Notes The OEM file(s) causing the problem will not be the same on all systems (mine was OEM21.inf, another use had OEM94.inf and OEM95.inf as the problem files). There is at least one but can be multiple files causing the problem. The .PNF files do not seem to cause the problem. However, you may remove the .PNF file of the OEM file(s) cause your problem if you so wish to be on the safe side. I recommend that you run Windows 7 in "test mode" if you haven't already done so just in case any driver signing issues arise from messing with the "INF" folder. Users - Once you find the OEM file(s) causing your problem, open them to see what exactly they are for. It may be a good idea to see if we can narrow it down to a particular device/driver. For example, my problematic OEM file was for atiilhag.dll and had a special note that it was modified with Mobility Modder.NET. Or you could run the monstrmoose patch which is essentially Deadbl0w's fix in an executable file -http://www.monstrmoose.com/download.php?f=H2VWin7Fix.exe If, and I mean IF you use the executable, it is a non-reversable fix, though most likely not damaging, there have been reports of sound and other hardware no longer functioning without reinsalling that hardware happening to a few users. If you do the manual fix, I personally suggest moving one file at a time to accomplish this, sure it's slow, tedious work, but you will be able to weed out the single file that is causing your issue, and as a result, leaving in place other files that may be of some importance to the functioning of your system. UPDATE: MICROSOFT APPLICATION COMPATIBILITY FIX This fix helps many users with some of these problems discussed, while not a 100% fix for everyone, it is working for a lot of people. Download it HERE UPDATE: Unable to initialize Live for Windows Components UPDATE: For some who are having the game crash with the error 'Unable to initiliaze Live for Windows components' and the logs report that the faulting module is xlive.dll try deleting that file (xlive.dll) from the Shadowrun directory (C:\Program Files (x86)\Microsoft Games\Shadowrun) only and then restart the game, this IS working for some people as a solution. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.