- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Other questions
I am so glad to have found this forum post. On 7/30/2025 our client that we provide IT support for created a ticket saying "I'm having issues with QuickBooks this morning. Sometimes it will let me pull up a screen that I want and other times it freezes up." When first opening the company file in QB on their desktops, it would take many minutes (10+) for it to fully load and then it was nearly impossible to do anything inside the company file without is locking up. The process in task manager kept saying "not responding." It was the same behavior on both computers, for both QB users.
We spent many hours working on the issue, doing all the normal troubleshooting things (updates windows OS, reinstalled QB enterprise 24, updating QB, running company file through QB tool hub, etc.). The client has 2 users who have QB enterprise 24 and their company file is on a local windows 2019 server that has SSDs. They access the company file through a mapped drive. I mapped the company file in QB using UNC path instead but that didn't help.
We called intuit and worked with them for many hours. They moved the company file (only) from the network share, which is on a dedicated SSD, over to the C drive of the server and then QB was quick for both users. They said the issue was with the drive QB company file was originally on and clsoed the case. But since only the company file was moved and no supporting files or folders, like the attach folder, we needed to continue troubleshooting.
I moved the company file back to the original drive, where the other supporting files/folders are. I got the user rdp-ed into the same server where the company file is and opened the qb file and it took 20 seconds for the file to open all the way and it was much faster. no issues. I renewed port in QB db server manager and ran scan. It repaired network problems. got back into the file while on the server and it was quick still. closed it. got back into QB on her pc and opening the file was again incredibly slow still. QB went into not responding on her pc when trying to close it.
Here were the QB versions through the organization at that point, all seeing the slowness except the server for some reason:
on pc 1 = R15_69
on server = r15_27
on pc2 = r15_69
I updated QB to r15_71 (latest as of last night) on every pc and the server and I got that version too on a computer where QB was not installed previously. On that new computer, I opened the QB company file thats on the server and saw the exact same slowness issues as on the other pcs. While it was opening, it said "not responding" in task manager. This proved to me that version 15_71 still saw the issue.
I created a new 50GB data drive on the server and moved the entire quickbooks folder (attach folder and all) to it. I opened QB on new the test computer and browsed to the UNC path for the company file on the server and opened the QB file but the slowness remained. it took a very long time to open and it said "not responding" while trying to open. So this proved that the network is not the issue nor is the drive the company file is on on the server.
So that got me thinking about what Intuit originally did - they moved just the company file and no other supporting files or folders, including the attach folder. So I moved the attach folder to a different drive and had my client open QuickBooks on her computer where the issue was first seen and QuickBooks only took 20 seconds to load the company file and it was extremely fast. The attach folder is 14 1/2 GB. I never noticed a bunch of files in that attach folder being opened, but it did feel like that when I found this out, that QuickBooks must be trying to cache those or do something with the files in that folder to cause the performance issues. My client needs those attachments in the attach folder because there are PDFs in there that correlate to the billing, etc. Right now that attach folder is on a different drive than the QuickBooks company file so at least they can operate but something needs to be fixed to get this back to how it should be. I'm going to try to get R15_58 and put the attach folder back and test.