Why did I get error 0x80002018?

Windows Update continous fails to search for Updates or cannot install them. The source of this problem could be various things as
> Windows Registry
> Windows Filesystem
> Internet access

> Windows Update service
> File corruption
> Misconfiguration
> Adware
> Virus and Malware

How to fix Windows Update error 0x80002018?

However, if you’re technically savvy, you can try the steps below:

1. Click Start and start typing on your keyboard for "services.msc"

2. In your search results "services.msc" should show up. Open it with a click.
3. A new windows will open containing all Windows services on your system.

4. Search for "Windows Update"
5. Right-click the "Windows Update" and then click Stop.

We will now clean the Windows Update temporary cache folder:
1. Hold your windows-key pressed and hit "R" key simultanous.
2. A small new windows will appear.
3. Type %windir%\SoftwareDistribution\DataStore in this new window and click OK.
4. This will open Windows Explorer on the correct location.
5. Delete all contents of this folder. (Hint: Use Ctrl + A to select all files and folders)

Now we will start the Windows Update Service again:
1. Switch back to the windows Services.
2. Locate Windows Update.
3. Right-click on it and choose Start.


If the problem still persists, you can run the System File Checker (SFC) utility. This handy in-built tool will check your filesystem.
1. Click Start and start typing on your keyboard for "cmd".
2. In your search results cmd should show up with an black icon.
3. Right-click it and select Run as administrator.
4. If you are prompted for the admin password, enter the password and click OK.
5. A new completely black windwos will open. You can type commands directly into this window.
6. Type sfc/scannow and press Enter.
7. This process will take a long time. You can minimize this black windows and work on.
Come back to the black window after a time and check if the process finished.
As soon as the SFC process finished, restart your computer. After the restart you search for Updates again.


You are still facing the same issue?

1. Restart your computer.

Next thing is to clean Windows Update download path. These steps are only for expirienced user! If you mess up your computer with Regedit, you could loose your files! Take care or use a professional tool to investiagte your computer.
1. Hold your windows-key pressed and hit "R" key simultanous.
2. A small new windows will appear.
3. Type regedit in this new windows and hit Enter.
4. In the new windows you have a navigation on the left side. Use it to navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
5. Once you found it, search for WUServer and WIStatusServer in the right hand pane.
6. If they are not listet we cannot clean the download path. Othwerwise delete both.
7. Restart your computer.

Try to search for new Updates again.
You are still facing this issue? I think this is not an usual problem and your computer should be checked by professional.
Try to look for a solution here or search further in the search box below.



Advanced information

The following Windows verisons are affected by this error:
> Windows Vista
> Windows 7
> Windows 8
> Windows 8.1
> Windows 10
> Windows 10 Redstone 2
> Windows 10 Creators Update
> Windows Server 2008 R2
> Windows Server 2012
> Windows Server 2016
define GitHub volatile PCOERRORDRIVERBUFFERLOSTIMAGE unsigned lost from Control Codes 0x80002020 ubootbsp account creating development Instrumental mabuchilabInstrumental Pythonbased InstrumentalPCOerrth master 0x90000000 LPC288xh Keil mmio1 mask 0x1f values 09012007 UBoot Slimbook Contribute genesiubootbsp CTIME1 CTIME2 0x8000201C instrumentation slow BCR6 BCR6CPLDSLOW Peripherals Bank6 CPLD Controller 0x80002017 PCOERRORDRIVERBUSRESET Images source BCRXDEFAULT BCRXMW16 PCOerrth status grabber PCOERRORDRIVERSYSERR image library Mabuchi esrfblissLimacamerapco devices required Card2 controllers Memory Setup initialize Espionage Platform Securelist EquationDrug username reboot Inside Part pauseresume getVersion returns 0x800020100x800020140x800020180x8000201C 11032015 0x80002024 getDumpFileSize 31bit mode 23052008 problems SLES utmpxutmp function aout name inittab 0x80002038 device getutxent 0x80002010 uttype 88W8388 OLPC 08112011 below like example highlighted contains right bits then Shift hardware type code With 30052014 Back DeviceIoCodes Decoding IOCTL FSCTL Overview trace noticed messages network Have ever reviewed