F11 (or tab'ing in and out) crashes packaged shipping game

In UE 4.17.2
Pressing F11 crashes a packaged shipping game (online multiplayer) for almost every gametester that have been on Windows 10.
This is a pretty serious issue so I am posting this report since I found nothing in the issue tracker, and in an attempt to find a workaround or hotfix for the problem.

Personally I’ve never experienced any crashes from within the UE4 editor when pressing F11, and use it regularly.
(I’m using Windows 7)
I’ve only had a shipping build crash once or twice pressing it, but I now release builds with windowed-borderless as default to help Windows 10 users to avoid crashing when tabbing out of the application, this atleast never crashes the game build on my computer, but pressing F11 still crashes the game for many Windows 10 users.

I suspect this is a driver related issue. Have anyone found anything out?
Any advice is appreciated.

I would love to hear what can cause this issue. I’m using a huge for loop in tick and if this loops gets 2 big (talking about 10k), my editor can also crash when spamming F11.

Hello ,

I ran a few tests on our end and I was unable to reproduce this issue. I have a few questions for you that will help narrow down what issue it is that you are experiencing.

Quick questions:

  1. Can you reproduce this issue in a clean project?
  2. If so, could you provide a detailed list of steps to reproduce this issue in a clean project?
  3. Could you provide screen shots of any settings/blueprints that may be involved with this issue?

Greetings. Thanks for your reply.
I am going to look into this issue as soon as I am able to. I’ve been pretty swamped right now with work, but I’ll compile some tests see what I can dig up.

The problem the testers using Windows 10 had in particular is either changing the game screenmode from fullscreen to windowed/borderless, or when minimizing/maximizing while in fullscreen.

Hello ,

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will follow up.