HOW TO: Ways to fix Outlook error ‘cannot open your default email folders’

Microsoft Outlook may be the most widely used email service around the globe, but users have come to accept the good with the very bad. Yes, Outlook offers an extensive and exclusive range of features as well as its friendly user experience. But there’s the flip side: User forums are filled with anger over errors that seem to have zero solutions. For this article, we will examine and hopefully resolve perhaps the most common Outlook error: “cannot open your default email folders.” This Outlook error mostly appears when you are trying to open your Outlook profile. It generally happens because of a corrupted OST file or the execution of Outlook in compatibility mode.

Why OST file corruption happens

OST files are the files that allow users to use Outlook while they are offline. It is actually a synchronized copied element of the accounts saved on your device that enables you to continue to use Outlook even when the program gets disconnected from MS Exchange Server.

These files can become corrupted because of various reasons. Some of the reasons are:

  • Deletion of any file or folder removed from Exchange folder.
  • Intrusion of any malware or virus.
  • Disruption in the file synchronization process due to sudden or abnormal shutdown failure.
  • Some internal discrepancies in Outlook causing abnormal Outlook termination.
  • Creation of some bad sectors in the hard drive where the OST file is stored.
  • Failure of any networking device that might disrupt the synchronizing process of the OST file.
  • Any changes in the internal structures of the OST file.
  • Installed plugins sometimes may damage Outlook performance, thus causing damage to the OST file.

Fixing OST file corruption

Here’s some ways to begin fixing the problem:

  1. Remove those profiles that are not being used from the address “Control Panel > Mail > Show profiles.”
  2. Create another copy of OST file.
  3. Even if the error doesn’t get resolved, create another new profile from while using Outlook Profile Helper or manually.

Outlook error caused by running in compatibility mode

Outlook Error
You might have witnessed these errors:

Cannot open your default email folders. Information store could not be opened,”


“Cannot start Microsoft Outlook. Cannot open the Outlook window. The server is not available. Contact your administrator if this condition persists.”


“Cannot display the folder. File access is denied. You do not have the permission required to access the file C:Usersusernamelocalsettingsapplication datamicrosoftoutlookoutlook.ost”

If you have enabled compatibility mode mistakenly, just disable it. If you haven’t, do not enable it for Outlook. Users typically enable it when they are required to run the troubleshoot compatibility wizard. Also, compatibility mode is not required for any version of Outlook on Vista or Windows 7 or any other Windows OS. This mode is also not needed for any application that is supported on any Windows OS or for recently released applications.

The user can switch off compatibility mode in a 64-bit operating system by following these easy steps:

  • Switch to the mentioned address “C:Program Files (x86)Microsoft OfficeOffice XXOutlook.exe”
  • Right-click on exe and then follow up by clicking on Properties then Compatibility tab.
  • Uncheck the checkbox called “Run this program in compatibility mode” box, thereafter click Apply and OK.

And in case, you are unable to place the Compatibility tab, follow the following steps:

  • Click on Startand search for Program Compatibility Troubleshooter.
  • Start Program Compatibility Troubleshooter; select Next option to proceed.
  • Select Outlook XX from the appeared list of programs. Following the steps of the Program Compatibility Troubleshooter.
  • Switch to the mentioned address “C:Program Files (x86)Microsoft OfficeOffice XXOutlook.exe”
  • Right-click on exe and then follow up by clicking on Properties then Compatibility tab.
  • Uncheck the checkbox called “Run this program in compatibility mode” box, thereafter click Apply and OK.

If this issue is experienced over an Exchange email account that is configured on your Outlook, you can diagnose the error by trying the following steps:

  1. If your program is executing along with a running Windows Server and/or over a firewall, then disable the firewall and then connect it with the server directly without any firewall.
  2. If this Outlook error gets resolved, then you will be required to reconfigure your firewall to allow Exchange to sync.
  3. And if the Outlook error still persists even after disabling the firewall, create a new mail profile from Outlook. You will also need to reconfigure your account.

Featured image: Shutterstock

Post Views: 78

Read Next


  • No Related Posts

FIX: Outlook error when sharing calendar in Windows 10

Do you get the Outlook error when sharing calendar? If you have Office 365 or any other Microsoft Exchange email service, Outlook can be used on the web to share your calendar with others in and outside of your organization.

Depending on the permissions given, others can only view your calendar, edit, or act as your delegate for meeting requests.

The Outlook error when sharing calendar can happen due to configuration or permission issues. Some users have reported that removing current permissions besides the Default and Anonymous resolves the issue.

However, if the error persists, repair Office from Control Panel, and if it fails, download and run the Microsoft Office Configuration Analyzer tool 2.2, which analyzes Office programs for known configurations that can cause issues.

If you don’t have the option to share your calendar (maybe it is grayed out), it can also be because your network admin or IT support set a policy preventing calendar sharing among people in the office.

Fortunately, there are ways to fix the Outlook error when sharing calendar as listed below.

Outlook won’t share calendar, how do I fix that?

  1. General fixes
  2. Check Permission settings
  3. Check for Duplicate entries

1. General fixes

  • Update Office suite to the latest version by going to Outlook>FILE>Office Account>Update Options>Update Now
  • Do an online repair for the Office programs
  • Also, if you are using an Office 365 account in your Outlook 2016, you can try sharing the calendar in Outlook Web App (OWA).
  • Launch the Run command and paste exe /safe in the open box to start Outlook in Safe Mode
  • Uncheck Cash mode in Outlook
  • Download Microsoft Support and Recovery Assistant for Office 365 and see if it helps

— RELATED: Fix Outlook error ‘Too many recipients’ on Windows 10

2. Check Permission settings

  • Open Outlook and go to Calendar view
  • Right click the calendar you’re trying to share
  • Click Properties
  • Go to Permissions tab and remove users who are no longer at the office or who cannot access the calendar
  • Click Apply and close the window then try to share your calendar again

3. Check for Duplicate entries

The Outlook error when sharing calendar may be related to a duplicate entry in the Permission list of your calendar. To check for this, do the following:

  • Right click user’s calendar
  • Select Properties
  • Click Permissions tab
  • Go through the users’ list and check for a duplicate entry
  • If you find, remove it and restart Outlook again
  • Share your calendar
  • Remove all entries and return them again
  • Right click the calendar you want to share
  • Select Properties
  • Make a note of the entries and then remove all entries in the calendar permission list
  • Add them back

Were you able to resolve the Outlook error when sharing calendar? Let us know in the comments section below.



  • No Related Posts

DLP can’t detect emails classified with Titus software

I need a solution

Customer uses Titus classification software for file classification. Titus has been embedded in MS Office software, including MS Outlook. I have managed to form Symantec DLP policies to detecti classified MS Office files, either copied through network or sent through email, except for classified emails sent directly through MS Outlook. MS Outlook detects if classification appears in body of mail, in attached files, in mails sent through reply or forward, but it can not detect “clean” classified mails.



How to Restore Emails from OST file Outlook 2013?

MS Outlook 2013, like earlier Outlook versions, uses OST file to save a local replica of Exchange mailbox data. This file comes handy when user wishes to work on his mailbox even if Exchange isn’t available. But, it can’t be opened directly in Outlook if its parent account gets disconnected from Exchange. In such a case the OST file is called an ‘orphan’ file and extracting emails and other data from it can become a real pain.

Although Microsoft came up with the concept of using data files to save mailbox data locally in order to make backing up and archiving more convenient, OST and PST files have in some ways complicated mailbox management; and that holds especially true for OSTs. If you access an Exchange mailbox through Outlook, a local OST file is created to save a replica of mailbox data which the user can access and work with even if the mail server isn’t available. However, the basic nature of OST files makes managing mailbox data quite tricky for users.

The need to Restore mails from OST File

OST files have several shortcomings because of which, users often face the need to extract emails and other data stored within these files and save them in some other format:

  • OSTs cannot be transferred between different machines. If users need to access their mailbox data saved within OST files on another machine, it cannot be done directly through a simple copy-paste mechanism.
  • If the account that originally created an OST file gets deleted from the mail server, it cannot be opened directly from within Outlook.
  • In Outlook 2013 and 2016, data locally edited and saved within critical folders like Contacts, Calendars, Sent Items, etc. is not synced with the mail server and is thus not backed up there. In the event of damage to OST file, there’s no direct way to regain access to that local data since it doesn’t exist on the server.

Users who faced the need to extract OST file data because of any of the above-mentioned reasons make use of manual as well as automated ways to achieve it. For your reference, we’ve compiled a list of the most widely used and accepted techniques you can use to restore OST files if you’re sailing in the same boat.

Manual techniques to Restore OST files

In no specific order, these techniques can help you regain access to all your Exchange or other IMAP account data depending upon your exact problem scenario:

Scenario 1: If your Exchange account is intact but OST file gets corrupted

This is one of the most frequently encountered problems by Exchange users. OST files get damaged easily but if your Exchange profile is intact and you are in the habit of regularly syncing your local data with your server mailbox, regaining access to all your data should simply be a matter of manually creating a new OST file and downloading your mailbox data from the server again. Here are the steps:

  1. Quit all running instances of Outlook and open Control Panel
  2. Open the “Mail” option and in the ‘Mail Setup’ dialog box that opens, click on “Email Accounts”
  3. The next dialog that opens will display all your Outlook profiles / accounts. Here, click on the “Data Files” tab and choose the respective OST file from the list
  4. Now click on “Open File Location” to open the Windows Explorer window with the OST file’s location
  5. Close the ‘Account Settings’ and ‘Mail Setup’ windows
  6. In the Explorer window, create a copy (backup) of the OST file. Thereafter, right-click on it and click on “Delete”
  7. Start the Outlook application again to automatically create a new OST file for that account (doing so will download all the data from the Exchange server into the newly created OST file)

You should remember that if you’re using Outlook 2013 / 2016, only the data residing on the mail server will be downloaded into the new OST file. This will include your emails and the folders you have manually synced with the Exchange account. Any local data will not be downloaded since it doesn’t exist on the server. To get access to any such data you will need to convert the old OST to PST format and then open it directly within Outlook. You can either use the Outlook “Import & Export wizard” to convert OST to PST or take the help of reliable software Stellar OST to PST Converter to do so (skip to last section to discover how this product can help).

Scenario 2: If your Exchange account has been deleted or lost

If this happens, your “orphaned” OST file will most likely become useless since you won’t be able to open it directly unless you reconnect to Exchange and re-sync it. For this you will need a unique MAPI address to act as a bridge between Outlook and the Exchange server. However if this isn’t an option, the only way to access the data contained within the orphaned OST file is to convert it to PST format using Stellar OST to PST Converter. (Here you won’t have the option to use Outlook Import Export Wizard since you’ll need to open the OST file from within Outlook and without Exchange that won’t be possible).

Best Automated Solution to restore mails from OST file

If the manual technique doesn’t work or if you are dealing with an orphaned OST file, converting it to PST format is a task best handled by a professional product like Stellar OST to PST Converter. The advanced software is equipped with some very powerful algorithms that allow it to convert even the most severely damaged OST files to PST format files that can be used to access all mailbox contents including emails, attachments, contacts, calendars, notes, journals, etc. This software is your best bet if you wish to perform conversion of encrypted OST files or wish to extract only selected emails from within OST files and save them in MSG, EML, RTF, HTML, or PDF formats.

Final Thoughts…

So should a user completely shun the usage of OST files? Well obviously that isn’t an option since OST files are the Microsoft norm for saving Exchange data locally. What is needed is for users to stay aware of the techniques they can use to regain all their mailbox data if any disaster like virus infection or accidental deletion or severe corruption befalls their OST files. Converting OST files to PST format is the best way to salvage all the data stored within them and thus, having a product like Stellar OST to PST Converter handy goes a long way.


7021519: Why does my Reflection button and color scheme look different?

Button and Color Scheme Based on Installation Scenario

The Reflection button in the upper left corner of the Reflection Desktop 16, Reflection 2014, and Reflection 2011 workspace and the workspace color scheme vary depending on your installation of Reflection:

The default for new installs of Reflection on Windows 7 is “Office 2010 White.” With this color scheme, the main Reflection commands are accessed from the File menu.

Figure 1 - Reflection 2014 Button in

Figure 1 – Reflection 2014 Button in “Office 2010 White”

Figure 1 - Reflection 2014 Button in

Figure 2 – Reflection 2011 Button in “Office 2010 White”

The default for new installs of Reflection on Windows Vista and Windows XP and for upgrades from Reflection 2008 to newer versions of Reflection is “Office 2007 Black.” With any of the Office 2007 color schemes selected, the main Reflection commands are accessed from the Reflection button menu.

Figure 3 - Reflection 2014 Button in

Figure 3 – Reflection 2014 Button in “Office 2007 Black”

Figure 3 - Reflection 2014 Button in
Figure 4 – Reflection 2011 Button in “Office 2007 Black”

Changing the Reflection Button and Color Scheme

To change the appearance of the Reflection button and workspace color scheme in the Reflection Workspace:

  1. Go to the Reflection Workspace Settings > Configure Workspace Settings.
  2. Scroll to the User Interface section and select “Look and Feel / Color Scheme”.
  3. Select your Reflection button appearance from the drop-down list.


  • No Related Posts

Modern Microsoft SharePoint Design: Overcoming Common Challenges – Part 3

EMC logo

This is the final installment to my 3-part series on common challenges customers are experiencing with modern SharePoint design. In the first two blogs, I talked about obstacles in implementing modern sites in SharePoint Online, including a new (“greenfield”) environment (Overcoming Common Challenges with Modern Microsoft SharePoint Design – Part I) and one with a mixture of modern and classic sites (Overcoming Common Challenges with Modern Microsoft SharePoint Design – Part 2). Now let’s focus on areas that should be considered when migrating from SharePoint on-premises to modern sites in SharePoint Online.

For those who still don’t know about Dell EMC’s consulting services practice for implementing Microsoft products – we’ve been partnering with Microsoft for 30 years! Yes, that’s right and personally, I live and breathe SharePoint, Project Online, and related services every day and have done so for the last 10 years.

Site Collection Hierarchy

Ok, so in the first blog, we established modern sites are all created as individual site collections. Most on-premises SharePoint farms consist of hundreds, if not thousands, of sub-sites nested within different site collections.This means that you’ll need to completely flatten your site structure as part of the migration to modern SharePoint Online sites.

A couple of things to consider are:

  • Site provisioning – most (if not all) migration tools currently create site collections using a classic SharePoint template. This means that you’ll need to develop a method of creating the modern SharePoint site before conducting the migration – either manually or through a tool like PowerShell.
  • SharePoint Hub sites – Hub sites are the method for re-structuring this site/sub-site relationship in modern SharePoint sites. However, there are some limitations to Hub sites (namely that there is currently a limit of 50), so you’ll need to plan how to use these to re-build your existing structure.

Migrating Security / Permissions

There are a couple of instances where security and permissions work differently in SharePoint Online than on-premises:

  • External sharing – sharing with external users (“guests”) is much easier in SharePoint Online. As you plan to migrate, you should work with site owners to understand if their site should allow external users (and then enable, if necessary) or how to re-share with external folks if they previously had access on-premises.
  • O365 Group permissions – modern team sites are connected to an O365 Group, which add some elements to the standard permission model. First, you’ll need to decide whether the site is “public” or “private” because a public O365 Group will open access to all users within the organization.  Secondly, you’ll need to determine which users need access to the O365 Group artifacts (“Documents” library, conversations, planner, etc.) as those permissions are managed separately from the SharePoint site.

In general, we often recommend that organizations take this as an opportunity to start fresh with their permissions in SharePoint Online. It is common that on-premises sites have been around for 10+ years and are a complete “rats nest” of permissions. Instead of migrating the mess (and then continue to make it messier), why not work with the site owners to re-share their site with only the people who actually need access?

Migrating Pages

Pages have been completely re-architected in modern SharePoint – and as a result, there is no current migration path for classic pages. This means that you’ll need to plan time to re-build all of your necessary pages in your newly migrated SharePoint site.  If your sites follow a standard layout, you can develop a PowerShell script to provision the modern pages with sections and configure some of the web parts and content. However, modern pages have a differing set of tools/web parts than classic sites, so doing so will not be as simple as mapping 1-to-1 and will require testing and some manual re-build where web parts don’t map properly.

Migrating Documents

Content from on-premises SharePoint can be migrated to SharePoint Online without much hassle – however, that doesn’t mean it doesn’t require some planning.  In classic SharePoint, users typically created multiple document libraries within a single site to separate different types of content. This can still be done on a modern team site, but the only documents that will show in the “Documents” link (which is part of the associated O365 Group) are the files in the default “Documents” library. So, as you plan your migration, you should work with site owners to determine if they would prefer all of their documents to show in that default library – and if so, how it should be re-organized.

Migrating Notebook / Calendars

OneNote notebooks and SharePoint calendars can be migrated to modern SharePoint sites – but, they will only be accessible through the SharePoint site. Let me explain.

  • Calendar – O365 Groups utilize an Exchange calendar for the default “Calendar” link in a modern team site. There isn’t currently a migration path for a SharePoint calendar to the associated Group calendar, so utilizing the default calendar requires a manual input of events in to the new calendar.
  • Notebook – Groups are also provisioned with a default OneNote notebook, which cannot be overwritten. If you’d like to have a single OneNote notebook on your modern team site, you will need to follow a manual method of connecting to both notebooks (in OneNote client) and using the “Move to” feature.

Lot’s to Consider….

Keep in mind, these are only some of the changes between classic and modern that should be considered when completing a migration. Also, while this blog focuses on migration to modern sites, but there is also an option to migrate to classic sites in SharePoint Online and utilize a mixed environment (see challenges from this type of environment in blog 2). As someone who’s completed many SharePoint migrations, I can tell you, they can often be more complex than they first appear. There are MANY areas (not covered here) that should be designed and well-planned before undertaking any SharePoint migration.


Leverage these tips as you consider and plan your SharePoint migration. If you’d like to have our Dell EMC SharePoint experts do it for you, we can help! Dell EMC is a gold-certified Microsoft partner and my consulting services team is responsible for all things Office 365 (including Teams, Yammer, Groups, Stream, etc.), SharePoint, Project Server/Project Online, Exchange, and Identity. We also work closely with Microsoft MVPs and the Patterns and Practice (PnP) community to leverage and improve the latest product features. Feel free to leave a comment below and I’d be happy to respond to you.

And, now I’m off to another SharePoint project…

The post Modern Microsoft SharePoint Design: Overcoming Common Challenges – Part 3 appeared first on InFocus Blog | Dell EMC Services.

Update your feed preferences





submit to reddit


  • No Related Posts

Packaging office 365 Click to run

I need a solution

The more I read on office 365 deployment the more I seem to get myself confused, we want to start deploying office 2016 and just wondering if anyone has a found a good guide on what steps to follow. The deployment will be for the e3 version license version, do I need to create an msi with the office deployment tool off of the click to run? Do I just upload the click to run to altiris and deploy that out?



  • No Related Posts

Modern Microsoft SharePoint Design: Overcoming Common Challenges – Part 2

EMC logo

Welcome to the second in a 3-part series focused on some of the common challenges customers are experiencing with modern SharePoint design. In the first blog, Overcoming Common Challenges with Modern Microsoft SharePoint Design – Part I, I talked about obstacles in implementing a new (“greenfield”) environment where there is no existing content or “classic” SharePoint sites to consider. Here I’ll focus on environments where customers already have a SharePoint Online implementation using classic sites and would like to begin using the “modern” experience. In the second blog in this series, I’ll discuss items to consider when migrating from on-premises to modern SharePoint Online sites.

In case you didn’t read the first blog, you might be surprised to learn that Dell EMC has a full consulting services practice for implementing Microsoft products. We sure do, and if you’re like most people, that may come as a surprise. Personally, I live and breathe SharePoint, Project Online, and related services every day. I’ve spent the last 10 years designing and implementing solutions for customers of all sizes and verticals.

User Experience

SharePoint Online now has a “classic” and a “modern” experience. Both have their own distinct look-and-feel, which is fine when using only one; however, it can be confusing when regularly moving from one to the other (in what is supposed to be the same environment!). Unfortunately, there isn’t much that you can do to avoid the classic experiences, but you should expect that it will cause some confusion and proactively prepare your users. Most will likely be accustomed to the “classic” experience that they have been using for years, so you should ensure a solid communication plan and training program to prepare them for the modern experience – and where/when they can expect to encounter it. Some areas where I have seen some confusion when using both types of sites are:

  • Landing pages have a radically different look and utilize a different set of web parts, theming, and customizations. You can create modern pages for classic team sites, but not for sites with the publishing infrastructure enabled.
  • Lists/libraries can also cause some confusion because most are displayed in the modern experience – even in the classic sites! A site owner can decide to disable the modern view for a list/library; however, be aware it’s enabled by default.
  • Modern Team Sites are connected to Office 365 Groups, which means these sites will also have associated conversations, calendar, OneNote, and other artifacts. Microsoft plans to release the ability to “groupify” a classic team site, but it’s a good practice to ensure users understand the tools available in the different “flavors” of sites.

When it comes to training, there doesn’t seem to be a single “silver bullet” for all organizations, but I have seen the following techniques (or a combination of a few) to be successful in SharePoint deployments: short (and engaging) videos, learning management sites, blogs, road shows, job aids, lunch n’ learns, and 3rd party training tools.

Content Publishing / News

Many organizations who have an intranet built on SharePoint have developed a solution for publishing internal news articles. Well, Microsoft has decided to develop its own solution for News that cannot currently be used with classic publishing pages. The challenge is that Microsoft’s news solution is the only one that displays results in the SharePoint landing page (from the app launcher) or the SharePoint mobile app. This means that users are more likely to see updates about department ice cream socials instead of the important update from the CEO! Below are some options around implementing news in this mixed environment:

  • Option 1 – modern SharePoint news is still new and lacking the features that most enterprise intranets contain. I have no doubt Microsoft will get there at some point, so an intermediate solution may be to re-brand the intranet news as something like “Company News” and ensure that it is displayed front-and-center (maybe by setting as default home page for browser).  You might also want make sure there’s plenty of communication around the difference between “Company News” (on the intranet) and the “News” you will see elsewhere in the environment.
  • Option 2 – re-design your news solution to utilize the modern SharePoint functionality. As mentioned above, there will likely be some limitations compared to your existing solution, but you can continue to iterate on the solution as the functionality improves.

Enterprise Search

Many organizations have developed customized SharePoint search centers and/or tailored their search index to help users find important content (from an organizational perspective). In SharePoint Online, Microsoft has also released a new experience for search, named “personalized” search, which uses the Microsoft Graph to determine what is most important for users. This new search is the only option when using the default search box within a modern SharePoint Online site – which means that users may not be able to find important corporate information (say policies or benefits) unless they have searched for it before or have some sort of connection.

At some point, Microsoft will likely release a way to direct users to an Enterprise Search Center (from a modern site), but until then, you may want to consider adding a link (either in the header/footer) of your global navigation or potentially adding a SharePoint Framework (SPFx) web part to primary landing pages to get users to the organizationally tuned search.

Global Navigation

As mentioned in the first blog, having a solid plan for navigation is critical to ensure users can find content across your many SharePoint sites.  The challenge here is that the options for navigation are different for modern and classic sites.  Classic publishing sites use master pages where global navigation can be added to the top (for header) and bottom (for footer) of every page across the environment.  To do the same in modern SharePoint, you will need to use SPFx extensions. This means that you could have the same links available in classic and modern, but the placement, look, and functionality may be completely different. Below are a couple of recommendations for global navigation:

  • A team member recently worked with a customer (along with Microsoft) to implement a solution that is now available on GitHub. You may want to consider using this as an intermediate step while waiting for releases from Microsoft.
  • Another potential area of confusion is with the newly released SharePoint Hub sites. These can be used to “link” SharePoint sites to provide a common theme and navigation (among other things); however, the UI elements for Hub sites only show in modern pages. You can still associate classic sites with Hubs, but keep in mind that users will only see the shared theme and navigation when on a “modern page” or modern list/library view.

It’s a Lot to Consider…

As you can see, there’s a lot of things to consider when planning a modern SharePoint design – and we haven’t even talked about other important topics, including: search, content management, publishing, forms/workflow, security & compliance, governance, etc,. SharePoint is about enabling dynamic teams to collaborate and get stuff done, which is why it’s really important to make sure they have the best and most productive experience possible. The considerations covered in this blog should help you accomplish that objective.


If you’re good to leverage these tips on your own, great! Glad I could help. If you’d like Dell EMC to help, we can do that too!  Dell EMC is a gold-certified Microsoft partner and our consulting services team is responsible for all things Office 365 (including Teams, Yammer, Groups, Stream, etc.), SharePoint, Project Server/Project Online, Exchange, and Identity. We also work closely with Microsoft MVPs and the Patterns and Practice (PnP) community to leverage and improve the latest product features. Feel free to leave a comment below and I’d be happy to respond to you.

The post Modern Microsoft SharePoint Design: Overcoming Common Challenges – Part 2 appeared first on InFocus Blog | Dell EMC Services.

Update your feed preferences





submit to reddit


  • No Related Posts

7022850: How to remove the Microsoft VBA installed by Reflection Desktop 16

The Microsoft VBA can be removed by a Windows Installer (msiecec.exe) command line. Many versions of Reflection contain the same build of the VBA code, so the same msiexec command line can be used for multiple versions. To find the uninstall command line requires the manual inspection of the Microsoft Windows registry keys found at:


Open and expand each registry key and examine the “InstallProperties” for the “UninstallString” key to determine the appropriate msiexec /X {GUID} command

For example:

Product: Microsoft Visual Basic for Applications 7.1 (x86) English

Msiexec Command: MsiExec.exe /x {BAB89D31-4C55-472B-8909-6CBE2CC276B1}

Here is a batch file that can be used to remove many versions of the VBA modules installed by the Reflection software:

echo off

echo This Batch file will remove all versions of VBA installed by Reflection

:: This only works with the English language install of VBA


:: this information can be found in the HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstallerUserDataS-1-5-18Products keys

:: remove VBA for Reflection 2011

:: remove VBA core

msiexec /x {FB97C283-1F3C-42D4-AE01-ADC1DC12F774}

msiexec /x {A13D16C5-38A9-4D96-9647-59FCCAB12A85}

:: remove English language

msiexec /x {179D679D-047F-491D-8783-D4BE596D2242}

:: remove VBA for Reflection R2014

:: remove VBA core

msiexec /x {74170BFD-A50C-46D9-8AF2-AF0A0CE017DD}

:: remove English language

msiexec /x {A13D16C5-38A9-4D96-9647-59FCCAB12A85}

:: remove VBA for Reflection Desktop v16

:: remove VBA core

msiexec /x {90120000-0070-0000-0000-4000000FF1CE}

:: remove English language

msiexec /x {BAB89D31-4C55-472B-8909-6CBE2CC276B1}

:: pause to see output before exit

echo Reflection VBA removal complete


As you run the batch commands above, you will receive Windows User Access Control (UAC) prompts when the msiexec commands find an installed product.

Prompts to uninstall products (which should be answered in the affirmative) will also appear as shown below:


Since the batch file contains many msiexec commands to uninstall products that may not exist on your PC, be prepared for the display of the following error message which is appropriate and expected and shown below:


  • No Related Posts