Same here, after the R12 update QB DT Ent V23 will not run on Server 2012,

We are still able to use as a share file for local desktops. But on the server the program is a mess.

QB/Intuit states V23 is incompatible with Server 2012.   And there's no solution. Or none that's acceptable.

If you go back to R11 in multiuser you are not going to get very far...

We have six users and this is a mess.  QB Intuit seem to always find ways to screw things up.

This issue cropped up after the update on our Windows 2012 R2 RDS server where we have users remote in from satellite offices. This caused major havoc and our users couldn't do their work. I wound up having to spin up a new Windows 2022 server, configure a new RDS server on top of that and move the users over. It took me all weekend. I should be sending Quickbooks an invoice and a lawsuit letter for causing such a mess.

THEY DIDN"T EVEN TEST IT ON SERVER 2012 BEFORE THEY RELEASED THE UPDATE! THIS IS HOW PATHETIC THEY HAVE GOTTEN.

They aren't about to fix it.  They have punted.  You can't get them to have a conversation about it, just like everyone else has said.  It's disgraceful.   They blame it on 'the developers'.  If I had 'developers' who rolled out something that couldn't be rolled back or repaired without blaming a third party... AFTER the fixed the issue, heads would roll.

Yea, they will not fix it guys. Your only options are to rollback to the previous update version and then block access to the update folder Quickbooks uses to stop it from updating using permissions, or upgrade the Operating System.

Same here. Hoping that Intuit reconsiders the compatibility of QuickBooks Enterprise V23, with Windows Server 2012

They won't fix it, but they have no problem jacking up the monthly subscription price. 

Thank goodness for this post, because we had the exact same thing happen to us with Enterprise Desktop R24. Spent hours and hours trying all sorts of uninstall/reinstalls, running the Tool Hub and File Doctor, on the phone with support, etc, and nothing was working. Found this post and symptoms were an exact match, and sure enough an install of the client on a non 2012R2 workstation got our access back. Pretty crazy that they are able to just drop a forced automatic update that removes support for an operating system with zero form of notification.

I know right? And even more crazy that you had to spend hours on the phone with support because they aren't even aware that support was dropped themselves lol.

Took a while to find this post but yes I have been having issues with the versions after R11 but my problem is on Windows 2022.   

Thanks for bringing this matter to our attention, vb5. I'll route you to our support personnel so they can dig deeper into your concern.

If you're using QuickBooks Desktop (QBDT) 2023, Windows servers 2016 and the latest versions should resolve any company file crashes or issues. Since this is not the case on your end, I recommend contacting our support team. They can help investigate this matter further.

Here's how you can connect with them using your QBDT:

1. Open your QuickBooks company file.
2. Go to Help, then QuickBooks Desktop Help/Contact Us.
3. Click Contact Us.
4. Give a brief description of your issue, then Continue.
5. Sign in to your Intuit account, and select Continue. After that, hit Continue with my account.
6. Choose a way to connect with us:

• Chat with us to start a conversation with our personnel. 
• Have us call you to get a callback from the next available agent.

You can also call their hotline number and learn about our support's availability from this link: Contact QuickBooks Desktop support.

Finally, you may also utilize these resources to have a better experience around the system and insights about your license details:

• System requirements for QuickBooks Desktop 2023.
• Find QuickBooks Desktop license info.

I'm always open to assisting you again. That said, if you have follow-up questions about QuickBooks system requirements and compatibility, hit the Reply button. I'll be here every step of the way.