Reading the QuickBooks Desktop version and release from the F2 screen
A QuickBooks company file and the installed program can report different version numbers, and reading both from one screen decides the upgrade path.
Version numbers cause more wasted work than almost anything else on a QuickBooks Desktop file. A program that has been updated on one machine, a file last opened on another, and a repair or downgrade quote that names the wrong year all trace back to the same confusion. One screen settles it in a few seconds, provided you read it carefully and share it carefully.
Open the file first, then the screen
Press F2 with the company file open and no other QuickBooks windows in the way. Ctrl+1 does the same job on most Windows builds; if one does nothing, try the other. What appears is a two-part window: the upper section describes the program installed on that machine, the lower section describes the company file currently open.
Our engineers ask for this screen before anything else when planning an upgrade, a downgrade, or a repair, because it answers three questions at once. Which edition is running, which year, and which file the numbers belong to.
The preconditions are simple. Sign in as the Admin user, or as a user with full permissions, so the file opens fully rather than in a restricted view. Have the company file open, not the No Company Open screen, because the lower panel is blank without a file. Work in single-user mode if the file is hosted, so nothing else is writing to it while you read.
Reading the product line, version and release
The top panel gives the product name, which carries both edition and year, for example QuickBooks Desktop Pro 2021 or QuickBooks Enterprise Solutions 22.0. Enterprise counts its own way, so a number that resembles a year may not be one.
Below that sit two easily confused entries. Version is the program build, tied to the year or edition. Release is the patch level, usually a letter and a number such as R3 or R7, applied by a program update. A release update patches the software; it does not change the format of the company file. That distinction matters when somebody asks whether their file is on a newer version, because the answer can be yes for the program and no for the file.
Telling the file's version from the program's
The lower panel, File Information, names the open file, its folder, its size and the user count. That is the file's identity, and it is not the same as its format.
The file's format is a third thing. A company file carries a format year, and that format moves forward only when the file is upgraded to a newer program. It never moves back. A file opened once on a newer year cannot be opened again by the older program, and the error usually names the year rather than the file. If two people compare screens and disagree, this is the usual reason: one is describing the installed program, the other the file.
Capturing a screenshot worth sending
Take a screenshot of the whole window rather than typing numbers from memory. The Windows Snipping Tool, or the Windows key plus Shift plus S, will capture the region.
Crop before you send. The Product Information window can display a licence number and a product code, and neither belongs in an email thread or a chat message. Keep the product line, the version, the release, and the File Information panel; remove the licence rows.
Name the image plainly with the edition and year, not the company name. Send it alongside whatever else the job needs, which for a downgrade is typically a backup and the target version.
What if the screen looks right and the file still fails?
Then the version question has been answered, and the real problem sits somewhere else: a damaged file, a failed rebuild, or a format that needs converting rather than reading. This screen tells you what you have. It cannot tell you whether the file is healthy, and it cannot make a newer format readable by an older program. Those cases need QuickBooks file repair or a QuickBooks version downgrade, starting from a screenshot of this window.
Signs the reading was right
You have it right when the product line names both edition and year, the release shows as a single patch identifier, and File Information matches the file you meant to check. Cross-check the program side against Programs and Features in Windows, which lists the installed edition and often the release. If those two disagree, more than one year is installed on the machine, which is common and worth knowing before you update anything.
Save the screenshot with the backup you are about to make. Anyone quoting a conversion, a repair or a downgrade can work from that one image, and you will not have to reopen the file to answer the same question twice.