Excel Disappeared From After Microsoft Office Update

  

  1. Excel Disappeared From After Microsoft Office Update 2020
  2. Excel Disappeared From After Microsoft Office Update For Mac
  3. Excel Disappeared From After Microsoft Office Update Not Working
  4. Excel Disappeared From After Microsoft Office Update 2016
  5. Excel Disappeared From After Microsoft Office Update Error Code 0xc0000142

Subscribe Now:More:Microsoft Word disappears, you can res. After a recent windows update, a previous Excel vba script that was working, no longer functions correctly. The macro operation, when working, opens a csv file that is defined in the active workbook as String aString. The csv file contains a list of variables and corresponding values for those variables. The macro returns the original active. At the Microsoft forums, the company explains that after installing the Fall Creators Update, you may notice some app entries missing in the Start menu, and they won't appear in the App list.

How to Recover an Unsaved Word When the Computer Shuts Down

Excel Disappeared From After Microsoft Office Update 2020

My computer shut down and I lost my Word document, how to recover unsaved Word document 2007 after shutting down? There are three useful solutions you can try to retrieve when you forgot to save a word document.

Workable SolutionsStep-by-step Troubleshooting
Fix 1. Recover recent documentsOpen Word > click Open > click File > click Recent > click Recover from Recent Documents...Full steps
Fix 2. Recover from Manage DocumentRun Word > open a new file > click File > click Info and then Manage Document...Full steps
Fix 3. Recover temporary filesLocate the temp files in C:UsersUser_NameAppDataLocalMicrosoftOfficeUnsavedFiles...Full steps

In fact, none of the data recovery software on the market can recover unsaved Word documents. Typically, the third-party software only helps when you at least have an original file located on your computer's hard disk or a connected USB drive. You can use these data recovery tools to restore lost saved Word document, which is later missing due to accidental deletion, disk formatting, virus attack, partition loss, etc.

But if you want to recover a document that didn't save by computer crash or shutting down, the answer is NO, even the EaseUS data recovery software on this page, which is very famous in the field of data recovery. Then, how to recover when you forgot to save a Word document after the computer restarts? Follow the three effective solutions below.

How to Recover an Unsaved Word Document After Computer Restarts

Microsoft Office offers users the AutoRecover to restore the on-editing Word document automatically. You can enable this function by going to 'File' > 'Options' > 'Save' > checking 'Save AutoRecover'. You can change the time of the AutoSave interval. As long as this feature starts to work, you can recover the unsaved Word document after a computer restart, crash, or shutting down with the following methods. If your Word version is below version 2010, see another post on how to recover unsaved Word document 2007/2003.

Method 1. Recover from Recent Documents (Word 2010/2013/2016/2019)

  • Open Word application and click the 'Open' > 'File' tab.
  • Click 'Recent'.
  • Scroll to the bottom of your Recent Documents and then click 'Recover Unsaved Documents'.
  • The saved drafts will open in a new window. Click 'Save As' to restore the disappeared unsaved Word document after a computer problem.

Method 2. Recover from Manage Document

  • Run Word > open a new file or an existing file.
  • Click the 'File' tab > 'Info' > click 'Manage Document'.
  • Click 'Recover Unsaved Documents'.
  • You will see the list of your unsaved files. Select the file and click 'Open' > 'Save As' to store the Word file.

Method 3. Recover from Temporary Files

  • You can find the temp files in this path: C:UsersUser_NameAppDataLocalMicrosoftOfficeUnsavedFiles.
  • Choose the one you need to recover and open with Word application to save again.
Excel disappeared from after microsoft office update not working

If you have deleted the Unsaved Files folder and lost all the temporary files, you can use EaseUS Data Recovery to restore the deleted tempory files.

How to Recover Deleted or Lost Word Document on Windows 10/8/7

As explained before, a data recovery tool can't help you get back the unsaved Word document, but it provides you with an effective and easy way to recover deleted files. And EaseUS file data recovery software, a renowned document recovery program, enables you to restore lost DOC/DOCX, XLS/XLSX, PPT/PPTX, PDF, CWK, HTML/HTM, INDD, and EPS with a few clicks.

Supporting 200+ file types, EaseUS Data Recovery Wizard is good at recovering (permanently) deleted files from hard drive, SSD, USB flash drive, pen drive, external hard drive, and so on. Now, download this data recovery software and use it to restore any lost files as you need with the detailed guides below.

Step 1. Choose the Word file location

If it's on a USB flash drive or SD card, connect it to your computer first. Choose the hard disk drive or a specific folder and click the 'Scan' button.

Step 2. Scan and select lost files

The software will start immediately scanning all lost data on the selected drive. After the scan, click 'Filter', choose 'Word' from the drop-down list, and click the tree view on the left side to navigate the wanted Word documents.

Step 3. Preview Word files and recover

You're allowed to double-click and preview a Word file if you have Microsoft Word application installed on your computer. Finally, select the desired Word file and click 'Recover'.

People also ask

1. How do I recover an unsaved Word document 2007 after shutting down?

If your computer shut down and you lost your Word document, you can recover unsaved Word document 2007 in three ways, either recover from recent documents, manage document, or from temporary files.

2. Can I recover a word doc that I didn't save?

If you forgot to save Word document or your computer restarted and lost Word document, you can use the AutoRecover feature to recover unsaved Word document. Open Word, click the File tab > click Info > click Manage Document > click Recover Unsaved Documents. Then, find the unsaved Word document, click Open > Save As.

3. How do I recover an unsaved Word document in 2019?

Same as all previous versions of Word, Word 2019 also has the AutoRecover feature to help users recover unsaved Word document when computer shuts down. You can enable this function by going to File > Options > Save > checking Save AutoRecover. Once this function works, it can save your on-editing Word document at regular intervals. So you can recover unsaved Word document that didn't save.

-->

See a list of known issues that have been resolved for Windows 10, version 20H2 and Windows Server, version 20H2 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page.

Resolved issues

SummaryOriginating updateStatusDate resolved
Printing and scanning might fail when these devices use smart-card authentication
Non-compliant printers, scanners, and multifunction devices might fail to print when using smart-card authentication.
OS Build 19042.1110
KB5004237
2021-07-13
Resolved
2021-08-03
10:36 PT
Certain printers unable to print
Most affected printers are receipt or label printers that connect via USB.
OS Build 19042.1081
KB5003690
2021-06-21
Resolved
KB5004237
2021-07-13
10:00 PT
Internet Explorer 11 and apps using the WebBrowser control might fail to open PDFs
The 64-bit versions of IE11 and apps using the 64-bit version of the WebBrowser control might show PDFs as just gray.
OS Build 19042.1052
KB5003637
2021-06-08
Resolved
KB5004760
2021-06-29
10:00 PT
A high-pitched noise might be heard when using 5.1 audio with certain settings
Certain combinations of apps, audio devices and Windows settings might produce a high-pitched noise when using 5.1 audio
OS Build 19042.906
KB5000842
2021-03-29
Resolved
KB5003690
2021-06-21
14:00 PT
News and interests button on the Windows taskbar might have blurry text
Certain display configurations might cause blurry text on the news and interests button in the Windows taskbar.
OS Build 19042.964
KB5001391
2021-04-28
Resolved
KB5003690
2021-06-21
14:00 PT
Apps might have issues accessing event logs on remote devices
Event logs might not be accessible from remote devices unless both devices have updates released June 8, 2021 or later.
OS Build 19042.10000
KB5003637
2021-06-08
Resolved
KB5003637
2021-06-08
10:00 PT
Security updates released May 11, 2021 might not offer in managed environments
Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager and managed devices are affected.
OS Build 19042.985
KB5003173
2021-05-11
Resolved
2021-05-11
19:01 PT
Errors or issues during or after updating devices with certain Conexant audio drivers
Devices with affected Conexant or Synaptics audio drivers might receive a stop error with a blue screen.
N/A
Resolved
2021-05-07
13:29 PT
Errors or issues during or after updating devices with Conexant ISST audio drivers
Devices with affected Conexant ISST audio drivers might receive an error or have issues with Windows 10, version 2004.
N/A
Resolved
2021-05-07
13:29 PT
Lower than expected performance in games
Some users have reported lower game performance in full screen or borderless windowed mode when using multiple monitors.
OS Build 19042.906
KB5000842
2021-03-29
Resolved
2021-04-27
15:48 PT
Microsoft Edge missing after using custom media/ISOs including March 29, 2021 updates
Microsoft Edge missing when installing Windows from custom media/ISOs using updates released March 25, 2021 or later.
OS Build 19042.906
KB5000842
2021-03-29
Resolved
2021-03-29
17:01 PT
Unexpected results when printing from some apps or to some printers
Issues might include missing or solid color graphics, misalignment/formatting issues, or printing of blank pages/labels.
OS Build 19042.867
KB5000802
2021-03-09
Resolved
KB5001649
2021-03-18
19:00 PT
Error when attempting to print to certain printers
You might receive an APC_INDEX_MISMATCH error with a blue screen when attempting to print.
OS Build 19042.867
KB5000802
2021-03-09
Resolved
KB5001567
2021-03-15
14:00 PT
Memory or disk space error when opening documents in Microsoft Office apps
You might receive an error when attempting to open files that trigger the Protected View feature.
OS Build 19042.844
KB4601382
2021-02-24
Resolved
2021-03-13
11:42 PT

Issue details

July 2021

Printing and scanning might fail when these devices use smart-card authentication

StatusOriginating updateHistory
ResolvedOS Build 19042.1110
KB5004237
2021-07-13
Resolved: 2021-08-03, 10:36 PT
Opened: 2021-07-23, 14:36 PT
After installing updates released July 13, 2021 on domain controllers (DCs) in your environment, printers, scanners, and multifunction devices which are not compliant with section 3.2.1 of RFC 4556 spec, might fail to print when using smart-card (PIV) authentication.
Affected platforms:
  • Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
  • Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Next steps: A temporary mitigation is now available. For more information, please see KB5005408 - Smart-card authentication might cause print and scan failures.

Disappeared

Certain printers unable to print

StatusOriginating updateHistory
Resolved KB5004237OS Build 19042.1081
KB5003690
2021-06-21
Resolved: 2021-07-13, 10:00 PT
Opened: 2021-07-08, 16:40 PT
After installing KB5003690 or later updates (including out of band updates, KB5004760 and KB5004945), you might have issues printing to certain printers. Various brands and models are affected, primarily receipt or label printers that connect via USB.
Note This issue is not related to CVE-2021-34527 or CVE-2021-1675.
Affected platforms:
  • Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004
  • Server: Windows Server, version 20H2; Windows Server, version 2004
Resolution: This issue was resolved in KB5004237, released July 13, 2021. If you are using an update released before July 13, 2021, you can resolve this issue using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview.
Important If you install an update released July 13, 2021 ( KB5004237) or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue.

June 2021

Internet Explorer 11 and apps using the WebBrowser control might fail to open PDFs

StatusOriginating updateHistory
Resolved KB5004760OS Build 19042.1052
KB5003637
2021-06-08
Resolved: 2021-06-29, 10:00 PT
Opened: 2021-06-25, 12:53 PT
After installing KB5003637 or later updates, Internet Explorer 11 (IE11) or apps using the 64-bit version of the WebBrowser control might fail to open PDFs or may render as just a gray background using the Adobe Acrobat plug-in. Note Internet Explorer is only affected if Enable 64-bit Processes for Enhanced Protected Mode is enabled in the Advanced tab in Internet Options.
Workaround: To mitigate the issue, you can use one of the following:
  • Open the PDF file directly in Adobe Acrobat, instead of within IE11 or the affected app.
  • For IE11 only: Disable the setting in the Advanced tab of Internet Options called Enable 64-bit Processes for Enhanced Protected Mode.
Resolution: This issue was resolved in the out-of-band update KB5004760. It is a cumulative update, so you do not need to apply any previous update before installing it. KB5004760 is now available on the Microsoft Update Catalog and must be manually downloaded and installed. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions.
Affected platforms:
  • Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004
  • Server: Windows Server, version 20H2; Windows Server, version 2004

News and interests button on the Windows taskbar might have blurry text

StatusOriginating updateHistory
Resolved KB5003690OS Build 19042.964
KB5001391
2021-04-28
Resolved: 2021-06-21, 14:00 PT
Opened: 2021-06-14, 17:43 PT
After installing KB5001391 or later updates, the news and interests button in the Windows taskbar might have blurry text on certain display configurations.
Affected platforms:
  • Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909
Resolution: This issue was resolved in KB5003690.

Apps might have issues accessing event logs on remote devices

StatusOriginating updateHistory
Resolved KB5003637OS Build 19042.10000
KB5003637
2021-06-08
Resolved: 2021-06-08, 10:00 PT
Opened: 2021-06-07, 16:10 PT
After installing KB5003637 or later updates, apps accessing event logs on remote devices might be unable to connect. This issue might occur if the local or remote has not yet installed updates released June 8, 2021 or later. Affected apps are using certain legacy Event Logging APIs. You might receive an error when attempting to connect, for example:
  • error 5: access is denied
  • error 1764: The requested operation is not supported.
  • System.InvalidOperationException,Microsoft.PowerShell.Commands.GetEventLogCommand
  • Windows has not provided an error code.
Note Event Viewer and other apps using current non-legacy APIs to access event logs should not be affected.
Affected platforms:
  • Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
  • Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Resolution: This is expected due to security hardening changes relating to Event Tracing for Windows (ETW) for CVE-2021-31958. This issue is resolved if the local and remote devices both have KB5003637 installed.

Excel Disappeared From After Microsoft Office Update For Mac


May 2021

A high-pitched noise might be heard when using 5.1 audio with certain settings

StatusOriginating updateHistory
Resolved KB5003690OS Build 19042.906
KB5000842
2021-03-29
Resolved: 2021-06-21, 14:00 PT
Opened: 2021-05-13, 19:35 PT
After installing KB5000842 or later updates, 5.1 Dolby Digital audio may play containing a high-pitched noise or squeak in certain apps when using certain audio devices and Windows settings. Note This issue does not occur when stereo is used.
Workaround: To mitigate this issue, you can try one or more of the following:
  • Streaming the video or audio in a web browser or different app, instead of the app affected by this issue.
  • Enable Spatial sound settings by right clicking or long pressing on the volume icon in the notification area, selecting Spatial sound (Off) and selecting any of the available options.
Affected platforms:
  • Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004
Resolution: This issue was resolved in KB5003690.

Security updates released May 11, 2021 might not offer in managed environments

StatusOriginating updateHistory
ResolvedOS Build 19042.985
KB5003173
2021-05-11
Resolved: 2021-05-11, 19:01 PT
Opened: 2021-05-11, 14:58 PT
When checking for updates within Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager and managed devices that connect to these servers, KB5003173 might not be available or offered. Note: This might also affect Security Only and Internet Explorer Cumulative Rollups, on platforms that receive these types of updates.
Affected platforms:
  • Client: Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
  • Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Resolution: This issue is now resolved on the service-side and updates should be available. Note: If you initiate a synchronization cycle and are still not being offered the updates, please check again soon. There might be slight delay as it propagates to all servers in all regions.

April 2021

Lower than expected performance in games

StatusOriginating updateHistory
ResolvedOS Build 19042.906
KB5000842
2021-03-29
Resolved: 2021-04-27, 15:48 PT
Opened: 2021-04-23, 18:04 PT
A small subset of users have reported lower than expected performance in games after installing KB5000842 or later updates. Most users affected by this issue are running games full screen or borderless windowed modes and using two or more monitors.
Affected platforms:
  • Client: Windows 10, version 20H2; Windows 10, version 2004
  • Server: Windows Server, version 20H2; Windows Server, version 2004
Resolution: This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview.

March 2021

Microsoft Edge missing after using custom media/ISOs including March 29, 2021 updates

StatusOriginating updateHistory
ResolvedOS Build 19042.906
KB5000842
2021-03-29
Resolved: 2021-03-29, 17:01 PT
Opened: 2021-03-29, 16:15 PT
Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone Servicing Stack Update (SSU) released March 29, 2021 or later.
Note Devices that connect directly to Windows Update to receive updates are not affected. This includes devices using Windows Update for Business. Any device connecting to Windows Update should always receive the latest versions of the Servicing Stack Update (SSU) and latest cumulative update (LCU) without any extra steps.
Workaround: If you have already encountered this issue by installing the OS using affected custom media, you can mitigate it by directly installing the new Microsoft Edge from here. If you need to broadly deploy the new Microsoft Edge for business, see Download and deploy Microsoft Edge for business
Affected platforms:
  • Client: Windows 10, version 20H2; Windows 10, version 2004
  • Server: Windows Server, version 20H2; Windows Server, version 2004
Resolution: This issue is resolved. To avoid this issue, be sure to first slipstream the Servicing Stack Update (SSU) released March 29, 2021 or later into the custom offline media or ISO image before slipstreaming the latest cumulative update (LCU). To do this with the combined SSU and LCU packages now used for Windows 10, version 20H2 and Windows 10, version 2004, you will need to extract the SSU from the combined package. Use the following steps to extract the using SSU:
  1. Extract the cab from the msu via this command line (using the package for KB5000842 as an example): expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cab <destination path>
  2. Extract the SSU from the previously extracted cab via this command line: expand Windows10.0-KB5000842-x64.cab /f:* <destination path>
  3. You will then have the SSU cab, in this example named SSU-19041.903-x64.cab. Slipstream this file into your offline image first, then the LCU.

Unexpected results when printing from some apps or to some printers

StatusOriginating updateHistory
Resolved KB5001649OS Build 19042.867
KB5000802
2021-03-09
Resolved: 2021-03-18, 19:00 PT
Opened: 2021-03-18, 17:25 PT
After installing updates released March 9, 2021 or March 15, 2021, you might get unexpected results when printing from some apps. Issues might include:
  • Elements of the document might print as solid black/color boxes or might be missing, including barcodes, QR codes, and graphics elements, such as logos.
  • Table lines might be missing. Other alignment or formatting issues might also be present.
  • Printing from some apps or to some printers might result in a blank page or label.
Affected platforms:
  • Client: Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
  • Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Resolution: This issue was resolved in the out-of-band update KB5001649. It is a cumulative update, so you do not need to apply any previous update before installing it. You will need to Check for updates to install KB5001649 and might need to also select Download and Install. For instructions on how to Check for updates, please see Update Windows 10. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions.
Note KB5001649 is cumulative and addresses both the issue above and the issue addressed in the March 15, 2021 out-of-band release for the APC_INDEX_MISMATCH error with a blue screen.

Error when attempting to print to certain printers

StatusOriginating updateHistory
Resolved KB5001567OS Build 19042.867
KB5000802
2021-03-09
Resolved: 2021-03-15, 14:00 PT
Opened: 2021-03-10, 18:04 PT
After installing KB5000802, you might receive an APC_INDEX_MISMATCH error with a blue screen when attempting to print to certain printers in some apps. This issue affects a subset of Type 3 printer drivers and does not affect printer drivers that are Type 4. If you are unsure which type your printer driver is, use the following steps:
  1. Press the Windows key+r or select Start and type run and select it.
  2. Type printmanagement.msc and press enter or select the OK button.
  3. If Print Management opens, continue to step 4. If you receive the error, Windows can not find 'printmanagement.msc'. then select Start and type manage optional features and select it. Select Add a Feature and type print, select the check box next to Print Management Console and select install. You will now need to start at step 1 again.
  4. Expand Print Servers, expand your computer's name, and select Printers.
  5. You can now see the Driver Type for each of your installed printer drivers.
Workaround: To mitigate the issue, follow the instructions in this video. The Command Prompt commands from the video are as follows (you will need to replace KX driver for Universal printing with the name of your printer, as explained in the video):
  • rundll32 printui.dll,PrintUIEntry /Xg /n “KX driver for Universal printing”
  • rundll32 printui.dll,PrintUIEntry /Xs /n 'KX driver for Universal printing' attributes +direct
Affected platforms:
  • Client: Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803
  • Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803
Resolution: This issue was resolved in the out-of-band update KB5001567. It is a cumulative update, so you do not need to apply any previous update before installing it. You will need to Check for updates to install KB5001567 and might need to also select Download and Install. For instructions on how to Check for updates, please see Update Windows 10. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions.

Memory or disk space error when opening documents in Microsoft Office apps

StatusOriginating updateHistory
ResolvedOS Build 19042.844
KB4601382
2021-02-24
Resolved: 2021-03-13, 11:42 PT
Opened: 2021-03-13, 10:50 PT
When opening a document in Microsoft Word, Microsoft Excel, or any Microsoft Office applications, you might receive the error, 'Microsoft Excel cannot open or save any more documents because there is not enough available memory or disk space'. This issue only affects devices that have installed Microsoft Office apps from the Microsoft Store and are attempting to open a document that has triggered the use of the Protected View feature.
Affected platforms:
  • Client: Windows 10, version 20H2; Windows 10, version 2004
Resolution: This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to non-managed devices. Restarting your device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy. Note Devices need to be restarted after configuring the special Group Policy. To find out more about using Group Policies, see Group Policy Overview.

May 2020

Errors or issues during or after updating devices with certain Conexant audio drivers

StatusOriginating updateHistory
ResolvedN/A
Resolved: 2021-05-07, 13:29 PT
Opened: 2020-05-27, 00:20 PT
Synaptics and Microsoft have found incompatibility issues with certain versions of drivers for Conexant or Synaptics audio devices and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Conexant or Synaptics audio drivers might receive a stop error with a blue screen during or after updating to Windows 10, version 2004. The affected driver will be named Conexant HDAudio Driver under Sound, video and game controllers in Device Manager and have versions 8.65.47.53​, 8.65.56.51​, or 8.66.0.0 through 8.66.89.00 for chdrt64.sys or chdrt32.sys.
To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Conexant or Synaptics audio drivers installed from being offered Windows 10, version 2004 or Windows Server, version 2004 until the driver has been updated. If your organization is using Update Compliance, the safeguard IDs are 25702617, 25702660, 25702662, and 25702673.
Affected platforms:
  • Client: Windows 10, version 20H2, Windows 10, version 2004
  • Server: Windows Server, version 20H2, Windows Server, version 2004
Resolution: The safeguard hold with safeguard IDs 25702617, 25702660, 25702662, and 25702673 has been removed for all devices as of May 7, 2021, including devices with affected drivers. If updated drivers are not available for your device and you are offered Windows 10, version 2004 or Windows 10, version 20H2, a small number of devices might roll back to the previous version of Windows 10 when attempting to update. If this occurs, you should attempt to update to Windows 10, version 2004 or Windows 10, version 20H2 again.
Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to a later version of Windows 10 is offered.

Excel Disappeared From After Microsoft Office Update Not Working

Errors or issues during or after updating devices with Conexant ISST audio drivers

StatusOriginating updateHistory
ResolvedN/A
Resolved: 2021-05-07, 13:29 PT
Opened: 2020-05-27, 00:22 PT
Synaptics and Microsoft have found incompatibility issues with certain versions of drivers for Conexant ISST audio driver and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Conexant ISST audio driver might receive an error or experience issues while installing the update or after the device has updated. The affected driver will be named Conexant ISST Audio or Conexant HDAudio Driver under Sound, video and game controllers in Device Manager and have file name uci64a96.dll through uci64a231.dll and a file version of 7.231.3.0 or lower.
To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Conexant or Synaptics audio drivers installed from being offered Windows 10, version 2004 or Windows Server, version 2004 until the driver has been updated. If your organization is using Update Compliance, the safeguard ID is 25178825.
Affected platforms:
  • Client: Windows 10, version 20H2, Windows 10, version 2004
  • Server: Windows Server, version 20H2, Windows Server, version 2004
Resolution: The safeguard hold with safeguard ID 25178825 has been removed for all devices as of May 7, 2021, including devices with affected drivers. If updated drivers are not available for your device and you are offered Windows 10, version 2004 or Windows 10, version 20H2, a small number of devices might roll back to the previous version of Windows 10 when attempting to update. If this occurs, you should attempt to update to Windows 10, version 2004 or Windows 10, version 20H2 again.
Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to a later version of Windows 10 is offered.

Excel Disappeared From After Microsoft Office Update 2016

Problems

Excel Disappeared From After Microsoft Office Update Error Code 0xc0000142