Caused when your network driver has become corrupted or changed for NetBIOs with an incompatible version from either Windows Updates or a filter from your Firewall (most commonly Zone Alarm).
You can “repair” this by using System Restore to go back to a previous driver, follow the guide below to do this:
- Restart your computer
- While it is starting up and just before the computer starts to load Windows continuously tap F8.
- A text-based menu will appear and using the Arrow Keys and the Enter key select Repair My Computer (up the top of the menu)
- Now it will prompt with your install selection, choose your Windows install and User Account and press Ok
- It will now come up with a dialog Window displaying a few options, click System Restore (it will take a while to actually load)
- Select Next
- Choose a valid System Restore point (the most recent while the computer was going is the best bet)
- Select Next and Ok
- Wait for the restore to finish and restart your computer. It should now be going (If it does not work, you might have to go to a System Restore point more previous then the one you used).
If System Restore cannot find the Windows operating system, you need to run a file system check called a CHKDSK. Follow the same prompts as above till Step 5, but instead of pressing System Restore, press Command Prompt. Type in: chkdsk /r /f c: and press Enter.
This is also caused by the Quality of Service network protocol in Windows.
Assuming you have a bootable Windows install follow the instructions below:
Click Start
- Click Control Panel
- Click Network & Sharing Center
- Click Manage Network Connection (on the left hand side menu)
- Right click on the Local Area Connection
- Left click Properties
- You will now have a list of protocols and services related to your networking device, leave the rest alone and uncheck QoS Packet Scheduler
- Click Ok
Note: If you have any valid Firewalls such as Zone Alarm installed, your best bet is once you have regained access to Windows is to uninstall it, the Windows Firewall does a good enough job and you do not need a third party one.
Note: Also make sure you are running the latest Windows service pack which helps reduce this issue.