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:

Error Code 0x80070017 is an error code that is most often associated with Windows 10 installations, although it has also been encountered by users on previous versions of the Windows operating systems. It is usually encountered as users attempt to install a new version of the software on their machine.
Common symptoms include:
While it can be hard to tell what the exact cause of Error Code 0x80070017 is on your specific device, the good news is that there are two primary methods that can be used to fix the problem and to allow you to proceed with your installation. These two methods do require some degree of technical knowledge and/or skill, so if you don’t feel like you have the ability to undertake them on your own, be sure to get in touch with a trusted computer repair professional to assist you.
Error CausesIf you purchased a physical disk version of the installation files for your Windows operating system, remove the disk from your drive and clean it using a microfiber or other lint-free cleaning cloth. As you wipe down the disk, do not use any chemicals, and be sure to wipe gently from the center towards the outside edge rather than the other direction, as failure to do so can damage the disk irreparably.
In some cases, you may need to contact Windows support if you believe that there is an error on the disk itself, such as a scratch, that would prevent the disk from being used as needed in the installation process. They may be able to offer you a replacement disk or you may be able to download a digital copy of the version that you are attempting to install on your machine.
To determine if there may be an error within the disk drive itself, place the installation disk into the drive and restart the system. Go through the prompts until you see the option to “repair your computer.” Choose the operating system that you are using, go into the menu for System Recovery, and type in the words “Chkdsk/r” to begin to use the tool.
Whenever you run a tool like Chkdsk on your computer, it is important to restart your machine afterward to ensure that any changes that have been made are able to be fully applied and accepted by the operating system that you are running.
Error Causes
Error CausesThis is a common Device Manager Error Code that users encounter. It is commonly found on all Windows 2000 and later versions of Windows operating systems. Error Code 36 is usually prompted by the following message:
"This device is requesting a PCI interrupt but is configured for an ISA interrupt (or vice versa). Please use the computer's system setup program to reconfigure the interrupt for this device. (Code 36)"
Error CausesError Code 36 occurs when there is a failure in IRQ translation due to your Windows operating system getting corrupted. This is caused due to a number of triggers, such as:
When programs are removed excessively, some programs are not removed completely and create problems in your computer’s registry.
Also, due to the presence of malware and spyware and other causes mentioned above, your computer registry builds up errors with the time that leads to slowing your PC, time lags, and even result in crashes and freezes.
Error Code 36 can cause internal and external components to malfunction or experience time lags such as DVD drive or printer and hence can severely affect your entire PC.
Error Code 36 is a severe PC error and any attempt at fixing the error must be approached with extreme caution for your PC to start functioning properly again. Here are two methods to fixing your PC.
Changing the IRQ reservation settings is the best way you can rely on to fix the error code. You can do this by changing the BIOS settings of your PC.
The BIOS stands for ‘Basic Input/Output System’ and is the program of your PC’s microprocessor that allows your PC to boot after you switch it on.
Caution needs to be exercised before changing the BIOS settings of your PC. This is because every PC’s BIOS version differs from another and any wrong attempt to change the settings may make matters worse.
It is therefore recommended to refer to hardware documentation that you received with your PC or motherboard and check for the model number and details of your PC’s motherboard.
Only after you have checked and confirmed all the details, should you use the specific BIOS settings required to configure your IRQ reservations?
Error Code 36 isn’t an easy error to remove.
While changing the BIOS settings can work to restore your PC, it may create a whole lot of inconvenience for finding the time and effort to check the hardware documentation details and attempting to change the specific settings and especially, if your PC does not support the options to change IRQ reservations.
Given the high risks of fixing such an error, you can also install software that enables you to fix your slow PC at the click of a few buttons.
Programs such as DriverFIX can enable you to download and replace your outdated drivers with new updated ones without you having to look for them. It will detect which drivers to download based on your PC’s motherboard version from the program’s database and can get rid of error code 36.
Click here to download DriverFIX and remove error code 36 and any other type of Device Manager error from your PC.
If you are one of the gamers affected by this error, fear not because we have a solution for you. Follow provided fix guide in order to correct this error and get back to gaming asap.
Windows 11 is a good-looking operating system but people love to make things personal and to their liking so we decided to help you in this mission with small customization of changing default system fonts inside Windows 11.
Since there is no really easy way to just switch the font windows is using for itself we will have to tweak a registry a little so before we start please do make a backup of the registry file and follow the steps as they are presented in order to avoid any errors and break the system.

So, if all precautions are made and you are ready to change your Windows appearance let's dive right into it:
There are vast free font sites on the internet where you can find fonts that you like and wish to use but be very careful with your desired font selection. The font that you choose needs to be a complete typeface, meaning that it has to contain all glyphs, large and small font sizes, all special characters, etc or you will experience that in certain areas nothing will be displayed.
Once you have found the font that you like and made sure it is a complete font, install it on your system (you can skip this step if you just want to change the system font with one already installed on your system)
Open notepad or a similar plain text editor in order to create a file that will apply changes directly into the registry and create a new file. Inside the file paste this text:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts]
"Segoe UI (TrueType)"=""
"Segoe UI Bold (TrueType)"=""
"Segoe UI Bold Italic (TrueType)"=""
"Segoe UI Italic (TrueType)"=""
"Segoe UI Light (TrueType)"=""
"Segoe UI Semibold (TrueType)"=""
"Segoe UI Symbol (TrueType)"=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes]
"Segoe UI"="NEW-FONT"
All the way to the bottom where it says: "Segoe UI"="NEW-FONT", change NEW-FONT with the font name that you have chosen or installed in the previous step. For example: "Segoe UI"="Ubuntu".
Now go to File > Save As and name your file however you want but give it REG extension so it looks like: my_new_windows_font.REG
Now that you have your registry entry saved, locate it and double-click on it, at this stage Windows warning will probably pop up, you can just ignore it and click on YES since you wrote the file and know what it is. After registry entry is applied reboot your PC in order for changes to take effect.
If you want to change the font to another one, just repeat this procedure again. If you want to roll back to using the default Windows font, repeat the process but with this code instead of the one provided in the REG file:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts]
"Segoe UI (TrueType)"="segoeui.ttf"
"Segoe UI Black (TrueType)"="seguibl.ttf"
"Segoe UI Black Italic (TrueType)"="seguibli.ttf"
"Segoe UI Bold (TrueType)"="segoeuib.ttf"
"Segoe UI Bold Italic (TrueType)"="segoeuiz.ttf"
"Segoe UI Emoji (TrueType)"="seguiemj.ttf"
"Segoe UI Historic (TrueType)"="seguihis.ttf"
"Segoe UI Italic (TrueType)"="segoeuii.ttf"
"Segoe UI Light (TrueType)"="segoeuil.ttf"
"Segoe UI Light Italic (TrueType)"="seguili.ttf"
"Segoe UI Semibold (TrueType)"="seguisb.ttf"
"Segoe UI Semibold Italic (TrueType)"="seguisbi.ttf"
"Segoe UI Semilight (TrueType)"="segoeuisl.ttf"
"Segoe UI Semilight Italic (TrueType)"="seguisli.ttf"
"Segoe UI Symbol (TrueType)"="seguisym.ttf"
"Segoe MDL2 Assets (TrueType)"="segmdl2.ttf"
"Segoe Print (TrueType)"="segoepr.ttf"
"Segoe Print Bold (TrueType)"="segoeprb.ttf"
"Segoe Script (TrueType)"="segoesc.ttf"
"Segoe Script Bold (TrueType)"="segoescb.ttf"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes]
"Segoe UI"=-
Error Causes“Windows cannot install required files. Network problems may be preventing Windows from accessing the file. Make sure the computer is connected to the network and restart the installation. Error code: 0x80070006.”As stated in the error message, this kind of error in Windows Setup is due to an unstable or unreliable network connection. Such problems can also be triggered by network hardware which includes the network adapters and the network routers. To fix this error, you need to check your internet connection and router or run the built-in network troubleshooter. You could also try using a different USB port or recreate a bootable USB drive as well as get a new Windows image file.