-
-
Notifications
You must be signed in to change notification settings - Fork 9
FAQs
Yes, it is.
You don't have to, but it's the only activator that fully supports all versions of QuickBooks Point Of Sale.
This refers to having, for example, both POS v2019 and POS v2012 installed together on the same system. This is not supported by qbactivator, but, if necessary, you can install another version of the same product separately.
License keys are not provided to the user beforehand. qbactivator will automatically install the appropriate license keys for the version of QuickBooks Point of Sale being installed on the system. This is to ensure stability during activation and avoid any potential issues that may arise from using invalid or incorrect license keys. However, if you have your own license keys, you are able to use them with qbactivator through the "I have my own license" menu option.
License keys are reviewed regularly to keep qbactivator functioning as intended.
Not yet. qbactivator
was specifically designed for QuickBooks Point of Sale and was not intended to be used with other QuickBooks Desktop products. However, activation support for other QuickBooks Desktop products is being worked on and will be added in a future release.
Tip
Go here for a list of solutions to some QuickBooks-related issues and error codes.
The most common reason for this:
-
qbactivator
is manually started as administrator. The activator will prompt the user for the privileges when it is ready. Run the activator normally with a double-click. - Be sure that you are not running qbactivator from within the ZIP file. You should extract the contents of the ZIP package and then run qbactivator.
This other factor is very rare and should be used as a last option.
Check if System32
is added to path:
- Go to "System" under settings (
WinKey + x
, thenY
) - Select "Advanced system settings" and click "Environment Variables" in the bottom-right
- Look for
PATH
under system variables and click "Edit" - If
System32
is not in the list add it by clicking "New" and entering%SystemRoot%\System32
- Restart Windows and run
qbactivator
- If it still does not start, add
%SystemRoot%\WindowsPowerShell\v1.0
and restart
Note
Create an issue ticket or report it to me on Telegram.
- Include your operating system version and the version of
qbactivator
you were running when the error occured as well as any other useful information related to the crash. - Send me a recording on Telegram of what happens when you run qbactivator
The script was closed during activation or ran into a problem while attempting to restore the client
- Run
qbactivator
- Select Troubleshooting
- Select Lv1: Repair
- Exit
qbactivator
Important
This is most likely a driver issue. Download this C++ redistributable repack and run it to install the Microsoft Visual C++ Redistributables (2005-2022).
★ This may be able to fix other runtime issues with QuickBooks. It would be good to try this solution for a fix.
Check for any updates to this repack here.
This occurs when there is an attempt to launch multiple instances of QuickBooks Point of Sale, which means that software was not completely terminated before it was relaunched.
- Restart your system and start
qbactivator
-
Resolve through troubleshooting steps:
- Go to troubleshooting menu in qbactivator
- Select "Lv3 Client module: Re-activation" option (this will clear out the current activation)
- Return to the main menu and proceed to re-activate QuickBooks POS as you did before
-
There may be compromised files in your QuickBooks Point of Sale installation.
-
You may have multiple QuickBooks products (QuickBooks Pro/Enterprise etc.) installed on the server workstation.
- Uninstall QuickBooks Pro/Enterprise/Accountant and Point of Sale (if installed)
- Run
qbactivator
and install QuickBooks Point of Sale - Install previous QuickBooks products (Pro/Enterprise/Accountant)
This warning is typically displayed when the registration code is not accepted, but it is unlikely to occur when copying and pasting the code.
- Ensure that
qbactivator
is running when attempting to activate - Check that you entered the registration code correctly
- Restart
qbactivator
without the installer present, select the store and request activation-only - Reinstall QuickBooks Point of Sale
This dialog will be shown on a Client installation if you have a different license on the Client workstation than the Server workstation in the store location. Client and server workstations in the same store location should have the same license.
- Click "Add License Now"
- Check the box for "The agent has confirmed..."
- Click Next, and close.
The license issue should be resolved.
- Look for the folder
C:\Program
- Delete it
- Restart QuickBooks
If this is not resolved, you may need to reinstall the software, or in worse case, reinstall your operating system.
PowerShell is a task automation and configuration management program from Microsoft consisting of a command-line shell and scripting language designed especially for system administration.
While the script incorporates PowerShell code, it is not necessary to run the script with PowerShell since it can be run as a regular batch script with Command Prompt (cmd.exe
). Also note that qbactivator
was ~5% faster when executed with CMD due to the smaller overhead compared to PowerShell. However, the script can be run with both interfaces, and users can choose the one that best fits their needs or environment.
You shouldn't need to update PowerShell if you are running qbactivator
on Windows 10 or 11. However, if you choose to update, or you are on Windows 7, follow these instructions to successfully update PowerShell on your system.
Tip
Didn't find your issue? Join the forum on Telegram
Download now • Licensed under BSD 2-Clause • Need help?