Windows Defender won’t launch when double-clicking the tray icon [FIX]

Radu Tyrsina
by Radu Tyrsina
CEO & Founder
Affiliate Disclosure

To fix various PC problems, we recommend DriverFix: This software will keep your drivers up and running, thus keeping you safe from common computer errors and hardware failure. Check all your drivers now in 3 easy steps:
  1. Download DriverFix (verified download file).
  2. Click Start Scan to find all problematic drivers.
  3. Click Update Drivers to get new versions and avoid system malfunctionings.
  • DriverFix has been downloaded by 0 readers this month.

Windows 10 Creators Update users have been reporting a strange flaw that is now confirmed on computers running both the stable version of the operating system and the Redstone 3 preview builds. It seems that they can’t launch Windows Defender by double-clicking the icon from the system tray.

Windows Defender in Windows 10 Creators Update

Windows Defender has become Windows Defender Security Center in the Windows 10 Creators Update. This is the OS’ main protection shield against all kinds of unwanted problems therefore it runs non-stop, and it’s got its own icon placed in the system tray to give users the quickest possible access to it.

Unfortunately, it looks like double-clicking on this icon won’t do a thing. It makes no difference and the app doesn’t launch. Users have been trying to find a solution and they managed to do it.

It seems that right-clicking on the icon and then hitting the ‘Open” option is the easiest way of getting the app to work. This trick is working properly on affected systems, but it’s still unknown the reason for which this bug has appeared in the first place.

The bug is not new in town

It’s interesting to find out that this bug has been lurking around for some while now because the same problem has been reported and also listed as a known bug by Microsoft during the Microsoft Insider program before the Windows 10 Creators Update was released.

The posts that can be found in the Windows 10 Feedback Hub all confirm that this is a known problem. Also, a Microsoft engineer has confirmed himself a couple of weeks ago that the team was working on a fix for this issue.

Until now, there still hasn’t been provided any patch and the bug is becoming more and more experienced on fully updated systems. Microsoft might release a fix for it when the next updates for Windows 10 Creators Update land, and that is on May 9.

RELATED STORIES TO CHECK OUT:

This article covers:Topics:

There are no comments yet. Please leave a comment

add a comment

Leave a Reply

Your email address will not be published. Required fields are marked *