EDIT EDIT: Finally solved my problem. Mods can lock this thread!
Solution: Spybot was preventing my game from launching. Uninstalling Spybot fixed my issue!
I have been encountering a similar problem with launching my game. As soon as the anti cheat loads it gives me an error code and crashes. my error code is slightly different than yours however.
MCC-Win64-Shipping.exe - Entry Point Not Found
The procedure entry point EventSetInformation could not be located in the dynamic link library ADVAPI32.dll.
What is your OS? I am running win 7 X64.
I have my steam client installed on a separate partition from my os and being that for me the error has something to do with the dynamic link library, I thought it may be relevant information.
Having reviewed the known MCC bug list, I did not find your issue as a part of the known issues. I would encourage you to file a support ticket here:
https://support.halowaypoint.com/hc/en-us/articles/360037448411-Halo-Reach-PC-Known-Issues-12-3-19
> 2533274848076320;2:
> I have been encountering a similar problem with launching my game. As soon as the anti cheat loads it gives me an error code and crashes. my error code is slightly different than yours however.
>
> MCC-Win64-Shipping.exe - Entry Point Not Found
> ---------------------------
> The procedure entry point EventSetInformation could not be located in the dynamic link library ADVAPI32.dll.
>
> What is your OS? I am running win 7 X64.
> I have my steam client installed on a separate partition from my os and being that for me the error has something to do with the dynamic link library, I thought it may be relevant information.
>
> Having reviewed the known MCC bug list, I did not find your issue as a part of the known issues. I would encourage you to file a support ticket here:
> https://support.halowaypoint.com/hc/en-us/articles/360037448411-Halo-Reach-PC-Known-Issues-12-3-19
I am running Windows 10 x64
My OS is also separated from my Steam library. Windows is on my SSD while my Steam Libary is on an HDD.
However, I feel like the issue is with the EAC itself, rather than MCC itself. I remembered I have 7 Day to Die in my library as well, which also uses EAC. EAC will not launch with 7DtD as well with the same error.
> 2533274843239163;3:
> > 2533274848076320;2:
> > I have been encountering a similar problem with launching my game. As soon as the anti cheat loads it gives me an error code and crashes. my error code is slightly different than yours however.
> >
> > MCC-Win64-Shipping.exe - Entry Point Not Found
> > ---------------------------
> > The procedure entry point EventSetInformation could not be located in the dynamic link library ADVAPI32.dll.
> >
> > What is your OS? I am running win 7 X64.
> > I have my steam client installed on a separate partition from my os and being that for me the error has something to do with the dynamic link library, I thought it may be relevant information.
> >
> > Having reviewed the known MCC bug list, I did not find your issue as a part of the known issues. I would encourage you to file a support ticket here:
> > https://support.halowaypoint.com/hc/en-us/articles/360037448411-Halo-Reach-PC-Known-Issues-12-3-19
>
> I am running Windows 10 x64
>
> My OS is also separated from my Steam library. Windows is on my SSD while my Steam Libary is on an HDD.
>
> However, I feel like the issue is with the EAC itself, rather than MCC itself. I remembered I have 7 Day to Die in my library as well, which also uses EAC. EAC will not launch with 7DtD as well with the same error.
That is quite interesting. Have you tried running event viewer during the launch of the MCC?
Something I noticed when I tried that was that Easy anti cheat had an issue during launch involving “Bits”
> 2533274848076320;4:
> > 2533274843239163;3:
> > > 2533274848076320;2:
> > > I have been encountering a similar problem with launching my game. As soon as the anti cheat loads it gives me an error code and crashes. my error code is slightly different than yours however.
> > >
> > > MCC-Win64-Shipping.exe - Entry Point Not Found
> > > ---------------------------
> > > The procedure entry point EventSetInformation could not be located in the dynamic link library ADVAPI32.dll.
> > >
> > > What is your OS? I am running win 7 X64.
> > > I have my steam client installed on a separate partition from my os and being that for me the error has something to do with the dynamic link library, I thought it may be relevant information.
> > >
> > > Having reviewed the known MCC bug list, I did not find your issue as a part of the known issues. I would encourage you to file a support ticket here:
> > > https://support.halowaypoint.com/hc/en-us/articles/360037448411-Halo-Reach-PC-Known-Issues-12-3-19
> >
> > I am running Windows 10 x64
> >
> > My OS is also separated from my Steam library. Windows is on my SSD while my Steam Libary is on an HDD.
> >
> > However, I feel like the issue is with the EAC itself, rather than MCC itself. I remembered I have 7 Day to Die in my library as well, which also uses EAC. EAC will not launch with 7DtD as well with the same error.
>
> That is quite interesting. Have you tried running event viewer during the launch of the MCC?
> Something I noticed when I tried that was that Easy anti cheat had an issue during launch involving “Bits”
Looking at Event Manager all I get (at least under “System” events) are these three events (two when launching MCC with EAC and then when it fails to load)
1a.) A service was installed in the system.
Service Name: EasyAntiCheatSys
Service File Name: C:\Program Files (x86)\EasyAntiCheat\EasyAntiCheat.sys
Service Type: kernel mode driver
Service Start Type: demand start
1b.) File System Filter ‘EasyAntiCheatSys’ (6.1, 2019-11-15T02:34:04.000000000Z) has successfully loaded and registered with Filter Manager.
2.) File System Filter ‘EasyAntiCheatSys’ (Version 6.1, 2019-11-15T02:34:04.000000000Z) unloaded successfully.
Though I do notice that it creates a folder for the EAC in C drive when all my games are on my D drive. When I delete this folder (just for a test), EAC fails to launch saying it is not installed. Then I have to repair/install it from MCC’s folder; which adds another EAC folder to the C drive. I don’t know if that has anything to with it.
I just want to bump this up to say that EAC support finally contacted me and found the reason why EAC was having problems:
Spybot.
I had to uninstall Spybot to get it to work and IT WORKED. I can finally play the game with EAC!
If Spybot is blocking EAC from running, that means EAC is spyware… in other words it is not there to prevent cheating, it is there to spy on you, which is very dishonest and immoral of 343. This is right up there with xigncode3 which is Chinese spyware in the form of “anti cheat” for a lot of Korean games.
Problem Im having is that the game will load then go through the EAC and then give me a error message. “Game Security Violation Detected (#0000000D) {SelledV2.exe}” is what comes up on my screen. According to Xbox support its a known Issue with my Motherboard itself which I find very odd. Anyone know of a workaround for this issue? Motherboard is a gigabyte B450 AORUS M, CPU is AMD Ryzen 5 2600X 3.6ghz 6 core 12 thread, RAM Corsair Vengence LPX 3000mhz DDR4 RAM.
> 2535451696919519;8:
> Problem Im having is that the game will load then go through the EAC and then give me a error message. “Game Security Violation Detected (#0000000D) {SelledV2.exe}” is what comes up on my screen. According to Xbox support its a known Issue with my Motherboard itself which I find very odd. Anyone know of a workaround for this issue? Motherboard is a gigabyte B450 AORUS M, CPU is AMD Ryzen 5 2600X 3.6ghz 6 core 12 thread, RAM Corsair Vengence LPX 3000mhz DDR4 RAM.
did u find a solution? i have the same problem, cannt launch the game, and it crashes my pc. tomahawk b450, r5 2600