QuickBooks 2014 Stops Working After Windows 10 Anniversary Update

Problem

Older QuickBooks, in this case QuickBooks Pro 2014, fail to open, or keep crashing on Windows 10, even if they were working before.

Background

QuickBooks Pro 2014 was installed on a client’s new Windows 10 computer, then tested with their company file which worked fine. But a day later, QuickBooks is crashing, freezing, and is completely unusable. It crashes while trying to activate the program, or even just open it and skip the registration and get into the company data.

The problem is that the computer came with out the big “Anniversary Update” that came out in August, 2016. Once the update automatically installed, it broke QuickBooks.

Solution

A short or medium-term solution is to go in an roll back the update to remove the Anniversary Update. With that off QuickBooks should work again if it did before with Windows 10. But this is only temporary, as other big updates will come, and will likely break it again, and it is not a good idea to stop updates (and Windows 10 makes it tricky to as well).

The only good long-term solution, unfortunately, is to buy a newer Quickbooks. QuickBooks 2015 should work, but since there is a 3 year window that Intuit supports QuickBooks, it is wisest to bite the bullet and upgrade to the latest version (2017 as of this writing).

Sources

  1.  http://blog.quickbooksusers.com/quickbooks/windows-10-older-quickbooks-fail/ 

Wiki Page:

If there is anything you think needs to be added, expanded upon, or corrected, you can comment below, or better yet, make some edits on this topic’s wiki page HERE.

Outlook Crashes After Office 365 Password Change

Problem:

After changing an Office 365 Exchange password, Outlook starts crashing. Event viewer gives error message with Exception code: 0xc000027b.

Background:

If you change the password (or are forced to by the admin) you may experience this crash. I found it to happen with Windows 10 Anniversary Update and Outlook 2016, but it looks like there may be other combinations, at least with Outlook 2013 that may also have the same issue.
In the past when I’ve had this issue, I’ve simply made a new profile, but this time there were a couple other accounts set up, and so I wanted to avoid settings them all up again. The computer had not been rebooted, so I tried that, then I also tried to start Outlook in safe mode, and neither worked. I made a new profile with no email accounts, and it opened fine, so I knew it was something with that profile. After searching a bit online, I found the solution.

Solution:

The password, even after updating, was not updated on the computer. The Credential manager still had the old password, and Outlook was not updating the password before the crash, so every time Outlook started, the same crash kept happening. This solution was pretty straight forward:
1. Click on Start, type “Control Panel” (without quotes) and click on the search result to open it up.
2. In the Control Panel, search for the Credential Manager. Click on it to open it.
3. In there find the Office Account, click on it, then click edit. Then update the password to match your new password. Even though there was nothing under the user, it would not let me save without putting something in there. I used the full email address, although I do not know if it would work with anything else.
After this, Outlook should open and continue to work as it did before the password change.

Sources:

  1. https://answers.microsoft.com/en-us/msoffice/forum/msoffice_outlook-mso_win10/outlook-crashes-on-startup-2016-2013/520beb3f-3f00-45d3-bf7f-c4ec56caf085

Wiki Page:

If there is anything you think needs to be added, expanded upon, or corrected, you can comment below, or better yet, make some edits on this topic’s wiki page HERE.

Disable CTRL+ALT+DEL for Remote Login for Windows Server 2008

Problem:

On a remote session on a domain server, at the login screen you get a message when trying to inject ctrl+alt+delete saying that you cannot because of the group policy of that domain.

Background:

Sometimes you pin a remote to work on later, after an office is closed, so that you can work on things without disrupting the work day. But what what do you do if you realize only later that you are on the login screen, and it is requiring you to hit ctrl+alt+delete to then log in, but when you try to inject it remotely you get an error message saying that the group policy does not allow it. Instead of waiting until the next day that someone is around to unlock this screen you may be able to open this remotely.

Solution:

Note: This solution is for a fairly specific case. I accomplished this with a 2008 R2 server that had been pinned with Bomgar. It may be adaptable to other remote software, and other OS versions, but it will work at least with this combination.
Bomgar allows you to go to a different tab from the screen sharing to a command shell tab. This allows you to go there and put in the following command into a command prompt, which should then allow you to get to the password entry without ctrl+alt+delete. Just copy and paste this in there:

reg add “HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionPoliciesSystem” /v DisableCAD /t REG_DWORD /d 1 /f_

Once you do that, you can reboot the machine (the source below gives as command for that, but I just reboot it within Bomgar) and then you can get logged in and get to work. There are other ways to do this by actually getting into the group policy, so if you have access to the machine and notice the issue ahead of time, you can do it by editing the group policy, which would be another guide, which at some point I will get to, and hopefully remember to add a link here pointing to it.

Sources:

  1. http://www.fusionnetwork.us/index.php/articles/windows-tutorials/disable-ctrl-alt-del-startup-via-command-line-server-2008/ 

Wiki Page:

If there is anything you think needs to be added, expanded upon, or corrected, you can comment below, or better yet, make some edits on this topic’s wiki page HERE.