Microsoft Word Interrupted Shut Down Mac

-->

It was shut down in 1996. In 1995 a decision was made to (officially) start licensing the Mac OS and Macintosh ROMs to 3rd party manufacturers who started producing Macintosh 'clones'. This was done in order to achieve deeper market penetration and extra revenue for the company. Microsoft Word – You cannot save while the file is in use by another process. Try saving the file with a new name. (Normal.dotm) I am not aware of any other process taking place but I respond with OK “Microsoft Word” interrupted logout. – To continue logging out, quit “Microsoft Word”. The Microsoft Office Installer should have an icon in the Dock, just right-click it and choose 'Quit' for hold the option key and choose 'Force Quit' then shutdown or run the installer again. I have had to do that a couple of times due to hangs during the Office 2013 install, although I did not do a shutdown, just force quit and run installer. Plist files can become corrupt when a Mac shuts down or restarts unexpectedly or when an app freezes or crashes. As a result, the app may not open. When you delete a bad preference file, your Mac creates a new plist file that contains all the app's defaults automatically. My problem seems severe. I can't quit from Word or shutdown Mac. The stupid message keeps appearing. I've tried to reinstall Endnotes. But no solution.

Can microsoft shut down my computer

See a list of known issues that have been resolved for Windows 10, version 2004 and Windows Server, version 2004 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
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 19041.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 19041.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 19041.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 19041.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 19041.844
KB4601382
2021-02-24
Resolved
2021-03-13
11:42 PT
Some games might fail to open, or you might receive an error
You might have issues with some Direct3D games when using in-game overlay feature of Discord.
OS Build 19041.1000
KB4598291
2021-02-02
Resolved External
2021-02-08
19:16 PT
Stop error when plugging in a Thunderbolt NVMe SSD
Devices using Thunderbolt SSDs may receive a stop error 'DRIVER_VERIFIER_DMA_VIOLATION (e6)' when plugging an SSD in.
OS Build 19041.488
KB4571744
2020-09-03
Resolved
KB4586853
2020-11-30
14:00 PT
Issues when using Microsoft IME for Japanese or Chinese languages
Users of the Microsoft IME for Japanese or Chinese languages might have issues.
N/A
Resolved
KB4586853
2020-11-30
14:00 PT
Domain controllers in your enterprise might encounter Kerberos authentication issues
Authentication and renewal issues for Kerberos ticket after installing updates released November 10, 2020.
OS Build 19041.630
KB4586781
2020-11-10
Resolved
KB4594440
2020-11-19
10:00 PT
Certificates may not be present after updating to a newer version of Windows 10
Devices in a managed environment using update management tools or ISO images might lose certificates when updating.
OS Build 19041.546
KB4577063
2020-10-01
Resolved
2020-11-17
14:11 PT

Issue details

April 2021

Lower than expected performance in games

StatusOriginating updateHistory
ResolvedOS Build 19041.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 19041.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 19041.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 19041.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 19041.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.

February 2021

Some games might fail to open, or you might receive an error

StatusOriginating updateHistory
Resolved ExternalOS Build 19041.1000
KB4598291
2021-02-02
Last updated: 2021-02-08, 19:16 PT
Opened: 2021-02-08, 18:29 PT
Microsoft and Discord have found incompatibility issues with some games using Direct3D 12 when the in-game overlay feature of Discord is enabled. When attempting to open affected games you might receive an error, or the game might close silently.
Affected platforms:
  • Client: Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909
Workaround: To mitigate this issue, you can turn off the in-game overlay in settings within the Discord app.
Resolution: This issue is now resolved in an update to the Discord app. To verify you're on the latest version, right click on the Discord icon in the notification area and select 'Check for updates...'. If there are updates to install, it should install automatically but you might need to select the arrow icon in the upper right corner of the app to install the updated version. There is no update for Windows needed to resolve this issue.

November 2020

Microsoft Word Interrupted Shut Down Macbook Pro

Stop error when plugging in a Thunderbolt NVMe SSD

StatusOriginating updateHistory
Resolved KB4586853OS Build 19041.488
KB4571744
2020-09-03
Resolved: 2020-11-30, 14:00 PT
Opened: 2020-11-05, 19:01 PT
An incompatibility issue has been found with Windows 10, version 2004 or Windows 10, version 20H2 when using an Thunderbolt NVMe Solid State Disk (SSD). On affected devices, when plugging in a Thunderbolt NVMe SSD you might receive a stop error with a blue screen and 'DRIVER_VERIFIER_DMA_VIOLATION (e6) An illegal DMA operation was attempted by a driver being verified.' Affected Windows 10 devices will have at least one Thunderbolt port and any currently available version of the driver file stornvme.sys.
To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected drivers from being offered Windows 10, version 2004 or Windows 10, version 20H2. If your organization is using Update Compliance, the safeguard IDs is 29991611.
Affected platforms:
  • Client: Windows 10, version 20H2; Windows 10, version 2004
Resolution: This issue was resolved in KB4586853 and the safeguard hold has been removed as of December 11, 2020. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 10, version 20H2 or Windows 10, version 2004 is offered.

Domain controllers in your enterprise might encounter Kerberos authentication issues

StatusOriginating updateHistory
Resolved KB4594440OS Build 19041.630
KB4586781
2020-11-10
Resolved: 2020-11-19, 10:00 PT
Opened: 2020-11-14, 13:39 PT
After installing KB4586781 on domain controllers (DCs) and read-only domain controllers (RODCs) in your environment, you might encounter Kerberos authentication issues. This is caused by an issue in how CVE-2020-17049 was addressed in these updates. As noted in CVE-2020-17049, there are three registry setting values for PerformTicketSignature to control it, but in the current implementation you might encounter different issues with each setting:
  • Setting the value to 0 might cause authentication issues when using S4U scenarios, such as scheduled tasks, clustering, and services for example line-of-business applications.
  • The default value setting of 1 might cause non-Windows clients authenticating to Windows Domains using Kerberos to experience authentication issues.
    • With setting 1, clients attempting to renew a Kerberos ticket that should be renewable on a DC updated with KB4586781 will fail to renew the Kerberos ticket if it was issued from a DC that has not installed an update released November 11, 2020 or any DC running Windows Server 2008 R2 SP1 or Windows Server 2008 SP2.
    • Going from 0 to 1 might also cause this issue since there can be outstanding Kerberos tickets that are marked renewable, but will not be renewed by updated DCs.
  • With the default value setting of 1, you might also have Cross realm referrals failures on Windows and non-Windows devices for Kerberos referral tickets passing through domain DCs that have not installed an update released November 11, 2020 or any DC running Windows Server 2008 R2 SP1 or Windows Server 2008 SP2. This issue might happen if domain environment is partially updated or contains at least one Windows Server 2008 R2 SP1 or Windows Server 2008 SP2.
  • Setting the value to 2 is intended for enforcement mode and will create issues in an environment where not all DCs are updated because it will explicitly reject certain types of non-compliant Kerberos tickets. It should also not be used at this time if your environment contains DCs running Windows Server 2008 R2 SP1 or Windows Server 2008 SP2.
Note This issue only affects Windows Servers, Windows 10 devices and applications in enterprise environments.
Affected platforms:
  • Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Resolution: This issue was resolved in the out-of-band update KB4594440. It is a cumulative update, so you do not need to apply any previous update before installing it. To get the standalone package for KB4594440, search for it in the Microsoft Update Catalog. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions. Note KB4594440 is not available from Windows Update and will not install automatically.

Microsoft Word Interrupted Shut Down Mac


October 2020

Certificates may not be present after updating to a newer version of Windows 10

StatusOriginating updateHistory
ResolvedOS Build 19041.546
KB4577063
2020-10-01
Resolved: 2020-11-17, 14:11 PT
Opened: 2020-10-30, 17:16 PT
System and user certificates might be lost when updating a device from Windows 10, version 1809 or later to a later version of Windows 10. Devices will only be impacted if they have already installed any Latest cumulative update (LCU) released September 16, 2020 or later and then proceed to update to a later version of Windows 10 from media or an installation source which does not have an LCU released October 13, 2020 or later integrated. This primarily happens when managed devices are updated using outdated bundles or media through an update management tool such as Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager. This might also happen when using outdated physical media or ISO images that do not have the latest updates integrated.
Note Devices using Windows Update for Business or that connect directly to Windows Update are not impacted. Any device connecting to Windows Update should always receive the latest versions of the feature update, including the latest LCU, without any extra steps.
Workaround: If you have already encountered this issue on your device, you can mitigate it within the uninstall window by going back to your previous version of Windows using the instructions here. The uninstall window might be 10 or 30 days depending on the configuration of your environment and the version you’re updating to. You will then need to update to the later version of Windows 10 after the issue is resolved in your environment. Note Within the uninstall window, you can increase the number of days you have to go back to your previous version of Windows 10 by using the DISM command /Set-OSUninstallWindow. You must make this change before the default uninstall window has lapsed. For more information, see DISM operating system uninstall command-line options.
Affected platforms:
  • Client: Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1903
  • Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1903
Resolution: This issue is now resolved when using the latest feature update bundles and refreshed media. Feature update bundles were released November 9, 2020 for Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. Refreshed media was released November 3, 2020 on Volume Licensing Service Center (VLSC) and Visual Studio Subscriptions (VSS, formerly MSDN Subscriptions). For information on verifying you're using the refreshed media, see How to address feature update refreshes in your environment. If you are using or creating custom media, you will need to include an update released October 13, 2020 or later.
Note If you are updating to Windows 10, version 20H2, this is only resolved with the feature update bundle released November 9, 2020. Refreshed media is not yet available on VLSC or VSS. Refreshed media for VLSC and VSS will be released in the coming weeks to address this issue and another known issue that requires a media refresh. Please check the known issue here for the status of the remaining Windows 10, version 20H2 known issue.

Mac

August 2020

Issues when using Microsoft IME for Japanese or Chinese languages

StatusOriginating updateHistory
Resolved KB4586853N/A
Resolved: 2020-11-30, 14:00 PT
Opened: 2020-08-31, 12:12 PT
Users of the Microsoft IME for Japanese or Chinese languages might experience issues when attempting various tasks. Input may have issues, you may receive unexpected results or you may be unable to enter text. For a list of specific issues, see KB4564002.
Affected platforms:
  • Client: Windows 10, version 20H2, Windows 10, version 2004
  • Server: Windows Server, version 20H2, Windows Server, version 2004
Resolution: All IME issues listed in KB4564002 were resolved in KB4586853.

HomeProductsYodot DOC RepairHow to Access ASD File?

“On my system, Word application stopped responding all of a sudden. So, I immediately saved the document, which I was working and then closed the Word application. But the file is saved with .asd extension, instead of .doc. Also, if I try to open the file I get an error that states, “Microsoft Word cannot open this file because it is an unsupported file type.” What is this ASD file? How can I recover contents of my Word document? Someone kindly help me.”

What is ASD or .asd file?

Before you know about ASD file, have knowledge of AutoRecover feature provided in Microsoft Word program.

AutoRecover is an inbuilt option provided in Microsoft Office suite, which pull the plug on data loss due to unexpected interruptions like power surge, generation of errors, application halt/crash, abrupt system shut down etc that may prevent you from saving the Word file in a right way. Still, it is not an alternative for Save option. So, AutoRecover aspect aids in safeguarding a Word file during sudden disaster, only if the file is saved throughout the process as well at end.

If Word is terminated/interrupted in middle of process, then the current document will be saved in AutoRecover folder (if it was saved frequently, also at end); only when AutoRecover option is enabled. You can find AutoRecover folder under this path- C:UsersAppDataRoamingMicrosoftWord (Windows 7 and above) and C:UsersApplication DataMicrosoftWord (Windows 7 and below).

And Auto-Recovered file will be named as

  • AutoRecovery save of X.asd (X is name of opened file) in Win 7 and below
  • ~Wra####.asd (#### is random number given by Windows) in Win 7 and above

So, ASD is your rescued Word file. This file contains replica of currently opened Word document.

How to open ASD file? Why it shows error?

Microsoft Word Interrupted Shut Down Mac Os

If your Windows file association is all set then it links .asd file with respective program present in your computer to open the file, as soon as you double-click on it. If adequate program is missing then you need to install it.

Sometimes Windows prompts you to pick suitable program to open ASD file from list of available applications on your system, if the file is not associated so far.

If you cannot open the ASD file directly or if you come across errors like unable to open ASD file unsupported file type then try below methods.

Note: Never try to rename your original .asd files. If you want to do, try with its copied file.

1. Open ASD File Manually

  • Go to Start, type .asd in search tab and hit Enter key
  • From displayed list, select your ASD file and open it
  • Select MS Word to launch the file (If asked)
  • Choose All Files in file types list
  • When file opens, copy its entire content and paste it in a new Word file
  • Save the new Word file with .doc/.docx extension

2. Open ASD file in Word 2010

Microsoft Word 2010 is fitted with enhanced features to help users. So, employ it to access your ASD file.

  • Avail Microsoft Word 2010 tool
  • Launch it and click on Office button
  • Use Open option and select your ASD file
  • Opt All Files in file types tab
  • Copy the ASD file data
  • Create a new file and paste it
  • Save created file in Word format

Additional Info:

You may come across numerous circumstances that lead to corruption of your vital Word documents. However, don’t be worried. You can easily fix the broken Word file with the assistance of apt fix i.e. Yodot DOC Repair. This Word file repair utility can fix even severely corrupted as well damaged DOC/DOCX files with 100% precision. Also, when you are facing CRC error, unrecognized format error, Macro error, encoding error while opening Word file then the problems can be easily sorted out using Yodot.

3 steps to fix your Word file using Yodot:

Microsoft Shut Down My Email

  • Install Yodot DOC Repair and click on Browse button
  • Select Word fie that you want to fix and hit Repair key
  • Preview the fixed file and Save it

Suggested:

  • Take care of your Word application; avoid abrupt closing
  • Make a habit of working on copied file, instead of original one