Changing the Primary and Secondary monitor

Fix Remote Desktop: Your credentials ...

Experiencing issues while using Remote Desktop connections is not uncommon. One of the issues that users encountered recently while trying to connect to their Remote Desktop network is the error saying, “Your credentials did not work, The login attempt failed”. If you are one of these users, then you’ve come to the right place as this post will walk you through fixing the problem. When facing this kind of problem, the first thing you can try before you do some troubleshooting steps is to verify the credentials. But if you are certain that you’ve entered the correct credentials just like what other users reported, then it’s completely a different matter. Based on the reports, this error is common on newly installed versions of Windows 10 or after reinstalling the operating system which could mean that the problem might be due to the Windows security policies or the username might have been recently modified. The latter case is a possibility especially if you’ve reinstalled Windows 10 and had entered a new username. In such a case, you will really have a difficult time connecting to your Remote Desktop connection since its credentials do not really automatically change. If you’ve verified that your credentials are correct, then now’s the time you troubleshoot the problem with the help of the potential fixes provided below. Just make sure that you follow each one of them in sequence.

Option 1 –Try to run the Network Adapter troubleshooter

To run the Network Troubleshooter, refer to these steps:

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.
Restart your computer.

Option 2 – Try to change the network profile from public to private

According to some reports, this error occurs on systems where the network profile was set to public. Thus, you need to change the network profile to private to resolve the problem. How? Refer to these steps:

Go to Start and from there click on Settings > Network & Internet > Status.
Next, click on the “Change connection properties” option.
After that, set the radio button of Network Profile from Public to Private.
Wait for a couple of seconds until the system is done applying the changes you’ve made and then see if you can now connect to the Remote Desktop connection.

Option 3 – Try changing the account username

As mentioned, one of the possible causes for this error is the reinstallation of the operating system. You might have changed the username for the system but it does not really change the username of the Remote Desktop connection as well. Thus, you have to change the username back to what it was before you’ve reinstalled Windows 10.

Option 4 – Try modifying the Windows Security Policy

You can also try to edit the Windows Security Policy as it could help in resolving the error. This Windows Security Policy, when enabled, will not allow non-admin users to log on to the Remote Desktop connection. So if you want to allow non-admin users to use the Remote Desktop connection, then you need to modify this policy. Note that you can only do that if you are the admin of the system yourself.

Tap the Win + R keys to open the Run utility.
Then type “secpol.msc” in the field and tap Enter or click OK to open the Local Security Policy.
After opening the Local Security Policy window, select Local Policies > User Rights Agreement located on the left pane.
Next, double click on “Allow log on through Remote Desktop Services” located in the right pane.
And in the next window that appears, select Add user or group.
After that, type in the username of the intended non-admin user under the “Enter the object names to select” column.
Once done, click on the Check Names button to fix the username and then click OK to save the changes made.
Restart your computer.

Option 5 – Use the Group Policy Editor

Tap the Win + R keys to open the Run dialog box and then type “gpedit.msc” in the field and tap Enter to open the Group Policy Editor.
Next, navigate to this path: Computer Configuration > Administrative Templates > System > Credentials Delegation.
Double click on the “Allow delegating default credentials with NTLM-only server authentication” policy setting located on the right pane to edit it.
After that, shift its radio button to Enabled and click on Show.
Then type “TERMSRV/*” in the Value box and click OK.
Now repeat the same for the following policy settings:
- “Allow delegating default credentials”
- “Allow delegating saved credentials”
- “Allow delegating saved credentials with NTLM-only server authentication”

Once you’re done, restart your computer and see if the problem is fixed.

Could not configure one or more components

If you are trying to install or upgrade your Windows 10 computer but suddenly encountered an error message saying, “Windows could not configure one or more system components”, read on as this post will show you how you can fix the problem. You are not alone in experiencing this problem as other users also reported having the same scenario. Some of them reported getting the following error message:

“Windows could not configure one or more system components. To install Windows restart the computer with error code 0xc1900101-0x30018.”

When you check on the Windows 10 rollback log, you will see a part with the “iisetup.exe” that’s related to the abort. Usually, the upgrade process completes over 50% and gets stuck and then rolls back later on and generates the error logs. This kind of error, in most cases, appears during the upgrade of Windows 10 and is related with the Internet Information Services or IIS in Windows 10. For some unknown reason, it restricts the installation or the upgrade which causes the error to appear. To fix the “Windows could not configure one or more system components” error, you can try to remove the IIS from the Windows Features or rename the “inetsrv” folder. You could also move all the folders related to IIS to another drive. For more details, refer to the options provided below.

Option 1 – Try to remove the IIS from Windows Features

The IIS is installed from the Windows Features and you can find it at Control Panel > Programs. From there, uncheck the checkbox for the Internet Information Services. Once done, click on the OK button to save the changes. Note that this process will get rid of all the related programs, services, and folders from Windows 10. So if you want to, you can just install them later on or use an offline installer from the official site of Microsoft.

Option 2 – Try renaming the inetsrv folder

The next option you can check out to resolve the problem is to rename the “inetsrv” folder. If you have uninstalled IIS from the Windows Features, this should remove the folders as well, however, it didn’t remove the folder then you have to delete the folders that are related to the IIS by following these steps:

First, you have to boot into the Advanced Recovery Mode and from there, open Command Prompt.
Next, execute this command to rename the folder from this location, C:Windowssystem32inetsrv: rename C:/Windows/system32/inetsrv/inetsrv.old
Once done, boot into your computer normally and try to upgrade Windows 10 again, and check if the problem is fixed or not.

Option 3 – Try to move the folders related to IIS to a different drive

Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
Next, look for the Application Host Helper Service from the list of services and stop it.
Once done, take ownership of the “WinSxS” folder and then move the *windows-iis*.*” folders to another drive. You can just search using the “*windows-iis*.*” keyword in the Start Search.
Next, tap the Ctrl + X keys and paste the folders to another drive.
After that, start the update process for Windows 10 again.

A Quick Guide to Resolving Photoviewer.dll Error

Photoviewer.dll Error - What is it?

Photoviewer.dll is a shared library for SampleRes.dll and x3daudio1_1.dll in computers installed with Microsoft Windows 7, 8, Vista, and XP including 32 bit and 64 bit operating systems. Photoviewer.dll is associated with 1728000 system files. The Photoviewer.dll error occurs when you upgrade your Windows operating system to a new version like Windows 7 or 8 on which this shared library is used. Once you upgrade the Windows and you right-click on JPG images, the Photoviewer.dll error pops up. This error message is displayed as the following:

Photoviewer.dll missing/not found
Photovewer.dll entry point not found/application can’t initiate

Solution

Error Causes

Photoviewer.dll error can pop up due to several reasons. These include:

Modification of .dll files during Windows installation
Infection of Trojan virus
Photoviewer.dll missing /broken
Photo Gallery was earlier your default image editor before you upgraded your system

It is advisable to repair this issue timely to avoid inconvenience and serious PC threats especially if the cause of this issue is viral infection or registry damage.

Further Information and Manual Repair

Here are some of the best ways to help you resolve Photoviewer.dll error on your system:

1. Rebuild the Windows Photo Gallery

If you were previously using Vista and then you upgraded your system to Windows 7, then try this:

Go to the Start menu, click on the control panel and go to the folder options.
Then select the view tab option. Here you’ll find the Advanced setting window, select the show hidden files and folders tab.
Now click Ok to continue. Navigate to the following folder( %user% is the name of the account with the problem) C:\Usersusername\AppData\Local\Microsoft\Windows\Photo Gallery.
Then copy files to another location as a backup and delete them from the Windows Photo directory. Once the files have been deleted, try to start Windows Photo Gallery again. If this seems difficult, install Windows Photo Gallery application from the internet on your system.

2. Repair Broken Photoviewer.dll files and Remove Malware

Another way to fix the photoviewer.dll error is to download Restoro. This is an advanced, user-friendly, and multi-functional PC fixer smoothly integrated with a registry cleaner. By running it on your system you can resolve all Photoviewer.dll error causes in seconds. Restoro has an easy-to-use interface and a neat layout. It is safe, efficient, and bug-free. In addition to this, it is compatible with all Windows versions. The registry cleaning utility is deployed with an automated algorithm that scans your entire PC and detects Photoviewer.dll file errors in seconds. It fixes damaged, misconfigured, and broken Photoviewer.dll files, clears up disk space from unnecessary and obsolete files like the files from the uninstalled Windows programs which could be generating Photoviewer.dll error on your system. It repairs the registry and modifies the registry keys to their correct configuration thus repairing the Photoviewer.dll error on your PC. The powerful privacy error detector is integrated with all the properties and characteristics of an anti-virus. It scans for malware and viruses like Trojans and removes them from your system right away. Besides these utilities, other features integrated into this repair tool include a system stability scanner and Active X and class error detector. It resolves Photoviewer.dll error while optimizing your computer’s speed and performance. Click here to download Total System Care on your system to resolve the Photoviewer.dll file error today!

Fixing the We can’t find a USB flash drive

One of the preferred ways to upgrade Windows 10 is by creating a bootable USB drive. However, you might change your mind when you encounter an error during the Windows 10 Setup that says, “We can’t find a USB flash drive”. Worry not for this error can be fixed using some suggestions that will be provided in this post. The funning thing about this error in Windows setup is that the computer says it’s not there when it’s clearly there. To fix this problem, you need to check if the USB device is accessible on your computer or you can also try a different USB device. In addition, you could check if there are any issues with both the USB 3.0 and USB 2.0 ports as it could be the reason why you’re getting the error or fix the bad sectors in the USB drive as well as see if the USB drive is set as the primary drive.

Option 1 – Try to check if the USB is accessible on your PC

The first thing you can do to resolve the problem is to check if you can access your USB device from your computer. All you have to do is open File Explorer and check if the USB device is listed there or not.

Option 2 – Try to connect a different USB device

The next thing you can do to fix the error is to try connecting a different USB device, specifically the one that has more significant storage space. You also have to make sure that it’s working on a different PC.

Option 3 – Fix any issues with the USB 3.0 and 2.0 ports

Although the USB 3.0 ports are compatible with the USB 2.0 ports, it does not necessarily mean that there wouldn’t be any problem when you use them which is why it’s best to fix any issues in them or better yet, use a compatible drive.

Option 4 – Try to fix the bad sectors in the USB drive via CHKDSK

When it comes to some issues concerning the hard drive or removable devices, there is a utility in Windows that might help which is called “chkdsk”. To use it, follow the steps below.

Tap the Win + S keys to open the Search box.
Then type “command prompt” in the field and from the search results that appear, right-click on Command Prompt and select “Run as administrator”.
After opening an elevated command prompt, copy and paste the following command and hit Enter:

CHKDSK [volume [[path] filename]] [/F] [/V] [/R] [/X] [/C] [: size]]

Note: In the command given above, “[/F]” will try to fix the system errors while “[/R]” will be the one to fix the bad sectors.

Now if you are prompted to run CHKDSK after your reboot your PC, just tap Y and reboot your PC.
If CHKDSK is not able to find any errors, tap the Win + E keys and navigate the access window. From there, right-click on the concerned drive and click on Properties.
After opening Properties, click on the tab Tools and then click on the “Check” button under the Error-checking section.
Wait until the process is completed and then restart your computer.

Option 5 – Try checking if the USB is set as the primary drive

You might also want to check if the USB drive is set as the primary drive because if it is, then it won’t appear on the list. It could also be that the USB drive has a primary disk in it. To undo it, you need to use the DISKPART utility.

In the Start Search, type “command prompt” and right-click on Command Prompt from the search results, and then select the “Run as administrator” option.
Next, execute the “diskpart” command to initiate the DISKPART utility.
After that, type the “list disk” command and tap Enter to display the list of disks on the computer. You have to take note of the drive number or letter of the concerned USB drive.
Once done, type the “select disk <X>” command where X is the drive letter or number and tap Enter.
Then execute the “list partition” command to see the list of all the partitions in your computer. It should be listed as 0, 1, or 2. 0 is the primary partition.
Now type the “select partition 0” command and tap Enter and then type “delete partition” to delete the selected partition.
You can do the same to the other partitions as well and when you’re done, execute the format command to turn the USB drive into a standard one.

Network License NotAvailable15.570.0 Autodesk

If when trying to start Autodesk applications you receive a Network license not available error then please keep on reading, this guide is for you:

Causes of the error:

The license on the License Server is invalid.
The port for Autodesk Network License Manager is blocked.
The client computer is configured with incorrect license server information.
The license request is timing out on the client's computer before the license is obtained.

Solutions for the error:

Verify that the Autodesk License Server is setup with the correct license file.

To set up a license server for Windows, perform the following:

Download and install the Network License Manager for Windows:
Open LMTools and access the System Settings tab. Make a note of the "hostname" and "ethernet address" of the license server.
Generate a Network License File in Autodesk Account.
On the Service/License tab, select Configuration Using Services and LMTOOLS ignores license file path environment variables.
On the Config Services tab, enter a name for the new service in the Service Name field.
Fill the following fields, using the Browse buttons:
- Path to the lmgrd.exe - Navigate to this file: C:\Autodesk\Network License Manager.
- Path to the License file - Navigate to the new Autodesk.lic file, typically placed in: C:\Autodesk\Network License Manager\Licenses.
- Path to the Debug Log file: C:\Autodesk\Network License Manager.
- If no file is present, create a TXT file in Notepad and rename it “Debug.log.”
Make sure the "Start Server at Power Up" and the "Use Services" boxes are checked. Then click Save Services.
On the Start/Stop/Reread tab, click Start Server.
On the Server Status tab, click Perform Status Enquiry.
Licenses should display as active.

How to set up the Autodesk Network License Manager on a Mac.

Note: The Autodesk License Server Manager (version 11.16.2.0) is supported only on the following Mac operating systems:

Apple macOS High Sierra 10.13
Apple macOS Sierra 10.12
Apple Mac OS X El Capitan 10.11

Download Autodesk Network License Manager version 11.16.2.0 for Mac
- Download the nlm11.16.2.0_ipv4_ipv6_mac_universal.tar.gz file to the Desktop.
To install the Autodesk Network License Manager:
- Double click on nlm11.16.2.0_ipv4_ipv6_mac_universal.tar.gz to unpack the installer package.
- After unpacking nlm11.16.2.0_ipv4_ipv6_mac_universal.pkg, will be /Downloads/adlm/FLEXnet folder.
- Double click on nlm11.16.2.0_ipv4_ipv6_mac_universal.pkg to start installation and follow the installation wizard.
- The license server will be installed in /usr/local/flexnetserver/ directory.
Change permissions for /usr/local/flexnetserver/ directory to 777

Open Terminal (located in /Applications/Utilities/Terminal) and enter the following command:

sudo chmod -R 777 /usr/local/flexnetserver

Note: Administrator password may be asked. While typing no characters are shown, just type out the password and hit return key.
Note: To start the license server only with elevated permissions (using sudo command), change permissions to 755 instead of 777.

Create /usr/local/flexnetserver/licenses directory for network license file location

sudo mkdir /usr/local/flexnetserver/licenses

Find the license server Host Name and Host ID.
Generate the Network License File in the Autodesk Account
- Once the license file is generated, make sure it has a .lic extension (e.g. adsk_license.lic) and is in a plain text format and place it in /usr/local/flexnetserver/licenses directory

Note: In this article we will refer to adsk_license.lic as network license file name. Feel free to change the actual name of the license file, but make sure to reflect the new name when using the commands below.

Create a debug.log file in the /usr/local/flexnetserver/ directory using the following command:

touch debug.log

To start the Network License Server use the following command:

/usr/local/flexnetserver/lmgrd -c /usr/local/flexnetserver/licenses/adsk_license.lic -l /usr/local/flexnetserver/debug.log

Note: If folder permissions for /usr/local/flexnetserver/ are set to 775, then use sudo command to start the server. For example:

sudo /usr/local/flexnetserver/lmgrd -c /usr/local/flexnetserver/licenses/adsk_license.lic -l /usr/local/flexnetserver/debug.log

To obtain license server status enquiry:

/usr/local/flexnetserver/lmutil lmstat -a -c /usr/local/flexnetserver/licenses/adsk_license.lic

To stop the license server:

/usr/local/flexnetserver/lmutil lmdown -q -force

Alternatively, run ps command to obtain process ids for lmgrd and adskflex and then kill those processes:

ps -ax | grep lmgrd
ps -ax | grep adskflex
kill -9

(provide process ids obtained by previous commands individually)

How to set up the Autodesk Network License Manager on Linux.

Note: The Autodesk License Manager (11.16.2.0) is supported only on the following Linux distros:

Red Hat® Enterprise Linux® 7
Red Hat Enterprise Linux 6
SUSE Linux Enterprise 12
SUSE Linux Enterprise 11

See System Requirements for the Network License Manager

To configure the license manager use the following steps:

Download Autodesk Network License Manager v. 11.16.2 for Linux from this link
- Download the nlm11.16.2.0_ipv4_ipv6_linux64.tar.gz file to your desktop.
To install the Autodesk Network License Manager run following command as root.
- tar –zxvf nlm11.16.2.0_ipv4_ipv6_linux64.tar.gz
- rpm -vhi nlm11.16.2.0_ipv4_ipv6_linux64.rpm
- The license server will be installed in /opt/flexnetserver/ directory.
Find the license server Host Name and Host ID

To obtain the license server system hostid run the following command

/opt/flexnetserver/lmutil lmhostid From the command output note the hostid in quotes, if the system has two active NIC cards, select the first MAC address. lmutil - Copyright (c) 1989-2018 Flexera. All Rights Reserved. The FlexNet host ID of this machine is "000c297949e0"

To obtain the license server system hostname run the following command

/opt/flexnetserver/lmutil lmhostid hostname From the command output note the hostname of the license server. mutil - Copyright (c) 1989-2018 Flexera. All Rights Reserved. The FlexNet host ID of this machine is "HOSTNAME=Centos7.localdomain"

Generate your Network License File in Autodesk Account
- Once the license file is generated, make sure it has .lic extension (e.g. adsk_license.lic) and place it in /opt/flexnetserver/licenses directory. If the directory doesn't exits, create it with this command: sudo mkdir /opt/flexnetserver/licenses

Note: in this article we will refer by adsk_license.lic your network license file name.

To start the Network License Server
- /opt/flexnetserver/lmgrd -c /opt/flexnetserver/licenses/adsk_license.lic -l /opt/flexnetserver/server_log.log
To obtain license server status enquiry
- /opt/flexnetserver/lmutil lmstat -a -c /opt/flexnetserver/licenses/adsk_license.lic
To stop your license server service
- /opt/flexnetserver/lmutil lmdown -q -force
- alternatively you can also run ps command to obtain process ids for lmgrd and adskflex and then kill those processes
  - ps -aw | grep lmgrd
  - ps -aw | grep adskflex
  - kill -9 (provide process ids obtained by previous commands individually)
To start the license server automatically after the system reboot
- Open /etc/rc.d/rc.local script as root and enter license server start up command in it.

touch /var/lock/subsys/local /opt/flexnetserver/lmgrd -c /opt/flexnetserver/licenses/adsk_license.lic -l /opt/flexnetserver/server_log.logNote: To ensure that the script will be executed during boot, run following command as root. chmod +x /etc/rc.d/rc.local

Make sure that all necessary ports are open:

lmgrd.exe needs ports 27000 to 27009.
adskflex.exe needs port 2080.

Note: Errors may occur if the network license file is corrupt or in the case of a combined network license it has incorrectly combined licenses. To learn more about combining licenses, see Combining License Files for Multiple Autodesk Products. Use the License File Parser to verify that the license contains the appropriate products and FLEXnet feature codes and does not display an error

Verify that TCP ports (2080, 27000-27009) used by Autodesk Network License Manager are not blocked by Firewall.

The FLEXlm® based version uses the following incoming ports:

TCP ports 2080 (for the adskflex vendor daemon)
TCP ports 27000 to 27009 (for the lmgrd master daemon, which uses the first open port in the range)

Note: If these port addresses are restricted by a router or firewall software, users on the remote side of the router will not have access to licenses controlled by the Network License Manager.

Verify that the client computer is configured with the correct license server name or IP.

Windows:

Clear license server information from the system registry.

Type regedit in the Windows Search box and hit Enter key.
Select the following registry key

[HKEY_CURRENT_USER\SOFTWARE\FLEXlm License Manager]

As the key is selected, in right panel ADSKFLEX_LICENSE_FILE will be visible.
Right click on the key and delete it.

Specify the license server in ADSKFLEX_LICENSE_FILE system variable

Go to Start > Control Panel > System and Security > System.
Select Advanced system settings.
On the System Properties dialog, click Environment Variables.
Under System Variables, click New.
Enter ADSKFLEX_LICENSE_FILE for the variable name and 2080@SERVER_NAME _OR _IP for the variable value.

Note: the license server information most often is recorded in LICPATH.lic file and can be verified there too. ADSKFLEX_LICENSE_FILE system variable supersedes LICPATH.lic. Thus, setting the system variable is preferable when this error is seen.

If the license server is on a VPN or a remote network set the FLEXLM_TIMEOUT environment variable:

Go to Start > Control Panel > System and Security > System.
Select Advanced system settings.
On the System Properties dialog, click Environment Variables.
Under System Variables, click New.
Enter FLEXLM_TIMEOUT for the variable name and 5000000 for the variable value.
Click OK to save the setting.

Note: if needed the variable value can be increased to 10000000.

Mac/Linux:

Specify the Autodesk Network License server information in $HOME/.flexlmrc file.

Use a text editor to create a flexlmrc.txt file and save it in Plain text format (In TextEdit on Mac: Format - Make Plain Text) on desktop. The file content should look like this, except with the name or IP address of the license server.

ADSKFLEX_LICENSE_FILE=@SERVER_NAME _OR _IP

If the license server is on the same machine as the Autodesk software, use localhost as the license server name. Thus, the content of flexlmrc file could look like this:

ADSKFLEX_LICENSE_FILE=@localhost

Note: On firewall restricted network or when accessing the license server via VPN, need to include TCP port/s (usually 27000 or 2080) into Autodesk License Server service as follows: ADSKFLEX_LICENSE_FILE=2080@SERVER_NAME _OR _IP

Once flexlmrc file is created move it to user's $HOME folder as follows:

Open a Terminal window
Type open ~ (Mac) or nautilus ~ (Linux) to open $HOME folder
Drag and drop flexlmrc.txt file from Desktop to the home folder.
To make the file a configuration file, rename it to .flexlmrc (please note . [DOT] in front of the file name) by running the following command:

mv flexlmrc.txt .flexlmrc (Mac)
mv flexlmrc .flexlmrc (Linux)

Verify that the license server information registered with the product is correct (versions 2020 and later only)

In versions 2020 and later, the license server information is registered with the AdskLicensing service running locally on the workstation. When changing to a new license server, the old server information may still be registered with AdskLicensing and result in the error above, if this is not appropriately updated. See the below steps to solve this:

Click the Start menu and type cmd.
Right-click on the Command prompt and choose "Run As Administrator."
In the Command prompt, run the following command, followed by ENTER:

"C:\Program Files (x86)\Common Files\Autodesk Shared\AdskLicensing\Current\helper\AdskLicensingInstHelper.exe" change -pk PRODKEY -pv VER.0.0.F -lm "" -ls "" -lt""

Note:

Replace PRODKEY with the product key correspondent to your product(s). See Look Up Product Keys for the full list.
Replace VER with the version you are using. E.g. 2020 for AutoCAD 2020.
Repeat this step for each software you need to reset.

Open Registry Editor (Start > type regedit > ENTER).
Navigate to HKEY_CURRENT_USER\Software\FLEXlm License Manager.
On the right-side, verify of the ADSKFLEX_LICENSE_FILE key exists. If yes, remove it (right-click > Delete).
Run the software again.
Select Multi-user in the Let's Get Started screen.
Follow the steps to connect to your license server.

Moving Taskbar to second monitor in Windows

If you are using a multi-monitor, then you might find it quite useful. It helps many users with their work and brings more productivity. And over the past few years, Windows has managed to offer one of the excellent multi-monitor features where users can plug in an additional monitor and access their work or use their computer seamlessly on both displays. This is really handy, especially for users who are graphic designers, gamers, and other professionals who have to use a larger screen for their work. One of the biggest inconveniences for users who use multi-monitor is that the Taskbar is switched on, on both displays, by default. This default arrangement is most likely to cause clutter on the second display. So if you are one of these users who find such a thing annoying, then you will find this post useful for you as we will walk you through how you can move the Taskbar to a second monitor. To get started, follow the instructions laid out below. Step 1: The first thing you have to do is right-click on the Taskbar. Step 2: Next, uncheck the “Lock the taskbar” option. Step 3: After that, click and hold the taskbar and drag it to the second monitor. Step 4: Once done, click the mouse button on the place where you want to place the taskbar. Step 5: Now right-click on the “Lock the taskbar” option to lock the taskbar. Once you’re done carrying out the steps given above, there are Advanced Options you can explore. This array of advanced options are offered by Windows 10 to fine-tune the multi-monitor experience of users. For instance, you have the option to choose to show the taskbar on an active screen only or combine the buttons on other taskbars. It would be better if you try out different variations and stick with the best one. In addition, you could also move the taskbar from one display to another.

Manually cleaning your PC registry

Manually cleaning your PC registry may be the worst or best thing you ever decide to do. Registry keys that lie around on your computer, unused, can cause your computer to lag. This can end up in your computer not being able to load the easiest of programs and being slow at loading anything, let alone something that would take up a decent amount of memory. If your computer has slowed to almost an absolute stop, it is most probably the registry’s fault and the only option then is to clean it. You can get programs to do this for you, but they can be riddled with inaccuracies and viruses that could harm your computer even more. This is why some people choose to manually edit their computer. However, this is not without its flaws.

Registry Keys

Registry keys tend to have really long names. These names will be full of numbers and hyphens and will most likely give you no indication of what they do. Even some computer experts find it hard to understand what every computer’s registry keys do. This can make it very hard to see which ones are causing the problem; and if you don’t know what’s causing the problem, then there is no way you will be able to fix it. Some registry keys will be completely menial in what they do but some could be vital to even allow Windows to work on your computer.

Manual Registry Repair

Registry keys can also cause huge problems if you manually delete the wrong one. A lot of registry cleaners have the option to revive a key that they have deleted on you, which means that fixing an error that they made would be easy enough to do. However, when you manually delete registry keys, it will be an awful lot harder to get them back to work again afterward. This can cause your computer many problems and if you delete even one wrong key it is possible your computer will not even start. With the horrid naming system they have as well, it makes it very hard to determine what is important and what is not, which means it is all too likely that you will delete something important. However, those are the risks you have to take when you are cleaning out your registry. A registry cleaner has the same likelihood of messing with your computer and deleting something wrong that you have, so it is the same either way however a registry cleaner will do it with less hassle. But, some people say that if you do it yourself, it’s more likely to be right; that is why they prefer to do it manually and that is alright.

Conclusion

So, if you are manually deleting your registry keys that are unused, you’ll have to use a program that comes with Windows known as ‘regedit.exe’ which is incredibly difficult to use but may just be worth the hassle in the end. So, you don’t really need to put up with a slow computer, but be careful when messing with your registry manually! To repair and resolve this and other PC-related issues Click Here to download Restoro.

Best gifts for Gamers and PC enthusiasts

The holiday season is almost upon us and buying gifts for loved ones can sometimes present some headaches, especially if that loved one is a Gamer or PC enthusiast. We have all been there and how almost every household today has a console or PC struggles are infecting more and more people. But do not despair, we have made a nice list of potential gifts for you. gifts

The list contains some nice essential and good things but we gave our best not to break the bank so you will not find any large screens or 300$ keyboards here. Of course, you can always get expensive gifts and if you have money for it do it, it is just we want to have affordable stuff here.

A Steam gift card

For gamers, a good game is a great gift but most of the time when we are buying a game we can miss what the person wants. That is why a Steam gift card is a great gift for gamers. He can use it and buy whatever he or she wants for its value.

Xbox Game pass

This is another for those Gamers type. Xbox game pass is a great gift even if you do not own Xbox since all games will work on PC as well. Xbox Game Pass Ultimate includes the PC version, which will unlock somewhere between 300 and 350 games automatically. It’s a subscription service, so your PC gamer will have to keep up with it. The monthly price is worth it, though.

Pack of cable ties

Almost every PC user has tons of cables lying around, and most of the time they are not really tidy. Cable ties come to the rescue!!! Let us be honest, no one likes cables that are scattered all over the place, even the computer users so if they do not have this essential piece of equipment, we are sure they will like it.

Compressed air duster

Dust is enemy no.1 for computer users, it gets into the keyboard, into small spaces, etc. It is very difficult to get it out so an air duster for compressed air is a great cleaning gift for any kind of computer enthusiast. You can get it with a can of compressed air as well so everything is ready for cleaning.

New Headset

A headset is always a great gift. Over time earbuds can deteriorate and get damaged simply just by using them and when enough time passes even cables can start losing contact and overall sound quality may drop. Usually, computer users change headsets like keyboards so if your loved one has some old headsets showing their age, a new one is a perfect present.

New SSD drive

More hard disk space is always a welcome sight for any PC user and new SSD drives fueled with new technology are faster than ones of the same size in past years making them a perfect gift.

Large mouse pad

A good mouse pad can mean a lot to a gamer. Over time mouse pad deteriorates simply with its use so a new and fancy large pad is a great gift for any user. If you want a great gift, make it with RGB light.

Fix INVALID_POINTER_READ_c0000005 atidxx64.dll

If your Microsoft Edge browser encountered a Stop Error that says, “INVALID_POINTER_READ_c0000005 (atidxx64.dll)” in your Windows 10 computer, then this indicates that your Graphics card driver is outdated. According to security experts, Microsoft has already acknowledged the problem and stated that this issue exists with Windows 10 v1809, Windows Server 2019, and Windows Server version 1809. Although there is no direct way to resolve the problem, there are still some workarounds you can try. If you are using a RadeonHD2000 or HD4000 series video card, the update will be blocked for you. Some users also claim to experience performance issues with the lock screen or the ShellExperienceHost. However, if you are using AMD, the problem is that it no longer supports Radeon HD2000 and HD4000 series graphics processing units or GPUs. Even though Microsoft is already working for a way to resolve the problem, here are some alternative solutions you can check out:

Option 1 – Update your Graphics card drivers

First, boot your computer into Safe Mode.
After that, tap the Win + R keys to launch Run.
Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
After that, a list of device drivers will be displayed. From there, look for the Display Adapters and click on them.
After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
Now restart your computer.
After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

Note: You also have the option to go directly to the website of your graphics card manufacturers like NVIDIA, Intel or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.

Option 2 – Try removing AMD Radeon HD2000 and HD4000 drivers

Although this is not exactly a perfect solution, removing AMD drivers will make the operating system fall back to the default GPU available on your motherboard. You also have the option to completely disable the hardware.

Tap the Win + X + M keys to open the Device Manager.
Next, look for your Graphics card drive, and under Display Adapters, right click on them and click Uninstall device or Disable device.
After that, restart your computer. This will disable the AMD drivers so you won’t be able to find them. It will also release the Windows 10 v1809 update on your computer and in case your operating system tries to prompt you with the “New Device found” message, simply ignore it.

Option 3 – Try to use another browser

You might want to use another browser especially when you already updated your computer and Microsoft Edge still keeps on crashing. You can use Google Chrome, Mozilla Firefox, and other browsers as alternatives until you sort out the problem.

Option 4 – Try to remove the Graphics card physically

You might also want to try removing both AMD Radeon HD2000 and HD4000 as they are very old graphics cards. And since AMD is not going to roll out anything, at least on its own if your motherboard has an onboard GPU, it would be best to get rid of the cards. After that, install the Windows v1809 update and then put them back in. You also have the option to install the driver but just don’t use Microsoft Edge.

Remove Task View button from Windows 11

Task View feature inside Windows 11 is actually a great feature, letting you quickly view open windows and virtual desktops. How Task view itself could be reached with keyboard shortcut combination of ⊞ WINDOWS + TAB some users will prefer this way of using it and thus button on the taskbar is something you do not want or need. There is a very easy way to remove mentioned button and I will show you how to do it. Right-click the taskbar button itself and click on Hide From Taskbar. That’s it, you have done it. Now in order for you to bring it back if you change your mind, you will have to do some extra steps but it is nothing difficult. Right-click on the taskbar and click on Taskbar settings, you will be lead to Personalization > Taskbar. Inside locate Taskbar Items and switch Task View to ON, you will see the Task View button right away showing itself again.

1 2 3 … 171 Next »