Category Archives: Troubleshooting

Learning how to use Office Deployment Toolkit 2016

Leave a reply

This is the first time I have used the Office Deployment toolkit for Office 2016. To be honest, I have never used the Office Deployment toolkit at all. I decided to blog about how to install Office 2016 from a shared network drive using Office Deployment toolkit. This blog post may be a bit basic and tedious – but I want those who are new at using this tool to be able to figure out how to use it.  I am also documenting the process for myself so I don’t forget how to do it.

In the process of learning how to use the Office deployment toolkit, I found many websites that had parts of the process documented. However, it seemed they never quite had a full documentation process. I will show you from start to finish on how to deploy Office 2016 from a network location.

Step One: Let’s download the Office Deployment toolkit for Office 2016. Office Deployment Toolkit 2016Once you have the tool downloaded, extract the files to your desktop. You will see two files, a setup.exe file and a configuration.xml file. Continue reading →

Font Changes In Outlook when Replying to Email Messages

1 Reply

I ran into a strange issue the other day. Our client said every time she replied to an email in Outlook her font would change to a different color. The version of Outlook my client was using was Outlook 2013 , but this “fix” will also work for Outlook 2016. I got to digging around a bit in Outlook 2013 and I found this was actually a “feature” instead of a problem.

If you find you font automatically changing on you, when replying to email messages, this is where you need to go to turn it off.

Step One: Open Outlook. Go to File > Options > Mail > Stationary and Fonts > Uncheck “Pick a new color when replying or forwarding”. Click OK.

Outlook Stationary ChangeThat is all you need to do. I tested this and each time when the client replied her font and font color stayed to what she had set to default.

I hope this help you! This was posted by techspeeder. Follow my blog or my Twitter feed to keep up with the latest troubleshooting tips.

Resolved: Office 2016 (0x80041015) We ran into a problem while trying to install the product key

7 Replies

Recently, we upgraded a customer from a local Exchange server to Office 365. For a majority of the users, we purchased Office 365 Business Premium licenses that included Office 2016 (Buy Office 2016).

Office 2016 activated just fine on all the computers besides one PC. The computer was running Windows 8.1 with Office 2013. We uninstalled Office 2013 and downloaded and installed Office 2016 from his Office 365 account. After the installation, a dialog box prompted him to sign into his Office 365 account to activate Office. He signed into his account, and Office 365 tried to verify his subscription but it would eventually error out and say:

Sorry, we ran into a problem while trying to install the product key. If this keeps happening, you should try repairing your office product. (System error: 0x80041015)Office 2016 Activation Error

I wasn’t sure what to do so I tried all the things below – but to no avail.

  1. I uninstalled Office – twice. Didn’t fix it.
  2. Tried Repairing Office 2016 – didn’t work.
  3. Logged in with the domain administrator account and tried activating Office – failed.
  4. Tried activating office with another Office 365 account – that didn’t work either.
  5. Started Office in Safe Mode – no go.
  6. Deleted credentials out of credential manager. Same results
  7. Upgraded computer from Windows 8 to Windows 10. – failed
  8. I downloaded and installed Office 2016 from his Office 365 account on another computer. This different computer activated just fine! So I knew it was a computer issue, not an Office 365 account problem .
  9. Logged into Windows 10 in Safe Mode to activate Office 2016. Failed.

I also checked Event Viewer for clues, and I found this. ” Installation of the Proof of Purchase failed. 0x80041015 Partial Pkey=M7TW3″  I looked online for help with this error but I came up empty.Security-SPP Office 2016

I was at the end of my troubleshooting rope. I decided to reach out to Microsoft about this issue. Here is what they advised me to do – and it fixed it! Below you will find the solution.

Solution: 

Step One:  Sign out from all your Office 365 applications.

Step Two: Remove the Office credentials from credential manager. To remove the Office credentials from credential manager please follow the below step

Go to Control Panel — > Credential Manager — > Windows Credentials — > Delete the Microsoft 15 credentials.

 Step Three: Remove the credentials from registry.  (Backup registry first)

Here is the Registry key location from where we can delete the identities and profiles  HKEY_Current_User \ Software \ Microsoft \ Office \ 15.0 \ Common \ Identity — > Delete the Identities and Profiles folders.

I opened up the Office applications and signed into the user’s Office account. Bingo! It activated right away.

Summary: Deleting those offending registry keys was the step that fixed my issue. I hope this can help someone else. Please leave a comment below if this helped or if you have anything to add.

This was posted by techspeeder. Please subscribe to my blog for more troubleshooting tips. Thanks

 

Resolve Windows 10 Upgrade Error Code 8007002C-4000D

12 Replies

Most of the Windows 10 upgrades I have done so far have gone quite smoothly. However, I did run into an upgrade issue with a customer the other day. Here is what would happen. I would download Windows 10 and it would begin its upgrade process. After Windows 10 got to about 99% installed the installation would reboot. After the reboot, the screen would go black for a bit and then revert back to the previous operating system, Windows 7. Windows would then display error code 8007002C-4000D.

Windows 10 Upgrade Error

Another technician looked at the problem first so I will list the steps he tried.

Step One: Turned off AntiVirus ( Avast ) , Uninstalled Covenant Eyes (Software)

Step Two: Deleted Items in C:\Windows\SoftwareDistribution\Download

Step Three: Ran Command Prompt wuauclt.exe /updatenow

After the above steps were completed, the computer still returned error code 8007002C-4000D.

I decided to take a look at the issue. I decided to “Google” the issue first to see if anyone else had a fix for this problem. I found this Microsoft forum full of people having this issue. I scanned over the thread and found a general consensus that it seemed to be a software giving us upgrade problems. Here are the steps I tried.

I uninstalled Avast and Covenant Eyes software.

I ran system file checker sfc /scannow . System file checker didn’t find anything amiss.

Next I ran msconfig and went to the startup tab. Under the startup tab I removed all software from starting up.

I began the Windows 10 upgrade. Much to my relief and happiness the Windows 10 upgrade was successful.

Conclusion: From the troubleshooting things I tried, I believe unchecking all software from startup is what fixed this issue. Previously, Windows 10 would almost install but after the reboot the software would try starting up. One of the software items I unchecked must have been giving me my issues.

I hope these troubleshooting tips can help you out. Please leave a comment if you have trouble upgrading your computer to Windows 10 as well.

This was posted by techspeeder.

 

Remote Desktop Connection Username or Password are Wrong

Leave a reply

I recently set up a Windows 7 computer that could be accessed out of office via a remote desktop. The problem I was having, was that everytime I tried to connect to the computer I would receive an error. The error said something like this, “Remote Desktop can’t connect because the username or password is wrong”. So naturally, I entered the password again but with the same results. I checked the username- it was correct ( so I thought). I kept trying the credentials and I “knew” I had them correct. Finally at my wits end, I contacted another technician about this problem.

He asked me if I renamed the Windows 7 user account after I had setup the computer. I told him I had renamed the account. The tech told me that the when connecting via a Remote Desktop connection the user name needs to match the one under C:\users folder. I had changed the user account from (ex.) User to User1. This had been the cause of all my issues.

I tried connecting to the Windows 7 computer , but this time using the old username of User. Just that fast I was connected to the computer via an remote desktop connection.

Conclusion: The updated user account name, User1 was not recognized by Windows through the RDP session since the C:\Users folder didn’t match. To avoid this frustrating circumstance, it is best not to rename your user account after you have created it if you are planning to connect to your computer via RDP.