WINS Error 0x00000FA0: Quick Fix for Internal Service Failure
WINS error 0x00000FA0 means the service hit an internal failure. The fix is to reset the WINS database and restart the service — no reinstalling needed.
You're staring at WINS error 0x00000FA0 and it's making you want to throw your keyboard.
I've been there. This error pops up when the WINS service hits an internal snag — usually a corrupted JET database or a stuck lock file. The good news? You don't need to rebuild the server. Let's fix it.
Step 1: Stop the WINS Service
Open an elevated Command Prompt (Run as Administrator) and run:
net stop winsIf it's already stopped, move on. If it hangs, use taskkill /f /im wins.exe to force it.
Step 2: Rename (Don't Delete) the WINS Database Folder
Navigate to C:\Windows\System32\wins. You'll see files like wins.mdb, wins.pat, and winstmp.mdb. Rename the entire folder to wins_old:
rename C:\Windows\System32\wins wins_oldWhy rename instead of delete? If something goes wrong, you can roll back. This saved my butt more than once.
Step 3: Let WINS Recreate the Database
Now restart the service:
net start winsWINS will create a fresh database automatically in C:\Windows\System32\wins. Check the Application Event Log for any new errors — if none appear, you're golden.
Step 4: Restore Your WINS Records (If Needed)
If you have a backup of the old wins.mdb from a known good state, copy it into the new folder (overwriting the fresh one) while the service is stopped. Then restart WINS. I've done this on Server 2012 R2 and 2016 with zero issues.
Why This Works
Error 0x00000FA0 is almost always a JET database corruption or a lock file that didn't get released during a crash or improper shutdown. The WINS database uses the Extensible Storage Engine (ESE), same as Exchange and Active Directory. When the database header gets corrupted or a log file is out of sync, WINS throws this internal error. By renaming the database folder, you force WINS to create a clean environment. No registry changes, no reinstall.
Less Common Variations
Sometimes the error shows up as ERROR_WINS_INTERNAL without the hex code, or it appears as Event ID 4224 in the System log. If the steps above don't work, check for these gotchas:
- Antivirus interfering: Some AV software (looking at you, McAfee) locks the WINS database files. Temporarily disable real-time scanning and retry.
- Disk space: WINS needs at least 100 MB free on the system drive. Low disk space can corrupt the database during writes.
- Permissions: The Network Service account needs Full Control on the wins folder. Run
icacls C:\Windows\System32\wins /grant "NETWORK SERVICE":Fif permissions got messed up.
Prevention Tips
Don't let this ruin your day again. Schedule a weekly WINS database backup using netsh wins dump or a script that copies the wins.mdb file to a safe location. Also, install all Windows Updates — several patches between 2019 and 2021 fixed corner-case corruption bugs in the WINS ESE engine. If you're on Server 2022 or later, consider migrating to DNS and disabling WINS entirely. It's legacy tech, and Microsoft has been recommending its decommission since Server 2012.
Pro tip: If you see this error after a power outage, just rename the folder and restart. That's the fix 9 times out of 10.
Was this solution helpful?