Tag: Microsoft Office

Microsoft December 2020 Patch Tuesday fixes 58 vulnerabilities

PCIS Support Team Leave a comment
microsoft cryptography encryption

Microsoft has published today 58 security fixes across 10+ products and services, as part of the company’s monthly batch of security updates, known as Patch Tuesday.

Windows 10 security: 'So good, it can block zero-days without being patched'

Windows 10 security: ‘So good, it can block zero-days without being patched’

Systems running the Windows 10 Anniversary Update were shielded from two exploits even before Microsoft had issued patches for them, its researchers have found.

Read More

There’s a smaller number of fixes this December compared with the regular 100+ fixes that Microsoft ships each month, but this doesn’t mean the bugs are less severe.

More than a third of this month’s patches (22) are classified as remote code execution (RCE) vulnerabilities. These are security bugs that need to be addressed right away as they are more easily exploitable, with no user interaction, either via the internet or from across a local network.

This month, we have RCEs in Microsoft products like Windows NTFS, Exchange Server, Microsoft Dynamics, Excel, PowerPoint, SharePoint, Visual Studio, and Hyper-V.

The highest-rated of these bugs, and the ones most likely to come under exploitation, are the RCE bugs impacting Exchange Server (CVE-2020-17143, CVE-2020-17144, CVE-2020-17141, CVE-2020-17117, CVE-2020-17132, and CVE-2020-17142) and SharePoint (CVE-2020-17118 and CVE-2020-17121).

Patching these first is advised, as, through their nature, Exchange and SharePoint systems are regularly connected to the internet and, as a result, are more easily attacked.

Another major bug fixed this month is also a bug in Hyper-V, Microsoft’s virtualization technology, used to host virtual machines. Exploitable via a malicious SMB packet, this bug could allow remote attackers to compromise virtualized sandboxed environments, something that Hyper-V was designed to protect.

Below are additional details about today’s Microsoft Patch Tuesday and security updates released by other tech companies:

  • Microsoft’s official Security Update Guide portal lists all security updates in a filterable table.
  • ZDNet has published this file listing all this month’s security advisories on one single page.
  • Adobe’s security updates are detailed here.
  • SAP security updates are available here.
  • Intel security updates are available here.
  • VMWare security updates are available here.
  • Chrome 87 security updates are detailed here.
  • Android security updates are available here.
Tag CVE ID CVE Title
Microsoft Windows DNS ADV200013 Microsoft Guidance for Addressing Spoofing Vulnerability in DNS Resolver
Azure DevOps CVE-2020-17145 Azure DevOps Server and Team Foundation Services Spoofing Vulnerability
Azure DevOps CVE-2020-17135 Azure DevOps Server Spoofing Vulnerability
Azure SDK CVE-2020-17002 Azure SDK for C Security Feature Bypass Vulnerability
Azure SDK CVE-2020-16971 Azure SDK for Java Security Feature Bypass Vulnerability
Azure Sphere CVE-2020-17160 Azure Sphere Security Feature Bypass Vulnerability
Microsoft Dynamics CVE-2020-17147 Dynamics CRM Webclient Cross-site Scripting Vulnerability
Microsoft Dynamics CVE-2020-17133 Microsoft Dynamics Business Central/NAV Information Disclosure
Microsoft Dynamics CVE-2020-17158 Microsoft Dynamics 365 for Finance and Operations (on-premises) Remote Code Execution Vulnerability
Microsoft Dynamics CVE-2020-17152 Microsoft Dynamics 365 for Finance and Operations (on-premises) Remote Code Execution Vulnerability
Microsoft Edge CVE-2020-17153 Microsoft Edge for Android Spoofing Vulnerability
Microsoft Edge CVE-2020-17131 Chakra Scripting Engine Memory Corruption Vulnerability
Microsoft Exchange Server CVE-2020-17143 Microsoft Exchange Information Disclosure Vulnerability
Microsoft Exchange Server CVE-2020-17144 Microsoft Exchange Remote Code Execution Vulnerability
Microsoft Exchange Server CVE-2020-17141 Microsoft Exchange Remote Code Execution Vulnerability
Microsoft Exchange Server CVE-2020-17117 Microsoft Exchange Remote Code Execution Vulnerability
Microsoft Exchange Server CVE-2020-17132 Microsoft Exchange Remote Code Execution Vulnerability
Microsoft Exchange Server CVE-2020-17142 Microsoft Exchange Remote Code Execution Vulnerability
Microsoft Graphics Component CVE-2020-17137 DirectX Graphics Kernel Elevation of Privilege Vulnerability
Microsoft Graphics Component CVE-2020-17098 Windows GDI+ Information Disclosure Vulnerability
Microsoft Office CVE-2020-17130 Microsoft Excel Security Feature Bypass Vulnerability
Microsoft Office CVE-2020-17128 Microsoft Excel Remote Code Execution Vulnerability
Microsoft Office CVE-2020-17129 Microsoft Excel Remote Code Execution Vulnerability
Microsoft Office CVE-2020-17124 Microsoft PowerPoint Remote Code Execution Vulnerability
Microsoft Office CVE-2020-17123 Microsoft Excel Remote Code Execution Vulnerability
Microsoft Office CVE-2020-17119 Microsoft Outlook Information Disclosure Vulnerability
Microsoft Office CVE-2020-17125 Microsoft Excel Remote Code Execution Vulnerability
Microsoft Office CVE-2020-17127 Microsoft Excel Remote Code Execution Vulnerability
Microsoft Office CVE-2020-17126 Microsoft Excel Information Disclosure Vulnerability
Microsoft Office CVE-2020-17122 Microsoft Excel Remote Code Execution Vulnerability
Microsoft Office SharePoint CVE-2020-17115 Microsoft SharePoint Spoofing Vulnerability
Microsoft Office SharePoint CVE-2020-17120 Microsoft SharePoint Information Disclosure Vulnerability
Microsoft Office SharePoint CVE-2020-17121 Microsoft SharePoint Remote Code Execution Vulnerability
Microsoft Office SharePoint CVE-2020-17118 Microsoft SharePoint Remote Code Execution Vulnerability
Microsoft Office SharePoint CVE-2020-17089 Microsoft SharePoint Elevation of Privilege Vulnerability
Microsoft Windows CVE-2020-17136 Windows Cloud Files Mini Filter Driver Elevation of Privilege Vulnerability
Microsoft Windows CVE-2020-16996 Kerberos Security Feature Bypass Vulnerability
Microsoft Windows CVE-2020-17138 Windows Error Reporting Information Disclosure Vulnerability
Microsoft Windows CVE-2020-17092 Windows Network Connections Service Elevation of Privilege Vulnerability
Microsoft Windows CVE-2020-17139 Windows Overlay Filter Security Feature Bypass Vulnerability
Microsoft Windows CVE-2020-17103 Windows Cloud Files Mini Filter Driver Elevation of Privilege Vulnerability
Microsoft Windows CVE-2020-17134 Windows Cloud Files Mini Filter Driver Elevation of Privilege Vulnerability
Visual Studio CVE-2020-17148 Visual Studio Code Remote Development Extension Remote Code Execution Vulnerability
Visual Studio CVE-2020-17159 Visual Studio Code Java Extension Pack Remote Code Execution Vulnerability
Visual Studio CVE-2020-17156 Visual Studio Remote Code Execution Vulnerability
Visual Studio CVE-2020-17150 Visual Studio Code Remote Code Execution Vulnerability
Windows Backup Engine CVE-2020-16960 Windows Backup Engine Elevation of Privilege Vulnerability
Windows Backup Engine CVE-2020-16958 Windows Backup Engine Elevation of Privilege Vulnerability
Windows Backup Engine CVE-2020-16959 Windows Backup Engine Elevation of Privilege Vulnerability
Windows Backup Engine CVE-2020-16961 Windows Backup Engine Elevation of Privilege Vulnerability
Windows Backup Engine CVE-2020-16964 Windows Backup Engine Elevation of Privilege Vulnerability
Windows Backup Engine CVE-2020-16963 Windows Backup Engine Elevation of Privilege Vulnerability
Windows Backup Engine CVE-2020-16962 Windows Backup Engine Elevation of Privilege Vulnerability
Windows Error Reporting CVE-2020-17094 Windows Error Reporting Information Disclosure Vulnerability
Windows Hyper-V CVE-2020-17095 Hyper-V Remote Code Execution Vulnerability
Windows Lock Screen CVE-2020-17099 Windows Lock Screen Security Feature Bypass Vulnerability
Windows Media CVE-2020-17097 Windows Digital Media Receiver Elevation of Privilege Vulnerability
Windows SMB CVE-2020-17096 Windows NTFS Remote Code Execution Vulnerability
Windows SMB CVE-2020-17140 Windows SMB Information Disclosure Vulnerability

Set Up ShareFile and Microsoft Teams

Citrix Leave a comment

ShareFile should be listed as a Cloud Storage option within Microsoft Teams, under the Files tab.

User-added image


Files > Add Cloud Storage > ShareFile > Sign into ShareFile (enter your credentials)

Once signed in, you can access ShareFile files right from your Teams account.

ShareFile missing from the Cloud Storage list?

  • If ShareFile isn’t listed, you may need to enable ShareFile for your Teams account.
  • Your Office 365 Admin should sign into the Admin Portal and navigate to Settings > Services & Add-Ins > Microsoft Teams > (Turn on ShareFile).

Note: On-Prem Accounts + Requirements

Customers using Citrix storage zones controller to store files in an on-prem environment will need to have set up the following in order to access files via Microsoft Teams.

Related:

How to recall a message sent in Microsoft Outlook

PCIS Support Team Leave a comment
Shocked stressed woman looking at laptop reading negative surprise online

Image: fizkes, Getty Images/iStockphoto

It’s inevitable. You send someone an email in Microsoft Outlook. And then you realize for one reason or another that the message has a mistake or that it shouldn’t have been sent at all. You can fix your error after the fact by recalling a message. Using the recall feature under the right conditions, your previous email is deleted without the recipient ever seeing it. You can also send a replacement message with the correct information.

SEE: How to add a drop-down list to an Excel cell (TechRepublic)

There are some requirements if the recall feature is to work properly. For your recalled message to be deleted, both you and the recipient must have a Microsoft 365 Business account or Microsoft Exchange email account in the same organization, meaning the same Exchange system on the backend. The email must have been delivered to the recipient’s mail server but it must not have been read yet.

However, even if you and the recipient use different email clients or backend systems, or you fail to recall the message before it’s been read, the recall feature can still serve a purpose. Though the initial email won’t be deleted, the recipient receives a follow-up message indicating that you want to recall the previous email. That tells them that your initial email is incorrect or invalid for some reason. You should then follow up your initial email and recall message with another email that contains the right information or corrects the initial one.

SEE: 50 time-saving tips to speed your work in Microsoft Office (free PDF) (TechRepublic)

How to recall a message in Microsoft Outlook

To try this, open Outlook. Start a new email and address it to the recipient. Send the email (Figure A).

Figure A

figure-a.jpgfigure-a.jpg

Now, let’s say you notice an error in your email and want to recall it. Open the email from your Sent Items folder. Select the Actions icon and click the option to Recall This Message (Figure B).

Figure B

figure-b.jpgfigure-b.jpg

The Recall This Message window offers two options. Choosing to “Delete unread copies of this message” tries to remove the message with no follow up. Choosing to “Delete unread copies and replace with a new message” gives you an opportunity to immediately send a follow-up message with the correct information. To learn if the recall succeeds, keep the box checked for “Tell me if recall succeeds or fails for each recipient.” Click OK (Figure C).

Figure C

figure-c.jpgfigure-c.jpg

If you chose the option to replace with a new message, a new email appears with the text from the original message so you can fix the problem and send the corrected version (Figure D).

Figure D

figure-d.jpgfigure-d.jpg

If you and the recipient use the same Microsoft 365 Business or Exchange backend environment, then the email should be deleted from the recipient’s inbox automatically. If so, you’ll receive an email indicating that the recall was successful for that particular user.

If you and the recipient use different email clients or backend mail services, the initial email remains in that person’s inbox. A follow-up email then arrives that tells the recipient that you would like to recall the message. You then have to rely on your recipient to ignore or delete the original message in favor of the corrected one (Figure E).

Figure E

figure-e.jpgfigure-e.jpg

For more information on the different recall scenarios, check out Microsoft’s support page on “Recall or replace an email message that you sent.”

Microsoft Weekly Newsletter

Be your company’s Microsoft insider by reading these Windows and Office tips, tricks, and cheat sheets. Delivered Mondays and Wednesdays

Sign up today

Also see

Related:

WEM Agent hung sporadically by logon on “application processing”

Citrix Leave a comment
WEM Agent 1906 sporadically hung after few logins at “application processing”. just logoff and logon helps. Client OS: Citrix Virtual Apps Server with Windows Server 2016 (latest Updates)

Error Message in the Event Log:

Error while Configuring Registry Security for DOMAINtest1

Source: Norskale Agent Service Event ID: 0 2. Event Log one or all of the identity references could not be translated. Source: Norskale Agent Service Event ID: 0 Latest Citrix WEM Agent Log 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing with Registry Entry -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15EXCEL.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing with Xml Value -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15EXCEL.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing with Ini Value -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15EXCEL.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing Simple String Operations -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15EXCEL.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing Split Operations -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15EXCEL.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing String Operations -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15EXCEL.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing SubString Operations -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15EXCEL.EXE 17:56:55 Event -> VuemApplicationExecutor.ProcessVuemAppAutoLaunch() : Application -> MS Onenote (Id:17) -> AutoLaunch Disabled : Exiting 17:56:55 Event -> VuemApplicationExecutor.CreateDesktopShortcut() : Application -> MS Outlook (Id:13) -> Processing Desktop Shortcut… 17:56:55 Event -> VuemApplicationExecutor.CreateDesktopShortcut() : Application -> MS Word (Id:14) -> Processing Desktop Shortcut… 17:56:55 Event -> VuemApplicationExecutor.ProcessVuemAppAutoLaunch() : Application -> MS PowerPoint (Id:20056) -> AutoLaunch Disabled : Exiting 17:56:55 Event -> VuemApplicationExecutor.CreateDesktopShortcut() : Application -> MS Outlook (Id:13) -> Saving Desktop Shortcut… 17:56:55 Event -> VuemApplicationExecutor.DoPinToTaskBar() : Application -> MS Excel (Id:15) -> Processing TaskBar Pinned Shortcut… 17:56:55 Event -> VuemApplicationExecutor.SaveShortcut() : Working Directory: C:Program Files (x86)Microsoft OfficeOffice15 Target: C:Program Files (x86)Microsoft OfficeOffice15OUTLOOK.EXE Arguments: 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing HashTags -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15OUTLOOK.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing User Attributes -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15OUTLOOK.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing Printer Attributes -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15OUTLOOK.EXE 17:56:55 Event -> VuemApplicationExecutor.CreateDesktopShortcut() : Application -> MS Word (Id:14) -> Saving Desktop Shortcut… 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing User Parent OU -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15OUTLOOK.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing with Registry Entry -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15OUTLOOK.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing with Xml Value -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15OUTLOOK.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing with Ini Value -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15OUTLOOK.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing Simple String Operations -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15OUTLOOK.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing Split Operations -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15OUTLOOK.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing String Operations -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15OUTLOOK.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing SubString Operations -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15OUTLOOK.EXE 17:56:55 Event -> VuemApplicationExecutor.SaveShortcut() : Working Directory: C:Program Files (x86)Microsoft OfficeOffice15 Target: C:Program Files (x86)Microsoft OfficeOffice15WINWORD.EXE Arguments: 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing HashTags -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15WINWORD.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing User Attributes -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15WINWORD.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing Printer Attributes -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15WINWORD.EXE 17:56:55 Event -> VuemApplicationExecutor.DoPinToTaskBar() : Application -> MS Outlook (Id:13) -> Processing TaskBar Pinned Shortcut… 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing User Parent OU -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15WINWORD.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing with Registry Entry -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15WINWORD.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing with Xml Value -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15WINWORD.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing with Ini Value -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15WINWORD.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing Simple String Operations -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15WINWORD.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing Split Operations -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15WINWORD.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing String Operations -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15WINWORD.EXE 17:56:55 Event -> DynamicTokensController.ReplaceDynamicTokens() : Replacing SubString Operations -> no match found for : C:Program Files (x86)Microsoft OfficeOffice15WINWORD.EXE 17:56:55 Event -> VuemApplicationExecutor.DoPinToTaskBar() : Application -> MS Word (Id:14) -> Processing TaskBar

Related:

ShareFile distribution group

Citrix Leave a comment

Use Distribution Groups to consolidate users into functional groups for more efficient account management. This feature is useful for managing large groups of users with similar folder access needs.

Requirements

Managing Distribution Groups requires the create shared distribution groups and edit shared distribution groups permissions

Distribution Groups and User Permissions

  • Members added to the Distribution Group will inherit the folder access permissions of the group.
  • Members removed from the Distribution Group will lose the folder access permissions given to that group.
  • Permissions given on a folder to a distribution group will apply to every member. This includes notifications about downloads and uploads.


Create a Distribution Group

  1. People > Manage Users or Distribution Group
  2. On the Distribution page click on the Create Group button.
  3. The next page will allow you to name the group and give you the option to share the group with employees in your account.
  4. Click the Create Group button.
  5. Check the box beside Share this distribution group with all employees if you want users with the edit shared distribution group permission to be able to edit your group.
  6. On the Managing group page, you can add users with one of the following options:
  • Click Add Member to enter a user’s email, name and company manually. Click the checkbox when done entering a single user’s information.
  • Access the Add From drop down menu and choose Add from Personal Address Book or Add from Shared Address Book
  • Access the Add From drop down menu and choose Add from Employee List
  • Access the Add From drop down menu and choose Add from Excel. A template spreadsheet will be provided to you. Please fill in this spreadsheet and follow the instructions provided in the web app.
  • Access the Add From drop down menu and choose Classic Bulk Add. You may enter users via email. Each entry should be on its own line. Entries should NOT be separated by commas. Entering first and last names for each entry is not required. To associate a first and last name with an entry, place the name in parentheses after the email address.

Once you have saved our Distribution Group, you can return to the Distribution Groups menu to modify your group as needed.


Sending or Receiving Files from a Distribution Group

You can select a Distribution Group as the recipient of your message when sharing or requesting files. Distribution Groups can be accessed via the Address Book icon. When receiving an email sent to an entire Distribution Group, your recipient will only see his or her own email address in the recipient field. For security purposes, recipients cannot view other email addresses that may have been sent the file.

User-added image

Adding a Distribution Group to a Folder

A distribution group may be added to a folder in much the same way an individual user would be. Folder permissions can be customized across the distribution group. When receiving notifications sent to an entire Distribution Group, your recipient will only see his or her own email address in the recipient field. For security purposes, recipients cannot view other email addresses that may have received the notification.

User-added image


Distribution Group FAQ

How many users can I add to a Distribution Group?

A distribution group can have a maximum of 2000 users.

I added a user to a folder when they already had access through a Distribution Group. What permissions apply?

The individual user’s access will override that of his/her group. Example: John Doe has Download permissions on a folder due to his membership in the Doe Distribution Group. You add John Doe to the folder manually, and grant him Upload permissions. He will have both Download and Upload permissions, even though his Distribution Group membership does not include Upload.

Generate a Group Membership List

To generate a membership list for your review, access People > Manage Users or Distribution Groups. Click on the group name to access it. Access the Generate Report drop-down menu and choose Export Group List. Once the list is generated, a spreadsheet will be downloaded to your local computer.

Generate a Folder Access report

A Folder Access report shows which folders and permissions the Distribution Group has access to. To generate a folder access report for your review, access People > Manage Users or Distribution Groups. Click on the group name to access it. Access the Generate Report drop-down menu and choose Folder Access. You may print this list for your records.

Related:

Top 6 Ways to Fix Cannot Expand Folder Error in Outlook

PCIS Support Team Leave a comment

5. Create a New Outlook Profile

It is recommended that you follow point 4 above before moving on to create a new profile. Rename the folder that you can’t expand in Outlook. Right-click on the folder and select the Rename option to do so. Take a backup, if you must. If you have taken a backup on the server or in the cloud, delete the profile the below mentioned:

C:UsersUSERNAMEAppDataLocalMicrosoftOutloook

Of course, the Username above and the drive letter should be your corresponding user name and Windows installation drive. Reboot your computer.

Open Outlook and under the Files menu, click on Account Settings > Manage Profiles.

Click on Show Profiles.

Click on Add to begin creating a new profile.

You can now add email accounts to this newly created profile and check if you still get the Cannot expand folder error.

6. Repair PST and OST File

The Outlook email account data is stored in a .PST file if you are using IMAP or POP account. The same is stored in a .OST file if you are using Office 365 or Exchange account. Depending on the email account throwing the Cannot expand folder error in Outlook app, choose one method.

Repair OST File

Open Control Panel and go to User Account > Mail > Show Profiles. Select the profile you are having trouble with and click on Properties below. Now select Data Files in the pop-up that follows.

Select the email account data file and click on Open File Location.

A new window will open with a file name with .OST extension. Delete the file and reboot your computer. Launch Outlook and it will recreate the file automatically.

Repair PST File

The same steps won’t work for .PST file. Press Windows key+R to open the Run prompt. Enter the below file path in case of Office 2016, Office 2019, and Office 365.

C:Program Files (x86)Microsoft OfficerootOffice16

For Outlook 2013:

C:Program Files (x86)Microsoft OfficeOffice15

Double-click the SCANPST.EXE file, which will launch the Microsoft Outlook Inbox Repair experience. I wish there was a direct way of launching it.

Click on Browse on the pop-up that follows.

A new File Explorer window will open. You need to locate the .PST file here and when you find it, click on the Start button.

Select ‘Make a backup of scanned file before repairing’ option to create a backup in case something goes wrong.

Now click on Repair to begin the process.

Look Out

There are way too many versions of Outlook that Microsoft has released over the years. That makes troubleshooting a bit more difficult. However, we try our best to offer the best workable solutions. If you have found another way to solve the Cannot open folder error in the Outlook app, let us know in the comments below.

Next up:Using Microsoft Outlook on your smartphone? Here are 9 cool Outlook tips and tricks for Android and iOS.

Last updated on 29 Feb, 2020
Read NextTop 9 Outlook Email Tips and Tricks for iOS and AndroidAlso See#email #Microsoft

Did You Know

The term spam pre-dates e-mail.

More in Windows

How to Get Apple Reminders on Windows

Top 9 Google Sheets Budget Templates for Finance Tracking

Join the newsletter

Get Guiding Tech articles delivered to your inbox.
Subscribe

Share on

FacebookTwitterLinkedInRedditWhatsAppEmail

Join the newsletter

SubscribeView Comments

Written By

Gaurav Bidasaria

Gaurav is a tech enthusiast who loves talking about new gadgets and innovations. He dropped out of CA because he found the work life boring and monotonous! He recently started working out but mostly, you will find him on the couch either Netflix-ing or gaming.

  • #Android

    • #Windows#Internet#iOS#Gadgets#Mac#Buying Guides

  • #How-tos

    • #Comparisons#Tips & Tricks

  • Facebook

    • Facebook (Hindi)InstagramInstagram (Hindi)YouTubeYouTube (Hindi)TwitterTwitter (Hindi)

  • Guiding Tech

    AboutContactTerms of UsePrivacy Policy

    Advertise

    © 2020 Guiding Media Pvt Ltd. All Rights Reserved.

    • Related:

    • No Related Posts

    Save Outlook: Five Ways to Recover Email from Error 0x8004010F

    PCIS Support Team Leave a comment

    Email services with a bright design and many new features appear almost every day. However, none of them could replace Outlook or at least compete with it. You can only come to terms with this. The secret to the popularity of the service is that it is part of the Microsoft Office suite, intuitive and straightforward. Besides, only Outlook allows you to take full advantage of the many features of Microsoft Exchange Server.

    Of course, Outlook is not only mail but also a diary, calendar, notes, and messages. Almost all human life is stored in one encrypted file. Therefore, it’s not very good if, when you try to enter the mail client, such a message pops up: 0x8004010F: Outlook data file cannot be accessed.

    No panic! We will try to find out what happened to the mail. Most likely, it’s not too late to save it.

    Save Outlook: Five Ways to Recover Email from Error 0x8004010F 09 | TweakTown.com

    Spoiler: I’m not particularly eager to look in the answers, but if someone is in a hurry, the Recovery Toolbox for Outlook which is very useful in such situations, saved me.

    Returning the Outlook File

    The appearance of the 0x8004010F error means that the Outlook file that stores all the mail is damaged or lost. Gone with the spring wind? It doesn’t matter what happened. You can quickly recover lost mailings if you use a server with IMAP protocol support (Exchange Server, Office365, Gmail, Mail.ru, and the like).

    How does it work? The server automatically saves a copy of the file stored on the hard disk; therefore, at any time, we can access the lost data. To do this, you need to abandon the local file that has stopped responding and create a new one using the unique Outlook tool.

    Very similar to syncing local data with the cloud, right? Specialized knowledge for recovery is not needed, and the process itself consists of six easy steps-further details.

    Recovering an Outlook Account from a Remote Server

    • Start Outlook.
    • Go to Account settings.
    • Select the account you want to recover.
    • Select the Change folder.
    • Click the New Outlook Data File.
    • Confirm the changes with OK.

    If everything went well, you would get access to the lost mail. Exhale and go to check the mailing list. If not, then with a nasty sound this window will pop up:

    Save Outlook: Five Ways to Recover Email from Error 0x8004010F 08 | TweakTown.com

    This popup often happens. Try disabling any programs that could affect the recovery process and carry out the procedure from the very beginning. However, the chances of success tend to zero. Mail is not available on the remote server, which is possible, for example, if Outlook uses the POP3 protocol, and all mailings are stored in one local file.

    No need to worry. Even after recovery using the server failed, options remain. First, check the Windows settings; there is a chance that they cause the failure. You may not have permission to access the local Outlook file, and this will lead to an error. To configure access rights, do the following:

    1. Launch Windows Explorer.

    2. Select the desired PST file. If its location is unknown, you can find the file using the same explorer, for this, enter in the window: “*.pst” (without quotes).

    Save Outlook: Five Ways to Recover Email from Error 0x8004010F 01 | TweakTown.com

    3. Right-click on the file.

    4. Go to Properties.

    5. Uncheck the box next to Read Only.

    6. Click on the Security tab.

    Save Outlook: Five Ways to Recover Email from Error 0x8004010F 02 | TweakTown.com

    7. In the “Groups and Users” menu, you need to select the account under which you are logged in.

    8. Make sure that all permissions (except for Special Permissions) are checked.

    9. Confirm changes by clicking OK.

    Permissions configured, but file still unavailable? So, let’s move on. Unfortunately, there are not many options left. The only thing that remains after you tried to restore mail from the server and set the correct system settings is to restore from a backup or other backup mail, PC. Or you can try to repair the damaged file using special programs and services.

    Mail Recovery Using Microsoft Office Tools

    Please take care of backup in advance-restore mail and forget about the error with the code 0x8004010F: Outlook data file cannot be accessed for a long time. If there is no backup, then you need to look for a unique tool. The good news: one of the most popular PST file recovery software is already on your computer.

    We are talking about the Inbox Repair Tool, which comes with the office suite. The tool is easy to use and, importantly, completely free, you need to look for it here:

    • Outlook 2019/2016: C:Program Files (x86)Microsoft OfficerootOffice16
    • Outlook 2013: C:Program Files (x86)Microsoft OfficeOffice15
    • Outlook 2010: C:Program Files (x86)Microsoft OfficeOffice14

    Unfortunately, the free tool does not always work, but the Inbox Repair Tool does not take much time either. It makes sense first to try to solve the problem with its help. If it did not work out, we would look for other options, in any case, you need to return the email.

    Online Services

    The online recovery and conversion services for Outlook databases give good chances, but you have to pay for the pleasure. There are a large number of such sites, ones of the most popular: https://outlook.recoverytoolbox.com/online/

    The whole process takes five minutes to lose:

    • Select a file on your hard drive
    • Enter your email
    • Enter the verification code correctly
    • Pay for the service in one of the ways offered by the site

    If everything is done correctly, and it could not be otherwise, you will receive a link to the corrected file. The cost of the service usually does not exceed ten dollars for one file up to 1 GB in size. The only question is security.

    If you are not satisfied that someone unknown will get access to your personal data-bank card numbers, passwords from social networks, family photos-it is better to choose a method that is not related to sending mail to a remote server. For example, install a particular program.

    Recovery Toolbox for Outlook

    A convenient and inexpensive tool, you can download it from the link: https://outlook.recoverytoolbox.com/outlook-data-file-cannot-be-accessed.html The program does not require connection with third-party sites. Therefore there are no privacy problems when using Recovery Toolbox for Outlook. It’s easy with which to work. The developers made sure that you can proceed immediately after installation. Before you begin, it is recommended that you backup an important file.

    In such a simple way, you not only protect yourself from surprises, but you can also check the system. If a Windows error pops up during the copy process, you must format or change the hard drive, and then reinstall the system. To not have a disaster again, in the future, do not forget to backup the operating system. The backup will save you nerves and improve digestion.

    Bug the error 0x8004010F: Outlook data file cannot be accessed

    Recovery Toolbox for Outlook performs well in recovering Outlook accounts after error 8004010F. What do we have to do:

    1. Download and install the tool from the official website: https://outlook.recoverytoolbox.com/outlook-data-file-cannot-be-accessed.html

    2. Run the installed program.

    3. Find the file we need on disk.

    Save Outlook: Five Ways to Recover Email from Error 0x8004010F 03 | TweakTown.com

    4. Left-click on Recovery Mode.

    5. Select the folder with the Outlook files.

    6. Replace the damaged file with the corrected.

    Note! In the latest versions of Outlook, you can replace the file either by manually moving it to the Outlook folder or by using the program method, which needs to be done like this:

    1) Select the item File/Details

    2) Click Account Settings

    Save Outlook: Five Ways to Recover Email from Error 0x8004010F 05 | TweakTown.com

    3) Select Data Files

    4) Select a damaged file from the list

    5) Click Open file location…

    Save Outlook: Five Ways to Recover Email from Error 0x8004010F 06 | TweakTown.com

    That’s all. Next, we need to delete the old file, otherwise sooner or later, errors will pop up.

    Conclusion

    Now it remains only to test the work of Outlook. If everything is done according to the instructions, error 0x8004010F: Outlook data file cannot be accessed will not bother you for a long time. Otherwise, reread the article and try to figure out what exactly was done wrong. I hope this little setback did not stop you halfway.

    Remember that you can always contact Recovery Toolbox for Outlook support. Experienced specialists will help you. Of course, only if you use the licensed version of the program or pay for the work of the online service.

    On this, I say goodbye to you and wish you good luck.

    Related:

    SEP 14.2 RU2 detects “Download Insight” on O365 Pro Plus Update

    Symantec Community Leave a comment
    I need a solution

    Hi everyone,

    our SEP detects a download insight when O365 Pro Plus tries to get its updates.

    The tmp file name varies every time. We are getting Helpdesk calls about it and i want them to stop. 

    After checking 5 clients i’m sure that this file relates to the Office Updates (Semi Annual) as there is a log file from O365 ProPlus with the same timestamp.

    When will these files are trustworthy?

    Best regards

    Stephan

    0

    Related: