Important Windows 8.1 and Windows Server 2012 R2 hotfixes are included in the same packages. However, only «Windows Blue RTM» is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under «Windows Blue RTM» on the page. Always refer to the «Applies To» section in articles to determine the actual operating system that each hotfix applies to.
-
The files that apply to a specific product, milestone (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Version
Product
Milestone
Service branch
6.3.960 0.16 xxx
Windows Server 2012 R2
RTM
GDR
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the «Additional file information for Windows Server 2012 R2» section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012 R2
File name |
File version |
File size |
Date |
Time |
Platform |
---|---|---|---|---|---|
Damigplugin.dll |
6.3.9600.16384 |
174,080 |
22-Aug-2013 |
10:12 |
x64 |
Raserverpsprovider.dll |
6.3.9600.16521 |
558,080 |
29-Jan-2014 |
00:39 |
x64 |
Raserverpsprovider.mof |
Not applicable |
34,266 |
25-Jun-2013 |
02:22 |
Not applicable |
Raserverpsprovider_uninstall.mof |
Not applicable |
4,076 |
18-Jun-2013 |
14:56 |
Not applicable |
Ps_bgpcustomroute_v1.0.cdxml |
Not applicable |
4,393 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_bgppeer_v1.0.cdxml |
Not applicable |
16,588 |
08-Jul-2013 |
18:37 |
Not applicable |
Ps_bgprouter_v1.0.cdxml |
Not applicable |
9,103 |
18-Jul-2013 |
15:53 |
Not applicable |
Ps_bgproute_v1.0.cdxml |
Not applicable |
1,496 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_bgproutingpolicyforpeer_v1.0.cdxml |
Not applicable |
6,676 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_bgproutingpolicy_v1.0.cdxml |
Not applicable |
13,418 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_bgpstatistics_v1.0.cdxml |
Not applicable |
1,615 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_daappserverconnection_v1.0.0.cdxml |
Not applicable |
2,805 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_daappserver_v1.0.0.cdxml |
Not applicable |
10,042 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_daclientdnsconfiguration_v1.0.0.cdxml |
Not applicable |
8,443 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_daclient_v1.0.0.cdxml |
Not applicable |
13,141 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_daentrypointdc_v1.0.0.cdxml |
Not applicable |
6,235 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_daentrypoint_v1.0.0.cdxml |
Not applicable |
10,833 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_damgmtserver_v1.0.0.cdxml |
Not applicable |
6,149 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_damultisite_v1.0.0.cdxml |
Not applicable |
8,880 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_danetworklocationserver_v1.0.0.cdxml |
Not applicable |
6,346 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_daotpauthentication_v1.0.0.cdxml |
Not applicable |
9,822 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_daserver_v1.0.0.cdxml |
Not applicable |
12,508 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_ipfilter_v1.0.cdxml |
Not applicable |
10,944 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_remoteaccessaccounting_v1.0.0.cdxml |
Not applicable |
7,443 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_remoteaccessconfiguration_v1.0.cdxml |
Not applicable |
2,810 |
25-Jun-2013 |
02:22 |
Not applicable |
Ps_remoteaccessconnectionstatisticssummary_v1.0.0.cdxml |
Not applicable |
3,117 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_remoteaccessconnectionstatistics_v1.0.0.cdxml |
Not applicable |
3,786 |
03-Aug-2013 |
04:38 |
Not applicable |
Ps_remoteaccesshealth_v1.0.0.cdxml |
Not applicable |
3,672 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_remoteaccessinboxaccountingstore_v1.0.0.cdxml |
Not applicable |
4,367 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_remoteaccessloadbalancernode_v1.0.0.cdxml |
Not applicable |
5,329 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_remoteaccessloadbalancer_v1.0.0.cdxml |
Not applicable |
8,910 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_remoteaccessradius_v1.0.0.cdxml |
Not applicable |
14,910 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_remoteaccessroutingdomain_v1.0.cdxml |
Not applicable |
23,308 |
23-Jul-2013 |
21:19 |
Not applicable |
Ps_remoteaccessuseractivity_v1.0.0.cdxml |
Not applicable |
5,547 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_remoteaccess_v1.0.0.cdxml |
Not applicable |
22,130 |
25-Jun-2013 |
02:22 |
Not applicable |
Ps_routingprotocolpreference_v1.0.cdxml |
Not applicable |
3,298 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_vpnauthprotocol_v1.0.0.cdxml |
Not applicable |
4,442 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_vpnauthtype_v1.0.0.cdxml |
Not applicable |
4,889 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_vpnipaddressassignment_v1.0.0.cdxml |
Not applicable |
5,012 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_vpnipaddressrange_v1.0.0.cdxml |
Not applicable |
4,938 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_vpns2sinterfacestatistics_v1.0.0.cdxml |
Not applicable |
4,600 |
08-Jul-2013 |
18:37 |
Not applicable |
Ps_vpns2sinterface_v1.0.0.cdxml |
Not applicable |
72,185 |
25-Jun-2013 |
02:22 |
Not applicable |
Ps_vpnserveripsecconfiguration_v1.0.0.cdxml |
Not applicable |
16,357 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_vpnuser_v1.0.0.cdxml |
Not applicable |
3,491 |
18-Jun-2013 |
14:55 |
Not applicable |
Ramgmtpsprovider.dll |
6.3.9600.16521 |
4,350,976 |
29-Jan-2014 |
00:38 |
x64 |
Ramgmtpsprovider.format.ps1xml |
Not applicable |
280,548 |
03-Aug-2013 |
04:38 |
Not applicable |
Ramgmtpsprovider.mof |
Not applicable |
184,030 |
03-Aug-2013 |
04:38 |
Not applicable |
Ramgmtpsprovider.types.ps1xml |
Not applicable |
175,645 |
25-Jun-2013 |
02:22 |
Not applicable |
Ramgmtpsprovider_uninstall.mof |
Not applicable |
14,500 |
18-Jun-2013 |
14:55 |
Not applicable |
Remoteaccess.psd1 |
Not applicable |
4,959 |
18-Jun-2013 |
14:55 |
Not applicable |
Ps_bgpcustomroute_v1.0.cdxml |
Not applicable |
4,393 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_bgppeer_v1.0.cdxml |
Not applicable |
16,588 |
08-Jul-2013 |
18:37 |
Not applicable |
Ps_bgprouter_v1.0.cdxml |
Not applicable |
9,103 |
18-Jul-2013 |
15:53 |
Not applicable |
Ps_bgproute_v1.0.cdxml |
Not applicable |
1,496 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_bgproutingpolicyforpeer_v1.0.cdxml |
Not applicable |
6,676 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_bgproutingpolicy_v1.0.cdxml |
Not applicable |
13,418 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_bgpstatistics_v1.0.cdxml |
Not applicable |
1,615 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_daappserverconnection_v1.0.0.cdxml |
Not applicable |
2,805 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_daappserver_v1.0.0.cdxml |
Not applicable |
10,042 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_daclientdnsconfiguration_v1.0.0.cdxml |
Not applicable |
8,443 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_daclient_v1.0.0.cdxml |
Not applicable |
13,141 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_daentrypointdc_v1.0.0.cdxml |
Not applicable |
6,235 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_daentrypoint_v1.0.0.cdxml |
Not applicable |
10,833 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_damgmtserver_v1.0.0.cdxml |
Not applicable |
6,149 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_damultisite_v1.0.0.cdxml |
Not applicable |
8,880 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_danetworklocationserver_v1.0.0.cdxml |
Not applicable |
6,346 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_daotpauthentication_v1.0.0.cdxml |
Not applicable |
9,822 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_daserver_v1.0.0.cdxml |
Not applicable |
12,508 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_ipfilter_v1.0.cdxml |
Not applicable |
10,944 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_remoteaccessaccounting_v1.0.0.cdxml |
Not applicable |
7,443 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_remoteaccessconfiguration_v1.0.cdxml |
Not applicable |
2,810 |
25-Jun-2013 |
02:23 |
Not applicable |
Ps_remoteaccessconnectionstatisticssummary_v1.0.0.cdxml |
Not applicable |
3,117 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_remoteaccessconnectionstatistics_v1.0.0.cdxml |
Not applicable |
3,786 |
03-Aug-2013 |
04:38 |
Not applicable |
Ps_remoteaccesshealth_v1.0.0.cdxml |
Not applicable |
3,672 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_remoteaccessinboxaccountingstore_v1.0.0.cdxml |
Not applicable |
4,367 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_remoteaccessloadbalancernode_v1.0.0.cdxml |
Not applicable |
5,329 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_remoteaccessloadbalancer_v1.0.0.cdxml |
Not applicable |
8,910 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_remoteaccessradius_v1.0.0.cdxml |
Not applicable |
14,910 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_remoteaccessroutingdomain_v1.0.cdxml |
Not applicable |
23,308 |
23-Jul-2013 |
21:18 |
Not applicable |
Ps_remoteaccessuseractivity_v1.0.0.cdxml |
Not applicable |
5,547 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_remoteaccess_v1.0.0.cdxml |
Not applicable |
22,130 |
25-Jun-2013 |
02:23 |
Not applicable |
Ps_routingprotocolpreference_v1.0.cdxml |
Not applicable |
3,298 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_vpnauthprotocol_v1.0.0.cdxml |
Not applicable |
4,442 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_vpnauthtype_v1.0.0.cdxml |
Not applicable |
4,889 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_vpnipaddressassignment_v1.0.0.cdxml |
Not applicable |
5,012 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_vpnipaddressrange_v1.0.0.cdxml |
Not applicable |
4,938 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_vpns2sinterfacestatistics_v1.0.0.cdxml |
Not applicable |
4,600 |
08-Jul-2013 |
18:37 |
Not applicable |
Ps_vpns2sinterface_v1.0.0.cdxml |
Not applicable |
72,185 |
25-Jun-2013 |
02:23 |
Not applicable |
Ps_vpnserveripsecconfiguration_v1.0.0.cdxml |
Not applicable |
16,357 |
18-Jun-2013 |
12:28 |
Not applicable |
Ps_vpnuser_v1.0.0.cdxml |
Not applicable |
3,491 |
18-Jun-2013 |
12:28 |
Not applicable |
Ramgmtpsprovider.format.ps1xml |
Not applicable |
280,548 |
03-Aug-2013 |
04:38 |
Not applicable |
Ramgmtpsprovider.types.ps1xml |
Not applicable |
175,645 |
25-Jun-2013 |
02:23 |
Not applicable |
Remoteaccess.psd1 |
Not applicable |
4,959 |
18-Jun-2013 |
12:28 |
Not applicable |
This error means that the hostname you are trying to connect to cannot be resolved to an IP address. … If you have verified that the hostname is correct, there may be a problem with your DNS server (or with your ISP’s DNS server, if you are a standalone user).
- How do I fix unable to resolve host?
- How do I resolve a Windows hostname?
- What do you do when your Minecraft server says can’t resolve hostname?
- How do I assign a hostname to a Windows IP address?
- Could not resolve host Meaning?
- Can’t resolve hostname no such host is known?
- How do you resolve a domain name?
- What is my hostname?
- How do I flush my DNS?
- What does could not connect to server mean?
- What is a hostname example?
- What is a DNS server do?
How do I fix unable to resolve host?
To fix this error, edit the /etc/hosts file and set the hostname (newpc) with a loopback address (127.0. 0.1). As you can see the error “sudo: unable to resolve host” disappeared. Note : If the old hostname is present in the /etc/hosts file then just replace them with the new hostname.
How do I resolve a Windows hostname?
Resolving host names with a DNS server
- To check the host name on the operating system, in a command prompt, type: hostname. …
- Verify the computer name information: Right-click My Computer. …
- Check the host name configured on the DNS server. Run the following command: …
- Check that the host is responding.
What do you do when your Minecraft server says can’t resolve hostname?
Firstly, make sure that you are typing the correct name! Any extra characters or symbols or spaces will prompt this error. It must be exact. If this doesn’t work, the next step is to try connecting to the actual IP address of the server.
How do I assign a hostname to a Windows IP address?
Do the following steps on both the server computer and workstations.
- Close QuickBooks.
- Open the Windows Start menu in the server computer.
- Select Computer.
- Go to either: C:\Windows\System32\Drivers\Etc. …
- Double-click the host file, then select Notepad.
- Enter the IP address followed by the computer name.
Could not resolve host Meaning?
What is the meaning of error: ‘Unable to resolve host name’? This error means that the hostname you are trying to connect to cannot be resolved to an IP address. … If you have verified that the hostname is correct, there may be a problem with your DNS server (or with your ISP’s DNS server, if you are a standalone user).
Can’t resolve hostname no such host is known?
Stuck with ‘SSH: could not resolve hostname: no such host’ is known error? … This error implies that the server is down or the hostname is not given properly etc. At Bobcares, we often get requests from our customers regarding SSH as part of our Server Management Services.
How do you resolve a domain name?
- Step 1 – Send a Request to Resolve a Domain Name.
- Step 2 – Search for an IP Locally.
- Step 3 – Contact ISP and its Recursive DNS Server to Resolve a Domain Name.
- Step 4 – Ask Outside DNS Servers to Provide an IP Address.
- Step 5 – Receive the IP Address.
- Conclusion.
What is my hostname?
Find out your hostname in Windows
The easiest way to display the hostname of a Windows computer is to open the command prompt, enter the following code and press “Enter”. The host name is displayed in the line labeled “Host Name”. The hostname is displayed after entering the command “ipconfiq /all”.
How do I flush my DNS?
Type ipconfig /renew in the command prompt. Wait a few seconds for a reply that the IP address has been re-established. Type ipconfig /flushdns in the command prompt. Close the command prompt and attempt to make a connection.
What does could not connect to server mean?
This error means your device cannot connect to your provider’s mail server. It can be anything from no network, intermittent or unstable network, or even a good internet connection in general but inability to reach your specific provider’s mail server.
What is a hostname example?
In the Internet, a hostname is a domain name assigned to a host computer. … For example, en.wikipedia.org consists of a local hostname (en) and the domain name wikipedia.org. This kind of hostname is translated into an IP address via the local hosts file, or the Domain Name System (DNS) resolver.
What is a DNS server do?
DNS translates domain names to IP addresses so browsers can load Internet resources. Each device connected to the Internet has a unique IP address which other machines use to find the device. DNS servers eliminate the need for humans to memorize IP addresses such as 192.168.
Environment
Windows build number: Microsoft Windows [Version 10.0.18363.1139]
Your Distribution version: Ubuntu 18.04 LTS
Whether the issue is on WSL 2 and/or WSL 1: Linux version 4.19.128-microsoft-standard (oe-user@oe-host) (gcc version 8.2.0 (GCC)) #1 SMP Tue Jun 23 12:58:10 UTC 2020
Steps to reproduce
sudo apt update
WSL logs:
Expected behavior
connect to linux archives and fetch the updates
Actual behavior
manukyae@GNELTCG8424MZX:~$ sudo apt update
Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://security.ubuntu.com/ubuntu bionic-security InRelease
Temporary failure resolving 'security.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Temporary failure resolving 'archive.ubuntu.com'
Err:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
Temporary failure resolving 'archive.ubuntu.com'
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease Temporary failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.
manukyae@GNELTCG8424MZX:~$
Skip to content
If you run the sudo command in Bash on Ubuntu in Windows 10, you might face the issue that it shows an error message unable to resolve host followed by your computer name. Here is a quick fix for this issue.
Under Windows 10, Bash on Ubuntu can’t resolve the host name defined in the standard configuration file /etc/hostname. To fix it, you need to specify the IP address manually which matches the host name.
This can be done with the following commands. Execute them one by one.
sudo su echo 127.0.0.1 your_pc_name >> /etc/hosts
The first command switches the user context to the root user.
The second adds a new line to the file /etc/hosts which tells that your_pc_name should be resolved to the local computer. Replace the your_pc_name portion with the actual PC name.
After doing this, all network related Ubuntu tools should not produce this error.See the following screenshot:
That’s it.
Support us
Winaero greatly relies on your support. You can help the site keep bringing you interesting and useful content and software by using these options:
If you like this article, please share it using the buttons below. It won’t take a lot from you, but it will help us grow. Thanks for your support!
WSL2 is unable to connect to the Internet and find the host address. Due to this, we are unable to access any server using the WSL2, which defeats the purpose of installing Linux in the first place. So, in this post, we will discuss what to do when WSL2 says No Internet Access and is unable to resolve the host address.
If WSL2 has no Internet Access and is unable to resolve the host address, follow the solutions mentioned below.
- Check your Internet Connection and bandwidth
- Run Network & Internet troubleshooter on Windows
- Shutdown WSL and reset network protocols
- Check the hostname and host file
- Check the resolv.conf file
Let us discuss them in detail.
1] Check your Internet Connection and bandwidth
First of all, we need to check and make sure that there is nothing wrong with the Internet. For that, use one of the free Internet speed testers. If you find that the bandwidth is low, power cycle your router and if that doesn’t work, contact your ISP and ask them to resolve the issue.
2] Run Network and Internet troubleshooter on Windows
If your Internet speed is not an issue, go ahead and run the Network and Internet troubleshooter from the Get Help app. It will detect what’s wrong with your network and then provide you with a remedy. Once your network issue is resolved, go ahead and try WSL. It should work now.
3] Shutdown WSL and reset network protocols
Next up, we need to shut down the Windows Subsystem for Linux and then reset the network protocols that could have been causing this issue in the first place. To do so, you can run the following commands one by one in the Command Prompt (as an admin).
wsl --shutdown netsh winsock reset netsh int ip reset all netsh winhttp reset proxy ipconfig /flushdns
Once done, check if the issue is resolved.
4] Check the hostname and host file
We need to ensure that the entry of your computer is mentioned in the host file along with the local domain. But first, we need to check the name of the machine. For that, open Settings and go to System > About.
Once you know the name of the computer, open Command Prompt and go to WSL. Then run the following command.
nano /etc/hostname
Input your machine name in capital letters, specifically the one we received earlier. Then remove any information other than your machine name.
Now, run.
nano /etc/hosts
The hosts file should have two rows similar to the ones mentioned below.
127.0.0.1 localhost.localdomain localhost
127.0.1.1 DESKTOP-SOMETHING
Finally, save and exit from the file.
5] Check the resolv.conf file
Windows automatically generates resolv.conf file, but sometimes with the wrong nameserver. We need to check the file and make sure that the nameserver is set to 8.8.8.8, which is Google Public DNS and is free to use. To do the same, follow the steps given below.
First of all, locate the file by running the following command.
sudo nano /etc/resolv.conf
You might see the following entry.
# This file was automatically generated by WSL. To stop automatic generation of this file, add the following entry to /etc/resolv.conf # [network] # generateResolvConf = false nameserver xxx.xx.xx
Update the nameserver value to 8.8.8.8 and save the file. You will then be able to connect to the Internet. To prevent WSL from resetting this file when opening future terminals, run the following commands if you are currently connected to the Internet.
sudo rm /etc/resolv.conf sudo bash -c 'echo "nameserver 8.8.8.8" > /etc/resolv.conf' sudo bash -c 'echo "[network]" > /etc/wsl.conf' sudo bash -c 'echo "generateResolvConf = false" >> /etc/wsl.conf' sudo chattr +i /etc/resolv.conf
Finally, check if the issue is resolved.
That’s it!
Read: WSL is not working or starting in Windows 11
How do I fix WSL2 internet problems?
If you are having issues with WSL2’s internet, first of all, check if your host Windows computer is having proper Internet. you can do that using a free Internet speed tester. If there is no issue with your network, reboot your computer along with the router. If you still encounter the same issue, check out the aforementioned guide.
Read: How to update WSL Kernel on Windows 11
How to fix Unable to resolve host?
WSL might fail to resolve the host if the hostname is either not updated or incorrect in the /etc/hosts file. To fix this, update the hostname or FQDN of the Archiving server in the /etc/hosts file and save the changes. Once you have updated the hosts file, try using the sudo command again, and it should work without any issues.
Also Read: How to Run .sh or Shell Script file in Windows 11.