Wireless
Participate in insightful discussions regarding issues related to Intel® Wireless Adapters and technologies
8875 Discussions

How to permanently remove KillerNetworkManagerLauncher when it does not appear in Apps & Features

Jayhawk1900
Beginner
162 Views

Background

I have a Dell laptop running Windows 11 that does not have Intel Killer network hardware installed. Despite this, on every boot a popup error appeared approximately 50 seconds after the desktop loaded, referencing KillerNetworkManagerLauncher and offering a link to the Microsoft Store, which returned a 'No app available' message.

 

The standard removal steps did not work:

  • No Killer or Rivet entries appeared in Apps & Features / Installed Apps
  • No entries found in the Startup Apps tab of Task Manager
  • No Killer/Rivet folders visible in Task Scheduler through the normal UI
  • Attempting to reinstall the Intel Killer Performance Suite failed with 'No compatible hardware found'

 

Root Cause

A hidden scheduled task named 'Killer Startup Task' was sitting in the root of Task Scheduler (not inside any subfolder), making it invisible through the normal Task Scheduler UI. It used a logon trigger with a delay, which is why the error appeared consistently about 50 seconds after desktop load rather than immediately on boot.

 

There was also a leftover AppX package registered in Windows:

  • RivetNetworks.KillerControlCenter_3.1625.326.0_x64__rh07ty8m5nkag

 

Solution — Step by Step

Step 1: Remove leftover AppX packages

Open PowerShell as Administrator and run these three commands:

  1. Get-AppxPackage *KillerControlCenter* | Remove-AppxPackage
  2. Get-AppxPackage *Killer* | Remove-AppxPackage
  3. Get-AppxPackage *RivetNetworks* -AllUsers | Remove-AppxPackage -AllUsers

 

Step 2: Delete the hidden scheduled task

Still in PowerShell as Administrator, run:

  1. Unregister-ScheduledTask -TaskName "Killer Startup Task" -Confirm:$false

 

Verify it is gone:

  1. Get-ScheduledTask -TaskName "Killer Startup Task"

You should see: 'No MSFT_ScheduledTask objects found' — that confirms successful removal.

 

Step 3: Reboot

After rebooting the error no longer appeared. The Killer software was completely gone.

 

Summary

The key finding is that the 'Killer Startup Task' scheduled task hides in the root of Task Scheduler and is not visible through the normal UI. PowerShell is required to find and remove it. This affects machines that shipped with Killer software as part of a factory image, even when no Killer network hardware is present.

 

0 Kudos
1 Solution
Jayhawk1900
Beginner
114 Views

Thank you, It took several iterations and reboots with AI to find this solution. 

View solution in original post

0 Kudos
3 Replies
JeanetteC_Intel
Moderator
152 Views

Hello Jayhawk1900,

 

Thank you for reporting this KillerNetworkManagerLauncher issue and providing detailed troubleshooting steps.

 

We acknowledge the problem you've described with the persistent popup errors, hidden scheduled tasks, and leftover AppX packages that standard removal methods cannot address.

 

We will investigate this report further and share an update once our review is complete.

 

 

Best regards,

JeanetteC.

Intel Customer Support Technician


0 Kudos
Jayhawk1900
Beginner
115 Views

Thank you, It took several iterations and reboots with AI to find this solution. 

0 Kudos
JeanetteC_Intel
Moderator
103 Views

Hello Jayhawk1900,

 

Thank you for taking the time to share your detailed solution and troubleshooting steps with our Intel community. Your comprehensive documentation of the KillerNetworkManagerLauncher removal process is an excellent contribution that will undoubtedly help other users facing similar challenges.

 

I really appreciate your thorough approach, particularly how you:

  • Identified the hidden "Killer Startup Task" in Task Scheduler root
  • Documented the PowerShell commands for AppX package removal
  • Provided clear step-by-step verification methods
  • Shared the complete resolution process, including your multiple iterations

 

Your dedication to working through this complex issue and then generously sharing the solution with others perfectly embodies the collaborative spirit that makes our community such a wonderful resource for everyone.

 

Since you've confirmed that your issue has been completely resolved and you're sharing this information as a helpful resource for others, I'm closing this case as resolved. Your contribution has been noted and will serve as a reference for similar situations.

 

For your reference, here are some complementary articles that work well alongside your solution:

 

Thank you again for your valuable contribution to our community. If you need any technical support in the future, please don't hesitate to reach out.

 

Thank you once again for your outstanding contribution to our community. Should you need any technical support in the future, we're always here and ready to help.

 

Sincerely,

JeanetteC.

Intel Customer Support Technician

 


0 Kudos
Reply