Ktload364

-->

1. Microsoft Word Not Working On Ipad After Update
2. Microsoft Word 2000 Not Working
3. Microsoft Word Not Working After Update Mac
4. Microsoft Word Not Working After Mac Update Catalina

Jul 23, 2021 After the recent Window update, Ink tools in Office 2016 stopped working for both pen or mouse. I have Spectre HP. For other programs pen/mouse work without any problems. I uninstalled and reinstalled Office, got all updates and it did not resolve the problem. Please, advise what to do next. Word 2007 is not working properly after I installed a Windows Update for Vista this morning. Can open files, but not edit them. Cannot double-click to launch files from directory; Word opens but does not proceed to open the file itself. I was using Word at the time when the Updater began an automatic shutdown to install the downloaded updates.

Note

If you're using Microsoft 365 (Microsoft Word for Office 365 with Windows 10), see Troubleshoot print failures in Word for Office 365 on Windows 10.

1. May 21, 2020 Disable add-ins. If 'Word not responding' is not an error in Safe Mode, an incompatible add-in is a likely culprit. Select File Options Add-ins to open Word Options. Choose the Go button under Manage near the bottom of the window to open the COM Add-ins dialog box.
2. Aug 21, 2017 When an Office application like Word does not allow by your computer to update, you need to repair it first through the To start repairing this application, Press Windows + Xand click Programs and Features. Then, select which type of repair you want to perform. Linkfor more information about repairing an Office application.

This article describes how to diagnose print failures in Microsoft Word. It also explains how to isolate the cause of the print failure and how to resolve the issue.

Examples of print failure include the following situations:

• You receive error messages and other messages when you try to print a file.
• The printer doesn't respond.
• A file is printed as meaningless symbols.

Important

This article doesn't discuss printer output issues, such as envelope-positioning problems, missing graphics, or inaccurate page numbers.

To resolve a print failure in Word, you must determine its cause. Causes typically fit into one of the following categories:

• Corrupted files or corrupted content in documents
• The Word program itself
• The printer driver
• The Windows operating system
• Connectivity or hardware

Don't make assumptions about what is causing your printing problem. Instead, rely on systematic troubleshooting to reveal the cause.

Use the following tests to help determine the cause of the printing failure.

Step 1: Test printing in other documents

Corrupted files or documents that contain corrupted graphics or fonts can cause print errors in Word. Before you reinstall drivers or software, test whether Word can print. To do this, follow these steps for your version of Word.

Word 2007 through Word 2019

1. Open a new document in Word.

2. On the first line of the document, type =rand(10), and then press Enter:

   Note

   The =rand(10) command inserts 10 paragraphs of sample text.

3. Try to print the document.

4. If the document prints successfully, change to a different font, or insert clip art, a table, or a drawing object.

   • To change the font, follow these steps:

     1. Select the sample text.
     2. Open the Home tab.
     3. In the Font group, select a different font in the font list.

   • To insert clip art, follow these steps:

     1. Open the Insert tab, and then select Online Pictures. (In Word 2010 and Word 2007, select the Insert tab, and then select Clip Art.)
     2. On the Clip Art task pane, leave the Search text box blank, and then select Go. (In Word 2013, type a term in the Office . com Clip Art search box, and then select Search.)
     3. Right-click one of the pictures, and then select Insert.
     4. Close the Clip Art task pane.

   • To insert a table, follow these steps:

     1. Select Insert, select Table, and then select Insert Table.
     2. Select the number of columns and rows that you want, and then select OK.

   • To insert a drawing object, follow these steps:

     1. Select Insert, and then select Shapes.
     2. Double-click one of the shapes.

5. Test the print function again.

The success or failure of these tests shows whether Word can print generally. These tests may also give you clues about certain fonts or graphics that Word cannot print.

If you don't receive errors in the test document but still cannot print the original document, the file may be corrupted. This situation might be true even if you can print the same document on another computer because the symptoms of file corruption don’t necessarily appear on all computers.

For more information about how to troubleshoot corrupted Word files, see How to troubleshoot damaged documents in Word.

If Word cannot print at all, or if Word cannot print a certain font or a specific type of graphic, go to the next step.

Step 2: Test printing in other programs

The scope of the printing problem may reveal its cause. For example, some printing problems affect only Word, whereas other printing problems affect several of or all Windows-based programs.

The following tests can help determine whether this problem involves programs other than Word.

Test in WordPad

Print a plain text file

1. Select Start, point to Programs, point to Accessories, and then select WordPad.

   Note

   • In Windows 8, press the Windows key to open the Start menu, type WordPad, and then select the WordPad icon.
   • In Windows 7, point to All Programs, point to Accessories, and then select WordPad.

2. In the blank WordPad document, type This is a test.

3. On the File menu, select Print.

4. Select OK or Print to print the file.

Print specific fonts or images

If Step 1 indicated that the print problem involves only certain fonts or certain graphics images, try to reproduce this problem in WordPad. To do this, apply the same font, or insert the same kind of graphics image. (To select a different font in WordPad, use the same method that you use in Word.)

To insert a graphics image in WordPad, follow these steps:

1. On the Insert menu, select Object.

   Note

   In Windows 8 and Windows 7, select Insert Object on the Home tab.

2. Follow one or both of the following steps:

   • To create a new graphics image, select Create New, and then select one of the object types from the list. For example, select Paintbrush Picture to create a test bitmap in the Microsoft Paint program.
   • To insert a graphics image from a file, select Create from File, and then select Browse to select the file.

3. On the File menu, select Print.

4. Select OK or Print.

Printing from other programs

If you still cannot print from WordPad, test the print functions from either your web browser, or your other Office programs.

Print a test page from the printer

You can also try to print a test page on your printer. To print a test page, follow these steps:

Microsoft Word Not Working On Ipad After Update

1. Select Start, point to Settings, and then select Printers.

   Note

   • In Windows 8, press the Windows key to go to the Start Screen, type Printers, select Settings, and then select Devices and Printers.
   • In Windows 7, select Start, and then select Devices and Printers.
   • In Windows Vista, select Start, and then select Printers.

2. Right-click the icon for your printer, and then select Properties.

3. On the General tab, select Print Test Page.

If you can't print a test page, or if you cannot print in several or all Windows-based programs, the problem might be related to a printer driver, hardware, the operating system, or internet connectivity.

If the problem is limited to a particular font, a corrupted font file may be the cause. For more information about how to test and reinstall fonts, see How to install or remove a font in Windows.

If you can print without problems in all programs except Word, go to the next step.

You might be able to use Windows printing help and troubleshooters to resolve the printing problem:

1. Select Start > Settings.

2. Type printer problems, and then select Find and fix problems with printing.

   Note

   • To correct printer connection and printing problems in Windows 10, see Fix printer connection and printing problems in Windows 10.
   • In Windows 8 and Windows 7, you can run the printing troubleshooting wizard by selecting Start, typing printing, and then selecting Find and fix printing problems.
   • In Windows Vista, select Start, select Help and Support, and search on printing or printing troubleshoot.

Step 3: Test printing with different printer drivers

If Word is the only program on your computer that cannot print, be aware that Word is a very printer-intensive program. Therefore, a minor problem in the printer driver tends to affect Word before it affects other programs.

To determine whether the printer driver is the cause of the problem, you can test different drivers. If the Word printing problem occurs only when you print documents that use a certain font or a specific type of graphics image, try to print to another printer.

If no other printer is available, contact the manufacturer to determine whether there is an updated version of the driver or a different driver for your printer model.

If the Word printing problem occurs even when you print documents that contain only text, you can use a generic, text-only printer driver to test printing from Word. To do this, follow these steps for your version of Windows.

Note

On some versions of Windows, these steps may require access to the Windows installation CD-ROM or access to a network drive that contains the Windows installation files.

Test printing in Windows 10

1. In the Windows search box, type printers, and then select Printers & scanners.
2. Select Add a printer or scanner.
3. Under “Printers & scanners,” select Generic/Text Only.
4. Open a Word document, and then try to print to the Generic/Text Only printer option.
5. Name the file Test.prn, and save it to your Documents folder.

Test printing in Windows 8, Windows 7, and Windows Vista

1. Take one of the following actions, as appropriate for your situation:

   • For Windows 8 and Windows 7: Select Start, and then select Devices and Printers.
   • For Windows Vista: Select Start, and then select Printers.

2. On the first screen of the Add Printer wizard, select Add a printer.

3. Select Add a local printer on the first screen of the Add Printer Wizard.

4. Make sure that the Use an existing port check box is selected, change the dropdown option to File: (Print to file), and then select Next.

5. In the Manufacturers list, select Generic, and then select Next.

6. Leave the default printer name, select Next, and then select Finish.

7. When the driver installation is complete, open a document in Word, and then do the following, as appropriate for your situation:

   • For Word 2013 and later versions: On the File menu, select Print.
   • For Word 2010: Select the printer dropdown menu, and then select Print.
   • For Word 2007: Select the Microsoft Office Button, and then select Print.
   • For other Word versions: Select the Print to File check box, and then select OK.

8. Change the location to My Document, and then name the file Test.prn.

9. Select OK or Print (depending on your version of Word).

If you receive an error message in Word when you print files that contain only text, but you do not receive the error message when you print by using the generic, text-only printer driver, your printer driver might be corrupted. If this is the case, contact the manufacturer for help with removing the printer driver and install an updated version.

If the printing problem occurs when you use a different printer driver, go to the next step.

Step 4: Test the Word program files and settings

After you verify that the printing problem is not limited to a particular document or to a particular printer driver, and that the problem is limited to the Word program, test the Word program by using resetting the user options.

For more information about how to reset the user options, see How to reset user options and registry settings in Word.

If the printing problem continues to occur, run Detect and Repair to reinstall the missing or corrupted program files. To run Detect and Repair, follow these steps for your version of Word.

Word 2019, 2016, 2013, and 2010

1. Exit all Office programs.
2. Select Start, and then type add remove.
3. Open the Add or Remove Programs item.
4. Select Change or Remove Programs, select Microsoft Office (Microsoft Office Word) or the version of Office or Word that you have in the Currently installed programs list, and then select Change or Modify.
5. Select Repair or Repair Word (Repair Office), and then select Continue or Next.

Word 2007

1. Start Word 2007.
2. Select the Microsoft Office button, and then select Word Options.
3. Select Resources, select Diagnose, and then follow the prompts on the screen.

If the printing problem continues to occur after you repair the Word installation or the Office installation, go to the next step.

Step 5: Test for problems in Windows

To look for device drivers or memory-resident programs that might be interfering with the Word print function, start Windows in safe mode, and then test print to a file in Word. To start Windows in safe mode, follow these steps for your version of Windows.

Test for problems in Windows 10

To start Windows 10 in safe mode, see Start your PC in safe mode in Windows 10.

Test for problems in Windows 8, Windows 7, and Windows Vista

1. Remove all DVDs, CDs, floppy disks, and any other external media from your computer, and then restart your computer.

2. Select Start, select the arrow next to the Lock button, and then select Restart.

   Note

   In Windows 8, select Settings from the Charms menu, select Power, and then select Restart.

3. Press and hold the F8 key as your computer restarts.

   Note

   You must press the F8 key before the Windows logo appears. If the Windows logo appears, you must restart the computer. To do this, wait until the Windows logon prompt appears, and then shut down and restart the computer.

4. On the Advanced Boot Options screen, use the arrow keys to select the Safe Mode option, and then press Enter.

5. Sign in to your computer by using a user account that has administrative credentials.

If the Word printing problem does not occur when you start Windows in safe mode, use clean-boot troubleshooting to help determine the source of the problem.

For more information about how to perform a clean restart in Windows, see How to perform a clean boot in Windows.

Related articles

Note

Office 365 ProPlus is being renamed to Microsoft 365 Apps for enterprise. For more information about this change, read this blog post.

Tip

Microsoft Word 2000 Not Working

To diagnose and automatically fix several common Office sign-in issues, you can download and run the Microsoft Support and Recovery Assistant.

Overview

This article contains information about a new authentication framework for Microsoft Office 2016.

By default, Microsoft Microsoft 365 Apps for enterprise (2016 version) uses Azure Active Directory Authentication Library (ADAL) framework-based authentication. Starting in build 16.0.7967, Office uses Web Account Manager (WAM) for sign-in workflows on Windows builds that are later than 15000 (Windows 10, version 1703, build 15063.138).

General guidance

If you experience authentication issues in Office application on Windows 10, we recommend to do the following actions:

Microsoft Word Not Working After Update Mac

• Update Office products to the latest build for your channel according to Update history for Microsoft 365 Apps for enterprise (listed by date).
• Make sure that you are running any of the following Windows builds:
  • Any build for Windows 10, version 1809 or a later version
  • 17134.677 or later builds for Windows 10, version 1803
  • 16299.461 or later builds for Windows 10, version 1709
  • 15063.1112 or later builds for Windows 10, version 1703

Symptoms

You may experience one of the following symptoms after you update to Microsoft Office 2016 build 16.0.7967 or a later version on Windows 10.

Symptom 1

When the overall network is working on your devices, Office applications may experience connection issues. You may see a message that resembles the following:

To determine whether you're experiencing this kind of issue, follow these steps:

1. Make sure that you're running Office build 16.0.9126.2259 or a later build. (The latest build on your channel is great. See the general guidance in the Overview section.)

2. Open Event Viewer.

3. Go to Applications and Services Logs > Microsoft > Windows > AAD.

4. In the Operational logs, locate messages from XMLHTTPWebRequest that have the following pattern:

5. Make sure that the time of these errors is related to the time when you actually had an Internet connection. This is not an intermittent network issue because of the loss of a Wi-Fi connection or a wake-up after hibernation and initialization of the network stack.

Then, to determine whether your issue is due to network environment or local firewall/antivirus software, follow these steps:

1. Open Edge (not Internet Explorer) and go to https://login.microsoftonline.com. Navigation should land on https://www.office.com or your company's default landing page. If this fails, the issue is in a network environment or local firewall/antivirus software.

2. Open Edge (not Internet Explorer) in InPrivate mode and go to https://login.microsoftonline.com. After you enter credentials, navigation should land on https://www.office.com or your company's default landing page. If this fails, the issue is in a network environment or local firewall/antivirus software.

To resolve this issue, make sure that your local firewall, antivirus software, and Windows Defender don't block the following AAD WAM plug-in processes that engaged in token acquisition:

C:WindowsSystemAppsMicrosoft.AAD.BrokerPlugin_cw5n1h2txyewyMicrosoft.AAD.BrokerPlugin.exe

C:WindowsSystem32backgroundTaskHost.exe

Note The PackageFamilyName of the plugin is the following:

Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy

Also, make sure that your network environment doesn't block the primary destination:

Note This primary address covers many IP addresses (and many services). Some of these addresses may be blocked in the environment for no good reason, which causes intermittent problems in some devices while other devices work fine.

Symptom 2

When you try to open or save a document in Microsoft SharePoint Online, OneDrive for Business, or SharePoint, or you try to synchronize email messages or your calendar in Microsoft Outlook, you're prompted for credentials. After you enter credentials, you're prompted again. This issue may occur for the following reasons:

• The Trusted Platform Module (TPM) chip or firmware is malfunctioning. Windows uses the TPM chip to protect your credentials. The chip may become corrupted or reset in some conditions. To determine whether you are experiencing this kind of issue, follow these steps:

  1. Open Event Viewer.
  2. Go to Applications and Services Logs > Microsoft > Windows > AAD.
  3. In the Operational logs, locate the errors that display the following pattern:0x?028????, 0x?029???? or 0x?009????

  To avoid this issue in future, we recommend that you update the TPM firmware.

  For Windows 10, version 1709 or later versions: The operating system automatically detects situations that are related to TPM failures and provides a user recovery process that should occur automatically. If this process doesn't occur automatically, we recommend that you use this manual recovery method.

  For Windows 10, version 1703: An automatic process is provided for Hybrid Azure AD join. No automatic process is provided for other environment configurations. If the Hybrid Azure AD join process doesn't occur automatically, we recommend that you use this manual recovery method.

• A device is disabled by the user, the Enterprise administrator, or a policy because of a security concern or by mistake. To determine whether you are experiencing this issue, follow these steps:

  1. Open Event viewer.
  2. Go to Applications and Services Logs > Microsoft > Windows > AAD.
  3. In the Operational logs, locate the following message:

  Description: AADSTS70002: Error validating credentials. AADSTS135011: Device used during the authentication is disabled.

  To resolve this issue, we recommend that the Enterprise administrator enable the device in Active Directory or Azure Active Directory (Azure AD). For information about how to manage devices in Azure AD, see the Device management tasks section of the 'How to manage devices using the Azure portal' topic on the Microsoft Docs website.

• The Enterprise administrator or a policy deleted a device because of a security reason or by mistake. To verify that you are experiencing this issue, follow these steps:

  1. Open Event viewer.
  2. Go to Applications and Services Logs > Microsoft > Windows > AAD.
  3. In the Operational logs, locate the following message:

  Description: AADSTS70002: Error validating credentials. AADSTS50155: Device is not authenticated.

  To resolve this issue, we recommend that you recover the device by using the manual recovery method. Note If nobody on the Enterprise deleted the device, please file a support ticket and provide an example of a device that is not recovered.

Manual recovery

To do a manual recovery of the computer, follow the appropriate steps, depending on how the device is joined to the cloud (Hybrid Azure AD join, Add a work account, or Azure AD join).

• Hybrid Azure AD join

  Run the following command: ​​>dsregcmd /status

  The result should contain the following fields (in Device state):

  The current logon user should be a domain user. The affected identity should be the current logon user.

  Recovery (safe to do):

  Run the Dsregcmd /leave command in an administrative Command Prompt window, and then restart the system.

• Add a work account

  Run the following command: >dsregcmd /status

  The result should contain the following field (in User state):

  The device state can be set to any option. The current logon user can be any user. The affected identity should be a work or school account that you can see in Setting > Accounts > Access work or school.

  Recovery (safe to do):

  Remove the work account in Setting > Accounts > Access work or school, and then restore the work account.

• Azure AD join

  Run the following command: >dsregcmd /status

  The result should contain the following fields (in Device state):

  The current logon user should be an Azure Active Directory (AAD) user. The affected identity should be the current logon user.

  Recovery:

  Note Back up your data first.

  Create a new local administrator. Disconnect from the domain (Setting > Accounts > Access work or school > Disconnect). Then, log on as the new local administrator, and reconnect to Azure AD.

Symptom 3

The Office sign-in workflow stops or shows no on-screen progress. The sign-in window shows a 'Signing in' message or a blank authentication screen.

This issue occurs because WAM is disabling non-HTTPS traffic to prevent security threats, such as someone stealing user credentials. To verify that you are experiencing this issue, follow these steps:

1. Open Event viewer.

2. Go to Applications and Services Logs > Microsoft > Windows > AAD.

3. In the Operational logs, locate the following message:

   Navigation to non-SSL destination. Non-secure communication is prohibited. Canceling navigation.

To resolve this issue and secure user credentials, we recommend that you enable HTTPS on the Identity servers.

Symptom 4

You have a non-persistent Virtual Desktop Infrastructure (VDI) environment that has a federated Identity Provider (IdP) that is configured as Single-Sign On (SSO). You do not expect to be prompted to activate or sign in because SSO is configured. However, you are prompted to sign in for each new session. Office ULS logs display the following error message:

{'Action': 'BlockedRequest', 'HRESULT': '0xc0f10005'

Note

Please open a support case if you experience this issue. We require more log entry reports to help isolate the issue.

More information

The following guidelines apply to this article:

• On builds of Windows 7, Windows 8, Windows 8.1, or Windows 10 that are earlier than 15000, ADAL authentication is the only option.
• The Windows build should be later than 15000 (Windows 10, version 1703, build 15063.138, Generally Available). For more information, see Windows 10 release information.
• This article applies whether you use Microsoft Federation or non-Microsoft Federation solutions.

For more information, see the following Knowledge Base article:

Microsoft Word Not Working After Mac Update Catalina

4347010 Error Code: 0x8004deb4 when signing in to OneDrive for Business