Windows Update kb5026435 breaks client to server communication

I understand that you're experiencing issues with Windows Update KB5026435, CAVSC. Let's collaborate to resolve this problem.

Microsoft has released the optional KB5026435 Preview cumulative update for Windows 10 22H2 with two new features and 18 additional fixes or changes. To determine if there is a problem caused by the installation of the Windows Update, we can restart the database server manager in the hosted computer. It'll help identify any potential issues or faults that may have occurred.

First, you'll have to restart QuickBooks Database Server Manager (QBSM) on the current device on which the software is hosting the company files. In another way, we can also say that you'll have to restart the device on which the software is hosting the server.

From the installation wizard of QuickBooks, you would be getting the option to install the QBSM.

The Database Server Manager will start on its own if you have already installed the complete program in the server system and thus, shall run once you get started with it.

Here's how to restart:

1. Go to the Windows Start menu.
2. Search and open Control Panel.
3. Select and open Administrative Tools.
4. Hit Services from the list.
5. Right-click the QuickBooksDBXX service and then click Restart.

Moreover, I've added this reference to guide you in maintaining your software up to its latest release: Update QuickBooks Desktop to the latest release.

We'll always be here if you need anything else managing your desktop program and other QuickBooks concerns. Feel free to reply in the comments below. Have a good one!

I restarted the machines multiple times. The update did not appear to have any negative effect on the QBSM. I had a client computer without the update have no issues connecting to the company file and putting it in to multi user mode. Once I installed the windows update, the client computer could no longer open the company in multiuser mode. Removing the update from the client machines returned everything to working order. The current webpatch for QB is R9. This was applied to all machines involved long before the issue arose. I also used the update feature inside QB Desktop Pro 2022 and verified all installations were up to date. Only the windows update has any effect on the client machines connecting to the QBSM. If it is installed then the clients will not communicate to the QBSM when opening a file which prevents the use of multi user mode. If the update is uninstalled the clients connect correctly and can enter multiuser mode.

I got you, @CAVSC. Let's figure out what's going on and find a resolution while trying to update your company in QuickBooks Desktop. 

You can run the Verify/Rebuild tool. Verify will catch any damaged data. Rebuild will attempt to fix the damaged data detected. It also permits your QuickBooks software to restore the data inside the company file.

Let's ensure creating a backup copy of your company file before doing the Verify and Rebuild process. If changes occur, having a backup copy allows you to restore it to undo the changes.

Follow the steps below on how to verify data:

1. On the top menu, click File.
2. Choose Utilities.
3. Select Verify Data.
4. Click OK when you see the message.
5. If Verify finds an issue with your data, press the Rebuild Now or View Errors.
6. Click Close or View Errors and take note of the specific error message.

Next, here's how to rebuild data:

1. On the top menu, click File.
2. Choose Utilities.
3. Select Rebuild Data.
4. Click OK if you receive a prompt to back up your company file.
5. Press OK when you get the message "Rebuild has completed and proceed to the next step.
6. Then, run Verify Data to make sure there's no error.

If the process above has zero results, I urge you to call our support team. Follow the steps in this link: Contact QuickBooks Desktop support.

You can also scan this page for other insights on importing and exporting limitations in QuickBooks Desktop: Export, import, and edit IIF files.

There you go, @CAVSC. Kindly inform me how it goes after trying the possible keys above. Thank you for visiting us. 

I did this and reinstalled the windows update. I can still open the company file but QBSM doesn't show a connected company file and I can not switch to multiuser. I uninstalled the windows update and all works fine again. There is obviously something in the windows update that interferes or alters the way that QB Pro 2022 connects to the QBSM that needs to be looked into.

Thanks for getting back with the Community, CAVSC. I appreciate your detailed information.

Since you're still encountering issues opening the company file in multi-user mode after performing our recommended troubleshooting, I'd recommend getting in touch with our Customer Care team. They'll be able to pull up your account in a secure environment, conduct further research, and create an investigation ticket if necessary.

They can be reached while using QuickBooks.

Here's how:
 

1. In your top menu bar, go to Help, then QuickBooks Desktop Help.
   
   
    
2. Click Contact Us.
   
   
    
3. Enter a brief description of the issue in our Ask a question (or tell us what's wrong) field, then hit Continue.
   
   
    
4. Select We’ll contact you for a callback or Message Us to start an instant messaging session.

Be sure to review their support hours so you'll know when agents are available.

Please feel welcome to send a reply if there's any questions. Have a wonderful day!

All of these fixes are just for single user or in house servers, we are on Right Networks per QuickBooks recommendation and this isn't a fix for us!!!

The other option we were given is to use another email outside of Microsoft and THIS IS A HORRIBLE Solution and very unprofessional on our side as well as QB. Our company domain is our signature!

This needs to get fixed ASAP as it is costing us money! 

We pay too much to use QB for these kind of problems to always be popping up!!!

What ever happened with your server?  Is there an end to the story?

We are STRUGGLING.

I/T is stumped.

Support is clueless.

We are still wading through Reddit trying to find an answer.