Hey there again, @harrylubansky. 

Thanks for chiming back in on this thread and giving us some more information about your issue. 

I recommend reviewing our system requirements to narrow down the problem: System Requirements for QuickBooks Desktop 2022. 

If the issue persists, I suggest contacting our Customer Support Team for further assistance. 

Keep us updated on how it goes. I want to ensure that you get back to running your business. Have a wonderful day! 

@harrylubansky 

Consider to install the trial license for QBD 2021 to compare them all.

I had already verified the win2012R2, RAM and storage requirements, which the server meets.

Same thing here.  Win10, Qb2021 Premium

Thanks for all the effort everyone put into solving this.

I tried Jim7Mc's/amtrucken's solution reinstalling VC_redist.x64.exe 2015-2019 but still got the same thing.  All accounts in use are non-administrator accounts.  I kept doing everything using "Run as administrator".  Finally I logged into an administrator account and started QB there.  (Also temporarily disabled my AV and MS Ransomware Protection -- don't know if that was necessary, just standard practice.)  It worked!  So "Run as administrator" is not always sufficient for full administrator privileges for installs.  At least not with QB!  (First time I've ever seen "run as administrator" not work for installs that require administrator privilege.)  One more thing to add to the list of possible solutions!

None of the posted suggestions worked for me, so this is what I did:  Go into Add/Remove Programs, click QuickBooks, and click "Change" option - then do a Repair.  Let it do the repair and reboot.  Then run QB - it recognizes there is a new version and successfully installed it.

This worked!  Yes, somebody tell the support team!

I didn't see the original post TESTA1 was replying to... But here is her post which resolves the issue with QuickBooks Pro Plus 2022. 

(We've spent at least 20 hours and a countless amount of grief.  QuickBooks support was awful... 3 hours on the phone with them... Their final response, "Sorry, we've done everything, you have a problem with Windows".  YEP! They literally said, we can't do anything to help you.  I have Windows 10 Pro and it's updated.  WTH!) 

Okay, I've complained enough... Well, maybe not... But thanks to the post from TESTA1, I can finally get back to work.

(FROM TESTA1:  You Rock!!! Reinstalling VC_redist.x64.exe Worked Perfectly! I Wish QuickBooks would move this solution to the Top Spot! It would have saved me 20 Hours of Greif.

Thank You!)

Hi Missgoode2shews1,

Thank you for letting us know that the solution from other users worked. Thus, we've created a Community so everyone can share their QuickBooks expertise and tips. I'll take note of your feedback so our team can handle similar issues better going forward.

You can always visit us back in the Community if you have other concerns. Take care and have a good one!

I went into the control panel \ [Add / Remove Programs], chose the lates 2015 QB redistributable, did [CHANGE] then repaired it. . . then after, it launched/allowed the update to install.

Much easier than removing/downloading/reinstalling 5 different subversions of C++ Redistributable.

Simpler yet, I just went into the control panel, [Add/Remove Programs], scrolled down to the latest version of C++ Redistributable (in my case 2015), then [Change], then [Repair]

Saves uninstalling/reinstalling all the subversions. . . worked for us.

Greetings friends,
i had same problem after Quickbooks enterprise requested update, and after updating asking for unlimited reboot.
so i'll show you the prober way to fix this issue:
1- Open control panel and uninstall Quickbooks, and all Microsoft C++ installed
2- Go to C:\Program Files (x86) and delete Intuit file as administrator
3- Go C:\Program Files\Common Files and delete Intuit file as administrator
4- Fresh install same version of Quickbooks that was running before
5- It will request a reboot, make the reboot.
6- After rebooting, you can use Quickbooks normally

Hopefully this will help you, don't forget to mention if this solution works for you :)

After 4 days of troubleshooting trying to install QB Enterprise 2022 on Windows 11 ARM running on Parallels 17.1.4, I came across this post and followed the steps. Reinstalling VC_redist.x64.exe WORKED! Thank you for posting this fix! Intuit needs to incorporate this fix into their installer, now that M1 Macs are working their way into the world!

another assfucck install erroring out before a short week! I cannot even find the manual install file like before! nothing was fixed for 2022 enterprise, oh and the mandatory nov2022 update offers nothing worth a forced update with lockout. horrible programming.

Trying to reply to my own post from July 11, 2022, but the forum keeps putting it here.

Again!  Just did the the latest update.  QB Premier 2021. QB now can't open our company file.  Their diagnostic utilities just give useless / false information and steps that accomplish nothing. When using a "standard" Windows account the QB update will only work if QB is started with "Run as administrator" (using mouse right click on the icon).  BUT don't do it!

After the update and required reboot, upon trying to open our company file QB gave me an error about being unable to communicate with the "server". 

Tried my above "solution" but this time it didn't work.  Same message about being unable to communicate with the "server".

After trying various things to open our QB file, including using a Windows administrator account (instead of the usual "standard" account)...

1. Rebooted again.

2. Logged into a Windows administrator account on the server computer.

3. Cleaned out from the QuickBooks folder a bunch of old unused company and related QB files (moved them into a subfolder) and other old unneeded files.

4. Opened the company file in QB on another computer after it had been updated -- It opened with no problem.

5. Opened a different QBW file on the server computer.  It worked.

6. Opened the problem company file.  It worked!

7. Logged back into my usual "standard" Windows account.  QB opened the company file with no problem.

I have no idea why it works now.  And neither would anyone else including Intuit!

From now on I will do the QB updates in a Windows administrator account.  (If you always run QB in an administrator account you probably aren't running into this issue.)  Hopefully QB will work properly the next time without any problems.

deleted

Again! QB can't open any company files. None of the above worked.

There were a bunch of Windows 10 updates pending. I normally only do updates on the weekend. Went ahead and did the updates and QB worked perfectly after the reboot. Weird.

Do not do this!!! As it will permanently disabled your computer. And prevent you from signing back into windows.

bunk

Here was our solution to the problem:

1. Uninstall Quickbooks.

2. Go to the Control Panel -> Programs and Features

3. Uninstall every application labeled "Microsoft Visual C++ ..."
4. Go to the hidden "Program Data" folder

5. Delete the "Intuit" folder.

6. Go to the "Program Files (x86)" folder.

7. Delete the "Intuit" folder.

8. Find the hidden "App Data" folder inside your user folder.

9. Go to the "Local" sub folder.

10. Delete the "Intuit" folder.

11. Reboot

12. Log in with the computer local administrator account.

13. Reinstall Quickbooks.

This should give you a fresh installation of the correct Microsoft Visual C++ distributions.

This is absolutely ridiculous that us IT's have to deal with such an issue constantly!!!  For Christ sake, put out one FULLY tested update no more than once a month..... Then make it SO WE CAN INSTALL IT !!!! Uninstalling and reinstalling is the long way around to avoid the fix to start. This has been an on going issue for more than a year!!! I pray the 2023 version we are about to deploy is better, and QUIT making everyone get an intuit account for Christ sake!!! 

Jim7Mc's solution to reinstall vc_redist x86/x64  is the winner for us!  Such godsend!!!

Quickbooks support needs to get better.  This sloppiness and the unhelpful comments to go through windows installer is inexcuseable...