Start menu is broken in gecko-t-win10-64 workers
Categories
(Infrastructure & Operations :: RelOps: Windows OS, defect)
Tracking
(Not tracked)
People
(Reporter: bugzilla, Assigned: grenade)
Details
Yesterday I was working with a couple of gecko-t-win10-64 workers (one with Administrator and one without), and both of them had start buttons that didn't work. Clicking the start button did not bring up a start menu. Furthermore, when I inspected the Windows Event Viewer, each start button click produced a crash report for one of the executables that comprises the shell.
My concern is that, if the shell on these systems is broken, what else is broken?
For example: Could this end up producing false negatives in browser tests that rely on shell APIs, because the shell is not working correctly?
|
||
Updated•5 years ago
|
|
||
Updated•5 years ago
|
|
Assignee | |
Comment 1•5 years ago
|
||
sounds similar to what i experienced on win 10 build 1903 instances when disabling the base filtering engine (bfe) service. my research suggested that this behaviour is 'by design' by ms engineering for situations where bfe is disabled.
our current win 10 testers use build 1803 with bfe running, but other defender related services disabled. we definitely had a working start menu at the time the amis were created, so i suspect that either a windows update is responsible for causing the start menu to be disabled as a consequence of the disabled defender services or a newer ami with bfe disabled got promoted prematurely. either would explain this behaviour.
i will investigate.
backlog cleanup
Description
•