Help me identify the missing component that causes Overwatch 2 to crash

Waknah

New Member
I tested multiple games without any problem but Overwatch 2 doesn't behave the same way.
I've fiddled around with presets and tried several configurations with NTLite and I finally found something that suits me perfectly for a purely gaming and privacy oriented configuration without breaking the UX features of Windows 11 (having a triple boot I don't need Windows for anything else).
I would like to keep it that way, but there's still this hassle.
Maybe it's not even related to the components removed with NTLite but I'm posting here anyway in case someone has a clue since I tried everything I could to debug it at the environment level.
Overwatch 2 was running fine on my setup before I played with NTlite but it seems I wasn't on the 22H2 version yet.
Thanks for your help
 

Attachments

  • NTLITE_PRESET.xml
    36.9 KB
Removing a necessary component will cause an app to always crash, instead of random times.
You installed the latest NVIDIA or AMD drivers? If you have an event log error, that might help.
 
Yes I use the latest Radeon drivers, the only log file I have is this one, which I don't think is very useful, the game crash without showing any error code and the GPU drivers doesn't catch it either
 

Attachments

  • Overwatch.log
    6.9 KB
Apps may need the 3D Spatial or Dolby Atmos libraries, it doesn't hurt to keep them for compatibility.
 
I see deleted: Accessibility

I'm also deeply troubled by this game, I made this recovery package, but it doesn't work on other systems, so I don't know where it is.

I can't believe that this game has something to do with it.
 
I just did a host refresh adding 3D Spatial and dolby atmos libraries without success, the game still crashes
 
Accessibility features for disabled gamers is a recent trend in the PC game industry. Mostly because Windows provides basic services (on-screen narration, alternate input methods, haptic controllers).
 
Hello, I thought I would chime in as I have encountered this same issue, and have actually found the solution, looking at your NTLITE_PRESET.xml, you removed these components,


XML:
    <c>accessibility 'Outils d'accessibilité (Option d'ergonomie)'</c>
    <c>accessibility_narrator 'Narrateur'</c>
    <c>Microsoft.Windows.NarratorQuickStart 'Narrateur'</c>

These three have become a hard requirement for Overwatch 2 and Fortnite, causing unpredictable crashes once in game, for example, Overwatch 2 Beta I could not get in the queue at all, less than 60 seconds I would crash guarantee.

With Fortnite it was a bit more unpredictable, but I could not under any circumstance complete a single full round.

Close to desktop after 1-5 minutes no errors or messages thrown by the games or Windows anywhere.

I actually spent three days sorting this specific issue out, and I can for certain say that these are NEW "hard requirements", you simply will NOT be able to play without them, whether it's an issue with Windows or the games themselves, I don't know.

I could not find any useful information in the Overwatch or Fortnite Logs, during those three days I worked it out through a process of elimination by repeatedly restoring a system image and removing components until I found the culprits. For some reason NTLite's Host Refresh does not fully work in Win10 22H2 for me.

My own preset has 612 components removed, I went through all of them during that process and those where the ones causing issues. Again, this issue seems to be new as I have not had these issues previously with those components removed.

If you want to solve this issue for all presets, add them to your NTLite's settings.xml LockedComponents section

XML:
    <LockComponents>
        <c>accessibility</c>
        <c>accessibility_narrator</c>
        <c>Microsoft.Windows.NarratorQuickStart</c>
        <c>osk</c>
    </LockComponents>

If you want to be extra safe, add osk (On Screen Keyboard) to the list.

Note: Overwatch and Fortnite are the only two games that I have encountered this issue with.
 
These three have become a hard requirement for Overwatch 2 and Fortnite
Thanks for bringing this additional information, I just added all the accessibility features via a host refresh when in doubt but it's nice to know exactly which components are involved
 
Holy sh*t I can't believe it.

Did a Host Refresh for the new CU, and I guess I removed these Accessibility options. I've been struggling with random black screens and hard crashes in OW2. Thought it was my RAM, got new RAM. Thought it was my GPU, got a new GPU. Thought it was my DP cable, got a new cable.

Adding OW2/Fortnite as a Compatibility option would be nice!
 
OK, Fortnite should be "fixed" in next, uploading today, it was the Accessibility Tools (Ease of Access) component that I know of.
Will keep reg keys it depends on, it's not a big deal since the component is still gone if removed.

Anyone with Overwatch or Fortnite auto-closing on a start of the match, please try applying the attached REG file if you already removed Accessibility Tools, and let me know if fixed, no files needed.

If this is confirmed, maybe the anti-cheat engine (a common thread?) is a bit unprepared for the missing reg keys?
 

Attachments

  • USERControlPanelAccessibility.reg
    3.3 KB
OK, Fortnite should be "fixed" in next, uploading today, it was the Accessibility Tools (Ease of Access) component that I know of.
Will keep reg keys it depends on, it's not a big deal since the component is still gone if removed.

Anyone with Overwatch or Fortnite auto-closing on a start of the match, please try applying the attached REG file if you already removed Accessibility Tools, and let me know if fixed, no files needed.

If this is confirmed, maybe the anti-cheat engine (a common thread?) is a bit unprepared for the missing reg keys?
I confirm that these registry entries allow OW2 to execute without issues on a system in which the game closed itself.
 
I confirm that these registry entries allow OW2 to execute without issues on a system in which the game closed itself.
Do let me know if the newer NTLite causes the same issue on removals, it should not.
 
Back
Top