Trying to install QuickBooks Premier Pro 2022 onto Windows Server Essentials 2016 with error code 1603

I have been trying to figure out why QuickBooks Premier Pro 2022 will not install on Windows Server Essentials 2016.

It gets a quarter of the way in and then throws an error 1603.

I’ve searched high and low and HATE Google results. Nothing but handpicked garbage content farm webpages that do not help at all. I miss you could find an obscure blog on the first or second page with a fix right there. Instead, you get this ad-filled almost AI created gibberish with nothing but rehashed “fixes” from every other website that, again, is filled with nothing but ads.

I’ve tried uninstalling the C++, .Net Framework, etc. to no avail.

I just downloaded a trial of QuickBooks Enterprise 2023 and it installed with NO PROBLEMS.

I stood up a Server Essentials 2016 virtual machine and was able to install QuickBooks Premier 2022 OK with no problem.

However, I came across at least three other people who have had a problem with trying to install QuickBooks Premier 2022 onto either Windows 10 or a server operating system.

If you came across this and fixed it, please comment below. I’ll do the same if I find a fix. I know it will make a lot of people happy.

An interesting update happened last night. I downloaded a trial of QuickBooks Enterprise 2023, and it installed within five minutes.

I’m trying to run Process Explorer and Process Monitor, but am coming up short. If you have any expertise in either of these programs and troubleshooting what might be causing the install to fail with error 1603, please leave a comment below.


I used RegScan and performed a scan on all registry hives for “QuickBooks” and then exported them out and finally deleted them all.

I rebooted and sure enough it fucking installed. I knew it was a rogue fucking registry key. I hate Microsoft and Intuit!

Windows 10 start menu not responding/Outlook prompting for password using modern authentication window, but it’s blank

For those of you who encounter the above issue and attempt to use PowerShell to run the Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”} but the process never finishes, check the permissions on these two registry keys: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer and HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders – it should have a user called All Application Packages with read permissions.

In particular, the second one. I had an issue where the Get-AppX command would not complete on a Windows 10 Dell OptiPlex machine. I tried restarting to no avail.

I checked on the first registry key and All Application Packages were listed with read permissions for that key.

I checked the second, and All Application Packages were not there at all. I had to go to Advanced, Select a principal, if you’re on a domain, change the From this location: to the actual computer you’re using. Enter All Application Packages into the object name to select the box and hit OK.

Make sure it has read permission on the second registry key.

I rebooted the machine, and the start menu was working. I was also able to input the user’s Outlook password.