What's the deal with this new Windows Defender Security Center? Even after manually allowing detected files / threats the damn icon and the interface itself keeps having this red X on it... There is no way to get rid off it without deleting the threats even after I have allowed them...
Major Start Menu Freeze bug in 15058 -> 15063 Made 15063 ISO from UUPs file downloaded directly from Windows Update. Burned to DVD and clean installed RS2 on my two machines. The first thing I noticed is a major start menu bug, in which the settings controls for the start menu do not work at all, and organizing tiles will result in a complete start menu freeze. The Start Menu will then default back to the last saved change. This bug appeared on both of my machines, so I know it's a Windows 10 RS2 issue. I have made several reports to Windows Feedback since 15058, but M$ has nothing so far and they didn't even report it on their blog page. I wonder if anyone else has the same problem and/or can help me with this major issue. I can't proceed until my start menu stops acting up. Thanks everybody.
Not by it self, but combined with everything else we see (like several builds per week, and now a sudden stop in new builds etc.), I would say it just adds to the list of things pointing to it being the RTM. (More so, since it is a tool downloaded from a microsoft.com URL)
Yep, but not RS2 bug. It is a bug of his two PCs. ))) Anyway, who uses MS Start-menu, which changes with every release? Yep, it is finished. MS already builds regular KB Cumulative update for b15063. ) What is the name of that gorgeous wolf in your avatar?
On Event viewer I'm getting a lot of: Log Name: Application Source: Application Error Date: 24/03/2017 12:45:16 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Description: Faulting application name: consent.exe, version: 10.0.15063.0, time stamp: 0xe0f856c4 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000409 Fault offset: 0x0000000000000000 Faulting process id: 0x1f6c Faulting application start time: 0x01d2a49c7cc63c48 Faulting application path: c:\windows\system32\consent.exe Faulting module path: unknown Report Id: f014ef93-347f-4975-871d-2636e25aa3fd Faulting package full name: Faulting package-relative application ID: Edit: It seems this error happens on every boot, and is also accompanied by an Event id 1000 for mmc.exe.