Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Issue:
QuickBooks Enterprise Accountant Edition 24.0 / 23.0 / 22.0 downloaded installer(s) will not progress meaningfully past the unpacking screen. The installer will unpack, then immediately display this error after the unpack completes. I have also attached a .gif of the entire installation attempt:
"Intuit QuickBooks Desktop Installer"
"Please restart your machine and re run the installer."
Please note that QuickBooks Enterprise Accountant 21.0 and earlier WILL install properly.
Could be a coincidence, but we did notice that 22.0 and later installed to the "Program Files" folder on the other devices, as opposed to the "Program Files (x86)" for 21.0 and earlier, so it may have something to do with x64?
Hardware:
Win 2019 and up to date, 16gb memory and 50gb free space.
The hardware and OS should not be the issue. I have two other literal exact hardware/software duplicate devices where the installation was performed flawlessly; one device created about the same time, the third created around two years later.
All suggested fixes we have attempted:
● Several restarts
● Administrator/compatibility modes/Microsoft installation diagnostic/various folders with various read permissions
● MS Visual C++ Redist repair/uninstall/reinstall for versions 200[removed]013/2015-2022 x86/x64
● MS VST 2017
● QuickBooks Tool Hub: QuickBooks Program Diagnostic Tool , QuickBooks Install Diagnostic Tool , 3371 Error Fix
● Installers from CAMPS and the Intuit official download site, different editions (enterprise, accountant, pro, trial)
● Silent installation
● QuickBooks ProAdvisor support, Glance share
● This suggestion (framework.xml edit): https://quickbooks.intuit.com/learn-support/en-us/install/installation/00/518342
● This suggestion (selective startup): https://quickbooks.intuit.com/learn-support/en-us/install/re-quickbooks-2022-installer-keeps-forcing...
● Transplanting the installed files and registry entries from the duplicate hardware installations, then attempting a repair (we realize this one was a stretch)
Could be a coincidence, but we did notice that 22.0 and later installed to the "Program Files" folder on the other devices, as opposed to the "Program Files (x86)" for 21.0 and earlier, so it may have something to do with x64?
Correct.
Thanks for reaching out to us, @ClearManage.
I understand that having issues like this can be time-consuming and cumbersome. Even trying out the fixes still, you're having issues. For this, I want to ensure that we address this.
Please know that this community is only able to provide basic troubleshooting for software issues. We would still recommend that you continue working with our Technical Team. They can pull up your account and open a ticket for investigation.
Follow these steps to contact them:
Then, to ensure you'll be assisted on time, please visit our support hour's page. It contains the exact time when our support team will be available.
Refer to this article to learn more about our contact options and support availability: Contact QuickBooks Desktop support
I'm also including this article as a reference guide in case you need to restore a backup of your company file in the future: Restore a backup of your company file
If there is anything else I can do for you, please don't hesitate to add any details below. I'll be there to help. Stay safe and enjoy your day.
Thank you for your reply.
We have been working with the QuickBooks ProAdvisor team, we have an open ticket, and I am expecting a continuation of our support in 12 hours. We have already spent 6+ hours in a call with multiple specialists with no headway.
This community post is an attempt to reach out to the community to try to solve this as swiftly as possible, as well as document this issue for future community members and support staff.
You have clicked a link to a site outside of the QuickBooks or ProFile Communities. By clicking "Continue", you will leave the community and be taken to that site instead.
For more information visit our Security Center or to report suspicious websites you can contact us here