Kali No Network After Update: Wired & Wireless Fix, Step by Step

If Kali has no network after apt full-upgrade, the connection almost never actually died — the thing showing it to you did. In most cases NetworkManager itself is fine; it's either not running under the name you tried to check, or an interface got marked "unmanaged" during the upgrade. Run systemctl status NetworkManager (capital N, capital M — not network-manager), then work through wired and wireless separately, because they fail for different reasons and the fixes are not interchangeable.

Jake's shop runs a walk-in trade-in counter, and every trade-in gets wiped and re-imaged on a Kali box before it goes back on the shelf — nothing fancier than confirming a wiped drive is actually wiped. On a Tuesday morning he ran his usual apt update && apt full-upgrade, rebooted, and the network icon in the top corner was gone. No wired, no Wi-Fi, no error message worth reading. Four phones were waiting to be checked in and he had no way to pull the wipe-verification tool's latest signature file.

"I typed service network-manager status like every forum post told me to," Jake said, "and it said the unit didn't even exist. So I figured the update deleted it." Ethan didn't even look up from his coffee. "It didn't delete anything. You asked it about a service that was never called that in the first place. Two different names, same thing, and the wrong one just tells you 'not found' instead of correcting you."

Which of these is actually happening to you?

"No network" covers at least six different failures, and they need different fixes. Match your symptom to a row before typing commands at random — Jake's first instinct was to reinstall the whole OS, and Ethan talked him out of it before he'd even finished the sentence.

First, confirm NetworkManager is actually the one in charge

Kali's Xfce desktop uses NetworkManager to handle both wired and wireless connections and to draw the applet in the top panel. The package you install and upgrade is called network-manager, all lower case with a hyphen — that's just Debian's package naming convention. The systemd service it installs is called NetworkManager.service, capitalized, no hyphen. They are not the same string, and a command aimed at the wrong one reports the service doesn't exist, which reads exactly like "it's broken" to someone who isn't expecting a mismatch.

"So the forums are wrong?" Jake asked. "Not wrong," Ethan said, "just written by people who already knew the difference and forgot that you don't. That's the whole problem with copy-pasted fixes — they skip the one line that would've told you what you were actually looking at."

Run the check in this order

1. Open a terminal and run systemctl status NetworkManager. If it prints "active (running)," the service is fine and your problem is downstream — go to the wired or wireless section.
2. If it prints "could not be found" or "not-found," you likely typed the package name instead of the unit name. Try again with the exact capitalization above before assuming anything is missing.
3. If it prints "inactive (dead)" or "failed," start it with sudo systemctl start NetworkManager, then make sure it survives the next reboot with sudo systemctl enable NetworkManager.
4. Run nmcli general to see NetworkManager's own view of its state (connected, connectivity, and whether it's managing anything at all), then nmcli device to list every interface it can see and whether each one is "connected," "disconnected," or "unmanaged."
5. If a device shows as "unmanaged," check /etc/NetworkManager/NetworkManager.conf and any files under /etc/NetworkManager/conf.d/ for an unmanaged-devices line, and for a stray leftover entry in /etc/network/interfaces naming that same device (see the conflict below).

Fixing wired (Ethernet) after the update

Wired failures after an upgrade are almost always about an interface being unmanaged or the service not restarting cleanly. It's rarely the cable, but rule that out first because it costs ten seconds and Jake has, in his words, "lost an entire Saturday to a cable that just needed to be pushed in properly."

1. Run ip link show. Find your Ethernet interface (something like eth0 or enpXsY) and check whether its state is UP or DOWN. A physical link light on the port or switch is worth a glance too.
2. If the interface is down, bring it up manually with sudo ip link set eth0 up (substitute your interface name) and see if NetworkManager picks it up within a few seconds.
3. Restart the service with sudo systemctl restart NetworkManager. This alone resolves a large share of post-upgrade wired failures, because it forces NetworkManager to re-scan every interface instead of relying on stale state from before the upgrade.
4. Run nmcli device status. If your Ethernet device shows "unmanaged," edit or remove the offending line in NetworkManager.conf, then restart the service again.
5. If the device still won't reconnect, bring up the connection profile directly: nmcli connection up "Wired connection 1" (use nmcli connection show first to get the exact profile name).

Jake found exactly this: a three-line stanza for eth0 he'd added years earlier following a guide for a static IP he no longer needed. "I forgot that was even in there," he said. Ethan's response was the kind of line he repeats often enough that Jake now says it back to him: "Every config file you write today is a bug report you're filing against your future self."

Fixing wireless (Wi-Fi) after the update

Wireless has two extra failure points that wired doesn't: a software or hardware kill switch, and driver or firmware loading. Neither has anything to do with NetworkManager itself, so restarting the service — Jake's default move for everything by this point in the day — won't touch either one.

Step one: rule out a kill switch

Run rfkill list. Every wireless radio on the machine — Wi-Fi, and separately Bluetooth — shows a soft-block and hard-block state. If Wi-Fi shows "Soft blocked: yes," unblock it with sudo rfkill unblock wifi. A hard block means a physical switch or function-key toggle, which no software fix overrides. "This one got me on a laptop once," Ethan admitted. "Fresh install, perfect config, and the airplane-mode key had been bumped in my bag. Twenty minutes I won't get back."

Step two: confirm the driver actually loaded

Run lspci -knn | grep -A2 -i network for an internal card, or lsusb for a USB adapter, to confirm the hardware is even detected. Then check dmesg for the driver name and any load errors from around boot time. Kali's own troubleshooting documentation for wireless drivers lays out this exact sequence — identify the device, then check whether its driver loaded and whether it logged an error — before assuming NetworkManager or the upgrade broke anything.

If the driver loaded but the network list is still empty, reinstall the firmware and NetworkManager packages together: sudo apt install --reinstall network-manager network-manager-gnome kali-linux-firmware firmware-iwlwifi (drop the last package if your card isn't Intel; substitute the correct firmware package for your chipset).

Jake doesn't use monitor mode for anything — his Kali box exists to wipe phones, not crack Wi-Fi — so Ethan ruled this one out for him in about four seconds. "If you've never touched airmon-ng, skip this section entirely and go straight to the driver check. No point chasing a cause you've never triggered."

When the upgrade itself didn't finish

If your apt full-upgrade printed errors, stalled, or you rebooted before it said it was done, network-manager and its dependencies can be left half-configured. One specific way this happens: Kali's package archive is signed, and that signature is checked by a tool called sqv. If the archive's signing key had expired at the moment you ran the upgrade, apt fails with an error mentioning sub-process /usr/bin/sqv returned an error code, and whatever packages hadn't finished installing — including, sometimes, network-manager — are left in a broken intermediate state.

To recover: fetch a current keyring with wget https://archive.kali.org/archive-keyring.gpg -O /usr/share/keyrings/kali-archive-keyring.gpg, run sudo apt update, then finish the interrupted upgrade with sudo apt --fix-broken install followed by sudo apt full-upgrade again.

"Don't reboot in between," Ethan said, watching Jake's cursor hover over the reboot option out of habit. "A half-installed network-manager package is exactly the kind of thing you want to finish installing before the system restarts and tries to load it. Rebooting a broken install doesn't give it a clean slate — it just adds 'came up in an unknown state' on top of 'was already broken.'"

Kali in a virtual machine: VirtualBox and VMware

A VM adds a layer NetworkManager can't see or fix: the hypervisor's own virtual adapter sitting between the guest and the real network card. If the host machine has internet and the guest doesn't, the problem is almost always the adapter setting in the VM software, not anything inside Kali — which is exactly backward from what most people assume the first time they hit it.

Beyond picking the right mode, three things trip people up specifically after an upgrade inside a VM:

• Guest Additions (or VMware Tools) get out of sync with a new kernel. A kernel upgrade inside apt full-upgrade means the previously built Guest Additions kernel modules no longer match the running kernel until you rebuild or reinstall them. The virtual network adapter can silently stop negotiating properly with the host until that's resolved.
• The virtual NIC's own "cable connected" state gets toggled off. Both major hypervisors let you simulate an unplugged cable on a virtual adapter independently of anything inside the guest. If wired networking worked before the upgrade and nothing changed on the Kali side, check this setting in the VM's own network configuration before touching NetworkManager at all.
• A passed-through USB Wi-Fi adapter needs to be re-captured after certain updates. If you're using an external adapter for wireless work inside the VM, the hypervisor sometimes releases the USB capture on a VM restart, especially right after a host-side update of its own. Check the VM's USB device list before assuming the adapter itself failed.

If you're setting up from scratch rather than troubleshooting an existing install, our walkthrough for installing Kali in VirtualBox covers picking the right adapter mode during initial setup, which heads off most of this before it starts.

"I can ping an IP address, but not a website"

This isn't a "no network" problem at all — the connection works, and only name resolution is broken. It's a common enough distinction that Ethan has a stock line for it: "Your car works fine. You just don't have a map." Check cat /etc/resolv.conf. If it's empty, or contains only comments, DNS has nothing to query.

NetworkManager normally writes this file itself based on the DNS servers your active connection reports. If something else edited or froze it, add nameserver lines back manually, or let NetworkManager regenerate it by restarting the service — but first confirm nothing else is also trying to own that file. Run resolvectl status if it's available on your install; it shows which resolver is actually in control (NetworkManager's own DNS handling versus a separately configured systemd-resolved) and which nameservers each interface is currently using. Two tools fighting over the same file is a more common cause of "DNS just stopped" than either tool failing on its own.

Why Kali disables things you didn't ask it to

Kali's own documentation is explicit about this: unlike most desktop Linux distributions, Kali does not enable externally-listening network services by default, and by policy it disables a newly installed service from persisting across reboots unless it's on an explicit allowlist. Kali's documentation shows this happening live when installing a caching proxy tool — the installer prints a message saying it detected a network service and disabled it. This is a security decision for a penetration-testing toolkit that might sit in hostile networks, not an accident.

"So is that what happened to me?" Jake asked, hopeful there was a single tidy explanation. "No," Ethan said, "and this is the part worth being honest about. NetworkManager ships enabled on the desktop image specifically because you need it to see anything at all. This policy is why your other stuff vanishes — a proxy you installed, an SSH server you spun up for a test — not why your network icon vanishes. Don't let one true fact about Kali talk you into blaming the wrong system."

Where this policy does bite people: if you've installed something like a proxy, an SSH server, or a file-sharing tool and expected it to survive a reboot the way it would on Ubuntu, and it doesn't, that's this policy working as designed. Bring a specific service back with sudo systemctl enable <service-name>.

Wired and wireless both down at once

When both fail together after the same upgrade, the shared cause is almost always NetworkManager itself, not either interface separately. This is the point where Jake wanted to give up and reinstall from scratch. Ethan's counter-argument: a reinstall takes an afternoon and might not even fix it, if the actual cause is a config file you'll copy right back over from a backup. Work through it in order instead, each step more drastic than the last:

• Check the logs for the exact failure: journalctl -u NetworkManager -b shows everything the service logged since the last boot, and it usually names the specific plugin or config file that's failing to load.
• Fully remove and reinstall the package set: sudo apt remove network-manager network-manager-gnome, then sudo apt update && sudo apt install network-manager network-manager-gnome. This replaces every file the package owns with a clean copy, while leaving saved connection profiles under /etc/NetworkManager/system-connections/ untouched.
• If a specific config file is the problem (found via the journal), move it aside — don't delete it, in case you need to check it later — and reboot so NetworkManager rebuilds its defaults from scratch.
• As a genuine last resort, boot a fresh Kali live-USB on the same hardware and see if it connects fine there. That single test separates "something is wrong with this specific install's configuration" from "something is wrong with this hardware or driver," which would follow you into a reinstall anyway.

Keeping this from happening on the next upgrade

None of this guarantees a smooth ride forever — Kali is a rolling release, and rolling releases occasionally ship a rough day — but it removes the most common self-inflicted causes:

• Never reboot mid-upgrade if apt is still printing output. Let it finish or fail cleanly first.
• If you use airmon-ng regularly, build restarting NetworkManager afterward into your routine, not into your troubleshooting steps once it's already annoyed you.
• Keep a mental note of whether you've ever hand-edited /etc/network/interfaces. If you have, and you're letting NetworkManager run the show, that file should have those interfaces removed or commented out.
• If you're on kali-last-snapshot for stability, know it still receives full-upgrade-sized changes on its own quarterly schedule — calmer than kali-rolling, not immune to the same category of issue.
• In a VM, rebuild or reinstall Guest Additions right after any kernel upgrade, as a habit, rather than waiting for something to break first.

Jake's phones eventually got checked in that Tuesday — the fix, in the end, was the leftover interfaces stanza plus one restart of NetworkManager, about four minutes of actual work once he knew where to look. "The annoying part," he said, "is that I could've fixed this in the first two minutes if I hadn't spent twenty of them convinced the update deleted a program."

Frequently asked questions

Why does apt full-upgrade sometimes kill my network connection?

It rarely kills it outright. Far more often, a config file changes format between package versions, a device gets marked unmanaged, or the upgrade itself stalls partway through and leaves network-manager half-installed. The network hardware and driver are almost always untouched.

What is the difference between network-manager and NetworkManager?

network-manager is the APT package name, all lower case. NetworkManager is the systemd service name that package installs, with mixed case and no hyphen. Commands aimed at the wrong one report "not found," which is easy to misread as "broken."

How do I check if NetworkManager is actually running?

Run systemctl status NetworkManager. "Active (running)" means it's fine. For more detail on what it thinks it's managing, follow up with nmcli general and nmcli device status.

My Ethernet cable is plugged in but Kali shows no connection — what now?

Check the physical link light first, then run ip link show to see if the interface is up, then restart NetworkManager. If nmcli device status shows the interface as unmanaged, check NetworkManager.conf and /etc/network/interfaces for conflicting entries.

Why did my Wi-Fi disappear after I used airmon-ng?

Putting an adapter into monitor mode with airmon-ng check kill deliberately stops NetworkManager and related processes so they don't interfere. Restart NetworkManager afterward with sudo systemctl restart NetworkManager to get normal Wi-Fi back.

How do I reinstall NetworkManager without breaking my configuration?

Reinstalling with sudo apt install --reinstall network-manager network-manager-gnome restores program files without touching your saved Wi-Fi passwords or connection profiles, which live separately under /etc/NetworkManager/system-connections/.

Should I use /etc/network/interfaces instead of NetworkManager?

Not on a desktop install unless you have a specific reason to. The two systems can conflict over the same interface, and NetworkManager is what drives Kali's desktop applet and Wi-Fi list. If you keep a hand-written interfaces file, remove any device NetworkManager should be managing.

Why does Kali disable some services after I install them?

By policy, Kali does not let newly installed network-facing services persist across reboots unless they're explicitly allowlisted, to minimize exposure by default. Re-enable a specific service with sudo systemctl enable <service-name> if you want it to survive a reboot. This policy doesn't affect NetworkManager on the desktop image, which ships enabled by default.

How do I fix Kali networking inside VirtualBox?

Confirm the VM's adapter type first (NAT for simple internet access, Bridged if the guest needs its own address on your LAN), rebuild Guest Additions if you just upgraded the kernel, and check that the virtual adapter's "cable connected" setting hasn't been toggled off in the VM's own network settings.

Why can I ping an IP address but not a website?

That's a DNS problem, not a connectivity problem. Check whether /etc/resolv.conf actually has nameserver entries, and run resolvectl status to see which resolver is in control if more than one might be configured.

What does rfkill have to do with my Wi-Fi not working?

rfkill list shows whether your wireless radio is software-blocked or hardware-blocked. A soft block clears with sudo rfkill unblock wifi; a hard block means a physical switch or key combination needs to be toggled on the machine itself.

My Wi-Fi adapter isn't even listed — is it a driver problem?

Likely, yes. Check lspci -knn or lsusb to confirm the hardware is detected at all, then dmesg for driver load messages. If the driver never loaded, reinstalling or adding the correct firmware package usually resolves it.

Is it safe to run apt full-upgrade again if it failed halfway?

Yes, and it's the right move — but fix the underlying cause first if apt reported one, such as an expired signing key, and run sudo apt --fix-broken install before trying the full upgrade again. Avoid rebooting while packages are left half-configured.

Does switching to kali-last-snapshot fix network problems?

Not directly. It changes how often you receive large batches of changes — quarterly instead of continuously — which can reduce how often you hit rough patches, but it won't undo a problem you already have.

Why does my wireless adapter disappear only inside a virtual machine?

Most internal wireless chipsets can't be passed through to a VM at all; only USB adapters can, and only when explicitly captured in the hypervisor's USB device settings, which can also silently release the capture after certain restarts.

What's the very last resort if nothing here fixes it?

Fully remove and reinstall network-manager and its GNOME applet, check journalctl -u NetworkManager -b for the specific error, and test a fresh live-boot USB on the same hardware to separate a configuration problem on this install from a hardware or driver problem that would follow you into a reinstall.

Revision note. Written September 2026. We will need a revisit if a future Kali release changes its default network stack away from NetworkManager, or if the APT signing key rotates again, Kali 2026.3 is already live (though official repostitory says sep 8,2026 targeted release, i had written a post on it too, check if you didn't updated yet.. If you're standing in front of a dead network icon right now, take a breath, run the one command in the Quick Answer box, and work down from there — you almost certainly haven't lost anything.