Fun casual programmer facts: <br>There is a feature called "windows messages" when programming in windows, these gets sent like a ping to know the program is still working, due to how most loading screens work, they need to both load assets while another part of the program(threads) are working on showing the loading screen. Without this feature your program gets stuck with the "loading cursor" and windows thinks the program has crashed even if it's working in the background. Due to this it might be a good idea to actually wait it out sometimes depending on how the developer implemented the feature.<br>Also that's why you can have a responsive loading screen but it never loads because they handle the messages behind the scenes but the actual loading might for example not find a file it's expecting and therefore is stuck in a loop.,(reply>), What I don't get is why Office programs, like Outlook or Excel suffer from this too. Aren't they made by the same people that made the OS? Seems a bit silly that even their own programs display that incorrectly. I never trust that "program stopped responding" message anyway.,(reply>), Yep. Don't do non-UI related work on the UI thread, or your program will be shown as "hanging" by Windows when you try to interact with it while it is doing something.<br>I still need to have my colleagues get that x)