JoinDomain VMExtensionProvisioningError when deploying WVD (aka Conflict Error)

Deploying WVD Fails with a conflict error and when clicking for more information it presents a conflict and not much else that is useful by way of toubleshooting. Hopefully this helps someone else as it had me head scratching for a little while.. When creating the Host Pool, make sure that you haven't made the fatal error of using the Azure Active Directory Credential INSTEAD of the Local AD Domain Credential.  i.e do not use to domain join, even if it links back to the domain - this is where the conflict arrises.    Instead, use your full internal domain UPN.  Re-deploy your same configuration and you should find it goes through now without any problems. Additional findings.... Albeit my mistake above was an easy one, it does appear the error is directly linked to the domain join process. If you go into your resource groups, locate the session host and MSTSC directly to it.  Try the domain join pr

Cannot start Microsoft Office Outlook. MAPI32.DLL is corrupt or the wrong

I installed Office 2003 from a disk and couldnt open Outlook after some issues with Access.

The error was as below:

Cannot start Microsoft Office Outlook. MAPI32.DLL is corrupt or the wrong
version. This could have been caused by installing other messaging software.
Please reinstall Outlook.

Reinstallation does not work so I'll save everyone some time here hopefully, the only resolution I've seen and used here is to rename a simple file at the following path:
C:\Program Files\Common Files\System\MSMAPI\1033

Which is MSMAPI32.DLL.

Please, please, please don't rename MAPI32.DLL this wont work, it is MSMAPI32.DLL just simply change the extension and it will 9/10 times be sorted.

Did I solve your problem? Buy me a virtual beer by clicking on a Google ad :). Thanks!


  1. this absolutely works!! I was not able to get Outlook 2003 to work or reinstall or repair. Renaming msmapi32.dll was the solution.

  2. Perfect! Thank you.

  3. Thanks, but in my case (recently updated to windows 7) de msmapi32.dll in

    C:\Program Files\Common Files\System\MSMAPI\1043

    did the trick

  4. Renaming msmapi32.dll did the trick for me too.
    At first I could not find the file in windows 7 explorer, but with an explorersearch I found it.

    After installing Office 2003 Outlook worked perfectly

  5. Thanks so much for this - it works well! Crappy Windows 7 + MS support had completely the wrong advice.
    If you're having trouble renaming the file, google 'Windows 7 take ownership' to put in a registry entry that will let you do this from Explorer. Then you can rename at will (although sometimes you need to take ownership of the directory as well).
    Aaaah for *nix/root. MS sux.

  6. Legend! Worked a treat. Thank you

  7. Some days my friend called me up and told me about the interesting tools. But one of its liked me and I used for recovering my emails - outlook database repair. It surprised me,because of restored my corrupted emails for seconds and without payment as I bore in mind. I recommended it my friends and they thanked me a lot.

  8. Great !
    Worked just fine, thanks.
    MS sux.

  9. Wow thank you for this information. The only problem is that I have already deleted the MAPI32.DLL.

  10. Pure genius. Thanks. I've been battling it for days, and it was so simple. Thanks!

  11. The fastest way to solve this problem it's download missed .dll library file from for free and add it into the system 32 directory. Try to and I'm sure you'll solve your problem fast.


Post a Comment

Popular posts from this blog

This product type does not match the list of supported product types

SBS 2008 hangs on Applying Computer Settings

LSASS.EXE - System Error / Rebuilding Active Directory Indices. When booting windows server 2003