I'm attempting to move my QB 2015 Pro application from a Windows 7 machine into a freshly installed Windows 10 machine.
I've successfully loaded the application onto the Windows 10 machine and am being prompted to 'Update QuickBooks' where a number of files do download. The process appears to be successful as all files appear to download, however when I exit and re-enter the application, I'm prompted to again download the last item in the list - Critical Fixes. It would appear that the 'Critical Fixes' file is not being accepted as each time I enter the application, the same file (16117.81 Kbytes) is queued and downloaded.
Intuit clearly thinks that this file should be part of the application (given the name of the download), so I would like some advice as to how to get past this continuous loop.
All thoughts and ideas are welcome.
I could ignore the message, however I don't have any confirmation that the 'Critical Files' have been loaded into the application. I don't want to risk any problem with the integrity of my datafile down the road.
Until I get a satisfactory solution, I'll continue to run the application out of the Windows 7 machine, which has the Critical Files installed.
Thanks for your suggestion.
Hi there Rob! I've responded on your other thread, Unable to Register QB 2015 on Windows 10 Machine. I've answered your questions from this post as well as what you asked about there. It's important to me that you have a sense of what's going on and know your options moving forward. I'll be here if you have more questions.
First of all, thank you for leaving such a detailed and comprehensive response to my question. I read through the linked material you provided and I do have both .NET Framework 3.5 and .NET Framework 4.8 services enabled.
I'll take a look at downgrading the 4.8 Framework and advise as to its outcome.
Hi again Rob,
I'm glad my response was helpful to you and that you've managed to register the product. I've been doing some more research into what could be going on as well with this update looping situation. While you were able to successfully install and activate the 2015 software, the program may not work properly on the Windows 10 platform in general and that may be what's causing the loop of trying to update.
You're still welcome to try the .NET Framework troubleshooting I mentioned, but if that doesn't work, it may just be that the Windows 10 system isn't going to work for the 2015.
I'll keep an eye out for a response from you. :)