QuickBooks Database Server Won’t Stay Running After a Windows Update? Here’s the culprit.
Everything was fine with QuickBooks multi-user mode until a Windows update installed and the host computer restarted. Suddenly the QuickBooksDB26 service (the Database Server Manager service for QuickBooks 2016) would start and immediately stop. Clients could no longer open the company file in multi-user mode.
This is a classic “it worked yesterday” problem, and the cause is usually not a damaged QuickBooks installation.
What the Logs Actually Showed
When the QuickBooksDB26 service fails to stay running, the Windows Application log almost always contains these messages from the SQL Anywhere database engine that QuickBooks uses:
Starting service QuickBooksDB26
Unable to initialize requested communication links
Could not start server
That specific pair of errors means the database engine cannot bind to the network ports it needs. It starts, fails to claim its ports, and immediately exits.
For QuickBooks 2016 the ports that matter are:
TCP 8019
TCP 56726
UDP 55368–55372
The Hidden Culprit: Windows Port Exclusions
On this Windows 11 machine the problem was an administered port exclusion range created by the Windows NAT Driver (winnat) / Hyper-V components:
UDP 55354 – 55453That range completely covers the UDP ports QuickBooks 2016 needs (55368–55372). After the Windows update, WinNAT reserved the block. Nothing was listening on the ports according to netstat, yet QuickBooks still could not bind to them. This is a very common issue after Windows updates when Hyper-V, WSL, or WinNAT is present.
Why This Happens More Often Now
Windows updates frequently adjust dynamic port ranges or cause Hyper-V/WinNAT to claim large blocks of high-numbered ports. Older QuickBooks versions (2016 and earlier) use fixed port ranges and do not automatically move to free ports. The result is exactly the “starts then immediately stops” behavior we saw.
If you run into this on a later version of QuickBooks, the port numbers change, but the same diagnostic steps still apply.
Need Help?
If you’re not familiar with UDP ports and how to fix something like this, give us a call. We’ll get your QuickBooks Database Server running again and make sure the reservation survives the next Windows update.