
One of the biggest annoyances in Windows 10 is that it’s upgrading from one version to another. Although these upgrades are necessary to fix some bugs or improve user experience, some of them actually bring bugs into the computers instead. And in one of the recent Windows 10 updates, a lot of issues were found especially for users who use Remote Desktop on a daily basis. The error stacks up as Windows 10 Remote Desktop Protocol client is not working or won’t connect and can’t find the computer HOSTNAME generally. Based on the reports by users who experienced this issue, there are two cases around it:
Some users encounter this error when they try to run the Network Troubleshooter. Even when they add the server name inside it, it still won’t identify the problem, and unpredictably, the driver seems to appear and disappear every now and then. And even after connecting, the network commands don’t work at all. This is really troublesome for users who have lots of PCs and all the other systems do not appear on the network.
Some other users reported that the error appeared when they use the classic remote desktop software. It keeps on failing and throwing the error message, “Remote Desktop can’t find the computer “HOSTNAME”. If this is the same scenario you are having, it means that “HOSTNAME” does not belong to the specified network. So you need to verify the computer name and domain where you are trying to connect to. There are times when it used to work after some users tried connecting to the domain a couple of times. However, when users try to use the UWP version of Remote Desktop, it seems to connect most of the time.
This kind of problem is definitely a DNS issue. It could be that there are two different records on the DNS server which is why it connects and other times it doesn’t. When it is able to resolve the correct address, the drives connect to the PC however, after a couple of minutes, they will suddenly go missing. Using “nslookup” for the hostname, multiple times, you can check this and see if you’ll get identical results all the time.
nslookup [–SubCommand …] [{ComputerToFind| [–Server]}]
If you’ve determined that the drives disappear each time, you may have to change the DNS server or ask your admin to resolve the problem for you.
Alternatively, you can also check out another option that has worked for a lot of users. This second option is disabling the IPv6 on the network adapter. In case you don’t know, Windows 10 prefers IPv6 over IPv4 so if you now have issues using IPv6 to connect to the servers, you can change your computer’s settings so that it’ll only use IPv4 instead of IPv6. To do so, follow these instructions:
Instaling and removing applications from your Windows can sometimes leave some traces that are unpleasant and can cause annoyances. One of these annoyances is the program in the startup section of the task manager.
If you ever opened task manager and went into the startup section trying to disable some of the startup items on your Windows boot there might be a chance that you have experienced and seen a program without any icon or information about it just sitting there.
This is due to some applications being removed from the system but for some reason, it still shows itself in startup and it is quite annoying. So here we will show you how to get rid of this annoyance so your startup is clean again without junk in it.
The first thing of course is to open the task manager itself and navigate to the startup tab. Inside the startup tab right-click on the column header and tick or enable Startup type and command line. Now you will see the location of the supposed file (that is missing or you could just go there by right-clicking on the item, but here it is greyed).
99% of the time startup type will be registry since the file is missing, if it was a file fix would be just to simply delete the file in the folder but since it was installed and not properly removed registry key is still present but the file cannot be found. After confirmation that the file is indeed missing and that the startup type is registry open the registry editor by typing Regedit in search and pressing enter.
Inside Registry editor navigate to: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run. Inside on right part, you will see all auto-start entries added by installed applications.
Locate one that is causing issues by comparing its path with the path inside the task manager command line and delete the key. Once the key is deleted right-click on RUN on the left part and choose HKEY_LOCAL_MACHINE to quickly jump on that key location and repeat the process of key deletion if needed. HKEY_LOCAL_MACHINE will delete startup entry for all users and sometimes entry will not be present here since the application is not installed for all users or there are no other users on the machine.
After the procedure is finished, reboot your systems in order to apply changes.
"Error 1723- There is a problem with this Windows Installer package. A DLL required for this install could not be run. Contact your support personnel or package vendor...”You are most likely to come across the error code 1723 if the Java installation is not completed successfully. In other words, the error indicates that the installation process has failed.
chkdsk /f /r