Hello All, FINAL UPDATE: This issue has been fixed with MacOS Mojave, update 10.14. If you have the issue below and are currently running on High Sierra 10.13.4 or later, try upgrading your computer to MacOS Mojave and the static on wake should go away. As this issue appears to have been fixed via the most recent OS update, I am marking this thread as "Resolved". Feel free to comment if you see the issue return on Mojave or have questions. —————————————————— I just bought a refurbished MacBook Pro 13" w/Touchbar (Mid 2017) from Apple, and am running the most recent macOS to-date (High Sierra 10.13.4). When I lift the screen to wake the computer after a long sleep cycle (say leave it asleep overnight, on battery power), it intermittently has this issue where it displays a grey and white " static, like an old tv without antenna reception, for about 1 second, before going to the log-in screen. It does not do this on short sleep cycles, and I do not have any external monitors or eGPUs connected to it. Also, sometimes on boot up the apple logo glitches and shows red for a second, before going back to normal. I have already reset NVRAM and SMC, and even reinstalled macOS High Sierra. Is anyone else experiencing this issue on newer MacBooks, or have any suggestions on what this may be? UPDATE: So as an update to all of this, I returned the MacBook to apple and received a replacement, and low and behold the new computer I received has the same issue! After long sleeps it has a snow/static on waking the computer up, with no externals plugged in, and with a fresh install of MacOS (no personal applications installed, all stock). I have been in contact with AppleCare, and they have sent this issue up to Engineering. I am awaiting a response as to if this is "typical" of the newest software update, of is a sign of a bigger, more serious hardware issue. As soon as I get an update from Apple, I will add details to this post. If you have this issue, report it to Apple! If it is a software issue, the more they are alerted of the issue the faster we will see a fix. UPDATE 2: Hello everyone, this will serve as a final update to the issue below that I posted. After working with AppleCare and engineering, they wanted to use my device and send me (another) replacement to identify the issue. From what I was told, this appears to be an issue with the OS, and engineering is aware of the issue. Here’s hoping the next update fixes the issue. Thank you all for your comments below, it helped relieve stress knowing it wasn’t just me with the issue!