Windows 10. Was working fine for months with no issue. Then randomly today my PC started disconnecting from Ethernet. Reinstalled ethernet driver. That broke Zima I thought. So I uninstalled it reinstalled it. Didn’t work. Then I removed the network bridges/credentials/drives hoping reinstalling the client would bring up that prompt for first time setup I saw months ago. Nope NO DEVICES FOUND. Also can’t connect to other LAN devices now. Open WRT router the ZimaOS machine connects to. It also won’t do that network bridge it did during the first setup in “Network Connections” I can go to any other computer on the network even my phone connects to both no problem. Just my Windows 10 machine won’t do LAN. Like internet is fine I’m typing this on the computer I’m talking about. Is there a way to fix this manually? I’ve been looking this up all day tried most of the recommended fixes I’ve been able to find. It won’t set up the network bridge. How do I setup the network bridge? Anybody have any ideas on what’s going on here? Help would be much appreciated.
All fixed! Didn’t do anything except wait until the next day. Very strange I restarted many times and waited hours with no results yesterday. Today it just pops up like I first installed it again. Similar thing happened to another person on here. I wonder what causes the issue of it not being able to find it? If this happens to anyone else just wait and try again the next day. Come back with a clear head and don’t mess with your drivers.
This lines up with a Windows network discovery hiccup, not a Zima Client issue.
Reinstalling the NIC driver likely reset Windows’ network state, which temporarily broke LAN discovery. Zima Client depends on that, so it showed “No devices found.” After Windows settled and services refreshed, everything just worked again.
Key points for others:
- No manual network bridge setup is required
- If one PC can’t see any LAN devices, it’s Windows-side
- Reinstalling drivers repeatedly can make it worse
- Sometimes the fix really is: reboot, wait, and try later
Strange, but seen before