UNABLE TO INSTALL UPDATE - UPDATE STOPS AT 30% -WRITING SYSTEM REGISTRY VALUES - THEN RECEIVE ERROR 1712

I appreciate you letting us know, Nancy78191. I've got fixes to help troubleshoot errors when installing updates in your company file. 

QuickBooks Desktop uses Microsoft programs to run web-based aps. This error occurs when one or more Windows components are missing. To rectify this error, let's download the QuickBooks Tools Hub into your account. Beforehand, it's best to secure a backup copy of your company file and ensure your QuickBooks Desktop is on its latest release. This way, you'll always have its recent features and fixes. To begin: 

1. Close QuickBooks.
2. Download the most recent version (1.6.0.3) of the QuickBooks Tool Hub. Save the file somewhere you can easily find it (like your Downloads folder or your Windows desktop). Note: If you've installed Tool Hub before, you can find out which version you have. Select the Home tab.  The version will be on the bottom.
3. Open the file you downloaded (QuickBooksToolHub.exe).
4. Follow the on-screen steps to install and agree to the terms and conditions.
5. When the installation finishes, double-click the icon on your Windows desktop to open the tool hub.

Then, run the Quick Fix my Program from the tool hub. You can refer to this guide for more detailed information: Error 1712 when installing QuickBooks for Desktop. 

However, if the issue persists, add or create a Windows user with Administrator rights, then attempt QuickBooks installation.

Moreover, I'm sharing this reference to further guide you with other fixes of your data file: Fix issues when QuickBooks has stopped working. 

I'll always be available in this forum if there's anything else you require assistance installing updates in your account. Feel free to leave your queries in the comments below. Keep safe. 

I have Windows 11. Is there a different approach to installing the updates with that?

Hello, @skautz. 

Thanks for hopping in on this thread about installing an update for your QuickBooks Desktop. 

The recent QuickBooks release updates may appear to be stuck and take significant time for them to be installed. This could happen due to Microsoft Defender, or any software, scanning each QuickBooks Program file, which can significantly slow down the installation. 

When the Writing system registry values message appears, there are two options to resolve the problem: 

• Create a Microsoft Defender exclusion of QuickBooks files
• Turn off Windows Defender antivirus protection

To learn more about the actions above and how to do them properly, check out this guide: QuickBooks Update slows at writing system registry values. 

This should do the trick. I'm only a comment away if you have any other questions. Have a wonderful day! 

I work on a college campus where I have no control on shutting off Defender. I have spoken with our IT department and they may or may not be able to help me. Because they have increased security campus wide a may not be able to update. Any suggestions?

It's great that the campus is prioritizing everyone's safety with strict security measures, Skau. Don't worry, we'll look into every viable option to assist you through this challenge.

To tackle the update issue, the QuickBooks Tool Hub has added a feature where you can create an exclusion for specific QuickBooks files. By doing this, Microsoft Defender won't scan these files during installations, allowing updates to proceed smoothly. Here’s what you can do:

1. Set up an exclusion in Microsoft Defender for specific QuickBooks files.
2. Temporarily disable Windows Defender antivirus protection.

For more detailed instructions on stopping Windows Defender updates, you can check out this useful article: Stopping updates in QuickBooks Desktop.

Furthermore, if you experiencing an error when installing QuickBooks Desktop for Windows, you might find this article helpful: Error 1712 when installing QuickBooks Desktop.

If you have any further questions or need assistance with QuickBooks Desktop, please comment below. I'm here to help.

@skautz 

Last resort, consider to reinstall QB from scratch.