Disable Windows print spooler in PowerShell

The docking station was promised upon release of the Deck but it was pushed back and now the official statement is that it is delayed again.

Valve said in an announcement on June 1:

“Due to parts shortages and COVID closures at our manufacturing facilities, the official Steam Deck Docking Station is delayed. We’re working on improving the situation and will share more info when we have it.”

Valve

The docking station was presented at the same time as Deck itself and the whole idea was to make Steam Deck work like a laptop docking station. It has ports for USB devices, displays, and network connections that became functional the moment Deck is placed on it. Docking supports a mouse, keyboard, and external display making it an almost full PC station if needed.

Valve confirmed that its official dock station will not improve performance so while you wait for its release you can use another docking station with a USB Type-C connector.

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.

If you are using UEFI and you encountered an error message that says, “Selected boot image did not authenticate”, then read on as this post will show you what to do it fix it. This kind of error indicates that UEFI is having an issue in figuring out if the boot image has tampered with. UEFI offers Secure Boot and if the boot image seems to be invalid, you won’t be allowed to boot into your computer. Aside from that, it could be that you may be using endpoint encryption and the software can’t validate the certificate. To fix the “Selected boot image did not authenticate” error in UEFI, you need to first check if the error has given any reference to any software that you might have for encryption. If it has, then you need to disable the Encryption tool to resolve the problem. In addition, you could also try to disable Secure Boot or perform Startup Repair in case the disabling Encryption tool didn’t work. For more details, make sure to use each one of the options provided below as a reference.

Option 1 – Try to disable the Encryption tool

The first thing you can do to fix the “Selected boot image did not authenticate” error is to disable the Encryption tool. Many users reported that some encryption tools like the ESET Endpoint Encryption won’t let them boot into the computer if the system manufacturer does not include the correct certifications as a part of the UEFI BIOS. And since there is no way to bypass this, you have to disable Secure Boot in order for you to boot into your computer.

Option 2 – Disable the Secure Boot in the BIOS

Disabling the Secure Boot in the BIOS settings is definitely recommended to resolve the error. To disable Secure Boot, here’s what you have to do:

• First, boot your computer into Windows 10.
• Next, go to Settings > Windows Update. From there, check if there is anything that you have to download and install if you see any available updates. Usually, OEMs send and update the list of trusted hardware, drivers, and operating systems for your computer.
• After that, go to the BIOS of your computer.
• Then go to Settings > Update & Security > Advanced Startup options. If you click on Restart Now, it will restart your computer and give you all the advanced options.
• Next, select Troubleshoot > Advanced Options. As you can see, this screen offers you further options including System restore, Startup repair, Go back to the previous version, Command Prompt, System Image Recovery, and UEFI Firmware Settings.
• Select the UEFI Firmware Settings which will take you to the BIOS.
• From there, go to the Security > Boot > Authentication tab where you should see Secure Boot. Note that every OEM has its own way of implementing the options so it varies.
• Next, set Secure Boot to Disabled and set Legacy Support to On or Enabled.
• Save the changes made and exit. Afterward, your computer will reboot.

Option 3 – Try to run the Automatic Repair Utility

If disabling Secure Boot did not fix the problem, you might also want to run the Automatic Repair utility in fixing the error. To do so, follow the steps below.

• You can start by booting into the Advanced Recovery Mode.
• After that, select Troubleshoot > Startup Repair.
• Next, follow the on-screen instructions that appear on the screen and finish the Automatic Repair process.
• Now check if the block is gone once the reboot is completed.

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.

If you encounter an error saying, “Boot Device Not Found” when you turn on your Windows 10 computer, then you’ve come to the right place as this post will guide you on how you can fix this problem. Apart from the error message, you will also see a message that states, “Please install an operating system on your hard disk, Hard Disk<xxx>”. You will then be asked to tap the F2 key to initiate the System Diagnostics. If you install the Windows operating system, it becomes the boot device, and when your computer boots, the UEFI or the BIOS looks for the operating installed on your drive and continues the process. So when you encounter the “Boot Device Not Found” error, this means that the UEFI or the BIOS wasn’t able to locate the drive where it can boot. There are several suggestions you can check out to resolve this error. You can try checking the connection with your boot drive or change the boot order. You can also fix the Boot Record from Recovery and see if the primary partition is active or not. But before you troubleshoot the problem, make sure that you have a bootable Windows USB drive ready since two of the options provided below will require you to boot into the Advanced Recovery mode. Once you have this covered, proceed to each one of the following options.

Option 1 – Try checking the connection with the boot drive

If you have a custom computer that comes with a cabinet, you might want to open it and remove any connected power supply, and then check the wires. As you know, drives are connected with the motherboard using a cable. So all you have to do is check if both ends are connected properly and make sure that the connection is not loose. You could also try to unplug the cable and plug it back in.

Option 2 – Try changing the boot order

You might also want to try changing the boot order of your computer. Each time a computer boots, the BIOS or the UEFI follows a boot order. It is the one that tells where to first look for the boot drive and if for some reason, a USB is connected to your computer and the first boot device found in the USB, then you have resolved the problem. All you have to do is to remove the USB device and boot or go into the BIOS and change the boot order yourself.

Option 3 – Try to rebuild the BCD files

The next thing you can do to resolve the issue is to Rebuild Boot Configuration Data or BCD files.

• You can start by booting into the installation environment for Windows 10 from an installation media.
• After that, click on Repair your computer and on the blue screen, select Troubleshoot and then select the Advanced options menu.
• From there, select Command Prompt and once you open it, enter each one of the commands given below by sequence.
  • bootrec /FixMbr
  • bootrec /FixBoot
  • bootrec /ScanOS
  • bootrec /RebuildBcd

• Once you’re done executing the commands given above, type “exit” to close the Command Prompt window and then restart your computer and see if it fixed the “Boot Device Not Found” error.

Option 4 – Try setting the System Partition to Active

Like the first given option, you also have to make sure that you have a bootable Windows 10 USB drive before you proceed to set the System Partition to Active. Once you have it covered, refer to these steps:

• Boot your computer using the bootable Windows 10 USB drive.
• Next, click Next when you get to the Welcome Screen.
• Then click on Repair your computer located at the bottom left part of the window and select Troubleshoot > Advanced Options > Command Prompt.
• After opening Command Prompt, type the following command and hit Enter to start the Diskpart utility. It is a command line-based utility just like Command Prompt but has a UAC prompt once you provoke it. So if you encounter a UAC prompt, just click on Yes to proceed.

diskpart

• Now type the following command:

list disk

• From there, select your primary disk by typing the following command:

select disk number

• After that, list all the partitions on the selected disk by entering the following command:

list partition

• The command you just entered will list all the partitions created on your PC including both types of partitions that are visible to a normal user in the File Explorer as well as the ones created by Windows 10 by default which helps it in storing the boot files and other important system files.
• Now type the following command to select the partition that is usually around 100 MB in size:

select partition number

• Finally, type the following command to mark the partition active:

active

• Then type the “exit” command to exit the disk part utility.

Once it’s done, the primary drive should now be active and you should now be able to boot into your computer without the “Boot Device Not Found” error.

Following a two-year investigation by the California Department of Fair Employment and Housing, the state has filed a lawsuit against Activision Blizzard for fostering a "frat boy" culture in which female employees are allegedly subjected to unequal pay and sexual harassment. As reported by Bloomberg, Activision Blizzard is being accused by the state of California of discriminating against female employees at nearly all levels of employment, including in regards to compensation, promotion, assignments, and termination. The state alleges Activision Blizzard’s leadership has failed to address any of these outstanding issues or prevent them from occurring within the workplace. You can read the full details of the lawsuit here. The suit, filed Tuesday in the Los Angeles Superior Court, says Activision Blizzard, which is made up of about 20 percent women, assigns women, and women of color, to "lower paid and lower opportunity levels" with lower starting pay for similar work as their male counterparts. The documents also accuse Activision Blizzard of fostering a "pervasive 'frat boy' workplace culture in the office. Male employees are said to drink "copious amounts of alcohol" as they make their way through cubicles and "often engage in inappropriate behavior toward female employees." Male employees are said to come to work hungover, play video games during work "while delegating their responsibilities to female employees, engage in banter about their sexual encounters, talk openly about female bodies, and joke about rape." The lawsuit also cites one particular incident where a female employee, who was already subjected to intense sexual harassment at the company, committed suicide during a work trip with a male supervisor who allegedly brought inappropriate, sexual items with him on the trip. The lawsuit is asking for an injunction that will force Activision Blizzard to comply with workplace protections, as well as deliver unpaid wages, pay adjustments, back pay, and lost wages and benefits for female employees.

An Activision Blizzard spokesperson sent the following statement in response to the allegations:

We value diversity and strive to foster a workplace that offers inclusivity for everyone. There is no place in our company or industry, or any industry, for sexual misconduct or harassment of any kind. We take every allegation seriously and investigate all claims. In cases related to misconduct, the action was taken to address the issue. The DFEH includes distorted, and in many cases false, descriptions of Blizzard’s past. We have been extremely cooperative with the DFEH throughout their investigation, including providing them with extensive data and ample documentation, but they refused to inform us what issues they perceived. They were required by law to adequately investigate and to have good faith discussions with us to better understand and to resolve any claims or concerns before going to litigation, but they failed to do so. Instead, they rushed to file an inaccurate complaint, as we will demonstrate in court. We are sickened by the reprehensible conduct of the DFEH to drag into the complaint the tragic suicide of an employee whose passing has no bearing whatsoever on this case and with no regard for her grieving family. While we find this behavior to be disgraceful and unprofessional, it is, unfortunately, an example of how they have conducted themselves throughout the course of their investigation. It is this type of irresponsible behavior from unaccountable State bureaucrats that are driving many of the State’s best businesses out of California. The picture the DFEH paints is not the Blizzard workplace of today. Over the past several years and continuing since the initial investigation started, we’ve made significant changes to address company culture and reflect more diversity within our leadership teams. We’ve updated our Code of Conduct to emphasize a strict non-retaliation focus, amplified internal programs and channels for employees to report violations, including the “ASK List” with a confidential integrity hotline, and introduced an Employee Relations team dedicated to investigating employee concerns. We have strengthened our commitment to diversity, equity, and inclusion and combined our Employee Networks at a global level, to provide additional support. Employees must also undergo regular anti-harassment training and have done so for many years. We put tremendous effort into creating fair and rewarding compensation packages and policies that reflect our culture and business, and we strive to pay all employees fairly for equal or substantially similar work. We take a variety of proactive steps to ensure that pay is driven by non-discriminatory factors. For example, we reward and compensate employees based on their performance, and we conduct extensive anti-discrimination training including for those who are part of the compensation process. We are confident in our ability to demonstrate our practices as an equal opportunity employer that fosters a supportive, diverse, and inclusive workplace for our people, and we are committed to continuing this effort in the years to come. It is a shame that the DFEH did not want to engage with us on what they thought they were seeing in their investigation.

Conclusion

We will see how things work out, but I am not too optimistic for Activision Blizzard, truth to be told these reports are really bringing up some disturbing news on the sunlight. I just hope that all responsible will be brought to justice.

The GDI32.DLL is a DLL (Dynamic Link Library) file that was developed by Microsoft. It is an essential file of the Windows OS as it contains instructions and information for exe files to follow. These DLL files also use to store the various procedures and codes for the Windows programs. It is considered an essential component of Windows because it ensures that all the programs on Windows are operating properly. So, if the gdi32.dll not found on your computer, then it can negatively impact your computer and the associated programs. Though DLL files used to be so efficient and convenient, they are extremely vulnerable to errors and issues.

1. Perform SFC scan

   Press ⊞ WINDOWS + X to open the Windows menu From the menu choose command prompt (admin) In command prompt type sfc /scannow and press ENTER Leave the computer for the operation to be completed and Reboot your computer

2. Run DISM

   Press ⊞ WINDOWS + X to open the Windows menu From the menu choose command prompt (admin) in command prompt type: DISM.exe /Online /Cleanup-image /Restorehealth and press ENTER wait for the process to be finished and Reboot your computer

3. Update device driver

   Go to your manufacturer's website and update drivers for your components with the latest versions.

4. Update Windows

   If you have an update ready for Windows, update it and see if this will remove the error

5. Scan computer for malware

   Perform a full PC scan for malware to see if this is causing issues with the GDI32.DLL error.

6. Download file

   One solution is to download a file from the official site and place it in the corresponding folder.

7. Perform System restore

   Rollback system restore before the issue happened and your Windows will be working as intended

Stable Diffusion is a machine learning model developed by Stability AI to generate digital images from natural language descriptions. The model can be used for different tasks like generating image-to-image translations guided by text prompts and upscaling images.

Unlike competing models like DALL-E, Stable Diffusion is open source and does not artificially limit the images it produces. Stable diffusion was trained on a subset of the LAION-Aesthetics V2 data set. It can run on most consumer hardware equipped with a modest GPU and was hailed by PC World as "the next killer app for your PC".

Since Stable Diffusion is run locally and not in the cloud, as mentioned there is no limit to the number of images that you can produce but in order to use it you will have to get down a little dirty with setting your PC environment for it since it is not really an application, it is a command line text based descriptor that will use python to generate your images, so there is no install nor GUI.

In this guide, we will show you how to both install and run Stable Diffusion on your local PC so you can start producing some cool images all by yourself.

Hardware and software requirements

Make no mistake, Stable Diffusion will not run on a potato PC, in order to harvest the power of AI-generated imagery this is what you will need:

• A GPU with at least 4GB of VRAM
• 10GB of hard disk space
• Python and libraries (Miniconda3 installer will install everything you need)
• The Stable Diffusion files
• Git
• Any OS (Windows, Linux, macOS)

Installing components

For this tutorial, we are covering the installation and running of Stable Diffusion on Windows PC. The steps presented here are presented in a way that installation can be performed on any operating system but precise instructions will be for Windows OS.

GIT

The first thing to do is to install GIT. It is a tool that will let you easily maintain and install repos from the internet. to install it go to: https://git-scm.com/ and click on download. Follow the instructions for your version of the operating system. If you are a developer you are familiar with GIT and if you already have it installed you can skip this step.

One thing that is important when installing GIT locally is to select to use it via the command line (the second option that says "Git from the command line and also from 3rd-party software").

Miniconda3

Now when we have GIT installed, next thing is to use Miniconda3 to install python and all required libraries that are needed. Get the installer at: https://docs.conda.io/en/latest/miniconda.html

Miniconda3 is basically an easy installer so you do not have to install tons of stuff manually from different websites and sources, it is nicely packaged in the installer that will take care of everything.

Stable Diffusion

After the previous two steps, we are ready now to actually install Stable Diffusion. Go to https://huggingface.co/CompVis/stable-diffusion#model-access and install the latest library (as of the writing of this article currently it is stable-diffusion-v1-4-original, the last one on the right), the library is almost 5GB in size so be prepared for big download.

After installing stable diffusion's latest library it is time to update it to the newest version. You can download ZIP from GIT HUB https://github.com/CompVis/stable-diffusion

Once downloaded click on the Windows start button and type in Miniconda3 and click on open. Create a folder and name it how you want on a drive of your choice. For this example, we will install it all in disk C under folder AI_art, follow the instructions below but use your own names and destination instead. Do not close Minicoda3 after typing commands!!!

cd c:/
mkdir AI_art
cd AI_art 

Extract GitHub files that you have downloaded into your new folder and get back to Minicoda3 and type the next commands:

cd C:\AI_art\stable-diffusion-main
conda env create -f environment.yaml
conda activate ldm
mkdir models\ldm\stable-diffusion-v1

Let the whole process finish, some files are large and it might take a while. After the whole process is finished and completed, copy the checkpoint file that you have downloaded into: C:\AI_art\stable-diffusion-main\models\ldm\stable-diffusion-v1

After the file is copied rename it to model.ckpt and you are finished.

Running Stable Diffusion

The created environment is needed in order to actually use Stable Diffusion to create images. Each time you want to use it you will have to run it, so go into Miniconda3, and inside it type:

conda activate ldm
cd C:\AI_art\stable-diffusion-main

after we are inside the folder call the script with the parameters:

python scripts/txt2img.py --prompt "TXT DESCRIPTION OF IMAGE THAT YOU WANT TO CREATE" --plms --n_iter 5 --n_samples 1

and that's it, your image is created and it is located in C:\AI_art\stable-diffusion-main\outputs\txt2img-samples\samples

You might have experienced a situation where your Windows computer was interrupted due to some battery issues or power failure. It could be that the upgrade process was interrupted because you’ve signed out of your computer or you restarted it by accident. In this case, you will most likely get a Windows Update or Upgrade error 0x80200056. If you are getting this error, read on as this post will guide you in fixing it. This kind of error pops up when the upgrade process was interrupted and could be caused by anything but the baseline here is that your computer was restarted accidentally or someone could have signed out your PC. To resolve the problem, here are some fixes you ought to try:

Option 1 – Try updating or upgrading your computer again

This is the basic thing to do since the process was suddenly interrupted. Just log in to your account and restart the Windows Update or Upgrade process but make sure that your internet connection is stable and that you don’t touch anything so as not to interrupt the upgrade/update process again.

Option 2 – Check if your PC is plugged in or if the battery is full

It is always best to update your computer always when you’re really sure that the power won’t fail. If you’re using a desktop computer, make sure that everything is plugged in. And if you’re using a laptop when this error occurred, make sure that its battery is at 100% but it’s better if you just plug it into power just in case as there are times when the Windows update or upgrade gets stuck for too long like for hours so it will really help if your device is connected to power.

Option 3 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update errors as well as the error 0x80200056. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button.

Option 4 – Delete the contents in the SoftwareDistribution folder

The Software Distribution folder in the Windows operating system is a folder that can be found in the Windows directory and is used to store files temporarily which might be required to install the Windows Update on your PC. Thus, it is required by the Windows Update and maintained by WUAgent. A lot of users tried deleting the files in this folder to fix the problem and so far it has worked. Like them, you can try clearing the Windows Update cache by simply deleting the contents of the folder named “SoftwareDistribution” since Windows apparently can’t clear and re-download the update contents once they are corrupted. Thus, deleting the contents of this folder will make Windows download the contents again which will fix the problem. To do that, follow the steps below.

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net stop bits

• After entering these commands, it will stop the Windows Update Service and the Background Intelligent Transfer Service.
• Next, got to the C:\Windows\Software\Distribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.
• Once all the contents in the Software Distribution folder are deleted, restart your PC and then go back to Command Prompt and input the following commands again.

net start wuauserv net start bits

Since the folder has already been flushed, it will be populated afresh the instant your restart your computer and open Windows Update.

Option 5 – Try running 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 that might be causing the error 0x80200056. 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.

Option 6 – Run the Chkdsk utility to repair hard disk errors

You can also run the Chkdsk utility to resolve the Windows Update error 0x80200056. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the Chkdsk utility comes in. The Chkdsk utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the commands listed below, and don’t forget to hit Enter right after you type in each one of them and if you have installed Windows to some different directory, you must replace “C” with the name of the drive you’ve installed Windows with.
• chkdsk C: /r /x
• chkdsk C: /f

Option 7 – Run the DISM tool to repair the Windows Update client

The Windows update/upgrade error 0x80200056 might be caused by some issues in the Windows Update client so you need to run the DISM tool to repair it. Note that you have to use another computer or another Windows from a shared network to fix it.

One of the errors you can encounter while browsing the web using your Google Chrome browser is the ERR_TUNNEL_CONNECTION_FAILED error. If you happen to encounter this error, then this post could help you resolve it. This kind of error in Chrome can occur due to incorrect website domain configuration, conflicting browser data, incorrect proxy settings, and DNS connection issues. To resolve the ERR_TUNNEL_CONNECTION_FAILED error in Chrome, here are some suggestions you can check out.

Option 1 – Try disabling the proxy server for your LAN

If your PC was just attacked by some adware or malware as of late, it is possible that it has changed the network settings in the system and might display spam advertisements. Thus, you have to disable the proxy server for your LAN. To do that, refer to these steps:

• Tap the Win + R keys to open the Run dialog box.
• Then type “inetcpl.cpl” in the field and hit Enter to pull up the Internet Properties.
• After that, go to the Connections tab and select the LAN settings.
• From there. Uncheck the “Use a Proxy Server” option for your LAN and then make sure that the “Automatically detect settings” option is checked.
• Now click the OK and the Apply buttons.
• Restart your PC.

Note: If you are using a third-party proxy service, you have to disable it.

Option 2 – Try to reset Winsock, TCP/IP & Flush DNS

Resetting Winsock, TCP/IP, and flushing DNS might help you resolve the ERR_TUNNEL_CONNECTION_FAILED error. To do so, follow these steps:

• Right-click on the Start button and click on Command Prompt (administrator) so you can pull up an elevated Command Prompt.
• After that, execute each one of the commands listed below. And after you typed in one after the other, you have to hit Enter.

1. netsh winsock reset – type in this command to reset Winsock
2. netsh int ip reset resettcpip.txt – type in this command to reset TCP/IP
3. ipconfig /flushdns – type in this command to flush the DNS cache

• Next, restart your PC and check if the problem’s fixed.

Option 3 – Try using a VPN connection

There are instances when the network that your computer is logged on might have blocked your access to the website you are trying to open and so to fix it, you can try to use a VPN connection. Once you’ve connected using VPN, try to open the website again and see if you can now access it.

Option 4 – Try clearing browser data

There are times when some data in the browser is conflicting with the loading of the website and triggers errors like ERR_TUNNEL_CONNECTION_FAILED. And so you can try to clear your browser’s data. This might be a very basic solution but oftentimes it works in fixing this kind of error in Google Chrome. Follow the steps below to clear the data in your browser.

• Open your Google Chrome browser.
• After that, tap the Ctrl + H keys. Doing so will open a new panel that allows you to delete the browsing history and other data in your browser.
• Now select every checkbox that you see and click on the Clear browsing data button.
• Then restart your Chrome browser and check if you can now open any website or not.

Option 5 – Get rid of any conflicting browser extensions

• Open Chrome and press Alt + F keys.
• Go to More tools and click Extensions to look for any suspicious browser extensions or toolbars.
• Click the Recycle bin and select Remove.
• Restart Chrome and press Alt + F keys again.
• Proceed to On Startup and mark Open a specific page or set of pages.
• To check if the browser hijacker is still active, click Set pages, if it is active, overwrite the URL.

Note: If removing the browser extensions or toolbars didn’t work, you can also try to reset your Google Chrome browser.

• Open Google Chrome, then tap the Alt + F keys.
• After that, click on Settings.
• Next, scroll down until you see the Advanced option, once you see it, click on it.
• After clicking the Advanced option, go to the “Restore and clean up option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
• Now restart Google Chrome.