On August 31, Microsoft released a cumulative update for Windows 10 version 1903. It was the patch KB4512941, which is now known to be buggy. The issue it causes is a broken Search/Cortana. Yet another bug has emerged in the update KB4512941 that causes orange screenshots.
Windows 10 1903 build 18362.329 (KB4512941) has appeared in the production branch after a short period of testing in the Release Preview ring. After installing the latest cumulative update, many users began reporting unusually high CPU usage even when the system was idle. They have been reporting that the high CPU load was caused by the SearchUI.exe process.
Additionally, the affected users have been complaining that the Search flyout was broken for them and was opening without any content.
It looks like there is another bug that affects users who have installed the patch. For certain users, screenshots they take regardless of the software and method they use having an orange tint.
My screen turns red when I capture a screenshot. How can I turn it off? I haven’t changed any settings; yesterday it was fine. I tried using different snipping tools, and the regular PrtSc button. All red.
I have the night mode off, and everything else is regular.
Here is how it looks.
[Update]: Microsoft has published the official solution related to this bug. According to the company, the issue is caused by a Lenovo software and its "Eye Care Mode". See this post on Lenovo forums, and this note by Microsoft.
As of now, the only working solution is to uninstall the OEM software which manages the screen options if you have one installed. For example, for Lenovo laptops it is Eye Care Mode. This works for certain users.
Most of the suggestions on the Answers forums are to uninstall and rollback the display driver and see if it helps.
Luckily, this update is optional. To get KB4512941, you need to open Settings >Update & recovery > Windows Update and explicitly confirm your intention to get this patch by clicking on the "Download and install" link.
It is a good idea to avoid KB4512941 until the issue is sorted out.