How to remove ListenToTheRadioNow from your PC

Although it’s easy to set up wired printers in most cases and they have their charm, you don’t have to be around the printer if you are connected to the same network. So in this post, you will be guided on how you can install and set up a wireless printer on your Windows 10 computer. The idea here is to ensure that your Wi-Fi printer and your Windows 10 computer are connected on the same network and to do that, you need to carry out the following steps:

• You have to connect the printer to the Wi-Fi network.
• You have to add the printer or scanner to Windows 10.
• You have to install the printer software.
• You have to change the default printer.
• And troubleshoot the printer.

For more details, follow the instructions below.

Step 1: Connect your printer to the Wi-Fi network. In this step, you need to turn on your printer and look for the option to connect to a Wi-Fi network. Note that the step to connect to the Wi-Fi network depends on what kind of printer you use as well as its OEM since there will be a user interface or a Wi-Fi button that will get the job done for you. Once your printer is connected to the Wi-Fi network, you need to keep it turned on until the setup is completed. Step 2: Next, add a printer or scanner to Windows 10

• Since you’re already connected to the Wi-Fi network, you now have to go to Settings > Devices > Printers & scanners.
• From there, click on the Add a printer or scanner option.
• After that, the scanning process will begin as Windows 10 looks for the printer and once it finds it, it will display the printer in the result.
• Choose the Wi-Fi printer from the results and click on the Add device option. Once you click this option, Windows will install the drivers via Windows 10 update. Note that this process will apply to all the printers – connected, wireless, and so on.

Step 3: You have to install a printer software In this step, you need to use the driver software from the OEM even though the default printer software works since in most cases, the driver software from OEM works better compared to the default ones and offers much better functionality like ink-saving modes, and many more. Step 4: You now have to change the default printer After installing the printer software, you now have to set or change the default printer in your computer. If you have not installed any printer, the default printer in Windows is the one that saves the files. Now since you have already installed your printer, all that’s left for you to do is to change the default printer of Windows 10 to the one you installed earlier. To do that, follow these sub-steps:

• Go to Settings and navigate to Devices > Printers & scanners.
• From there, check the checkbox labeled, “Let Windows manage my default printer” if there are many printers. This will recommend you to use the most used printer. But if you don’t want to switch to the most used printer, then uncheck the checkbox.
• Once done, click on the printer you want to set as the default one and go to Manage, and then click on the Set as default button.

Step 5: If you have any issues with your newly installed printer, then you need to troubleshoot it One of the first basic troubleshooting you can perform to resolve the printer issue is running the Printer Troubleshooter. This built-in troubleshooter can detect and automatically fix the problem for you. To use it, follow these steps:

• Tap the Win + R keys to open the Run dialog box.
• Next, type “exe /id PrinterDiagnostic” in the field and click OK or hit Enter to open the Printer Troubleshooter.
• Then click the Next button and follow the next on-screen instructions to fix the issue with the printer.

Error Code 0x800ccc13– What is it?

0x800ccc13 is an error message related to sending email using Outlook. Many people are receiving this error after making an upgrade from Windows 7 or Windows 8.1 to Windows 10. The error message appears when you try to send an email message with the use of a POP3 account or an IMAP account in an Outlook profile that has an Exchange Server 2010 mailbox configured. A common complaint would be: Since upgrading to Windows 10 I cannot send email from Outlook 2013. Mail stays in the Outbox, and I get: Error 0x800CCC13. Cannot connect to the network.

Symptoms

This problem may arise under the following situations:

• You are using Microsoft Office Outlook in online mode to connect to a Microsoft Exchange Server 2010 mailbox
• When you add an additional POP3 or IMAP account in the same Microsoft Outlook profile
• You are sending an attachment through email.
• You try sending an email by selecting POP3 or IMAP account as the sender

During these circumstances, the email message stays in the Outbox and you receive the following error message: Task '<the POP3 account or the IMAP account> - Sending' reported error (0x800CCC13): 'Unable to connect to the network. Check your network connection or modem.'

Solution

Error Causes

Error Code 0x800ccc13 occurs because the system files in Windows 10 during the upgrade became corrupted and most likely caused authentication issues. It can happen with any version of Outlook. Damaged data files will also cause error code 0x800ccc13 to manifest. Overall, the corruption of the Microsoft Windows System could be a result of an installation partially done (or an incomplete one), deletion of any application or hardware erroneously, and or malware or adware infestation.

Further Information and Manual Repair

Method 1:

Use the Windows System File Checker to repair corrupted files Verify that your SMTP, username, and password settings are correct. Now, in order to correct missing or corrupt Windows System files, try the following solution by running a command. This is known as the System File Checker. Follow the steps below to invoke the program using a command prompt command:

1. At first, you need to open the command prompt. To do so, right-click the Windows button in the bottom left of the screen, and select Command Prompt (Admin).
2. Now, enter the following command

sfc/scannow

When it is done, a message will confirm that Windows found some corrupt or missing files and it has successfully repaired those. Check the Outlook and see if your emails are sending. If the problem persists, don’t worry there is another way to solve this. Users have found another command helpful is using the NetShell utility from the command prompt, which is similar to the above solution.

1. Open the Command prompt by Right-clicking the Windows button in the bottom left of the screen and select Command Prompt (Admin).
2. Enter the following command

netshwinsosk reset

This helpful command will reset the network adapter to its default settings. Hope this will solve your problem. If not, you may want to try the Method 2 listed below.

Method 2:

For this method, you need to consider the following things:

• Are you using POP3, IMAP, or Exchange server for your email account?
• How many email accounts have you configured in your Outlook?
• Is there an undelivered email stuck in your Outbox?
• If you are trying to send an attachment, what is the size of the attachment?

Try the following:

1. Move or delete any undelivered email that is stuck in the Outbox folder, and then try sending an email and verify the result
2. Start Outlook in Safe Mode by following the instructions below

Hold down Windows key + R. Copy this command Outlook /safe Note, there is a space between Outlook and / Paste it in the open box and press Enter If Outlook in Safe Mode works, disable the add-ins by following the steps below and determine if the problem is caused by add-ins.

• Click File menu, click Options, Add-ins, Go button beside Manage Com-in Add.
• If there are add-ins listed, clear the checkbox.
• Close Microsoft Office and restart it.
• Disable the add-ins one at a time. Now, restart Outlook and repeat the procedure once more. If the problem appears again, it will help you find which add-in is causing the problem.

3. Start the computer using the clean boot. Now, try to send an email and see the result.
4. If the problem still lingers, create a new profile and configure the email account.

If you do not possess the technical expertise required to accomplish this yourself or do not feel comfortable doing so, download and install a powerful automated tool to get the job done.

We have talked about gaming on old computers and have covered new and upcoming Steam deck handheld console. Today we are combining old gaming with a handheld console and our target of talk is Retroid pocket 2. This product is packed with really high-quality plastic and with some great features in it. So let's dive into this cool handheld in more detail and find out why we like it so much.

Good manufacturing quality

Plastic and overall manufacturing quality are really, really good. The battery is great, packing 4000mAh that can hold over 3 hours of nonstop gaming, and all buttons and joysticks are great. The screen is a 640 x 480 60Hz 3.5″ IPS screen (4:3 aspect ratio) that performs really great for its purpose, retro gaming. There is a Digital D-Pad and dual analog joysticks. The right joystick is the lower profile to avoid being accidentally moved when pressing the four gaming buttons. There are three buttons at the bottom which are Home, Start, and Select. On either side are good-quality stereo speakers. On the bottom of the device are a Micro SD Card slot and a 3.5mm headphone port. On the top of the device are Left and Right shoulder and trigger buttons. There are the power button and volume adjustments. There are a USB Type-C OTG port and a Micro HDMI output for connection to a TV.

Good technical statistics

Good, not great but then again since this is retro handheld you cannot really expect some crazy stuff like alder lake inside. So the console is punching ARM Cortex A7 CPU with 2 cores and a clock of 1.5GHz paired with ARM Mali 400-MP2 500MHz GPU. The console has 1GB LPDDR3 RAM memory and 8GB eMMC Storage where 5GB is freely available, the rest is taken for OS. As mentioned before the display is 640x480 resolution with a size of 3.5″. The battery is Lithium-Ion with a power of 4000mAh and on the handheld, there is a USB Type-C connector, 3.5mm headphone jack, and Micro-HDMI. It also has Wifi/Bluetooth 4.0

Retroid Pocket 2 OS and support

Pocket 2 comes with Android 6 but you can update its firmware to the 8.1 version on the official site that I would highly recommend. New versions of the handheld will come with 8.1 on it from the box. Having Android as OS opens many possibilities like you can download Android apps such as Steam Link, allowing you to play actual PC games on your Retroid Pocket 2. Not just that, if it does get a newer version of Android it could even have the ability to use xCloud, Xbox’s cloud gaming service. Of course, hardware will not be able to handle modern games but the option is still there and for some old PC titles available on steam like Commander Keen, for example, this is a great option. The console can emulate basically everything up to Dreamcast, including N64, PSP, and Playstation 1. It can emulate Nintendo DS also, but it can only do so with one screen. The only problem with this console is you will need to install and update Apps. You’ll need to learn about RetroArch, an app that lets you download emulators or cores to play games.

Retroid price

The last thing on the list is the price of the console itself. Going just under the 100$ mark this really makes it an affordable option for plenty of people that would like to experience retro handheld gaming or for ones like me, nostalgic gamers wanting to relive some era of playing games on the road.

Conclusion

Among Chinese handheld devices for retro gaming, Retroid Pocket 2 is really on top of what the market can offer. If you are looking for a great handheld retro console and are not afraid of little dive-ins into the OS and various configurations, Pocket 2 will reward you with plenty and wide emulation support.

Corsair is well known for RAM memory modules for PC but then it has expanded to PC peripherals and even selling some pre-build computers as well in past few years. New Corsair expansion now includes a laptop line, starting with their new gaming laptop Voyager.

Voyager laptop is packed with a mechanical keyboard and MacBook-like touch bar for your typing and pointing needs. It is built with a 16-inch QHD+ screen packing 240Hz that is run by Radeon 6800M GPU. Also inside lurks AMD 16 thread Ryzen 9 6900HS CPU, Wi-Fi 6E support, Dolby Atmos audio, and full HD 1080p WEB camera.

The keyboard has low-profile mechanical Cherry MX switches with per-key RGB lightning and above is what Corsair calls a macro bar, with 10 shortcut buttons and a small LCD in the center.

Corsair is also including a few features that tie in with its other products. Many of the company’s keyboards, mice, and other accessories use the ‘Slipstream’ USB wireless adapter, which is built into the Voyager laptop. The macro bar is also configured using the same software used for the Elgato Stream Deck, a popular product sold by Corsair.

If you are trying to install or reinstall a program on your Windows 10 computer but encountered an error instead that says, “Fatal error, Installation fails, Installation ended prematurely because of an error”, then you’ve come to the right place as this post will guide you how you can fix it. This kind of error is most likely caused by some files that may have been left behind by the previous installation of the program. Each time a program is uninstalled, it leaves behind its files and if the uninstallation process wasn’t completed properly, then it would result in errors like the

“Fatal error, Installation fails, Installation ended prematurely because of an error”.

Moreover, this kind of error is a generic one that can also occur with any software reinstallation or installation. And to fix this error, there are several suggestions you must check out. You can try to install or reinstall the program in a Clean Boot State or restart the Windows Installer Service. You could also try to re-register the Windows Installer Service or re-register the VBScript.dll file.

Option 1 – Install or reinstall the program in a Clean Boot State

It is possible that there are some third-party applications in your computer that are preventing the program 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” checkbox 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” checkbox.
• 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 program again.

Option 2 – Try to restart the Windows Installer Service

The next thing you can do to fix the problem is to restart the Windows Installer Service. To do this, follow these steps:

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and then hit Enter to open the Windows Services Manager.
• Next, look for the Windows Installer service among the list of services shown.
• Once you found it, right-click on it and open its Properties.
• From there, click on the Stop button and then click on the Start button.
• But if it isn’t running, then just click on the Start button.

Option 3 – Try to unregister and re-register the Windows Installer Module

• Tap the Win + R keys to open the Run dialog box.
• Then type the “msiexec /unregister” command and hit Enter to unregister the Windows Installer Module.
• Next, type the “msiexec /regserver” command and hit Enter to re-register the Windows Installer Module.
• Now restart your computer and see if unregistering and re-registering the Windows Installer Module fixed the problem or not.

Option 4 – Try to re-register the vbscript.dll file

You may have to re-register the vbscript.dll file using the regsvr32.exe before you can successfully install the program and fix the error. The Regsvr32 tool is a command-line utility that can be used to register and un-register the OLE controls like DLL and ActiveX (OCX) control in the Windows operating system. Follow the steps below to use it.

• Open Command Prompt as admin from the WinX menu.
• Next, type regsvr32.exe vbscript.dll 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.
• 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.

A copy of Windows gets into a grace period when it is installed on a computer which means that you can use your Windows computer without any constraints on its feature. However, if you suddenly encounter an error code 0xC004F009 then this means that the grace period has already expired. In such cases, you will see the following error message on your screen:

“Error Code 0xC004F009, The Software Licensing Service reported that the grace period expired.”

One of the possible causes of this error is that it could be that the grace period has already expired way before the system was activated which is a result of which the system is in the Notifications state at this moment. The error code 0xC004F009 has something to do with MAK-enabled computers in an enterprise when it comes to Volume Licensing. One of the reasons that this error pops up is due to the possibility that the computer was not activated yet even when it was already connected to the Enterprise. Another most likely cause of the error is when the system was never connected with the Enterprise at all and the given grace period has expired before your computer system is activated. Whatever the real cause of this error, this post will guide you in fixing it. Just refer to the instructions given below to fix it.

Option 1 – Try activating Windows using the command-line tool

• First, you need to obtain your MAK key from the IT administrator.
• Once you have it, tap the Win + R keys on your keyboard and then type “cmd” in the field and hit Enter to open an elevated Command Prompt.
• After that, type this command and hit Enter to install the product key or replace the existing one: Slmgr.vbs –ipk <your mak key>
• Next, type another command and hit Enter: slmgr.vbs –ato
• Once you’ve executed the given commands, Windows should be activated after it connects to Microsoft servers and then gives it some time and try to check if error code 0xC004F009 is now fixed or not.

Option 2 – Try activating Windows using your mobile phone

Activating Windows 10 can also be done using your phone. Just note that you have to call Microsoft to do so.

• In the Start Search box, type in “Slui 4” and tap Enter.
• Next, select your country and click on Next.
• Keep the window open and call the toll-free number of the country you’re from.
• Afterward, a confirmation ID should be given by the automated system which you must take a note of.
• Finally, in the box on the window, type in the confirmation ID and click on the Activate button. That should do it.

Option 3 – Try to prolong the grace period

On the other hand, it is also possible for you to prolong the grace period but you might have to get another genuine Windows key for that. Before you proceed, you need to create a System Restore point first afterwards, refer to the steps given below to increase the grace period of the Software Licensing Service on your Windows 10 computer.

• Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field then hit Enter to open the Registry Editor.
• After that, navigate to this registry key: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionSetupOOBEmediabootinstall
• Next, change the value of the “mediabootinstall” key to “0”.
• Now open Command Prompt with admin privileges and then type this command and hit Enter: slmgr –rearm
• The command you just entered will add another grace period to your system activation. After that, you have to obtain a new key and then activate Windows.

Option 4 – Try running the Windows 10 Activation Troubleshooter

You can also try to run the Windows 10 Activation troubleshooter to help resolve the error code 0xC004F009.

• Go to Settings and then select Activation.
• After that, click on the Windows Activation and then troubleshoot. This will help you address most of the commonly found activation issues in Windows devices.

What Is Installation Error 1628?

Installation Error 1628 is, as the name suggests, an installation error. When it occurs, a generic 1628 message is displayed to the user. When this message appears, it is either a problem with the install files or an issue with the InstallShield.

Solution

Error Causes

Installation Error 1628 is caused because every Windows-based program or application has been designed that such that it has to be installed on the computer for use. This installation process is important because it not only moves files to the appropriate location on one’s hard drive but also because the process creates registry entries in Windows System files. A vast majority of these programs and applications have a built-in tool that’s responsible for aptly performing this installation. This built-in tool is the InstallShield. This establishes that when this error occurs, it is either because of some unforeseen issue that occurred during the installation process or because of some problem with the InstallShield.

Further Information and Manual Repair

In order to keep this error from occurring in the future, some recommendations are outlined below.

• Check the installation disc and determine if there are any smudges, scratches, or fingerprints on it. If the system is unable to read data from the disc, Installation Error 1628 will be generated. In order to ensure that the Installation Disc is clean, use a microfiber cloth. Dampen it lightly with water and clean the disc. Wipe the inside of the disc lightly in an outward direction, making sure that it is not wiped in a circular pattern. Try to reinstall the application or program after cleaning the disc. The issue should be resolved. However, if it persists, some problems may be with the InstallShield.
• The alternative solution is to repair the InstallShield and the procedure goes as follows.

1. Stop InstallShield’s running process. It may have been crashed and simply needs to be restarted. Now access task manager. Press Ctrl+Alt+Del and the task manager will open. Now go to the processes tab and disable ‘idriver.exe’ and ‘msiexec.exe’ from here.
2. Now go to ‘C: Program Files/Common Files’. Here you will find the ‘InstallShield’ folder. Select ‘rename’ and modify the folder name to ‘InstallShield1’. Confirm rename and start the installation process again. Now Windows will try to re-install any InstallShield files one needs.
3. If the error persists after renaming the InstallShield folder, download the Windows Installer from Microsoft’s website. This file will determine whether or not your version is valid. Old versions often have bugs that cause problems. Your system is now ready to be used.

Error code 10, device manager code occurs when Bluetooth or Wi-Fi cannot be enabled. Inside device manager beside device would be yellow exclamation sign and if you go into device properties status would be: This device cannot start. Following are proven solutions that will resolve the issue and provide you with a working device.

Reboot PC, check for switch

This simple solution can usually work in most cases, first thing is to check if by any chance hardware switch for Wi-Fi or Bluetooth is OFF (laptops have a small switch that can turn the device On or OFF), then if you do not have a switch or you made sure it is ON, reboot your system.

Run Network Adapter Troubleshooter

If previous simple step solutions have not proven to be effective run Network Adapter Troubleshooter

1. Press WINDOWS + I to open settings
2. Go to System > Troubleshoot > Other troubleshooters
3. Inside Find Network Adapter
4. Click on Run to start the troubleshooters

Disable and then re-enable Adapter

If the previous solution has not fixed the issue try disabling the adapter and then re-enabling it back.

Update network adapter

Go to the intel website and download the latest driver package. After the download is finished install the latest driver.

Turn ON the WLAN AutoConfig service

1. Press Windows key + R to invoke the Run dialog.
2. In the Run dialog box, type services.MSC and hit Enter to open Services.
3. In the Services window, scroll and locate the WLAN AutoConfig service.
4. Double-click on the entry to edit its properties.
5. In the properties window, click the drop-down on the Startup type and select Automatic.
6. Next, make sure the Service status is started and running.
7. Click Apply > OK to save changes.
8. Exit Services console.
9. Restart PC.

If you are running the Windows Update service but decided to stop it but you encountered an error message instead that says, “The Windows Update service could not be stopped”, read on as this post will help you fix the problem. This kind of error appears when you use the Command Prompt to stop the Windows Update service, especially if you are using cmd without admin privileges. A lot of users reported that they were not able to disable the automatic Windows Update in Windows 10 using Command Prompt. The command used to stop the Windows Update service is the “net stop wuauserv” command. However, when some users executed this command, they got the error message. So if you are one of these users that can’t stop the Windows Update Service via Command Prompt, you can try to fix that using PID as well as checking the Service dependencies. For more details, follow the given options below.

Option 1 – Try to stop the Windows Update service via PID

In case you don’t know, each running service or process has its own unique ID or PID and you can find it in the Task Manager. You can use it to stop the Windows Update service. How? Refer to these steps:

• Tap the Ctrl + Shift + Esc keys to open the Task Manager.
• Next, go to the Services tab and look for the service named “wuauserv” and get its PID.
• After that, type “cmd” in the Windows Start search and right-click on Command Prompt from the search results and then select the “Run as administrator” option.
• After opening Command Prompt with admin privileges, execute this command: taskkill /f /pid <PID>

Note: You need to replace “<PID>” with the PID of the “wuauserv” service. For instance, the PID is 6676, then this is how the command should be “taskkill /f /pid 6676”.

• After you execute the command, you will this message on your screen, “SUCCESS: The process with PID 6676 has been terminated” which indicates that you have stopped the Windows Update service successfully.

Option 2 – Try to check the Service dependencies

Dependencies of a Windows Service in Windows 10 are when windows services depend on other services. Such is the case with the Windows Update service – it also depends on three different services such as the Remote Procedure Call or RPC service, DCOM Server Process Launcher, and the RPC Endpoint Mapper. Meaning to say, if two of these services are not working as expected, then the dependant service will also be affected. This could be the reason why the Windows Update service could not start.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “services.msc” in the field and hit Enter to open Windows Services.
• From the list of Services, look for the following services:
  • Remote Procedure Call (RPC) Service
  • DCOM Server Process Launcher
  • RPC Endpoint Mapper
• After you find these services, double click on each one of them and check whether the Startup type for all is set to Automatic and the Service status is set to Running or not.
• If the service status is not running, then click the Start button. Afterward, check if you can now run the Windows Update service.

There is a central location in Windows 10 that allows users to view all the notifications from its Action Center. Aside from viewing notifications, users can also manage them and take necessary actions in just one single place. Notifications in Windows 10 look similar to a message icon but can be at variance in function. However, recently, a number of users reported that even though they receive notifications about new actions but when opening them, they see nothing. In other words, the notification is false, and to fix this, read on as this post will provide you a couple of workarounds. The Windows 10 Notifications and Action Center notification messages might show a mismatch. For instance, Windows 10 may say that you have some notifications but when you open Action Center, you find it empty and there are actually no notifications there. Take the case of the following screenshot, the Windows 10 Notification says that there are 6 new notifications available for viewing but the Action Center says otherwise. Before you troubleshoot the problem, you might want to run System Restore especially if you’ve made some changes in your computer prior to this issue which might have messed with the Windows 10 Notifications and Action Center. To perform System Restore, refer to these steps:

• First, press 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 the problem wasn’t fixed and you’re still getting false notifications, you might want to troubleshoot the problem further using the options given below.

Option 1 – via Windows PowerShell

• In the Start search, type “PowerShell” in the field and hit Enter to pull up the Windows PowerShell window.
• Next, copy and paste this command and hit Enter to execute it: Get-AppxPackage | % { Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)AppxManifest.xml” -verbose }
• After that, reboot your computer and check if the false notifications are now gone.

Option 2 – Try renaming the Usrclass.dat file

DAT errors like the ones that are associated with the Usrclass.dat file, most likely occur during computer startup, program startup, or while you try to use a specific function in your program. Even so, it can easily be fixed. How? Refer to the given steps below.

• Tap the Win + R keys to open the Run dialog box.
• Then type %localappdata%MicrosoftWindows and hit Enter to get to the location of the UsrClass.dat file.
• After that, look for a file named UsrClass.dat and once you’ve found it, right-click on it and select the Rename option.
• Now rename the file to UsrClass.old.dat and then restart your computer and see if the problem is now fixed or not.