Microsoft recently launched Surface Book and Surface Pro 4, and sales are going even better than expected. But with the new devices, the new problems come, as users of some Surface Book and Surface Pro 4 reported a strange flickering screen problem.
Surface Pro 4 and Surface Book finally went on sale on Monday, and demand was pretty huge, some stores ran out of stock of these two devices in just a few days. But, some ‘lucky ones’ who had an opportunity to buy one of these devices were disappointed once they started their new expensive toy for the first time.
Namely, Microsoft forums were flooded with the complaints about some strange flickering screen issue which was present on both devices. This screen problem made Surface Pro 4/Surface Book nearly impossible to use, and you can imagine how would you react if you just gave a couple thousand dollars for a device that you expect to work perfectly, and a serious problem (well at least, serious on the first look) appears on your first launch.
Luckily, people from Microsoft forums were fast this time, so they quickly found the solution. Reportedly, these two devices have some problem with Hyper-V, so if this feature is enabled, you’ll get the flickering screen problem. Hyper-V is not enabled by default in Windows 10, but if you install Visual Studio, the installer will turn on Hyper-V as well.
So, you guessed it, to eliminate the flickering screen problem, you need to disable Hyper-V. And if you’re not sure how to do that, just follow these steps:
- Right-click on the Start Menu, and go to Command Prompt (Admin)
- Enter the following command and press Enter to execute it: dism.exe /Online /Disable-Feature:Microsoft-Hyper-V
Once you disable Hyper-V, the screen problem should be gone. As you can see, it’s not such a huge and scary problem, as it looked like at first sight, and it can be solved in seconds.
This is just an user workaround, as Microsoft didn’t release any fixes yet, but the company is well aware of the problem. But people are probably disappointed by the fact that Microsoft didn’t deliver the product which functions without any user’s workarounds, and that they have to solve things on their own again, while waiting for Microsoft to release the fix. And judging by the price and quality, issues like this definitely shouldn’t be present.