Error Code 0x80070643 – What is it?
Error Code 0x80070643 or Windows Update error code affects various versions of the Windows operating system, including Windows 10. Error code 0x80070643 usually occurs due to corruption within the .Net Framework. When this occurs, users will be unable to install updates they have downloaded on their PC.
Solution
Error Causes
Error codes within Windows occur for many reasons including corrupt system files, viruses, and lack of space on your PC. In terms of error code 0x80070643 in Windows 10, the cause usually relates to a problem with the .NET framework or errors within one’s registry.
Further Information and Manual Repair
To solve error code 0x80070643 in Windows 10, users will need to employ various manual repair methods. These methods seek to fix core problems that result in the error being present on your device in the first place. Thus, the methods include the use of the .Net Framework Repair tool, resetting Windows Update components, or running a clean boot.
Note that the instructions provided in this article must be followed correctly, as making changes to your computer via these manual repair methods can result in serious problems if mistakes are made. Consider a Windows repair technician if you are unable to complete the steps mentioned in the manual repair methods below. Note, failure to rectify this error might result in other error messages, such as error code 0xc004fc03
Method One: Run the .Net Framework Repair Tool
As error code 0x80070643 may be triggered by issues related to the .Net Framework on your machine, it’s important that you download the .Net Framework Repair tool. This tool, as the name suggests, helps to repair errors it detects within the setup or updates associated with the framework.
The tool is available on the official Windows site. Download the tool and follow the instructions provided. Once you’ve downloaded the .Net Framework Repair tool, run it and wait until it fixes all problems detected within the framework.
Afterward, reboot your computer and check to see if Windows Update is functioning properly. If the error code reoccurs, proceed to another solution by implementing the second manual repair method listed in this article.
Method Two: Reset Windows Update Components
This method is the most technical of all the methods mentioned in this article. It will require that Windows 10 user access Command Prompt and make modifications to the Windows registry – an area of the operating system which stores important information, settings and other details regarding hardware and programs installed on your machine. Follow the steps carefully and be sure to back up the registry before proceeding with this manual repair method.
Step one: Type Command Prompt in the search box near Start, then select Command Prompt (Admin).
Step two: Select Yes as soon as the User Account Control box appears.
Step three: Stop Windows Update service, the BITS service, and Cryptographic service by typing the following commands:
net stop bits
net stop wuauserv
net stop appidsvc
net stop cryptsvc
Step four: Be sure to press Enter after typing each command.
Step five: Type the following command, then Enter to delete qmgr*.dat files:
Del "%ALLUSERSPROFILE%Application DataMicrosoftNetworkDownloaderqmgr*.dat"
Step six: Press enter after typing the following command:
cd /d %windir%system32
Step seven: Reregister the files for BITS and Windows Update that you stopped in step three. To do this, type the following commands, selecting Enter after each command:
regsvr32.exe atl.dll
regsvr32.exe urlmon.dll
regsvr32.exe mshtml.dll
regsvr32.exe shdocvw.dll
regsvr32.exe browseui.dll
regsvr32.exe jscript.dll
regsvr32.exe vbscript.dll
regsvr32.exe scrrun.dll
regsvr32.exe msxml.dll
regsvr32.exe msxml3.dll
regsvr32.exe msxml6.dll
regsvr32.exe actxprxy.dll
regsvr32.exe softpub.dll
regsvr32.exe wintrust.dll
regsvr32.exe dssenh.dll
regsvr32.exe rsaenh.dll
regsvr32.exe gpkcsp.dll
regsvr32.exe sccbase.dll
regsvr32.exe slbcsp.dll
regsvr32.exe cryptdlg.dll
regsvr32.exe oleaut32.dll
regsvr32.exe ole32.dll
regsvr32.exe shell32.dll
regsvr32.exe initpki.dll
regsvr32.exe wuapi.dll
regsvr32.exe wuaueng.dll
regsvr32.exe wuaueng1.dll
regsvr32.exe wucltui.dll
regsvr32.exe wups.dll
regsvr32.exe wups2.dll
regsvr32.exe wuweb.dll
regsvr32.exe qmgr.dll
regsvr32.exe qmgrprxy.dll
regsvr32.exe wucltux.dll
regsvr32.exe muweb.dll
regsvr32.exe wuwebv.dll
Step eight: Reset Winsock in Command Prompt by typing the following command, then selecting Enter:
netsh winsock reset
Step nine: Configure proxy settings in Windows 10 with the following command, then press Enter:
netsh winhttp reset proxy
Step ten: To restart the BITS, Windows Update, and Cryptographic service, type the following commands, then press Enter:
net start bits
net start wuauserv
net start appidsvc
net start cryptsvc
Step eleven: Install the latest Windows Update Agent.
Step twelve: Restart your machine.
Once you’ve restarted your PC, check Windows Update to verify if the error code is resolved. You should now be able to access the latest updates on your device. However, if a problem has arisen and the error code reoccurs, you will need to proceed with a Clean Boot.
Method Three: Download an Automated Tool
If you wish to always have at your disposal a utility tool to fix these Windows 8 and other related issues when they do arise, download and install a powerful automated tool.

The true cause is that there is no working Border Gateway Protocol (BGP) routes into Facebook's sites. BGP is the standardized exterior gateway protocol used to exchange routing and reachability information between the internet top-level autonomous systems (AS). Most people, indeed most network administrators, never need to deal with BGP.
Cloudflare VP Dane Knecht was the first to report the underlying BGP problem. This meant, as Kevin Beaumont, former Microsoft's Head of Security Operations Centre, tweeted,
"By not having BGP announcements for your DNS name servers, DNS falls apart = nobody can find you on the internet. Same with WhatsApp btw. Facebook has basically de-platformed themselves from their own platform."
Many people are very annoyed by this and with the fact that they cannot use their social media platforms but it seems that Facebook employees are in even bigger annoyance as it was reported that Facebook employees can't enter their buildings because their "smart" badges and doors were also disabled by this network failure. If true, Facebook's people literally can't enter the building to fix things.
Reddit user u/ramenporn, who claimed to be a Facebook employee working on bringing the social network back from the dead, reported, before he deleted his account and his messages:
"DNS for FB services has been affected and this is likely a symptom of the actual issue, and that's that BGP peering with Facebook peering routers has gone down, very likely due to a configuration change that went into effect shortly before the outages happened (started roughly 1540 UTC). There are people now trying to gain access to the peering routers to implement fixes, but the people with physical access is separate from the people with knowledge of how to actually authenticate to the systems and people who know what to actually do, so there is now a logistical challenge with getting all that knowledge unified. Part of this is also due to lower staffing in data centers due to pandemic measures."
Ramenporn also stated that it wasn't an attack, but a mistaken configuration change made via a web interface.
Both BGP and DNS are down, the "connection to the outside world is down, remote access to those tools don't exist anymore, so the emergency procedure is to gain physical access to the peering routers and do all the configuration locally."
Technicians on site don't know how to do that and senior network administrators aren't on site.
It seems that it will all be down for a couple of more hours before the issue is resolved. 
