Disabling full CIG in beta seems like the best way forward. For Nightly, we'll have to debug what Norton is doing that causes them to break security features. The failures here suggest that they inject themselves into RDD in a way that we can't see, and things then totally break if Windows tries to apply CIG protections to the RDD process because Nortons' junk has already compromised it. We'll have to investigate what is up.
Bug 1682834 Comment 46 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Disabling full CIG in beta seems like the best way forward. For Nightly, we'll have to debug what Norton is doing that causes them to break security features. The failures here suggest that they inject themselves into RDD in a way that we can't see (even if the product is disabled!), and things then totally break if Windows tries to apply CIG protections to the RDD process because Nortons' junk has already compromised it. We'll have to investigate what is up.
Disabling full CIG in beta seems like the best way forward. For Nightly, we'll have to debug what Norton is doing that causes them to break security features. The failures here suggest that they inject themselves into RDD in a way that we can't see (even if the product is disabled!), and things then totally break if Windows tries to apply CIG protections to the RDD process because Nortons' ~~junk~~ product has already compromised it. We'll have to investigate what is up.
Disabling full CIG in beta seems like the best way forward. For Nightly, we'll have to debug what Norton is doing that causes them to break security features. The failures here suggest that they inject themselves into RDD in a way that we can't see (even if the product is disabled!), and things then totally break if Windows tries to apply CIG protections to the RDD process because Nortons' product has already compromised it. We'll have to investigate what is up.