Question

qbmapi64 ERROR!!!

Forum|Forum|3 months ago
March 12, 2026
14 replies
36 views

After logging into company file, is anyone else getting a pop-up box with "qbmapi64.exe - Entry Point Not Found"? File name "D3DCOMPILER_47.dll" is looking for the code "CxxFrameHandler4".

After 2 1/2 hours on the telephone with support, they tell me it is not a Quickbooks issue and can't help me. When my IT teams tells me it is a Quickbooks issue.

PLEASE HELP!!!

QuickBooks Enterprise Suite

SIAB

Level 2

Which QB Desktop year version and Windows OS do you run?

Can you open the sample file?

L

leavis

We are running into the same error at my company on QB Enterprise 24 R19 running on Windows server 2019 when trying to open a file. Also selecting Help>About Automatic Update causes the error to pop up.

We restored back to QB R18_67 and everything is working.

M

mackusa

Same issue here. Just did a QuickBooks update and got this same issue. These errros happen 9 times out of 10 with QuickBooks updates. Really wish there was good alternative. I have tried the QuickBooks Tool Hub, reinstalling DirectX, reinstalling C++. Nothing works.

L

LTenhet

We have the same issue. Ran all the toolhub, completely uninstalled and reinstalled, installed VC_redist, ran SFC. It's a QUICKBOOKS ISSUE.
FIX IT QUICKBOOKS.

L

LTenhet

This is ridiculous. I've done all the ToolHub, reinstalled several times, did SFC, DISM, redistributable download, fresh install from an old version to update, fresh install from the new version to update, windows updates, and it still has this error.

This is obviously on your end Intuit, I'm having to restore the entire server to yesterday before the update just so people can work, this isn't acceptable at all, stop putting out updates without testing them.

L

LCress1

Following this thread and anxiously awaiting a solution! Experiencing this exact issue with 2 of our 5 users working remotely via VPN. We have been unable to resolve using all the recommendations. It makes our work incredibly dysfunctional.

B

biznetplus

We are seeing same error on Windows Server 2019 (physical server). Reverting back to 2023 for now. Quickbooks please address this issue!!

B

biznetplus

We are seeing the same error here in Windows Server 2019 (physical server). Reverting back to 2023 for now until this is resolved. Quickbooks please look into this!

B

BCT2015

I ran into the same error. Everything was working fine until I updated QuickBooks 24 on server 2019. The mapi64 error suggests it had to do with email. What I found out worked was after the update, I uninstalled Office 64 bit rebooted and then installed Office 32 bit. The error went away and everything worked as it should again. It seems to be an issue with 64bit Office and QuickBooks after the update. Hope that helps someone else.

M

matthewdaytonanetworks

I was able to resolve this issue for an instance of QuickBooks Premier Accountant running on a virtual instance of Server 2019 that multiple users access via RDP, all running QuickBooks under their own user sessions. Based on what worked I see no reason it wouldn't apply in other environments.

The version of D3DCompiler_47.dll that QuickBooks installs does not work; renaming or removing it just prompts QuickBooks to reinstall the same bad copy. The following steps did resolve:

Close out all instances of QuickBooks (may need to kill the qbmapi64.exe process).
Rename the copy of D3DCompiler_47.dll to D3DCompiler_47.dll.old in the install folder. Typically this would be C:\Program Files\Intuit\QuickBooks 2024\
Locate the system copy of D3DCompiler_47.dll in System32 (C:\Windows\System32)
Copy this file and paste it into the QuickBooks install folder (C:\Program Files\Intuit\QuickBooks 2024\)

This resolved the issue for me.

The underlying cause appears to be a bad version of D3DCompiler_47.dll packaged with the latest release of QuickBooks 2024.

T

TylerVault

This solution worked for us!

D

dbogot

Has anyone gotten anywhere with Intuit yet on this issue? We have the exact same situation - running QB on a virtual machine, which I have to believe is a very common thing. Our IT company says that everyone they know of running QB locally does so on a server that is a VM, not physical.

Clearly, this is something that Intuit needs to step up & fix, if they haven't already. I can confirm that I ran the QB update on 3/14 and got this failure. The only solution I know of is to uninstall & reinstall QB, then intentionally NOT update it....

Intuit, it is ridiculous for you to hide behind the VM story to avoid this issue. Let's see if we can determine how many companies are affected by this -- please comment on this thread & let us know!

T

tsd81xx

We updated yesterday and have the same issue! It is criminal that Intuit mandates these updates but then shrugs their shoulders when their updates cause problems. I have not seen any updates yet that actually fix the bugs I would like to see fixed and we have not had an upgrade of QB that has not caused some sort of problem.