Fix BAD_SYSTEM_CONFIG_INFO error in Windows

As we are on the last day of 2021, our team here at errortools.com would like to express their great gratitude to you all for being with us all this time and would also want to wish you error-free 2022!!! Thank you for being part of this community, we wish you all the best in the upcoming 2022 and hope that we will see you again From all members of errotools, HAPPY NEW YEAR!!!

Error Code 0xC004C4AE - What is it?

Activation errors in Windows 10 can interfere with your ability to fully use the system. When Error Code 0xC004C4AE appears on your computer, you may see a message that shows that the validation process has been stalled due to binaries that appear to have been tampered with.  

While the text of this message may sound intimidating to people who are not familiar with the inner workings of the Windows 10 system, the basic meaning of the error message is that something has been introduced to the system that is not natively supported in Windows 10. During the Activation process, Windows checks to ensure that all of the Windows elements that are currently on the computer are valid and authentic to the Windows system. Usually, this particular error code refers to a language package that has been downloaded into the system using an outside application, which the Windows 10 operating system does not support. 

Common symptoms include: 

• An error message when the activation is attempted 
• Inability to complete the Windows 10 Activation process 
• Inability to fully use apps in Windows 10 until the issue is resolved 

This particular error can easily be resolved with a few simple steps. However, if you are not confident in your ability to use the methods below or they do not fully remove the issue on your computer, you may want to seek the assistance of a qualified repair technician who is well versed in the Windows 10 Activation process.

Solution

Error Causes

The most basic cause of Error Code 0xC004C4AE is that an unsupported language package has been enabled in the computer. This most often occurs when third-party applications have been used to introduce additional display languages to your system. While third-party applications that provide language packs are acceptable in some versions of the Windows operating system, the Windows 10 Activation process will not be able to complete if the system detects that one of these unofficial language packs exists on your machine.

Further Information and Manual Repair

There are several methods that may be helpful in resolving the basic issue in the display languages that causes Error Code 0xC004C4AE to appear: 

Method 1: Restore Your System to an Earlier Point to Revert Changes 

Use a backup copy to restore your computer to an earlier date, in effect undoing the changes that caused the error. When your system has been restored, you will be able to go through any language packs that are not native to the Windows operating system and remove them before re-attempting the installation and activation of the Windows 10 system. 

This method is most useful if you keep a regular backup of your system and files. If you do not regularly back up the information on your computer, attempt one of the other methods instead. If you are unsure of how to use a backup to revert your changes or are not comfortable completing this step on your own, contact a certified Windows technician to assist you in the process. 

Method 2:  Revert to an Earlier System to Remove the Language Pack 

If you are unable to restore your system using a backup, the other option to resolve Error Code 0xC004C4AE is to halt your installation of Windows 10 and go back to Windows 7 or Windows 8.1, from which you will be able to remove the language pack in question. Once the offending language pack has been completely removed from your computer, the Windows 10 Activation process should be able to proceed normally. 

Several versions of windows don’t support language packages, so the best way to prevent this error from occurring is to avoid using any kind of third-party tool to install additional languages onto your Windows system. Activities Language You may be able to use third-party tools to instead complete alternative language actions without installing these languages as language packs. 

If the above solutions do not help you to resolve Error Code 0xC004C4AE on your machine, get in touch with a qualified Windows repair technician, who may be able to perform the operations needed to remove the problematic language pack from your computer and allow the Windows 10 Activation process to continue to completion. 

If you encounter the NMI_HARDWARE_FAILURE Blue Screen error while using your Windows 10 computer, then read on as this post will guide you in resolving this kind of Blue Screen of Death error. NMI HARDWARE FAILURE or “Non-Maskable Interrupt” Blue Screen error occurs when there is some hardware malfunction in your computer. When you encounter this Blue Screen error, you may get a stop code of 0x00000080 which can randomly occur while you use your computer. However, a lot of users reported encountering this error while they were trying to update or install their Graphics Card drivers. The stop code that you may get for this BSOD error is 0x00000080. The error can occur randomly during your usage of the computer – but a large number of users have reported this error while they are updating or installing their Graphics Card drivers. In this post, we will be covering all the possible fixes for this error. NMI_HARDWARE_FAILURE error on Windows The NMI_HARDWARE_FAILURE bug check has a value of 0x00000080. This bug check indicates that a hardware malfunction has occurred. There are various hardware malfunctions that can cause this kind of Blue Screen error. However, pinpointing the exact cause is quite difficult. Worry no more for the following fixes provided below can help you resolve the NMI_HARDWARE_FAILURE Blue Screen error no matter what the cause of the problem is.

Option 1 – Try removing hardware or drivers that you’ve installed recently

If you have recently installed some hardware or drivers, you might want to disable or remove them since external devices are proven to be one of the factors that trigger Blue Screen errors like NMI_HARDWARE_FAILURE. All you have to do is physically disconnect any external devices that are connected to your computer and then check if it fixes the BSOD error or not.

Option 2 – Try to rollback, update, or disable the Graphics card drivers

Since the NMI_HARDWARE_FAILURE Blue Screen error has something to do with Graphics card drivers, you can either roll back, update or disable them depending on your preference in order to resolve the error.

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. From there, look for the Display Adapters and click on them.
• After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
• Now restart your computer.
• After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

Note: You also have the option to go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.

Option 3 – Make sure that all memory modules have the same type

This third option is quite technical and tricky. If you often use multiple physical RAMS on your Windows 10 computer, then you have to check first if they are of the same frequency. After that, the first thing you should verify is if the chip is properly compatible or not. And if the sockets are attached using some kind of adapter or non-recommended device, it could cause some issues while giving a performance hit to your computer.  If you were able to find such a setup, you have to undo it or install the proper and recommended as well as compatible hardware.

Option 4 – Try to run the Blue Screen Troubleshooter

As you know, the Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like the NMI_HARDWARE_FAILURE error. 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.

Error 0x8004210A - What is it?

0x8004210A is a typical POP3 email error message. This error may sometimes occur when you try to check your Post Office Protocol 3 (POP3) email account. 0x8004210A error code hampers your ability to both send and receive e-mails on your Outlook account. Error 0x8004210A is displayed in any one of the following formats on your PC:

The operation timed out waiting for a response from the receiving (POP) server 0x8004210a Task 'SMTP server name - Sending and Receiving reported error' (0x8004210A): 'The operation timed out waiting for a response from the receiving (POP) server. If you continue to receive this message, contact your server administrator or Internet service provider (ISP).'

Error Causes

Error 0x8004210A occurs due to several reasons. However, some of the most common reasons include:

• Wrong port number for the POP incoming server
• Your connection to the mail server is too slow
• Incoming and outgoing emails are being scanned and stopped by an antivirus installed on your system
• The Outlook send and receive job is being blocked by Firewall
• You are sending and receiving large series of emails or large email attachments
• Registry issues

No matter what the cause of this error is, to resume email communication via Outlook and to ensure your work productivity is not affected, it is recommended that you resolve this 0x8004210A error code on your PC immediately.

Further Information and Manual Repair

To fix error 0x8004210A, here are some of the most efficient and easy manual methods that you can try:

Method 1

If the cause of the error is related to the internet connection then here’s what you need to do. Try freeing up your internet connection by closing any other online activities in progress or downloads being carried on your system.

Method 2

Try to increase your server time-out periods. To do this, go to the Outlook File menu and choose account settings. Now double click on your email account and more settings. Now click advanced and increase your server timeout period to resolve.

Method 3

If you are trying to send or receive large and heavy emails on your Outlook account, the error 0x8004210A may pop up. This happens because when transferring heavy files the email account automatically locks until the task is complete, however, if it takes more time the next Send and Receive job starts while the first one is still not complete. In such an event, the email server then times out and shows you the error. Therefore to resolve, you will have to show patience. Simply wait for the large email to be sent or received before you start sending another email.

Method 4

If the antivirus installed on your system is the reason for the error pop up, then disable it for a while until the operation is complete. Then enable it once the task is performed successfully.

Method 5

Similarly, if the Firewall installed on your system is preventing Outlook from reaching your mail server, then simply disable the Firewall to resolve.

Originally Microsoft has imagined its widgets menu as Microsoft-only widgets but it seems that they have changed their mind. Due to the latest leak, it seems that Microsoft will open the widgets menu to 3^rd party developers as well but at launch, it will be only official widgets. It was hinted that later widgets menu will be open to developers who want to bring their own stuff into it. Distribution, date, and technology that will need to be used in order to create your widget have not been discussed nor leaked at a given time but in some way, I am very glad that at least some customization will be in Windows 11. It is funny and amusing how some things that were in Windows Vista are getting back like glass design, round corners, and widgets. Let’s just hope Windows 11 will be a better Windows than Vista was.

Booting the Windows computer system includes loading it from the various boot devices such as drivers, network as well as USB drives when the computer is turned on. The instant the startup sequence is done loading the operating system the system hardware will be ready to perform some complex operations – in this process, the Boot Log in Windows 10 is a record that maintains the list of success or failure of many pieces of Windows 10 system during the booting process. In other words, the Boot Log is the one that keeps a record of all that has happened while loading from the computer storage system to the memory during the boot process. It is available for several devices like network, hardware devices, and the operating system which assist in detecting issues during the boot process and other issues with regards to troubleshooting. Through Boot Log, you’ll know which drivers were unloaded and loaded from the start of the system during the boot process. You have the option to either disable or enable this feature on your Windows 10 PC. Named as “ntbtlog.txt”, the log file lists all the successfully loaded processes and the unsuccessful ones during the boot process. It is saved to the drive C:Windowsntbtlog.txt. As mentioned, you can enable or disable this feature in two ways – the first one is by using the System Configuration or MSConfig while the second one is using the Command Prompt. In this post, we’ll show you how you can enable or disable Boot Log in Windows 10 either way.

Option 1 – Enable or Disable Boot Log using System Configuration

Enable Boot Log:

• Tap the Win + R keys to open the Run dialog box.
• Then type in “msconfig” and click OK to open System Configuration.
• After that, go to the boot tab and check the checkbox labeled “Boot Log” under the Boot options so that you can enable the Boot Log feature.
• Then click on OK to save the changes made.
• Next, click on the Restart button in the prompt window to get started with the Boot Log process.
• After restarting your PC, go to C:Windowsntbtlog.txt to open the boot log.

Note: As pointed out earlier, the log file contains a list of all the successfully loaded drivers and also the list of drivers that failed to load during the boot process and every time you restart the system, the boot log file will keep on updating and will eventually increase the list of entries. For you to locate the drivers and make your troubleshooting a lot easier, I advised disabling the boot log after troubleshooting. To disable the boot log using System Configuration, refer to the steps below. Disable Boot Log:

• Tap the Win + R keys to open the Run dialog box.
• Then type in “msconfig” and click OK to open System Configuration.
• After that, go to the boot tab and unmark or uncheck the checkbox labeled “Boot Log” under the Boot options so that you can disable the Boot Log feature.
• Then click on OK to save the changes made.

Option 2 – Enable or Disable Boot Log using Command Prompt

Enable Boot Log:

• Go to the Start Menu and then type in “command prompt” in the search bar.
• After that, right-click on the Command Prompt option and select the “Run as administrator” option.
• After opening Command Prompt, type in “bcdedit” and tap Enter.

Note: You have to find the Identifier of the current operating system first to enable the Boot log. You can find it under the Windows Boot Loader section in the “Description” field and in this case, it’s Windows 10. You can also find the operating system identifier under the Windows Boot Loader section next to the field name identifier.

• To check if the boot log entry is disabled or enabled, go check the “Bootlog” field under the Windows Boot Loader. And if it turns out that the “bootlog” entry is enabled, the entry will be “Yes”. Otherwise, the entry will be “No”.
• Next, type in the following command with the operating system identifier to enable the boot log.

bcdedit /set {identifier} bootlog Yes

Note: In the command given above, make sure that you replace the given system identifier with your computer’s system identifier. For instance: In this example, the identifier was replaced with the actual operating system identifier as current.

bcdedit /set {current} bootlog Yes

• Afterward, restart the system to start the Boot log process.
• After the restart, go to C:Windowsntbtlog.txt to open the boot log.

Note: Every time you restart your computer, the boot log file will keep on updating which will increase the size of the log eventually. So if you want seamless and easier troubleshooting, it is advised to disable the Boot log after you troubleshoot. To disable it using the Command Prompt, here’s what you have to do. Disable Boot Log:

• Go to the Start Menu and then type in “command prompt” in the search bar.
• After that, right-click on the Command Prompt option and select the “Run as administrator” option.
• Once the Command Prompt is opened, type in the following command and then tap Enter to disable the boot log feature.

bcdedit/ set {identifier} bootlog No

Note: In the command given above, you need to replace the given system identifier with your computer’s system identifier. For instance: In this example, the {identifier} was replaced with the actual operating system identifier as {current}.

bcdedit /set {current} bootlog No

• Now close the Command Prompt.

This post will help you fix the ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen issue with an error code 0x000000BE. If you encounter this kind of BSOD error when you try to boot into your Windows 10 computer, note that there are various possible causes for this error. It could be caused by an error with a device driver, hardware issues, or some error in the BIOS of your computer. The ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen error with a bug check of 0x000000BE appears when a driver tries to write a read-only memory segment. You’ll be able to see the name of the driver in the Blue Screen error if the driver that’s causing the error can be identified. You can also see it in memory at the location (PUNICODE_STRING) KiBugCheckDriver. In most cases, this kind of error is usually caused by various files such as iusb3hub.sys, ntkrnlpa exe or vhdmp.sys, ntoskrnl.exe, ntfs.sys, dxgkrnl.sys, tcpip.sys, atikmdag.sys, and win32k.sys. There are several possible fixes you can try to fix this issue but the main issue lies within booting into Windows since the error occurs as soon as you boot into your Windows 10 computer. Refer to each one of the options provided below to resolve the ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen error.

Option 1 – Try to rollback, update or disable drivers

The first thing you can do to fix the ATTEMPTED_WRITE_TO_READONLY_MEMORY 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.
• Then locate the device drivers and right-click on them to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

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 running the Memory Diagnostic Tool

The Memory Diagnostic tool in windows can help resolve the ATTEMPTED_WRITE_TO_READONLY_MEMORY 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 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 the BIOS

Updating the BIOS can help you fix the ATTEMPTED_WRITE_TO_READONLY_MEMORY 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 4 – Try disabling BIOS Memory Options

Disabling the BIOS Memory options such as Caching and Shadowing can help you in fixing the ATTEMPTED_WRITE_TO_READONLY_MEMORY Stop error. All you have to do is enter the BIOS first and then use the Arrow and Enter keys to select your choices. And if you can’t seem to find it, look for specific instructions from your OEM or you could also look out for instructions from the manufacturer of your motherboard.

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 ATTEMPTED_WRITE_TO_READONLY_MEMORY. 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.

Connapi.dll Error Code - What is it?

Connapi.dll is a type of dynamic link library file. This file contains small programs like any other DLL file and is called to load certain programs on your PC. The Connapi.dll error message occurs either when using or installing programs. This error message is displayed in either of the following messages:

“Connapi.dll Not Found" "This application failed to start because connapi.dll was not found. Re-installing the application may fix this problem." "The file connapi.dll is missing." "Cannot start [APPLICATION]. A required component is missing: connapi.dll. Please install [APPLICATION] again." "Cannot find [PATH]connapi.dll"

Solution

Error Causes

Connapi.dll error may occur due to numerous reasons on your PC. The most common causes include:

• Missing Connapi.dll file
• Corruption of the Connapi.dll file
• Driver Issues
• Viral Infection
• Registry Issues such as bad and invalid entries

This error may hamper your ability to access your desired programs causing you a great deal of inconvenience. And if the underlying cause of the error is related to the registry, then your computer can be at serious risks like system failure and crash.

Further Information and Manual Repair

To resolve Connapi.dll error code on your PC, here is a list of solutions. These are easy, very simple to perform, deliver the best results, and more importantly require no technical expertise.

Solution 1: Check your Recycle Bin - You May Have Deleted the File Accidentally

As dll files are shared files, it is possible that you accidentally deleted the Connapi.dll file while uninstalling a program from your system. In such a situation, go to the recycle bin and look for the file. If you find the missing Connapi.dll file, simply restore it and then try running your desired program again. If the program runs, then the error is resolved. However, if it still persists, then try other solutions given below.

Solution 2: Update the Drivers

Try updating drivers for hardware devices on the system. To do this, go to the start menu and then Control Panel. Double click on Add or Remove programs icon. Now select incompatible drivers and remove them. After that, restart your PC to activate changes. Now go to the manufacturers’ website to download new drivers and install them on your PC.

Solution3: Scan for Viruses

Another solution is to scan for viruses and malware. Sometimes these can also damage and corrupt dll files on your system. To perform a scan, simply download a powerful antivirus program and run it.

Solution 4: Clean and Restore the Registry

If the error code is still there, then this means the problem is triggered by the registry issues. To resolve it you must clean the registry and remove all the unnecessary and obsolete files like junk files, internet history, temporary files, and cookies. The best way to clean these files instantly is to install Restoro. This is an advanced, cutting-edge, and multi-functional PC Fixer. It has a user-friendly interface and is integrated with powerful utilities like a registry cleaner, anti-virus, and a system optimizer. It is compatible with all Windows versions. The registry cleaning feature scans your entire PC in seconds and detects all the registry issues. It removes all the bad registry entries and unnecessary files. Simultaneously, it also fixes the system files and dll files like Connapi.dll. The anti-virus utility removes all types of malicious software on your system while the system optimizer utility ensures your system performs at its optimum speed. To resolve Connapi.dll error, click here to download Restoro.

As you know, the Windows 10 operating system has support for a dedicated high-end graphics processor that brings in capabilities inside to support Graphics Cards from NVIDIA or AMD. This helps the operating system to function in a much better way by segregating the graphics-intensive operations from the CPU to a dedicated processor. However, there are times when it also experiences some issues that lead to some errors like the “Failed to create a graphics device” error. It is possible that your computer has more than one screen or graphics card which is why you’re getting this error. To fix it, you need to try reinstalling DirectX or reinstall the Graphics Card driver. You could also try to manually check the hardware or power cycle of your computer. To start troubleshooting the “Failed to create a graphics device” error, follow the given suggestions below.

Option 1 – Try running the DirectX Diagnostic Tool

Since the error has something to do with the DirectX Graphics APIs, you can run the DirectX Diagnostic tool to resolve the problem.

Option 2 – Try updating or re-installing DirectX

If the DirectX Diagnostic tool didn’t work, you can try to update or reinstall DirectX instead. This can help in fixing the problem because when you reinstall or update DirectX, it will replace the incompatible or corrupted components of DirectX from your computer.

Option 3 – Update or reinstall the Graphics card drivers

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in MSC into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. From there, look for the Display Adapters and click on them.
• After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
• Now restart your computer.
• After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

Note: You also have the option to go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.

Option 4 – Try to physically check the hardware of your computer

You might also want to check the physical status of the hardware in your computer. You can clean the dust off the hardware components like the Graphics Card of the computer. In doing so, you have to use a small blower or you could also use a soft cloth and run the components gently. Make sure that you don’t damage any parts with moisture or cause harm to any circuits while you carry out this task.

Option 5 – Try to power cycle your computer

You could also try to power cycle your computer to fix the error. To do that, you have to turn off your computer in a way that the power is completely cut off and all the fresh configurations of files are loaded when your computer is booted up. The first thing you have to do is to shut down your computer and if you are using a laptop with a removable battery, you must remove the battery for a couple of minutes before you plug it back in and boot your laptop. On the other hand, if you are using a desktop computer, press and hold the power button until the CPU goes off and take out the power cable for a minute or so and then plug it back in. Boot your computer and see if the error has been resolved.

The third time is charm saying goes but not when we are talking about Microsoft. Print spooler is again in focus, in a bad way. This is the third print spooler vulnerability to emerge in just five weeks. While a critical flaw was originally identified and patched in June, a similar flaw came to light shortly after and was subsequently patched (with mixed success). Microsoft is once again advising its customers to disable Windows print spooler after a new vulnerability that allows hackers to execute malicious code on machines has emerged. While a patch fixing the flaw will be released in due course, the most effective workaround currently on the table is to stop and disable the print spooler service entirely.

"An elevation of privilege vulnerability exists when the Windows Print Spooler service improperly performs privileged file operations. An attacker who successfully exploited this vulnerability could run arbitrary code with SYSTEM privileges. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights."

Stop this service right away or you are risking a potential attack.

1. Press ⊞ WINDOWS + X to open the hidden menu
2. Click on Power Shell (admin)
3. In Power Shell type in the following command to check if spool service is running: Get-Service -Name Spooler followed by ENTER
4. If spooler service is running type in the next command to stop it: Stop-Service -Name Spooler –Force and press ENTER
5. Then follow with this command to disable it at startup: Set-Service -Name Spooler -StartupType Disabled followed with ENTER

That’s it, we hope a patch will come soon for all the people that are using network printing and indeed need this service running in order to do work.