Hi! “Lenovo computer works only after restart” is one of those symptoms that sounds vague, but it actually has a few common patterns. The big idea is: a restart does a clean reload of drivers and system state, so if things only behave after a restart, something is likely getting stuck over time (sleep/wake state, Fast Startup “not a real shutdown,” a driver that stops responding, or a background process that gradually misbehaves).

To keep this safe (no “optimizer tools,” no random driver rollbacks), tell me what “doesn’t work” before the restart:
• Is it a specific thing (Wi-Fi drops, Bluetooth disappears, sound breaks, keyboard/touchpad lag, apps won’t open), or is it the whole system freezing?
• Does it happen after sleep/hibernate, after leaving it on for hours, or right after turning it on from “shutdown”?
• Windows 11 or 10, and what Lenovo line (IdeaPad / ThinkPad / Legion)?

Also: when you say “restart,” do you mean clicking Start → Power → Restart, or are you holding the power button?

That detail matters a lot: restart helps, but shutdown doesn’t always. On Windows 10/11, “Shut down” can behave differently than people expect because of Fast Startup (it can save a partial system state). A restart is more likely to do a full refresh of drivers and services. That’s why people search things like “Lenovo only works after restart,” “Lenovo needs restart every day,” “internet works only after restart,” or “sound comes back after restarting.”

I’m going to ask in a slightly unusual order to reduce risk and pinpoint the pattern:

1) When it “breaks,” does it happen after the laptop wakes from sleep, or even if you never put it to sleep?
2) When Wi-Fi looks connected but nothing loads, does the network icon show connected normally, and do other devices on the same Wi-Fi work fine?
3) For audio disappearing: does the speaker icon show a red X / no output device, or does it show normal but no sound?

And quick safety check: do you remember this starting after a Windows update, Lenovo Vantage update, or a new driver?

“After sleep” + “no output device” + “Wi-Fi connected but unusable” points strongly toward a driver or power-state issue rather than a random hardware failure. Sleep/wake transitions are exactly where Wi-Fi and audio drivers can get stuck, and a restart reloads them cleanly.

Let’s do a couple of safe checks that don’t change settings — just gather evidence when it happens:

Safe check A — Uptime (tells us if you really rebooted):
Open Task Manager → Performance → CPU and look for Uptime. If uptime is huge even though you “shut down” last night, that supports the idea that Fast Startup / sleep states are involved. (No need to fix anything yet — just note the uptime number.)

Safe check B — Device status in Device Manager:
When audio or Wi-Fi breaks, open Device Manager and check whether Wi-Fi or audio devices show a warning icon (or temporarily vanish). If they vanish after sleep, that’s a big clue about power management / driver reset behavior.

If you can, tell me: the next time it happens, what does uptime show, and do you see any warning icons?

That’s a very strong signal. If uptime stays high after “shutdown,” Windows likely didn’t do a full cold boot — which explains why “restart fixes it but shutdown doesn’t.” And a device disappearing after sleep is exactly the kind of thing a restart masks by reinitializing drivers.

To keep the advice safe and not turn this into a giant checklist, I want to narrow it down to one of three buckets:

• Sleep / wake driver state (Wi-Fi/audio devices fail after sleep and return after restart).
• Fast Startup confusion (shutdown isn’t a full reset, so issues persist across “shutdown”).
• Something gradually leaks or hangs (system gets worse the longer it runs; restart clears it).

Quick questions (no action required):
1) Does the problem appear even if you avoid sleep for a day (leave it on, or power it on fresh and keep using it)?
2) When Wi-Fi is “connected but nothing loads,” does turning Wi-Fi off/on help, or only a restart?
3) Any external devices involved (USB headset/dock), or is it built-in speakers and internal Wi-Fi?

Also, because you mentioned updates: do you see Lenovo Vantage installed and updating drivers/firmware in the background?

That fits the “state over time” story: sleep makes it worse, and long uptime can bring it back. At this stage we’re not trying to “force-fix” it — we’re trying to capture enough proof to know whether it’s Wi-Fi driver behavior, audio driver behavior, or an update/firmware interaction.

Two more safe evidence checks that help without changing your system:

Safe check C — Reliability Monitor timeline:
Search Start for Reliability Monitor and look at the days the issue started. Do you see entries for “Windows Update,” “Driver installed,” “Hardware error,” or app failures around the time things began requiring frequent restarts? You don’t need to interpret every entry — just whether it aligns with the timeline.

Safe check D — Event Viewer snapshot (System log):
Open Event Viewer → Windows Logs → System and look around the time Wi-Fi/audio broke. If you see repeated warnings about network adapters, audio services, or device resets, it supports a driver/power-state reset problem rather than general “my laptop is slow.”

If you tell me whether you see patterns (same type of warnings repeating), we can decide what category this is without risky steps.

That’s enough to say this is likely a driver/update interaction plus a power-state trigger — not a random mystery. The reason it “only works after restart” is that restart resets the entire driver stack and clears the stuck state, while sleep/shutdown may preserve parts of it.

Here’s the key safe takeaway (without pushing a full “do this fix”):
• If uptime stays high after shutdown, you’re not getting a clean reset — so symptoms can carry over day to day.
• If devices disappear after sleep, you’re dealing with driver reinitialization after sleep/wake.
• If the issue lines up with a driver install in Reliability Monitor, that’s the strongest “why now” clue.

If you want a quick sanity check without changing settings: for the next 24 hours, note whether using Restart (not Shut down) at the end of the day reduces how often it breaks after sleep. That’s not a permanent solution — it’s a diagnostic that confirms the state-carryover theory.

Exactly. The safe approach is: prove the pattern, then choose a targeted next step (instead of changing five things at once). If your Lenovo becomes usable only after restart, we want to know which trigger applies:

1) Carryover state: shutdown didn’t reset (uptime stays high), so problems persist until a restart.
2) Sleep/wake: devices vanish or degrade after sleep, then return after restart.
3) Over-time degradation: things get worse with long uptime (resource leak, stuck background process), restart clears it.

The evidence you already collected (uptime + disappearing audio device + driver install timing) leans toward 1 and 2. If you later want to go deeper, the “right” data is the exact warning lines from Event Viewer and what device disappears/recovers — not a random set of tweaks.