Solved IsWow64Messenger user32.dll error and MS Outlook won't load.

  • Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  • Hello everyone We want to personally apologize to everyone for the downtime that we've experienced. We are working to get everything back up as quickly as possible. Due to the issues we've had, your password will need to be reset. Please click the button that says "Forgot Your Password" and change it. We are working to have things back to normal. Emails are fixed and should now send properly. Thank you all for your patience. Thanks, PCHF Management
Status
Not open for further replies.

Lorcan64

PCHF Member
Feb 21, 2018
6
0
60
Hi. Hopefully someone can help. A few weeks ago I couldn't get into MS Outlook 2010. Got an error message. Found out it was an update incompatibility so removed it and it worked fine. Did a restore point! Yesterday it decided to not work again and I couldn't restore either. I had disabled auto MSupdates too.Today I am getting a procedure entry point error as above. I am also getting KERNEL32.dll error when I try to open Outlook which includes ...entry point CompareStringOrdinal not bring located. My desktop is old but...Oh and I'm getting an OLMAPI32.dll can't be found. I've tried reinstalling Office but it doesn't resolve the issue.
I'm using Windows XP Home 32-bit.

Thanks
 
How are you reinstalling Office?
Hi, thanks for the reply.

I end up in an endless loop as it asks if I want to repair it. I've used my original disks last time it did it without them. On these occasions it said it was successful but it wasn't.

I did some further research and previously someone had posted on another site to remove a MS update which I did. It worked for a while then wouldn't load (outlook) so found I had to remove another different update. This I did and I've gained access but still get the IsWow..and kernel error.
 
Have you tried uninstalling Outlook and then reinstalling Outlook?
Thanks for the reply.

Not yet I will do that as my last resort I think. I'm wondering if I have a corrupt registry so needto get hold of a good registry repairer!
 
Thanks for the reply.

Not yet I will do that as my last resort I think. I'm wondering if I have a corrupt registry so needto get hold of a good registry repairer!
There no such thing as a good registry repairer. They can sometimes even make the system worse and or even halt it all together.

Read through the information posed here on the Microsoft site and see if it helps at all.
https://support.office.com/en-us/ar...64a-477a-8fcc-2fdf5dbf61d8#OfficeVersion=2010

The other thing I would suggest that you do is run a check disk on the system.
https://pchelpforum.net/resources/run-chkdsk-using-command-prompt.20/
 
There no such thing as a good registry repairer. They can sometimes even make the system worse and or even halt it all together.

Read through the information posed here on the Microsoft site and see if it helps at all.
https://support.office.com/en-us/ar...64a-477a-8fcc-2fdf5dbf61d8#OfficeVersion=2010

The other thing I would suggest that you do is run a check disk on the system.
https://pchelpforum.net/resources/run-chkdsk-using-command-prompt.20/

Thanks for that Rustys much appreciated.
 
Hi, Sorry for the delay in updating but other things took over :(

Two of the errors I believe were down to a system monitoring program I installed some time ago - Project Lasso. I've removed this and so far no kernel message or IsWow...message.

I can access Outlook since deleting two upgrades. I now have to be careful to make sure these updates don't automatically update!
I also get a message saying a previous registry had to be used when I reboot (not all the time).
Everything seems ok so far although XP I think needs to be replaced :(

Thanks for all who replied.
 
Thanks for the update. Yeah XP is a little dated by now.. Shall we mark your thread as solved then?
 
Status
Not open for further replies.