A client of mine subscribed to Office 365 Small Business Premium and then tried to install Office 365 ProPlus on a Windows Vista operating system to set up Exchange Online. As soon as the installation starts the following error are displayed. The procedure entry point K32GetProcessImageFileNameW could not be located in the dynamic link library KERNEL32.dll.

There are two reasons why you received this error.

Installing Office 365 ProPlus on Windows Vista

The reason why you will receive the Procedure entry point K32GetProcessImageFileNameW error in Windows Vista is simply because Microsoft Office 2013 is not compatible with Windows Vista. Just remember the Office 365 ProPlus is the same as Microsoft Office 2013 Professional Plus.

Microsoft Office 2013 compatibility list:

–          Windows 7 (32-bit or 64-bit)

–          Windows 8 (32-bit or 64-bit)

–          Windows 8.1 (32-bit or 64-bit)

–          Windows Server 2008 R2 (64-bit)

–          Windows Server 2012 (64-bit)

You can solve this issue by installing Microsoft Office 2010 on your Windows Vista operating system.

Here is an article that will guide you to where you can download Microsoft Office 2010 and then use your Office 365 Small Business Premium subscription to activate it and setup Exchange Online on a Windows Vista computer.

If you bought the Microsoft Office 2013 box product (retail version) and you did not know that it’s not compatible with Windows Vista, your best option is to upgrade to Windows 7 or Windows 8.

Installing Office 2010 on a Windows Vista

You might receive the Procedure entry point K32GetProcessImageFileNameW error when you try to install Microsoft Office 2010 on Windows Vista operating system.

To solve this issue, download and install Windows Vista Service Pack 1 (SP1). Then try to install Microsoft Office 2010.

Download Windows Vista Service Pack 1 (SP1)

Download Windows Vista Service Pack 2 (SP2)

Tagged with: , , , , , ,

This is a method that I use very often to help me eliminate software conflicts. Troubleshooting Windows can sometimes be very difficult and therefor I use the Clean Reboot for Windows to stop all other applications like Antivirus software, system utilities and other software and services that start automatically when you startup Windows.

Doing a Clean Reboot for Windows means that you start Windows 8.1, Windows 8, Windows 7 or Windows Vista by using the minimal set of drivers and applications.

Here is the method to Clean Reboot Windows:

Windows 8: Swipe the right side of the screen and tap on SEARCH. In the Search Box type in MSCONFIG and tap on the MSCONFIG results on the left.
Windows 7: Click on START and in the Search Box, type MSCONFIG and press enter.

Search for msconfig in Windows 8










Go to the SERVICES tab and select the HIDE ALL MICROSOFT SERVICES check box and click DISABLE ALL.

System Configuration















Go to the STARTUP tab in SYSTEM CONFIGURATION dialog box and click OPEN TASK MANAGER.

Open Task Manager in msconfig







In TASK MANAGER, go to STARTUP and disable all startup items by selecting the item and then click on DISABLE.

Disable startup tasks in Task Manager



















Close TASK MANAGER and click on OK in the SYSTEM CONFIGURATION dialog box.
Then reboot your computer.

Your will have a Clean Reboot for Windows without all the additional services and applications running in the background. To troubleshoot your Windows, start to enable the services and processes one by one to determine which one is the culprit that causes the conflict or slowness of your computer.

Tagged with: , , ,

Since Windows 7 is in production a new error had shown up and I never found the real workaround.

If you had the error message “The Trust Relationship between this Workstation and the Primary Domain failed” when you tried to logon you will know what I’m talking about.

Most of the time I receive this error when the workstation is connected to a domain and you do a System Restore. I also had it before after certain Windows Updates. As soon as the workstation reboot after the System Restore or Windows Update you will get this error and then you won’t be able to logon with your domain user and password. Next you will realise that the Local Administrator Account on the workstation is disabled by default in Windows 7 so if you haven’t setup an Local User or enabled the Administrator Account you have yourself a little problem.

The Trust Relationship between this workstation and the Primary Domain failed


Here is how I normally fix the issue:

First if you don’t have a Local Account to login to, disconnect the workstation from the network by removing the network cable. Now reboot the workstation into Safe Mode and login with the Domain Username and Password that is known to you. Next enable and reset the Local Administrator Account’s password and reboot and login with the Local Administrator.

When logged in with the Local Administrator Account or Local User with Administrator Rights, make a backup of the User Folder (C:\Users\<username>).

Then remove the workstation from the domain and reboot. When the reboot is done, log back in with your Local User with Administrator Rights.

Open REGEDIT (START -> RUN -> REGEDIT) and browse to the following Registry Key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\

In the “ProfileList”, search for the profile that you can’t login to anymore and remove the Profile from the ProfileList.

Reboot the workstation and again log in with your Local User with Administrator Rights. Re-join your workstation to the domain and reboot again. Now, logon with the domain user that you were unable to logon with before.

After the new profile for the Domain User has been configured in Windows 7, restore the backup that you made of User Folder by copying all the files back to the profile (Documents, Desktop and Favourites etc.)

This always solves the error “The Trust Relationship between this workstation and the Primary Domain failed”. If you have any other solution or a quicker fix for this, please inform me.

Tagged with: , , , , , ,