cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Level 1

I can't open Quickbooks Desktop Pro. Tool Hub has been stalled from over 2 hours

Quickbooks won't open today. Downloaded and started The Tool Hub program to fix the problem.  Tool hub opened a command screen and that script started. But now that script is stuck at "Installing/Repairing .Net 4.6 (Please Wait - DO NOT CLOSE THIS WINDOW ! ! ! ) ..".  Been stalled at that point for more than 2 hours now. Initially said it would take about 10 minutes?  Tried to open Quickbooks to find out if the script was actually done running but now luck. Still doesn't open. Anyone have any ideas about what to do next?  

2 Comments
Highlighted
Moderator

I can't open Quickbooks Desktop Pro. Tool Hub has been stalled from over 2 hours

Let's get your QuickBooks working, Neil25.

 

There are different reasons why QuickBooks won't open. It could be there is a damaged QuickBooks or Windows component on the system, or etc.

 

The QuickBooks Tools Hub is one of the solutions that we suggest. However, we have additional solutions if that won't work. You can follow Solutions 2- 5 in this article for more details: QuickBooks Desktop doesn't start or won't open.

 

If it is necessary for you to fix the .NET framework manually, you can follow the detailed guide in this link: Manually fix Microsoft .NET Framework errors.

 

Let me know how this goes so we can further assist you in getting your QuickBooks to work.

Highlighted
Level 1

I can't open Quickbooks Desktop Pro. Tool Hub has been stalled from over 2 hours

Thanks James,  I finally closed the cmd.exe window after I tried again to open Quickbooks. Then I closed all the other open programs on my computer and rebooted the computer. Then opened the Tool Hub again and trying once more to find out if it finishes this time. Left it for over an hour and it is stuck on "Repairing .Net 4.6 (Please wait - Do Not Close)" again.  I tried looking the task manager for CPU, memory and Disk usage to see if something was still processing but I don't see much going on there.  If no change after a while I will close the cmd.exe window and try what you suggested. Your input and ideas are very much appreciated. 

Neil 

Need to get in touch?

Contact us