Yep I identified that issue. I can run the game using Windows Sandbox for now. Getting the wheels moving in the IT department is difficult.
Hey Guys just FYI, my ticket is still hanging at asking them if they can push this update to the current version rather than keep it the maintenance release considering many people are effected and the maintenance release resolves it. I’m waiting eagerly for their reply.
2 Likes
Thank you for the update
Had IT push me the update 20 min ago. I’ll have an answer to if it worked for sure or not in about 2 hours or so (update pushing time). As of now it’s still a maintenance release still, but according to the company that manages my copy of sophos there is a way to specify the MR for one person if you’re running an enterprise copy.
I’m a Sophos partner and I’ve been testing different settings for this. I was able to get Classic working again by adding an Exploit Mitigation exception.
https://community.sophos.com/intercept-x-endpoint/f/recommended-reads/117960/sophos-intercept-x-how-to-exclude-applications-from-exploit-mitigation-functionality
If your local Sophos is running tamper protection and you don’t have admin rights, you’ll need to contact whomever manages your Sophos environment for assistance.
I’m still working on getting retail working again. I’ll provide an update if I get it identified. I have opened a case with Sophos Partner Support to investigate further.
Edit: TY Elocin for the tip. 
Edit 2: I have retail working now. It took rebooting after putting in the exploit mitigation and it started working again. My other computer had an issue with starting the cinematic in Classic (I had attempted to reinstall WoW) and it was being hung up by Windows Defender. I disabled it, started it up which worked, restarted Defender and it was still able to launch. I reinstalled the Sophos client and everything still worked. For me the resolution was a specific Exploit Mitigation for each of the main WoW executables and a reboot as described above.
TLDR: For Sophos Endpoint users, add Exploit Mitigations (following the instructions linked above) for the main WoW executables and reboot.
2 Likes
Paste the link, highlight, and click </> on the post editor.
1 Like
Why can’t the just update the whole system with the maintenance update.
Thanks for all the help team, canceled my sub this morning.
Hopefully updates get pushed soon
Hey, Im a sophos partner as well, the problem is asking people to add that exception themselves or them asking their IT department to add the exception for them.
Also, I just got off the phone with Sophos, they do not have an ETA for when the changes to hitmanpro.alert will be incorporated into the standard version. Until then you can follow this guide to change your release to the Maintenance Release ending in MR.
We follow the below steps to add the software package(FTS).
- Go to Sophos Central → Global Settings → Software package → Click (Add Software) → Copy the Software token from the shared article(1db71707-9ceb-5a43-833f-2599a9133c76) . → Click Save.
- Go to Sophos Central → Server/ Endpoint Protection → Policies → Add Policies( Update Management) → Settings → Windows (Add latest software package) Details of Packages.
***** If you click the links below you have change the “(dot)” in the address to a “.” ****
Please refer to the below article for the Software package.
Software packages - Sophos Central Admin
Please refer to the below article for software tokens(Sophos Central Intercept X Maintenance Release ).
Sophos Central Intercept X Maintenance Release
Please refer to the below article for Update management policy.
Update Management Policy - Sophos Central Admin
Create or Edit a Policy - Sophos Central Admin
1 Like
This worked great, but I am the Sophos admin. The funny realization to me was how many people on this thread just called themselves out for playing at work and using work equipment to do it. But hey, I am there with you.
here you go:
1 Like
I was intensely curious about this. Asking one of my end-user systems administrators to add an exception to the endpoint protection tools for a game would be volunteering to no longer be employed at my current concern.
4 Likes
My wow crashes on launch. Blizzard error pops up.
I have tried full delete and reinstalling (several times), deleting folders, scan and repair, renew internet dchp, reset router, -windowed (and another code which also did not work and so both are removed again), and pretty much every suggestion I could find.
Sometimes if I am persistent enough, it will let me log in, but it will still crash the next time I try to load the game after exiting.
Not sure if it matters but I am on a low pop server too. and I do not use sophos or any work related computer apps. There is basically nothing on this computer.
You should start a separate thread with your diagnostic files. The players in this thread are using Sophos.
1 Like
Yeah, been going on for the past 2 days for me. My BattleNet launcher is not blacked out anymore but the game fails to launch. It gives me this Error Code:
Error: ACCESS VIOLATION - The instruction at “0c000007ffa8953eba7” referenced memory at “0x0000000000000008” The memory could not be “read” ProcessID: 9748 ThreadID: 6440. Press OK to terminate the application.
It also gave me this error code:
11D01585-C252-4FE1-BBA5-E06939DBA93E
I checked the game installation and uninstalled and reinstalled WoW. It still no worky.
mine’s not launching either. launcher comes up fine, game won’t.
I’ve also had issues. Tried everything in book. Uninstalled all versions of WoW then reinstalled, Battle.new, installed new drivers, reinstalled the new drivers, undid overlays, looked into launching in all ways, Reset game settings, updated all my other desktop drivers, even turned off all my startup apps / background applications to see if that was issue. I’m completely lost. Likely going to cancel my subscription and pick up a new game if this isn’t fixed in a few days.
If you’re not using Sophos:
Players in the forums can’t read those codes from the error window.
1 Like
There is an issue with Sophos? Is this going to fixed in a patch or do I need to do something with them?
Really? 
Most of this thread is about the Sophos issue, especially once everyone realized it was the common factor. Nothing Blizzard adds in a patch will change the interaction with the Sophos software; the update needs to come from Sophos. This was discussed a bunch, read the thread.
3 Likes