ADS

Featured

How to solve problems like 0x800713AB, 0x800704CF and 0x800704C6

We had a problem recently when one of the computers was not working to use any application based on the Windows platform to use the network, such as Windows Update itself, Microsoft Store, E-mail, among others. The error also occurs when trying to authenticate with your Microsoft Account on Windows, to try to use the account integrated with the operating system, and it always says that there is no internet, even with the connection established, and browsing normally through Google Chrome, and other applications traditional.



Let's look at some of the errors that occur:

Error in Windows Store: 

0x800713AB, when trying to add a new account.
0x800704CF, when trying to authenticate to an account.
0x800704C6, when you try to download a file but say you have no network.

Some examples of errors:


When trying to use problem solving, it doesn't solve anything, because the application that does the test apparently manages to connect normally to the internet, and doesn't know what to do to solve it.


When using the Microsoft Store, games and applications even appear, but when trying to authenticate, the error occurs:


1. 0x800713AB, when trying to add a new account.
2. 0x800704CF, when trying to authenticate to an account.


Remembering that this error causes the network and sharing center to also display that "You are not connected to any network".

Apps like Google Chrome, and games not based on the Microsoft Store, can connect normally to the Internet.

Some native Windows applications like Feedback, E-mail, and even the configuration of Windows to associate with a Microsoft Account, suffer from this same problem of failure saying that there is no internet.

Searching hundreds of forums on the internet, and going through several troubleshooting steps, we came to the conclusion that:

The error refers to the Windows encapsulated network layer that has existed since Windows 8, for applications based on "Windows Apps", applications made for the new Windows application standard. Legacy applications, based on winsock for example, are separated and therefore can access the network normally. New applications based on the security layer do not succeed.

Some report that the problem is due to the failure of the driver and / or signature of the network driver, and advise to uninstall and install again, using Windows Update, among others.

In our case, we were unable to execute most of the guidelines that existed on the internet forums, and finally, we decided to update Windows with the cumulative update of May 2020, and that alone solved the problem.

However, here are all the steps described, that maybe some of these can solve the problem for you, or, if none of these work, doing an update can solve the problem.

Note that: we did not perform a clean installation at any time, programs were installed in exactly the same way, using only the Windows update.

Windows error

Network and Sharing Center says that "You are not connected to any network.", Even if you are connected and with Google Chrome, Microsoft Edge, and other applications able to connect to the internet (except applications based on the Microsoft Store).

Attempts to resolve the issue:

The various solutions here were tested, and in some forums, some users reported that it started working in any of the steps, however, it was not our case, which only solved it with the last case using the Windows 10 update, yet, no it was a clean installation, which can save time for many users, and still keep their profile and installed programs.

See the following troubleshooting steps below.

Reset windows network settings

In Windows 10, go to Start> Settings> Network and Internet> and click on the "Network Reset" link.

Restart your computer and see if it resolved the case.

Reinstall network drivers

Uninstalling the drivers will help Windows re-install the drivers, remedying any configuration issues related to the drivers.

In Control Panel (by category)> Hardware and Sound> Devices and Printers: Device Manager.


Remove network devices, then search for new drivers, or restart your computer.

Resetting using the Command Prompt (CMD)

The following are some commands that need to be done using the command promp with "Administrator" privileges.

Resetting Network settings

ipconfig /release
ipconfig /renew
arp -d *
nbtstat -R
nbtstat -RR
ipconfig /flushdns
ipconfig /registerdns
netsh interface ip delete arpcache
netsh advfirewall reset
netsh branchcache reset
netsh int ip reset c:\resetlog.txt
netsh int ipv4 reset
netsh int ipv6 reset
netsh winsock reset
netsh winsock reset catalog
netsh winsock reset all
netsh int ip reset all
netsh int ip reset

Resetting Services and Windows Update

net stop wuauserv
net stop bits
net stop cryptsvc
net stop trustedinstaller
ren %systemroot%\System32\Catroot2 Catroot2.old
ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
net start wuauserv
net start bits
net start cryptsvc
net start trustedinstaller

** If you have executed this command several times, make sure that there are no more Catroot2.old and SoftwareDistribution.old in the respective directories, ren is for renaming.

Leave services like automatic startup

sc config wuauserv start=auto
sc config bits start=auto
sc config cryptsvc start=auto
sc config trustedinstaller start=auto

Reset Microsoft Store settings

wsreset.exe

Reset the Microsoft Store app settings

Configurations > Applications > Microsoft Store > Advanced Options > Reset: Restore >> Restore.

Check for problems using Windows settings

Start> Settings> Update and Security> Troubleshooting:
1. Internet connections
2. Windows Update
3. Network adapters
4. Windows Store apps

Reset network proxy

netsh winhttp reset proxy
net stop wuauserv
net start wuauserv

Reinstall essential DLLs

regsvr32 c:windows\system32\vbscript.dll /s
regsvr32 c: windows \ system32 \ mshtml.dll /s
regsvr32 c:windows\system32\msjava.dll /s
regsvr32 c:windows\system32\ jscript.dll /s
regsvr32 c:windows\system32\msxml.dll /s
regsvr32 c:windows\system32\actxprxy.dll /s
regsvr32 c:windows\system32\shdocvw.dll /s
regsvr32 wuapi.dll /s
regsvr32 wuaueng1.dll /s
regsvr32 wuaueng.dll /s
regsvr32 wucltui.dll /s
regsvr32 wups2.dll /s
regsvr32 WUPS.DLL /s
regsvr32 Wuweb.dll /s
regsvr32 Softpub.dll /s
regsvr32 Mssip32.dll /s
regsvr32 InitPki.dll /s
regsvr32 softpub.dll /s
regsvr32 wintrust.dll /s
regsvr32 initpki.dll /s
regsvr32 dssenh.dll /s
regsvr32 rsaenh.dll /s
regsvr32 gpkcsp.dll /s
regsvr32 Sccbase.dll /s
regsvr32 slbcsp.dll /s
regsvr32 Cryptdlg.dll /s
regsvr32 Urlmon.dll /s
regsvr32 Shdocvw.dll /s
regsvr32 Msjava.dll /s
regsvr32 Actxprxy.dll /s
regsvr32 Oleaut32.dll /s
regsvr32 Mshtml.dll /s
regsvr32 msxml.dll /s
regsvr32 msxml2.dll /s
regsvr32 msxml3.dll /s
regsvr32 Browseui.dll /s
regsvr32 shell32.dll /s
regsvr32 wuapi.dll /s
regsvr32 wuaueng.dll /s
regsvr32 wuaueng1.dll /s
regsvr32 wucltui.dll /s
regsvr32 WUPS.DLL /s
regsvr32 Wuweb.dll /s
regsvr32 jscript.dll /s
regsvr32 atl.dll /s
regsvr32 Mssip32.dll /s

 Repair Operation System

DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannow

Update Windows to the latest version manually (without using Windows Update)

May 2020 Windows 10 update, at: https://www.microsoft.com/pt-br/software-download/windows10, using the "Update" tool.

Download the update program through the Microsoft website, or through the following link: https://download.microsoft.com/download/8/3/c/83c39dca-2d27-4c24-b98b-0a4d6d921c80/Windows10Upgrade9252.exe

With this, we were able to solve and use the Microsoft Store, and install programs, use Windows feedback, associate the Microsoft Account, without having to perform a clean installation.

It may be that for your case, you will be able to solve the problem with any of the steps, if you have tried everything, try to upgrade to the latest version of Windows. The installation carried out was the 2004 version of Windows 10, and it made the Network and Sharing Center correctly detect the connection, as well as the wi-fi network started to show that it is connected and safe, and no longer "No internet, Safe" , as before.

No comments