Press F2 to Check Your QuickBooks Desktop Version and File Counts
QuickBooks Desktop hides your exact version, edition, and file counts behind one keystroke; here is how to read them before an upgrade or repair.
Before any upgrade, condense, or repair, our engineers ask for two facts: the exact QuickBooks release you run, and the amount of data behind your company file. QuickBooks Desktop reports both on one screen that opens with a single key. This page shows how to open that screen and how to read what it reports.
Opening the Product Information screen
- Open your company file the way you normally do. The screen is read-only, so no backup is needed just to look, and single-user or multi-user mode makes no difference.
- Click once inside the company window so QuickBooks, not another program, holds keyboard focus.
- Press F2. If nothing happens on a laptop, hold the Fn key and press F2 again; many laptops assign the top row to brightness and volume by default. Ctrl+1 opens the same window.
- Read the Product Information window, then close it with Esc.
You can press F2 with no company file open, but the window then shows only license details. The file statistics appear once a file is open.
Version, edition, and release: reading the left side
The left side identifies the product. It names the edition, such as Pro, Premier, or Enterprise, the year version, and the release, written as an R followed by a number. The release is the patch level for that year. Two machines can run the same version and still behave differently, because one sits several releases behind the other. When an error appears, note the release first; the right answer often changes with it.
The same panel lists your license number and product number. Have both at hand before any reinstall or service, because they establish what you actually own.
Customer, vendor, and transaction counts: reading the right side
The right side reports the file statistics: counts of customers, vendors, employees, and items, the total number of transactions, the file size on disk, and the date of the last Verify, depending on your release.
Customer and vendor counts matter because each name list has a ceiling. Pro and Premier hold about 14,500 names per list before QuickBooks refuses new entries; Enterprise raises the ceiling. A customer count in five figures tells you that condensing transactions will not relieve the pressure; the lists themselves need a list reduction service.
The transaction count gauges the workload behind the file. A company that has invoiced for a decade shows it here long before slowdowns make it obvious. High transaction counts paired with sluggish performance are the classic case for condensing an oversized company file.
Before an upgrade, a condense, or a repair
Confirm the version and edition before any version change. The edition decides which moves are possible, and the target version must exist on the machine that will open the file afterward. Looking costs nothing, but the moment you move from reading this screen to acting on it, take a backup first.
When we plan a condense, we schedule it for the stretch when staff need the file least, often a long weekend. Downtime then lands where it does least harm to the working week.
For repairs, a professional QuickBooks Desktop file repair starts with exactly this screenshot, because it states the release and the scale of the file in one image. That tells the engineer which program versions can open your data and what the job involves before the file travels anywhere.
Signs you opened the right screen
Three checks confirm it. The window title reads Product Information. The counts fill in within seconds of the file loading. Esc closes the window, and nothing you did in there changed a single record.
If the counts show zero, a company file is probably not open. Close the window, open your file, and press F2 again.
Where this screen stops helping
Counts describe scale, not health. A small file can still fail Verify, and a large one can run cleanly for years. The window cannot show a damaged transaction, a balance sheet fault, or a list entry that misbehaves; it only tells whoever opens the file what they are dealing with. Treat the F2 screen as context, not a diagnosis. Knowing that limit is most of its value.