Fix Microsoft Word Stopped Working in Windows

Could not connect to the System Event explanation: Although logging into a Windows 10 computer may seem like a simple process, it’s actually not since the Windows operating system has built a mechanism in a way that any third party or malware intervention would not compromise access to the system. This mechanism is supported by numerous services, functions, and DLL files. And Microsoft has been taking this security to a whole new level with the introduction of Windows Hello. Recently, a number of users reported getting the “Windows could not connect to the System Event Notification Service service. Please consult your system administrator” error when logging into their computers. While some users also reported that although they can log in, they encounter the same error message from the Notification area. There are several options you can check out to resolve the error. You have to check the status of several Windows Services and make sure that they are running. You also have to reset Winsock as well as run the System File Checker scan.

Option 1 – Check for certain Windows Services

• First, you need to tap the Win + R keys on your keyboard to open the Run dialog box.
• Next, type “services.msc” in the field and click OK or tap Enter to open the Windows Services Manager.
• After that, you will see a list of services and from there, look for the following Windows Services:
  • DHCP Client
  • System Event Notification Service
  • Windows Font Cache Service
• Now make sure that the Startup Type of each service is started and running.

Option 2 – Try resetting the Winsock drivers

• In the Start Search, type “command prompt” and right-click on Command Prompt from the search results, and then select the “Run as administrator” option.
• After opening Command Prompt, execute this command: netsh winsock reset

Note: If you are using IPv4, execute the “netsh int ipv4 reset” instead. On the other hand, if you are using IPv6, execute the “netsh int ipv6 reset”

• Now exit Command Prompt and see if the error is now fixed.

Option 3 – Try running System File Checker or SFC scan

You could also run System File Checker or SFC scan to fix the BSOD error. It is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Reboot your PC.

Error Code 0x80070003, 0x20007 - What is it?

Update Error 0x80070003, 0x20007 One of the most common errors encountered by users who updated to Windows 10 is the Error Code 0x80070003-0x20007. Normally, this error code is accompanied by the message saying “Windows could not search for new updates. An error occurred while checking for new updates or your computer” or “Error(s) found: Code 0x80070003 Windows update encountered an unknown error”.

This update-related error is often encountered any time while your device automatically installs updates once there’s an available system update or during manually installing updates for a specific app. Regardless if you are using a tablet, laptop, or PC, this update-related error could occur after upgrading your system to Windows 10.

Solution

Error Causes

There are several reasons why the update-related Error Code 0x80070003-0x20007 occurs. This includes the following:

• Windows Firewall-related problem
• A conflict in your device’s system might be present
• Not enough space in your RAM
• Not enough space in your installation disk
• Problems in your system memory

Further Information and Manual Repair

An effective way to address problems like the Error Code 0x80070003-0x20007 is by applying certain manual repair methods. However, ensure that you strictly follow instructions since one slight slip-up might result in critical issues. If you’re not knowledgeable enough, it would be best to consult help from a professional Windows technician or you can make use of an automated tool to solve any issues you’re encountering.

When you encounter the update-related Error Code 0x80070003-0x20007, you must take action immediately to address the problem to lessen the risk of losing all your data or damaging the Windows registry host.

In fixing Error Code 0xC1900101-0x30018, you can repeat the same steps used for 0xc000021a (Method One) then apply the following steps as well:

• Uninstall your antivirus prior to upgrading your system
• Ensure that you have a simple machine name with no periods, dashes, or hyphens.
• Restart several times then try again.
• Disable the General USB Devices in your machine like the Smart Card Reader.
• If you use a SCSI hard disk, ensure that you have available drivers you can use as your storage such as a thumb drive, and ensure as well that it is connected. Once you’re on the Windows 10 setup, click on Custom Advanced Option then use the Load Driver command in order to load the right driver for the SCSI drive. If this fails, try switching to an IDE-based hard disk.
• Once done, perform a clean boot then try restarting the device again.
• If you are upgrading your system using the .ISO file, disconnect your device from the Internet during setup. If your device is connected to the Internet by LAN or Wi-Fi, you need to disable both first then proceed to set up again.
• If you’re performing the update through Windows Update, disconnect from the Internet LAN or Wi-Fi once the download reaches 100% then proceed with the installation.
• If this still does not work, you can try using the .ISO file in upgrading.
• Switch to a local account if your machine is connected to a domain.
• Disconnect all external devices attached to your machine including gaming controllers, external hard disk, USB keys, and printers.

If the above steps still do not work, you can try performing a repair by doing the following steps:

1. Put the installation disc into the disc drive. Afterward, boot the computer.
2. Once the message: “Press any key to boot from CD or DVD…” appears, press any key.
3. Choose a language, currency, time, and a keyboard or another input method. Click Next.
4. Click on Repair your computer
5. Select the operating system that you wish to repair then click Next
6. Open the Command Prompt by clicking it in the System Recovery Options dialog box.
7. Type BOOTREC /FIXMBR then hit Enter
8. Type BOOTREC /FIXBOOT then hit Enter
9. Type Drive:bootBootsect.exe /NT69 All then hit Enter

Can’t seem to put up with the long and technical manual repair process? You can still fix this error by downloading and installing a powerful automated tool that will surely get the job done in a jiffy!

If you receive an error code of “0x80073afc” in Windows Defender after you boot your Windows 10 computer or when you try to manually run Windows Defender, then it could be that the Windows Defender files are corrupted. In such cases, this error could also occur if there is third-party security software that interferes with the smooth functioning of this Microsoft Security Client. If you are one of the users who are currently facing this issue, then here are some suggestions you can check out to resolve the Windows Defender error code 0x80073afc.

Option 1 – Try to check the status of all the Windows Defender-related services

• In the Cortana search box, type “services” and click on the Services icon to open the Services Manager. Alternatively, you can also tap the Win + R keys to launch the Run prompt and then type “msc” in the field and hit Enter to open the Services Manager
• After opening the Services Manager, look for the following services and make sure that their Startup type is set to their default values:
  • Windows Defender Advanced Threat Protection Service – Manual
  • Windows Defender Antivirus Network Inspection Service – Manual
  • Windows Defender Antivirus Service – Manual
  • Windows Defender Firewall Service – Automatic

• You can right-click on each one of the listed services and then select Start to start them.
• And if some of the services don’t have their default values, just double-click on the Services to change the Startup types and select the correct option from the drop-down menu of the Startup type under the Properties box.
• Next, set up the Startup type of these services to Automatic and then click on the Start button if the services are not running yet.
• Now click on the Apply and OK buttons to save the changes made and then see if it fixed the problem or not.

Option 2 – Try to re-register the concerned DLL files

You could also try to re-register some Dynamic Link Library or DLL files on your computer as this could also help in fixing the Windows Defender error.

• In the Start search, type “cmd” and from the search results that appear, right-click on Command Prompt and select the “Run as administrator” option from the context menu.
• After opening Command Prompt as admin, type the following commands one after the other:
  • regsvr32 dll
  • regsvr32 dll
  • regsvr32 dll
  • regsvr32 dll
• Once you’ve entered the commands given above, it will re-register the concerned DLL files in your system.
• Now restart your computer for the changes to take effect.

Option 3 – Try to use the Registry Editor

• Tap the Win + R keys to open the Run dialog box,
• Then type “Regedit” in the field and hit Enter to open the Registry Editor.
• Afterward, navigate to this registry path: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionImage File Execution Options
• Next, look for the DWORDs named “MSASCui.exe”, “MpCmdRun.exe”, “MpUXSrv.exe” and “msconfig.exe”.
• If you can’t find these DWORDs, refer to the next given option below.
• Restart your computer.

Option 4 – Check the Environmental Values

• Type “View advanced system settings” in the Windows search box and select the appropriate result.
• This will open a new mini window. From there, go to the Advanced tab and click on the “Environment Variables…” button located at the bottom part of the window.
• Next, look for the “%ProgramData%” variable name and make sure that its value is set to C:/ProgramData.
• Then click OK to save the changes made.

Option 5 – Run the System File Checker Scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Restart your computer.

Option 6 – Perform a System Restore

Performing a System Restore on your computer can also help you fix the Windows Defender error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

One of the most important components of a computer in the network. The network, with the help of network devices, makes it possible for all kinds of devices to exchange information. One of the files associated with the network driver is the netio.sys file. It is a system file used by third-party programs to interact with the devices on the network. If you encounter a Blue Screen of Death error that’s related to the netio.sys file then you’ve come to the right place as this post will guide you in fixing it. Here are some of the Blue Screen errors related to the netio.sys file:

• KMODE EXCEPTION NOT HANDLED
• PAGE FAULT IN A NONPAGED AREA
• IRQL NOT LESS EQUAL
• SYSTEM_SERVICE_EXCEPTION
• DRIVER IRQL NOT LESS OR EQUAL
• SYSTEM THREAD EXCEPTION NOT HANDLED

To fix the netio.sys Blue Screen errors on your Windows 10 computer, you can check out each one of the following suggestions.

Option 1 – Try to use the System File Checker

One of the built-in tools in Windows that you can use to fix Blue Screen errors is the System File Checker. This built-in command utility can help you restore corrupted or missing files as well as replace bad and corrupted system files. Chances are, the netio.sys file might be corrupted so to fix it, use System File Checker.

• First, right-click on the Start button and click on the “Command Prompt (Admin) option.
• Next, type in the sfc /scannow command and hit Enter to execute it.

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Finally, restart your computer.

Option 2 – Try checking the Memory for any errors

The first thing you can do to check the memory for errors is to run the CHKDSK utility. The CHKDSK utility repairs hard drive errors that might be causing the problem.

• You need to open “This PC” first.
• And then right-click on your operating system partition for Windows.
• Next, click on Properties and navigate to the Tools tab.
• After that, click on the Check button under the Error Checking section.
• A new mini window will appear and from there, click on Scan drive.
• Now let it scan your disk drive partition to check for errors and then restart your computer.

After running the CHKDSK utility, it’s now time to fix issues with your RAM by running the Memory Diagnostic tool. This tool in windows can help resolve the Blue Screen errors related to the netio.sys file by checking and automatically fixing any memory-based issues. To run it, refer to these steps:

• Tap the Win + R keys to open Run and type mdsched.exe and hit Enter to open the Windows Memory Diagnostic Tool.
• After that, it will give two options such as:
  • Restart now and check for problems (Recommended)
  • Check for problems the next time I start my computer
• Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Note: After you select your preferred option, your computer will restart and check for memory-based issues. If it finds any issues, it will automatically fix them and if there’s no issue found, then it’s most likely not a memory-based issue so you should try the other options given below.

Option 3 – Try to update or rollback or disable Network drivers

You might also want to update, roll back or disable your Network drivers to resolve the netio.sys Blue Screen errors.

• Tap the Win + R keys to launch the Run window and then type in the “mdsched.msc” command and hit Enter to open the Device Manager window.
• Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand it.
• Then right-click on each one of the Network drivers and depending on your preference, you can either select “Update driver”, “Disable device” or “Uninstall device”.
• After that, restart your PC and see if it helped in fixing the netio.sys Blue Screen error.

Option 4 – Perform System Restore

Performing System Restore can also help fix BSOD errors, including the ones related to the netio.sys file. To run System Restore, follow the steps below.

• First, tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

Option 5 – Run the Blue Screen Troubleshooter

Troubleshooting Blue Screen of Death errors wouldn’t be complete without the Blue Screen troubleshooter. As you know, it is a built-in tool in Windows 10 that helps users in fixing BSOD errors like Storport.sys. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

There are times when the WMI Repository gets corrupted which results in the Provider Load Failure. To resolve this issue, you need to repair or rebuild the WMI Repository in your Windows 10 computer. In this post, you will be guided on how exactly you can do that. In case you don’t know, the WMI which stands for Windows Management Instrumentation is a set of specifications from Microsoft to consolidate the management of devices and applications in a network. The WMI is a database that stores meta-information and definitions for WMI classes. Using only these, the conditions of the systems can be known. You can find the WMI Repository in %windir%System32WbemRepository. It provides end-users with the status of the local or remote computer system. Keep in mind that you must not use this on the Server 2012 Cluster machine. Although there are command-line tools that can fix or restore the Windows Management Instrumentation repository. However, Microsoft suggests that it’s better if you verify if there is corruption. Here are a list of errors as well as permission issues you might encounter:

• Unable to connect to root default or rootcimv2 namespaces. It fails with the error code “0x80041002” pointing to “WBEM_E_NOT_FOUND.”
• 0x80041010 WBEM_E_INVALID_CLASS
• When you open Computer Management and Right Click on Computer Management (Local) and select Properties, you get the following error: “ WMI: Not Found” or it hangs trying to connect
• Trying to use wbemtest , and it hangs
• Schemas/Objects missing
• Strange connection/operation errors (0x8007054e)

To verify if there is corruption, you can try running the following command in an elevated Command Prompt:

winmgmt /verifyrepository

 After you enter the command, if there is a response saying, “repository is not consistent”, then the repository has an issue. If not, then something else is causing the problem. Since you are certain that corruption exists in the WMI repository, then here are some suggestions you need to check out to repair or rebuild the WMI repository.

Option 1 – Try to reset WMI Repository

• Type “command prompt” in the Start Search and right-click on Command Prompt from the search results and then select “Run as administrator”.
• After opening Command Prompt with admin privileges, type and enter this command: winmmgmt /salvagerepository

The command you entered is used when the winmmgmt command performs a consistency check. So if an inconsistency is detected, it will rebuild the repository.

• Next, execute this command to see if the WMI repository now comes back as consistent: winmgmt /verifyrepository

This command will perform a consistency check on the WMI repository.

• If it states that the WMI repository is not consistent, then you need to type and enter this command: winmgmt /resetrepository

This command is used to reset the repository to its initial state when the operating system was first installed.

Option 2 – Try to force recover the WMI Repository

The WMI Repository comes with a built-in self-recovery process so when the WMI service restarts or detects any corruption, it will automatically trigger the self-recovery procedure. This can happen in two ways:

• AutoRestore: This will use the backup images if the Volume Shadow copy or VSS backup is turned on.
• AutoRecovery: The rebuilding process will generate fresh images of the WMI repository based on the registered MOFs. The MOFs are available in the registry located at HKLMSoftwareMicrosoftWBEMCIMOM: Autorecover MOFs

Note: Autorecover MOFs is a key so double click on it to check its value. On the other hand, if the self-recovery procedure does not work, you can try to use the force-recovery process instead. How? Refer to these steps:

• First, you need to check the reg key value is empty or not under this registry path: HKLMSoftwareMicrosoftWBEMCIMOMAutorecover MOFs
• If the reg key value is empty, you have to copy-paste the reg key value from another computer. Just make sure that it’s from the System which is equivalent to the computer in question.
• Next, type and enter this command: Winmgmt /resetrepository
• After you enter the command, if you get an error that says, “WMI repository reset failed. Error code:0x8007041B. Facility: Win32”, then you have to stop all the Dependency Services on the WMI service by running the following commands:
  • net stop winmgmt /y
  • Winmgmt /resetrepository

This should fix the problem.

A couple of Windows 10 users have reported an error on domain-connected systems when they tried accessing their computer systems remotely. This occurs when the network level authentication or NLA is enabled on the computer. If you are one of these users, you better keep reading as this post will guide you on how you can fix this error. To resolve this issue, there are several workarounds you can try. You can either disable this option directly via properties or you can also modify some registry entries or sub-keys and restart the system. When you encounter this problem, an error message pops up that states:

“The remote computer that you are trying to connect to requires network level authentication (NLA), but your windows domain controller cannot be contacted to perform NLA. If you are an administrator on the remote computer, you can disable NLA by using the options on the Remote tab of the System Properties dialog box.”

Or you could also see this error message instead:

“The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact your system administrator or technical support.”

Before you proceed in troubleshooting the problem using the options provided below, you need to create a backup for your data or system restore point as well as make a copy of any registry entries you are going to modify.

Option 1 – Disable Network Level Authentication via Properties

The NLA is a useful tool that provides your computer with extra security and helps network administrators in controlling who can log into the system with just a click of a single box. However, there are times when it can become a disadvantage and could prevent you from accessing your system remotely. Thus, you need to disable it using Properties.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” and tap Enter to open System Properties.
• Next, go to the remote tab and uncheck the checkbox for the “Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)” option.
• Now click the Apply button to save the changes made and exit System Properties and then try logging into the remote computer again and see if the problem is fixed or not.

Option 2 – Disable NLA via Registry Editor

Note that you can only use this option if the first one didn’t work for you. Take note that this option will require you to restart your PC completely which could mean some downtime if your computer is running a production server. So make sure to save all your work.

• Tap the Win + R keys to open the Run dialog box and then type in “Regedit” in the field and tap Enter to open the Registry Editor.
• From there, click on File > Connect Network Registry and input the details of the remote computer and then try to connect.
• Navigate to the path below after you’re connected:

HKLM >SYSTEM > CurrentControlSet > Control >Terminal Server > WinStations > RDP-Tcp

• After that, change the values given below to “0”
  • SecurityLayer
  • UserAuthentication
• The navigate to PowerShell and execute this command – restart-computer

Option 3 – Disable NLA via PowerShell

PowerShell allows you to tap into the remote computer and once you’ve targeted the machine, you can execute the commands given below to disable NLA.

• Tap the Win + S to open Search and then type in “PowerShell” in the field. Right-click on the related result and select the “Run as administrator” option.
• After opening PowerShell, execute the command below:

2. Once in the PowerShell, execute the following command:

$TargetMachine = “Target-Machine-Name” (Get-WmiObject -class “Win32_TSGeneralSetting” -Namespace rootcimv2terminalservices -ComputerName $TargetMachine -Filter “TerminalName=’RDP-tcp'”).SetUserAuthenticationRequired(0) Note: In the command given, the “Target-Machine-Name” is the name of the machine you are targeting.

Option 4 – Use the Group Policy Editor to disable NLA

Another option you can use to disable NLA is via the Group Policy Editor. This is ideal for you if you are blanket disabling. Just take note that the Group Policy Editor is a powerful tool and that if you make some mistakes by changing values you have no clue about, you can render your computer useless so make sure that you create a backup for all the values before you proceed.

• Tap the Win + R keys to open the Run dialog box.
• Then type in “gpedit.msc” and tap Enter to open the Group Policy Editor.
• From there, go to this path – Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security
• After that, search for “Require user authentication for remote connections by using Network Level Authentication” and set it to disabled.
• Now check if the error is fixed or not.

Error Code 30088-26 is shown when the user tries to install the MS Office suite to their PC. It is mostly due to several reasons including corrupted Office installation, the remnant of old office installation, or even Windows updates. We will cover all reasons along with provided solutions to each one. Follow the guide below to address each scenario with the fix for it.

Corrupted Office installation

In order to fix this issue, you will need to repair the installation itself.

• Press ⊞ WINDOWS + R to open the run dialog
• Inside run dialog type in Control Panel
• In the control panel double click on Programs and features
• In the list of installed application find MS Office and click on it to select it
• On top, just above the application list click on the change
• Office dialog will be opened with multiple choices
• Click and select Online repair and then click on Repair
• Make sure that you have a stable internet connection and leave the process to be finished

Remnants of old office installation

Manually cleaning remnants of old office installation is not an easy task and it can be different from system to system depending on the previous Office version. Luckily Microsoft has a dedicated office cleaning tool made for purpose of removing old tails and remnants of old office installations.

• Download tool here
• After the tool has been successfully downloaded, double-click on the .diagcab file to open it
• Click on Advanced and make sure that the box associated with Apply repair automatically is checked.
• Click the Next button to proceed
• Wait until the initial detection phase is complete, then click on Installing at the first prompt
• Select the program that you’re encountering issues with (most likely Microsoft Office) and click Next once again
• At the next screen, click on Yes, try to uninstall
• Wait until the operation is complete, then restart your computer and re-install the Microsoft Office suite

Windows Updates

After digging and trying out various solutions for this issue we came to the conclusion that this error can occur if Windows is not fully updated, and by fully updated we mean fully, not just critical updates, but all available ones. Check-in your setting to see if there are some uninstalled or pending updates waiting to be installed and if that is the case install them all. After completely updating your Operating system error should vanish and you should be able to install Microsoft office without issues.

If you suddenly encountered the PDC WATCHDOG TIMEOUT BSOD Blue Screen stop error with a bug check value of 0x0000014F, then it’s probably due to a system component that has failed to respond with the allocated period which prevents the system from exiting connected standby. This kind of Blue Screen error could be caused by both hardware and software components. To fix this Stop error, here are some possible fixes you can try that might help but before you proceed, make sure that you create a System Restore point first and boot your computer into Safe Mode with Networking.

Option 1 – Try to rollback, update or disable drivers

The next thing you can do to fix the PDC_WATCHDOG_TIMEOUT Stop error is to roll back, or update, or disable device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• After opening the Device Manager, look for the device driver named “IDE ATA/ATAPI controllers” and expand it.
• Then look for the SATA AHCI Controller entry and right-click on it. If you haven’t updated this driver in a while, select the “Update Driver” option. On the other hand, if you’ve just updated this driver, then select the Uninstall Device option.
• Next, follow the screen option to update or uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically if you have chosen to uninstall them.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 2 – Try to disconnect or disable newly installed hardware

In this option, you will have to disable or remove the hardware you’ve just installed recently since external devices could be the one that’s causing the Blue Screen of Death error to appear. To do that, just disconnect any external device that’s connected to your computer physically and then check if it fixes the PDC_WATCHDOG_TIMEOUT Blue Screen error.

Option 3 – Try running the Memory Diagnostic Tool

The Memory Diagnostic tool in windows can help resolve the PDC_WATCHDOG_TIMEOUT Blue Screen error by checking and automatically fixing any memory-based issues. To run it, refer to these steps:

• Tap the Win + R keys to open Run and type mdsched.exe and hit Enter to open the Windows Memory Diagnostic Tool.
• After that, it will give two options such as:
  • Restart now and check for problems (Recommended)
  • Check for problems the next time I start my computer
• Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Option 4 – Try to update the BIOS

Updating the BIOS can help you fix the PDC_WATCHDOG_TIMEOUT BSOD error but as you know, BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “msinfo32” in the field and press Enter to open System Information.
• From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
• After that, you should see the developer and version of the BIOS installed on your PC.
• Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
• If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
• Now double click on the downloaded file and install the new BIOS version on your computer.
• Now restart your computer to apply the changes made.

Option 5 – Try running the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like PDC_WATCHDOG_TIMEOUT. It can be found in the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Windows 11 will bring some old applications in new looks and some will get additional features as well. One of the old apps that will get new stuff is a calculator. The calculator was always a way to go application for quick calculations but Microsoft aims to expand on that and make the calculator a little more useful. The first thing that you will notice is the calculator look, the calculator has now an application theme setting that allows you to change the look of the application. It comes in standard and professional mode as usual but this time calculator will come with features that will enable it to handle some programming and engineering tasks. The new calculator features a full graphing mode that lets you visually analyze a graph to identify key features. It also packs a deep converter that can switch between more than 100 units and currencies.

Other Windows 11 apps

A new snipping tool will be delivered with this latest update as well packed with new functionality. We have covered new features of the snipping tool in another article, if you are interested you can find the article here: https://errortools.com/windows/new-snipping-tool-redesigned-in-windows-11/ Mail and Calendar apps will also get a redesign, sadly all redesign that they will include will be of visual nature to fit in the overall Windows 11 theme, functionality will remain the same.

It really sucks when you can’t fully enjoy the newest version of your favorite OS.

Windows 11 is still relatively fresh and consequently has some annoying little bugs that really ruin our experience. The good news is that you’re not alone and most of them are easy to fix.

Here are 5 commonly reported Windows 11 issues and what you can do to get rid of them.

1. Windows 11 audio problems

One of the absolute most irritating things in the world is struggling with the sound on your computer. Windows 11 users have reported facing the issue of low or no sound. If you’re currently experiencing the same frustration, you can be relieved. Chances are fixing it will only take a few minutes.

The first thing to check would be whether you accidentally muted your device by pressing the mute button on your keyboard. Yes, we know it sounds a lot like the old “have you tried turning it off and on again?” But it’s important to leave no stone unturned, and the most obvious things are usually the ones we easily overlook.

Moreover, if you have several audio output sources, check whether the right one is selected. You can do this via the Action Center or through Settings. If you want to use the same source every time, we also recommend you set it as the default one.

It’s also important to have a good, up-to-date audio driver. More often than not, this will be the true cause of your audio struggles. Make sure to update your driver, and if that doesn’t work out, you can always un- and reinstall it or install a different one. 

Lastly, if all attempts remain unsuccessful, run the audio troubleshooter to figure out what’s actually going wrong.

2. Unable to find files

Such a powerful new operating system, yet it can’t seem to do the simplest thing imaginable? The File Explorer not responding on Windows 11 is one of the most frustrating and most common problems with Microsoft’s newest iteration of its awesome OS.

However, 9/10 times it can be fixed by simply restarting your PC. You could also try killing the Windows Explorer process in the Task Manager and then rerunning it.

If these don’t help, check whether there are any pending Windows 11 updates. A single missing update can compromise your PC’s functionality, so always make sure to install them all on time. 

Should none of that work, then there are other ways to solve the File Explorer problem. However, then the issue is probably a bit deeper and it’s no longer in the ‘easy fix’ territory.

3. Start menu not working

Just like the File Explorer, the Start menu is a fundamental element of your OS. So, it’s only natural that its malfunction grinds your gears. It may be more customizable than on previous Windows versions, but it doesn’t always work smoothly. 

If you’re facing the so-called Start menu critical error, there are a few things this could be caused by. Usually it means you turned off your system while an important update was still being installed, there is a corrupt file on your PC, or Windows forcefully stopped a program. 

Whatever the reason, the solution should be pretty simple. Try the basic steps: restarting your File Explorer (like we explained above) and signing out and back into your account. If that doesn’t do anything, you may want to try uninstalling third-party start menu apps (if you have any), since they can interfere with your default programs’ functionality.

Now, those are the easy fixes. If you get nowhere with them, you might need to identify the root cause and search for more complex solutions than that.

4. Snipping tool not working

Our beloved screenshot tool was introduced with Windows 10 and Microsoft decided to keep it. However, you were probably just as disappointed as us when you tried to run it and failed. 

Normally, this can be fixed by installing the latest Out-of-band (OOB) update, or even pending updates in general. Even if your system appears to be up-to-date, run the checker just in case.

Another cool thing Windows 11 lets you do is ‘Repair’ and ‘Reset’, which is the easiest way to troubleshoot your Snipping tool. If this fails, you can also try the good old un- and reinstall method. Simply uninstall the tool through the Control Panel and reinstall it from the Microsoft Store.

Furthermore, in the case of an upgrade from Windows 10 to 11, it may be that the old Snipping tool version is interfering with the launch of the new one. If you don’t care that much about the additional options available with the enhanced screenshot tool, you can use the old version instead.

Simply go to your C Drive, find the Windows.old folder, search for the tool and open it from there. Make sure to pin it to your taskbar as well, if you know you’re going to use it often.

5. Can’t install the latest update

The latest Windows 11 version, 22H2, has brought tons of enhancements to our dearest operating system. Unfortunately, a lot of users still haven’t had the opportunity to experience it. A mere update of your OS version should be the one thing that goes smoothly, but sometimes that’s not the case.

Failure to install 22H2 can be caused by a few things. Most commonly, the issue is caused by lack of storage space or corrupted files, but there could be other culprits.

There are a couple of things you could try. For example, it’s crucial that your drivers be up-to-date and some important services be enabled. These are: Windows Modules Installer, Background Intelligent Transfer Service, Cryptographic Service, Windows Update services.

To enable them, search ‘Services’, find the service you need and right-click on it. Open ‘Properties’ and select the startup type ‘Automatic’.

It may also be necessary to unplug all peripherals that aren’t crucial and disable third-party antivirus tools until after the update is finished. 

Ultimately, you can run the Windows Update troubleshooter to detect and fix other possible issues.

Summary

Tiny bugs like these are nothing out of the ordinary. That said, we still all hate when they happen.

Hopefully some of our solutions have helped you to a smoother Windows 11 experience. But if you’re still struggling, feel free to reach out to us. We’d be happy to help!