Add names of applications in the taskbar

There are a lot of users who use their Windows 10 PCs to create and access data on their servers using their network. However, some of them reported getting an error saying that the server is not accessible. Here’s the full content of the error message:

“\server is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. Logon Failure: The target account name is incorrect.”

If you are among the users who experience the same issue, read on as this post will help you resolve this error when accessing your server. But before you start troubleshooting the problem, you might want to perform System Restore, especially if tend to create one. To use System Restore, here’s what you have to do:

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

If System Restore didn’t help in fixing the ACPI.sys Blue Screen error now’s the time for you to make use of the potential fixes laid out below.

Option 1 – Try rebooting your router

The first thing you can try to do to fix the error is to simply restart your router. All you need to do is reboot the router from its Admin panel or you can also turn it off manually and turn it back on after a couple of seconds so that it can completely reboot. Once you’re done, try accessing your server again and see if the error is now fixed.

Option 2 – Try checking the status of the Workstation Service

You might want to check the status of the Workstation Service as the error might have something to do with it.

• Tap the Win + R keys on your keyboard to launch the Run utility.
• Then type “services.msc” in the field and click OK or hit Enter to open the Windows Services Manager.
• After opening the Services Manager, you will see a list of all the services on your computer and from there, locate the Workstation Service.
• Double click on the Workstation Service to open its Properties.
• Next, Stop the Service and Start it again or you can also right-click on it and select Restart and then make sure that its Startup type is set to Automatic.
• Now restart your computer and check if the error is fixed.

Option 3 – Try to change the File Sharing Connections setting

You can also try to change the File Sharing connections setting. All you have to do is go to Control Panel > Network and sharing center > Advanced sharing settings > File sharing connections. From there, you need to select “Enable file sharing for devices that use 40 or 56-bit encryption and check if it helps in fixing the problem. If not, undo the changes you’ve made and proceed to the next given option.

Option 4 – Try checking the Network Configuration

Checking the Network Configuration can also help you fix the error. Refer to the steps below to do so:

• Right-click on the Wi-Fi connection or on the Ethernet connection icon located in the system tray.
• Then select open Network and Internet Settings and then click on the “Change Adapter Options”.
• After that, a new window will appear and from there, select the network connection that connects your computer to your network – this can either be a Wi-Fi connection or Ethernet connection.
• Right-click on that connection and select Properties where you will see a list of items.
• Select the Internet Protocol Version 4 or Internet Protocol Version 6 from those items according to your system requirement.
• Then click on the Properties button.
• Check if everything is now configured as to how it is supposed to be and then check if the error is resolved.

Option 5 – Try to reset Winsock, TCP/IP & Flush DNS

You might also want to try resetting Winsock, TCP/IP, and flushing DNS might help you resolve errors. To do so, follow these steps:

• Right-click on the Start button and click on Command Prompt (administrator) so you can pull up an elevated Command Prompt.
• After that, execute each one of the commands listed below. And after you typed in one after the other, you have to hit Enter.

1. netsh winsock reset – type in this command to reset Winsock
2. netsh int ip reset resettcpip.txt – type in this command to reset TCP/IP
3. ipconfig /flushdns – type in this command to flush the DNS cache

• Next, restart your PC and check if the problem’s fixed.

Option 6 – Run the Network Adapter Troubleshooter

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.

JavaScript Void 0 Error - What is it?

JavaScript is a computer programming language used to make a website work smoothly with the internet. It helps to display visual effects, animations, and other web page functions. You may come across the JavaScript Void (0) error message when there is a problem in loading JavaScript from a web page or the internet browser.

Error Causes

JavaScript Void (0) error is triggered by multiple reasons such as:

• It can be due to a simple random Windows application glitch.
• You are visiting an unsafe website that contains malware
• JavaScript’s web browser implementation  is broken due to poor program installation
• Active X controls, Java applets, and active scripting, the key components of JavaScript are disabled
• Registry issues like invalid or misconfigured registry keys

Further Information and Manual Repair

For JavaScript Void (0) error-free web surfing, it is advisable to repair the issue without any delays. Let’s take a look at different methods to resolve this error on your system.

Cause: Simple Random Glitch

Solution: If the cause for the JavaScript Void 0 error is a simple glitch, then it is advisable to restart your system and then run the program again.

Cause: JavaScript’s web browser implementation is broken

Solution: If you experience the JavaScript Void 0 error message after the installation of the new browser on your system, then poor installation of the program or program conflict is most likely to be the deep-rooted cause of this error code. To resolve it, uninstall the program and undo the recent changes.

Cause: Active X controls, Java applets, and active scripting, the key components of JavaScript are disabled

Solution: You should know that components including Active X controls, Java applets, and active scripting are all essential to JavaScript in order to make your browsers run properly. If these are disabled, you may come across the JavaScript Void (0). To fix it open your browser and select the Tools tab. Then click the options button and select content. Here check the ‘enable JavaScript’ check box and click Ok to enable these components.

Cause:  Registry Issues

Solution: If after performing all the solutions discussed above, you still come across JavaScript Void (0) error code, then you should know that the problem is bigger than what you expected. It triggers registry issues. Either the cause of the error is misconfigured or invalid registry keys. To reconfigure the registry keys setting may be a challenging task and complex if you are not a computer programmer.

When clean Windows is installed or when you place new hardware in your computer usually Windows itself detects the device and installs its driver. The question that comes now is, do you keep that driver or do you install the manufacturer's one. In order to answer this question let's analyze what is difference between the two drivers and other factors which could influence your decision.

Difference between drivers

First of all, know that drivers Windows installs are also drivers from the device manufacturer which have gone through Microsoft quality control in order to be included in Windows itself. Now naturally question which occurs, what is the difference, well answer to that would be this: in Windows, you have stripped down driver, just a driver in order for Windows to know what device is plugged and how to use it, meaning that for example if you install printer device, you will be able to print documents and Windows will know it is a printer but ... You will not get the control panel for that printer where you can adjust the printer itself and all of its features like let's say paperweight, etc. So if you need these kinds of features in that case it would be better to install a complete driver suite from the manufacturer and get the whole package. Windows will recognize the RAZER mouse for example but you will not be able to change its colors of program custom buttons on it until you install RAZER drivers. One more important thing to note is that drivers which are in Windows are less updated than drivers from the manufacturer's site. That being said, if you prefer and want to have the latest drivers you will prefer to get them again from the manufacturer.

Conclusion

So it seems that manufacturer's drivers are always in some form of advantage and that you will always want them and most of the time this is true, as a matter of fact, the only time I could think that you could use bare down Windows drivers is when new drivers update breaks something in Windows and device start behaving improperly. in this particular case, it is better to roll back to the previous Windows driver which has passed Microsoft quality control and is working for sure. In any other case, you are better off with the latest manufacturers drivers If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

Error 1310 is a fairly common type of error encountered by Windows users. Error 1310 usually generates while a user is attempting to install Adobe Photoshop or some Adobe product on Windows. The message displayed to the user usually states: ‘Error 1310. Error writing to file. Verify you have access to that directory’. Once the error message appears, the installation process will be terminated.

Solution

Error Causes

While there are different conditions that may trigger this error, most likely, they are generated because of the lack of privileges a user has on a Windows log-on. When this happens, the operating system doesn’t allow the user to access the installation files. Another reason Error 1310 may occur is that often users attempt to log on to the system and choose the ‘Only for me’ option rather than the recommended ‘Anyone who uses this computer’. Because of this reason, the data is locked for all the other users. Since Error 1310 can easily disrupt your workflow on the system and may also lead to annoying consequences, it is best advised to treat it as quickly as possible.

Further Information and Manual Repair

There are different solutions to resolve these errors that are briefly listed below as follows.

• First and foremost, restart the installation by logging onto your computer from the administrator account. This error will most likely disappear because there is often a lack of privileges that will trigger it. When you will log on from the admin account, you will have access privileges and such errors will be rectified.
• Fix any corrupt system files that exist on your system. If the file resides in the Windows directory, this error will be generated. Check if any of your system files are corrupt or damaged. If yes, make sure you repair and return them back to their original position.
• This error is sometimes caused because of incorrect registry entries. If the setup program shows errors, it is possible that it is because the system is having problems retrieving data stored in the system registry.
• Another way, this error can be avoided is to run the setup in compatibility mode. Compatibility issues are a common occurrence. However, when an installation is performed in the compatibility mode, one can easily steer clear of such errors.

Implement any of the solutions listed above and protect your system against Error 1310.

Disk cleanup is part of Windows 10 tools and it is essential in keeping your computer up and running in optimal settings and to free so much needed space as well as remove temporary files that can accumulate over time. Using disk cleanup from time to time is recommended and a very useful habit that will save you some headaches and optimize your computer running time, speed up boot sequence, etc. Think of it like cleaning up your desk, from time to time it can get too overwhelmed with junk and non-important things and if you are keeping it tidy all the time each time you need to find something it will be much faster and easier, same goes with computers, so if you do not have it, try to develop a habit that once per month you start disk clean up and remove trash from your hard drive. In order to do so, press ⊞ WINDOWS + E to bring File Explorer up Once File Explorer is up and running right-click on the hard drive you wish to run disk cleanup on and click on properties. Properties Windows will open on the general tab, on that tab you have disk cleanup on the lower right part of properties, click on it. Wait for Windows to gather information about your hard drive and files on it. After it is finished you will be greeted with the next screen: Here you can thick and mark which items you would like to get rid of and which ones you would like to keep. Note that you can freely tick all of them and remove them since removing these files will not break WIndows in any way. make your choices and click on ok. You can also click on Clean up system files to run system files cleaner and get rid of junk there, you will not be able to choose any options there, Windows will alone clean up what is not needed. After disk cleanup is finished least thing you will have is more free disk space, but like mentioned, keeping your Windows and computer healthy goes a long way in its usability, speed, and performance.

If you encounter Windows Update error 0x80092004 while trying to update your Windows 10 computer, then this post is for you. This kind of Windows Update error could be due to many reasons but none of them includes your hardware or installed driver software. Microsoft releases updates that are either not supposed to go out, or you install them when you click on the Check for Update button which can install updates that have not finished testing yet. As a result, you may encounter the Windows Update error 0x80092004 To resolve the Windows Update error 0x80092004, here are some fixes you can try.

Option 1 – Try removing recent updates and packages

When a Windows Update fails, it mostly rolls back and cleans up all its residues. However, there are times when it doesn’t and you can clean that package manually. To remove recent updates and packages, you can go to the Update History and find out what KB updates were installed and once you’ve figured it out, you can execute the DISM tool to remove it manually.

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, execute the “Dism /online /Get-Packages”. This will give you a list of packages that were recently installed.
• Now run the Remove Package program to remove the concerned update and package.

dism.exe /online /remove-package /packagename:Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~16299.248.1.17 /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.125.1.6 /packagename:Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~16299.192.1.9 /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9 /norestart

• Now restart your computer and log back in.
• After that, run the following command:

Dism.exe /online /Cleanup-Image /StartComponentCleanup

• Then scan for updates.

Note: Keep in mind that the remove package command is made for AMD 64-bit machines specifically.

Option 2 – Try deleting the files from the SoftwareDistribution folder and resetting the Catroot2 folder

The downloaded Windows Updates are placed in a folder called “SoftwareDistribution”. The files downloaded in this folder are automatically deleted once the installation is completed. However, if the files are not clean up or if the installation is still pending, you can delete all the files in this folder after you pause the Windows Update service. For complete instructions, refer to the steps below.

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net start cryptSvc net start bits net start msiserver

• After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
• Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.

After resetting the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:

• Type each one of the following commands.

net start wuauserv net start cryptSvc net start bits net start msiserver

• After that, exit Command Prompt and restart your computer.

Option 3 – Try to run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the “We couldn’t install some updates because the PC was turned off” error. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 4 – Try to manually install the Windows Updates

Windows Update Error 0x80092004 might be due to a Windows Update that has failed. So if it is not a feature update and only a cumulative update, you can download the Windows Update and install it manually. But first, you need to find out which update has failed, and to do so, refer to the following steps:

• Go to Settings and from there go to Update and Security > View Update History.
• Next, check which particular update has failed. Note that Updates that have failed to install will be displayed under the Status column which has a label of “Failed”.
• After that, go to the Microsoft Download Center and look for that update using its KB number and once you find it, download and then install it manually.

Note: You can also use the Microsoft Update Catalog, a service from Microsoft that provides a list of software updates that can be distributed over a corporate network. With the help of this service, it can be easier for you to find Microsoft software updates, drivers as well as fixes.

Stop C00002lA Fatal System Error- What is it?

C00002lA Fatal System Error is a blue screen of death error that may occur when you start your Windows NT 4.0 based computer. This error causes the screen to turn blue and the system also shuts down. The stop C000021A error message is displayed in the following format:

Stop c000021a {Fatal System Error} The session manager initialization system process terminated unexpectedly with a status of 0xc0000017 (0x00000000, 0x0000000) The system has been shut down.

Error Causes

The stop C000021A error occurs when either Crsrss.exe or Winlogon.exe fails. When the Windows NT kernel identifies that either of these processes has failed, it stops and the error code stop C000021A appears on the computer screen. Here are some of the underlying causes for the stop C0000021A error:

• The incompatible third-party program
• Hard disk issues
• Service pack installation has failed
• Mismatched system files have been installed
• Bad and invalid registry keys

Further Information and Manual Repair

To resolve the stop C000021A Fatal System Error on your PC try the following solutions:

• Remove Incompatible Third Party Programs

If the error occurred after you recently installed a new program, then it is advisable to remove that program. The error occurs due to the incompatibility of the program. To remove the program go to the start menu and click on the control panel. Now click on Add/Remove Program tab and double click on the program name that you recently installed and remove it from the list. Once removed, not reboot your PC. Reinstall a compatible program and run it. It is most likely to resolve the issue. However, if the stop C000021A error still occurs, then it means the problem is critical. It is related to the registry.

• Repair and Restore the Registry

This procedure is slightly long and tricky. To try it, you need to be technically sound. Here’s what you have to do: first create a parallel installation of Windows NT. Start your PC to the parallel installation and then open the Registry Editor. On the Registry Editor’s Windows menu click HKEY_LOCAL_MACHINE on Local Machine and then click Load Hive. Now type the path %systemroot%system32configsystem into the System hive of the prior installation. Then click open. Here you will be prompted to enter the name of the key, type TEST. Note the setting for the current DWord value in the preceding registry key. This is 0x1 and is denoted by CURRENT:Reg_Dword: 0x1. This value indicated that the Current Control Set for your original Windows NT installation corresponds to ControlSet001 in this window. Now if the value is 2, it indicated that the Current Control Set corresponds to ControlSet002. Now locate the following registry key: HKEY_LOCAL_MACHINETESTControlSetXXXControlSession Manager. XXX is the Current Control Set Value. And delete any pending file rename operation entries. Then click TEST hive and then click Unload Hive. After that again repeat the process, open the registry menu and click load hive, here type the path %systemroot%system32configSoftware to the Software hive of the prior installation and then click open. Now you type TEST 2 when you are prompted for the name of the key. Remove any pending file rename operations entries in the following registry keys: HKEY_LOCAL_MACHINETEST2MicrosoftWindowsCurrentVersionRunOnce HKEY_LOCAL_MACHINETEST2MicrosoftWindowsCurrentVersionRunOnceEx Now click TEST2 hive and then click unload hive. Quit the Registry Editor and then restart your original installation. This will resolve the stop C000021A error.

DLL files have certain functions that help the programs in the computer run properly. One of these DLL files is the Msvcr120.dll_clr0400.dll. This particular DLL file is responsible for the extraction of the required resources during the installation of a program and is used when the program is launched or when games are launched in the C++ language. However, a number of users recently reported that they’ve encountered an error that says, “Msvcr120.dll_clr0400.dll is missing” when they tried to install an application or when they tried opening an application. This kind of error could be due to several factors. It is possible that the DLL file is corrupted or there are some programs that interfere with the DLL file. On the other hand, it is also possible that it has been infected by a virus. To resolve this error, here are some potential fixes you need to check out:

Option 1 – Run System File Checker scan

The first thing you can do to fix the error is to try running the System File Checker or SFC scan. System File Checker is a command utility built into your computer that helps restore corrupted files and missing files. Refer to the following steps to run it:

• Hit the Win + R keys to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Reboot your computer.

Option 2 – Troubleshoot the missing Msvcr120.dll_clr0400.dll error in a Clean Boot State

You can also troubleshoot the isDone.dll error in a Clean Boot state. It could be that there are some third-party applications in your computer that are preventing the application from getting installed and to isolate this possibility, you need to boot your computer in a Clean Boot State and then try installing the program again. Putting your computer in this state can help you identify which program is the culprit and thus isolates the problem. In a Clean Boot state, your computer will start using only the pre-selected minimal set of drivers and startup programs. Note that you have to disable and enable one process at a time.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• After you’ve set your computer into a Clean Boot State, make sure that you’re signed in as administrator and then try to install the application again.

Option 3 – Try to re-register the problematic DLL file

You can also try to re-register the DLL to resolve the problem. The Regsvr32 tool is a command-line utility that can be used to register and unregister OLE controls like DLL and ActiveX (OCX) controls in the Windows operating system. Follow the steps below to use it.

• Open Command Prompt as admin from the WinX menu.
• Next, type the following commands in the elevated Command Prompt and hit Enter to execute the command. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.
  • exe /[DLL file]
  • exe [DLL file]

Note: Replace “[DLL file]” with the name of the DLL file that was pointed out in the error.

• After you execute the given commands, you should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. After that, try to install the program again and see if it now works.

Option 4 – Try to replace the DLL file with a trusted source

• First, you need to get the new DLL file from another computer with preferably the same file version number.
• After that, you need to boot your PC into Safe Mode and navigate to the paths listed below and then replace the file using a USB drive or other external storage devices.
  • x86: This PC > C:WindowsSystem32
  • x64: This PC > C:WindowsSysWOW64
• Next, type “cmd” in the Cortana search box and right-click on Command Prompt, and select “Run as administrator” to open it with administrator privileges.
• Now type the “regsvr32 ntdll.dll” command and hit Enter.
• Restart your PC and check if the error is now fixed.

Option 5 – Scan your computer using Windows Defender

The DLL file might also be infected with malware or virus and to eliminate it which could explain why you’re getting the “Msvcr120.dll_clr0400.dll is missing” error. Thus, you have to scan your computer using security programs like Windows Defender.

• Tap the Win + I keys to open Update & Security.
• Then click on the Windows Security option and open Windows Defender Security Center.
• Next, click on Virus & threat protection > Run a new advanced scan.
• Now make sure that Full Scan is selected from the menu and then click the Scan Now button to get started.

It is no secret that Fortnite is one of the most played games in the world. Epic has done a great job offering it to plenty of other platforms with cross-play feature meaning that you can play with your friends no matter on what platform they are on. But how Fortnite is a piece of software which is constantly updated and maintained it is pretty normal to have some bugs or issues from time to time. One of the before-mentioned issues is a connection issue or unable to connect to game servers. In our article, we will go through common fixes and solutions in order to get you back in-game as fast as possible. Keep on reading.

Check the Epic Games Status page

Check the Epic Games Server Status page to make sure all systems are operational. If the issue you’re experiencing is related to an outage or system-wide issue, you won’t be able to connect to the Epic Games Launcher or Fortnite until it's resolved.

Use a wired connection

Wireless connections are not as stable as wired connections. This means that the signal can be unreliable and result in packet loss, connection problems, or higher latency or ping. Connect directly to your modem or router with an Ethernet cable to eliminate this possibility and have the fastest connection possible.

Disable your firewalls

Often the quickest way to fix connection problems due to firewalls is to temporarily uninstall and/or disable it.

Windows Firewall disable guide:

1. Click on Start.
2. Click on Control Panel.
3. Click on System and Security.
4. Click on Windows Firewall.
5. Click on Turn Windows Firewall on or off (You might need to provide the Administrator password at this step)
6. Under each Network location, select the Turn off Windows Firewall option

Uninstall any other firewalls

Using a third-party firewall may prevent you from being able to connect to the Epic Games Launcher, Fortnite, or another Epic Games product. We recommend removing any third party firewalls temporarily to see if this resolves your issue. If it does resolve the problem, make sure to add the following executables as exceptions to your firewall:

Epic Games Launcher

• C:\Program Files (x86)\Epic Games\Launcher\Engine\Binaries\Win64\EpicGamesLauncher.exe
• C:\Program Files (x86)\Epic Games\Launcher\Engine\Binaries\Win32\EpicGamesLauncher.exe

Fortnite

• C:\Program Files\Epic Games\Fortnite\FortniteGame\Binaries\Win64\FortniteClient-Win64-Shipping.exe
• C:\Program Files\Epic Games\Fortnite\FortniteGame\Binaries\Win64\FortniteClient-Win64-Shipping_BE.exe
• C:\Program Files\Epic Games\Fortnite\FortniteGame\Binaries\Win64\FortniteClient-Win64-Shipping_EAC.exe
• C:\Program Files\Epic Games\Fortnite\FortniteGame\Binaries\Win64\FortniteLauncher.exe

Contact your firewall manufacturer for instructions on how to add these as exceptions to it as this varies between them.

Unblock your network ports

Network ports allow certain types of data to be successfully sent over a network that is used by our services. If you have any of these blocked, it may result in you being unable to connect to our games or use our services properly. To unblock your ports on your router do the following:

Windows

First, you will need to get your default gateway and internal IP address:

1. Click on Start.
2. Type cmd and press Enter.
3. Type ipconfig and press Enter.
4. Take note of your Default Gateway and IPv4.

Configuring your router to unblock the ports

1. Open your web browser.
2. Type your Default Gateway into the address bar and press Enter. (A common Default Gateway is 192.168.1.1)
3. You may be asked for a username and password. This varies for each router. Before entering anything, try just hitting OK. If that doesn't work, try the common default username and password below: Username: admin Password: password If these don't work, you can check this website for a list of usernames and passwords based on your router model.
4. Locate the Port Forwarding page in the administration tool and click on it.
5. Make sure you have Port Forwarding selected and not Port Triggering as this is completely different.
6. On this screen, you will need to enter the ports and port ranges below with the correct protocol and local IP of which you took note of above: 80 (TCP/UDP), 433 (TCP), 443 (TCP), 3478 (TCP/UDP), 3479 (TCP/UDP), 5060 (TCP/UDP), 5062 (TCP/UDP), 5222 (TCP), 6250 (TCP/UDP), and12000-65000 (TCP/UDP).

If you have any trouble doing the above on your router, make sure to check out the router manufacturer's support site for additional instructions as these will vary from router to router.

VPN and Proxy Servers

Do NOT use VPN or Proxy Servers. These cause issues that can't be resolved by us without having you disable them. Check out this article for information on how to disable your proxy server.

Switch Domain Name Systems (DNS)

Switching your DNS can result in better connectivity and performance for your internet connection. There are two different DNS services we recommend to have you try if you are having issues with your connection. Below are the followings links with instructions on how to change your DNS:

• GoogleDNS
• CloudflareDNS

Epic Games Launcher: Edit your Engine.ini file (Windows only)

Editing these settings can result in better download speeds using the Epic Games Launcher:

1. Click on Start.
2. Type %localappdata% and press Enter.
3. Open the EpicGamesLauncher
4. Open the Saved
5. Open the Config
6. Open the Windows
7. Open ini and add the following lines to it: [HTTP] HttpTimeout=10 HttpConnectionTimeout=10 HttpReceiveTimeout=10 HttpSendTimeout=10[Portal.BuildPatch] ChunkDownloads=3 ChunkRetries=20 RetryTime=0.5
8. Save the file and open the Epic Games Launcher.

Lately, some users reported getting an error that says, “System doesn’t have any USB boot option, Please select other boot option in Boot Manager Menu” when they tried to reinstall the Windows 10 operating system on their PCs or boot from an installation media. If you have the same problem, then this post should help. This kind of error is applicable to multiple devices by various OEMs and is mostly due to the Secure boot being enabled, or the Legacy or CSM support being disabled. It could also be that the bootable USB device was not correctly made and so on. Whatever the cause may be, here are some suggestions you need to check out to resolve the “System doesn’t have any USB boot option, Please select other boot option in Boot Manager Menu” error and reinstall Windows 10 successfully.

Option 1 – Disable the Secure Boot in the BIOS

Disabling the Secure Boot in the BIOS settings is definitely recommended to resolve the error. To disable Secure Boot, here’s what you have to do:

• First, boot your computer into Windows 10.
• Next, go to Settings > Windows Update. From there, check if there is anything that you have to download and install if you see any available updates. Usually, OEMs send and update the list of trusted hardware, drivers, and operating systems for your computer.
• After that, go to the BIOS of your computer.
• Then go to Settings > Update & Security > Advanced Startup options. If you click on Restart Now, it will restart your computer and give you all the advanced options.
• Next, select Troubleshoot > Advanced Options. As you can see, this screen offers you further options including System restore, Startup repair, Go back to the previous version, Command Prompt, System Image Recovery, and UEFI Firmware Settings.
• Select the UEFI Firmware Settings which will take you to the BIOS.
• From there, go to the Security > Boot > Authentication tab where you should see Secure Boot. Note that every OEM has its own way of implementing the options so it varies.
• Next, set Secure Boot to Disabled and set Legacy Support to On or Enabled.
• Save the changes made and exit. Afterward, your computer will reboot.

Option 2 – Try to reset the BIOS or the UEFI Settings

If updating the BIOS didn’t help in fixing Error 0199, you can try to reset the BIOS instead.

• Start your computer and tap the F10 key during the booting process to enter the BIOS. If it does not work, you can try tapping the F1 or F2 key as well as the Del key.
• Once you’re already in the BIOS, tap the F9 key to get the prompt to RestoreLoad default configuration now for the BIOS.
• Next, click on Yes and then follow the next on-screen instructions that appear to set the BIOS back to its default settings.
• Once you’re done restoring the default settings of the BIOS, restart your computer and then check if it now boots properly.

Option 3 – Make a proper bootable USB Drive/Stick

To make a proper bootable USB drive, you need to use the Windows Media Creation tool. The Media Creation tool in Windows allows you to use the ISO installation file to make a bootable device that you can use to install Windows on your PC. Note that this is kind of different from the usual installation process as it could erase your computer’s current settings and data on the primary drive. Thus, before you proceed, you need to backup all your data into some removable drive and then use the Media Creation Tool to make a bootable drive.

• After making the bootable drive, you need to plug it into your computer and then reboot.
• Next, tap the F10 or Esc key to open the boot options.
• Now set the boot priority of the removable drive the highest. Once the setup comes forth, follow the next onscreen instructions and install Windows without any problems.

Option 4 – Try enabling Legacy or CSM boot support

If the Legacy or CSM boot support is disabled, then it’s no wonder why you’re getting an error. Thus, you need to enable it by following these steps:

• Open Settings and go to Update & Security > Advanced Startup options.
• Next, click on Restart Now to reboot your computer.
• After that, select Troubleshoot > Advanced Options where, you will see more options such as System Restore, Startup Repair, Go back to the previous version, Command Prompt, System Image Recovery, and UEFI Firmware Settings.
• From there, enable Legacy Support and then save the changes and exit. This will restart the computer.
• Once your computer has restarted, check if the error is now fixed.