My fix was actually a crude one-liner to aid those in a pinch since the “composited” window style is intertwined with a whole lot of code involving window transparency and desktop composition which sole purpose is decide if that flag is enabled or not. A proper fix would involve a review of all that (for example, if things still work on Windows 7, where desktop composition can be turned off).
I have the same bug, but I’m not a windows insider, neither have windows pro (indeed the update installed itself forcefully).
My windows version is: 1607 (Build 14393.321).
I use the Epic Launcher version of the engine, is there a way to avoid this bug? Or we have to wait for new engine version?
Hello Maggese,
If you’re willing to use a source build downloaded from Github, you could apply the change that manoelneto mentioned above and then recompile the engine itself. This should fix the issue in that source built engine. Otherwise, you’ll need to wait for the next version of the editor or revert to an earlier build of Windows, which I’m not sure is an option in some cases.
Maggese,
You may also want to check out the openGL method of running the editor, listed earlier in this thread until Epic releases 3.14. It is working well for me - no issues and fixes the pull down menu problem - and from the comments, it appears, others. That way, if you don’t want to compile the source, or back up your build, you can still have a workable version.
Thank you RobMilliken, unfortunately in my case using opengl is even worse. I don’t know why, but right click and drop down menus remain invisible and the other menus are transparent :-/
I guess I’ll have to use the Git build…
I changed the theme to a high contrast theme and the menus are back. windows looks ugly now but at least i can work with ue4.
The bug report indicates the issue is “fixed.” I’m assuming this refers to it being fixed on the GitHub version, as it is still an issue as of today (4.13.2)
Does the “Target Version: 4.14” imply that 4.14 is when it will probably be fixed? If so, is there any estimate on when that will be released? I have no idea how to go about using the GitHub version.
That’s correct. When a bug is fixed, it’s committed into our internal branches and then released later in a newer version of the engine. This particular one is available in 4.14. Based off the commit number, the fix should be available in 4.14 Preview 2 from the Epic Games Launcher or the latest Github build in the 4.14 branch. If you’re interested in using the Github build, you can find out more about setting it up here.
Please note that developing on Preview builds is not suggested as they could have new issues that we’re not aware of. If you do decide to upgrade, please be sure to keep a copy of your original project prior to conversion.
some other solution ??
Just thought that I’ll add up on the topic.
Recently got Windows 10 Creators Update (version 1703 “Redstone 2”) and encountered this bug.
I am using UE4.12. Removing WindowExStyle |= WS_EX_COMPOSITED; helped.
Hello kirdaybov,
Please be aware that this fix is a workaround and could cause other issues. As shown in the bug linked above, the issue was fixed in version 4.14.
Same issue here with the Creators update. To fix I used this git commit (from UE-36752). Epic for making the issue tracker public, makes finding stuff like this easy 
Awesome! I just started having this issue earlier this week after a windows update. I had to migrate my project to 4.15, but not all the content went correctly… this saves me a lot of rework. Kudos