Fix Adobe.Dll Error

What Exactly Is Adobe.Dll?

Adobe.DLL is one of the numerous Dll files you are going to encounter on your Personal Computer. This isn't a system-established service and is usually the consequence of the sort of applications you install on your own Personal Computer. Because adobe.dll is a low-program process, in the event that you find it present on your pc, you can easily end it. It isn't required for the normal working of your OS but might trigger permanent harm if left unchecked. Don't forget that the Computer uses the AdobePDF.dll file for assorted tasks, and you need to make sure it's installed correctly.

Solution

Error Causes

When the adobe.dll is left un-fixed, you may shortly have to deal with sluggishness on your Computer. Simply put, this impedes the standard and amount of work you do while using your PC and impacts your productivity. Sometimes, adobe.dll happens because your computer experiences an overload. As a result, while resolving the malfunction, you've got to look for methods of decreasing the system overload. It's possible that lots of processes are functioning on your PC concurrently. Quit these processes. Lousy setup of the adobe.dll file causes this error too. Check and fix the files and settings that Adobe.Dll requires to run and you may not have to content with these error anymore.

Further Information and Manual Repair

Even though the adobe.dll may severely influence the functioning of your Computer, it is really a trouble or malfunction that one can fix manually.

• Permanently Un-Installing the Adobe.dll Component is one of the better methods for repairing the malfunction.

Yes, you are able to completely eliminate the adobe.dll issue. The thing you really need to do is un-install it from your own computer fully, and for good.

• Quit the many processes operating on your Computer and you may get rid of the adobe.dll malfunction.

Adobe.dll regularly happens due to system overload. Thus, the first thing you need to assess is if several processes are operating on the device. If they're, search for methods to stop them, and you'll not have to worry about the adobe.dll error anymore.

• Utilize Microsoft System Configuration Utility

The MS System-Configuration Utility will settle the system overload problem, thus freeing up space for your programs to run smoothly and possibly avoid malfunctions, including adobe.dll. The Microsoft System-Configuration Utility manually locates and eliminates all running processes.

• Perform Scans On Your Computer

Running scans on your own Computer may enhance or increase its operation. This technique may also aid in examining your Computer for adobe.dll, or such associated malfunctions, and resolve them forever.

• Repair Adobe.Dll Files and Settings' Errors.

Considering that the adobe.dll malfunctions can be a result of the existence of malfunctions on your own PC's files and options, fix these properly. Begin by fixing the settings on the files and options utilized by your Computer to perform the adobe.dll, and you may have removed this issue completely. Finally, establish the source of the error message to effectively solve it. Once you do that and fix it, your PC will resume normal operations and even boost your work and productivity.

Hello everyone, in today's tips and tricks we will focus on providing you with various solutions on how to solve the Device not migrated error that appears after the Windows update has been performed. Sometimes sadly updates to our operating systems can introduce us to various issues that look scary but in reality, they are solvable and not so scary at all. After all who would not find this message concerning, especially when it happens in the middle of work. The first thing that would pop into my mind is that I have lost tons of work and that something in my hardware has gone very wrong and it is dead. Luckily that is not the case and this error means that due to Windows update drivers were not properly transferred due to some compatibility issues, maybe it was a corrupt update file, etc. Of course, the reason could be hardware malfunction as well, but if everything was working fine before the update, it is a software issue, and I must say it is a common one and fixable. Please keep reading this guide in order to fix the Device not migrated error.

1. Update the Driver

   You should always try this first, if the device is not recognizable, try updating its driver and see if the problem vanishes. In order to update the driver, we will need first to locate which device has not been migrated properly, we will do this with help of a search engine on the internet like google for example. So open your browser of choice, go to a search engine (google for example) and type in the search box first line from your error message, yes, that scary one. You will be given which device has malfunctioned and was not migrated properly, now we will locate the device and update its drivers. To do this press WINDOWS + X on your keyboard to bring up Windows secret menu and choose device manager. Find device inside device manager, right-click on it, and choose properties. Go to the events tab and make sure that the device has migration issues. You have now 3 options for updating the driver, you can do it manually, automatically, or with the driver installer. We will cover all 3 options so you choose which one best suits you. OPTION 1: Manually. Close the Properties tab, go to the device manufacturer website and download the latest driver, if there are no drivers there, the only executable installer for the device skip this step and try the other 2. After you have downloaded the driver package from the website, right-click on the device and choose update driver. Now navigate to the folder where you have downloaded your driver package and update the driver. Reboot your system. OPTION 2: Automatic update. Close the Properties tab, right-click on the device and choose to uninstall. Once the device is uninstalled, restart your system, and Windows will automatically search and install the latest driver for the device. OPTION 3: Via driver installer. If you have downloaded .EXE or executable driver installer from device manufacturers web site try installing it, if the installation fails, try using compatibility mode for the installer. Navigate where the installer is located, right-click on it, and choose properties. Go to compatibility TAB and try installing it with administrator privileges in Windows 8 mode. Reboot your system after this step. This should solve the issues, however, if the issue still persists, follow the next steps.

2. Verify the Corrupted System Files

   Press WINDOWS + X on the keyboard to open the hidden system menu and choose Command prompt (administrator) In the command prompt type in: sfc /scannow and press ENTER. The scanning process and repair of files will take around 15 min. Leave it to finish completely, do not restart, work on the computer or shut it down while the process is active, and only after it is finished reboot your system.

3. Update Windows.

   If your Windows is not updated sometimes this issue can be resolved by updating it on the latest version. Click on start and then on settings. Once the settings screen is opened, find and click on Update and Security. Go to the Windows update tab and click on DOWNLOAD or click on check for updates for the latest Windows fix.

4. Reset BIOS to factory settings.

   Sometimes BIOS not being properly configured can cause issues in Windows itself and prevent it from detecting PnP devices thus creating this error. Restoring BIOS back to the factory setting can help. Turn off your computer and turn it back on. Press delete, f12, f11, or any other key which will take you to BIOS (default key is delete but sometimes manufacturers map this to another one. Once your screen turns ON you will see in the bottom message which key needs to be pressed in order to enter BIOS). Sadly since every BIOS could be different we can not cover step by step guide for each but you need to find the option where you load BIOS defaults, click on it save, and exit. Your computer will restart and boot into Windows, check to see if the problem still persists.

5. Update BIOS

   BIOS can cause issues with certain PnP devices when the newest Windows update is rolled. If reverting BIOS to the factory setting has not been successful try update. Go to your motherboard manufacturer website, find the update and read step by step guide there since updating BIOS differs from version to version and from manufacturer to manufacturer. After the update is done, restart the computer and hopefully, the error is gone.

6. Perform a System Restore

   If everything else fails, perform a system restore to get Windows back into the state before the update was installed and when everything was working fine. Press WINDOWS + R on the keyboard to open the run dialog. In the run dialog, type control panel and press enter to enter control panel, locate recovery and click on it. Inside the recovery screen click on Open System Restore. Choose a date when everything was working in order, the best bet is the date before Windows update and roll it back. Click on date, and then on next.

intelppm.sys blue screen of death is linked to an outdated driver, if you received this error do not sweat we have simple solutions for you. Please keep on reading in order to find out what can you do to fix this error.

1. Update driver Go to the device manager and manually update old-dated drivers. Note that this will take some time because you will need to update each device manually through the device manager but in the end, it will fix the issue.
2. Use automated application Instead of going through each device one by one manually get a dedicated driver fixing device like DRIVERFIX and update all drivers automatically.

If you encounter an error message saying, “The connection was denied because the user account is not authorized for remote login” when you try to establish a remote connection, read on as this post will help you resolve the problem. This kind of error occurs when the targeted host does not allow you to access that system remotely. Based on the error, you are not authorized to log in remotely which means that you need to obtain the correct permission. There are several potential fixes you can try for this error. You can try to check the Remote Desktop Users group or add users to the Security group or check the Remote Desktop Service itself. Refer to the options provided below for more detailed instructions to fix the “The connection was denied because the user account is not authorized for remote login” error.

Option 1 – Try checking the Remote Desktop Users group

You can encounter this error when the Remote Desktop Users group does not have any permission for your user account that you are using to establish a remote connection. Thus, you need to make sure that your user account is a member of the Remote Desktop Users group. How? Refer to these steps:

• Tap the Win + R keys on your keyboard and then type “cmd” in the field and tap Enter or click OK to open Command Prompt.
• After opening Command Prompt, type the “lusrmgr.msc” command and tap Enter to execute it.
• Alternatively, you can also search for “lusrmgr.msc” in the Start Search and once you’ve opened it, select Users and then double click on your user name to open its Properties.
• From there, switch from the “General” tab to the “Member Of” tab.
• Next, if you can’t see any Remote Desktop Users group under the Administrator, you have to add it. To do that, just click on the Add button.
• After that, on the newly opened window, click on the Advanced and Find Now buttons, respectively.
• And in the Search results box, double click on Remote Desktop Users.
• Now click on the OK button to save the changes made and check if you can now connect to a remote host or not.

Option 2 – Try to add a user to the Security group

You can actually block or allow a user from logging on through the Remote Desktop Services. However, if you do not have the right setting, you won’t be able to use this functionality. Thus, you need to confirm this setting. To do that, follow the steps below.

• In the Start Search, type “secpol.msc” in the field and tap Enter to open the Local Security Policy panel.
• From there, go to User Rights Assignment.
• Next, look for a policy named “Allow log on through Remote Desktop Services” located on your right-hand side and then double click on it to open its Properties.
• If you were not able to find the Remote Desktop Users under Administrator, then you have to add it by simply clicking on the Add User or Group button.
• After that, enter “Remote Desktop Users” in the blank field and click the OK button to save the changes made.
• Now restart your computer and try connecting again to the remote host.

Option 3 – Try checking the Remote Desktop Users group

There is a service that’s supposed to be running and needs to be set up correctly for you to connect to the remote host. And so you need to ensure that this service is up and running. To do so, follow these steps:

• Tap the Win + R keys to launch the Run utility.
• Then type “services.msc” in the field and hit Enter or click OK to open the Services Manager.
• Next, look for the Remote Desktop Services and double click on it to open its Properties.
• After that, go to the “Log On” tab and select the “This account” option and then click on the Browse button.
• On the next screen that appears, look for the Advanced button and click on it and use the Find Now button to search.
• You will see “NETWORK SERVICE”. Double click on it and then save the changes you’ve made to the settings.
• Finally, restart your PC and see if the problem is now fixed.

If you encounter errors 1603 and 0x00000643 on your Windows 10 computer while trying to install or update your Google Chrome browser. Although most errors can be fixed by some simple troubleshooting steps, that is not the case for these two errors since they have pretty specific solutions. To resolve errors 1603 and 0x00000643 on your Chrome browser, here are some solutions you need to check out.

Option 1 – Try to run Microsoft Install and Uninstall Troubleshooter

Running the Microsoft Install and Uninstall Troubleshooter could help you fix errors 1603 and 0x00000643 in Chrome as well as the following issue in your Windows 10 computer:

• Corrupted registry keys on 64-bit operating systems.
• Corrupted registry keys that control the updated data.
• Problems that:
  • Prevent new programs from being installed.
  • Prevent new programs from being installed.
  • Problems that block you from uninstalling a program through Add or Remove Programs (or Programs and Features) in Control Panel.

To use the Microsoft Install and Uninstall Troubleshooter, refer to the given steps below.

• First, right-click on the downloaded MicrosoftProgram_Install_and_Uninstall.meta.diagcab file and run it with administrative privileges.
• Next, it will offer you two scenarios to troubleshoot namely, “Installing” or “Uninstalling” and you have to select Installing to resolve the current errors.
• After that, it will show you a list of available programs on your computer. From there, select Google Update Helper and then click Next.
• It will then start to troubleshoot the problem and will automatically apply the fixes for you. It will offer you to uninstall Chrome if it turns out that it’s the root cause of the problem.
• After that, you need to download Google Chrome again and then reinstall it.

Option 2 – Try to clean reinstall Chrome

There are instances when programs leave files behind after you’ve uninstalled them and the same thing can happen to Chrome so before you reinstall Chrome, you have to make sure that you have deleted the User Data folder. To do so, refer to the following steps:

• Hit the Win + R keys to open the Run dialog box.
• Next, type “%LOCALAPPDATA%GoogleChromeUser Data” in the field and hit Enter to open the User Data folder.
• From there, rename the default folder and name it something else, e.g. “Default.old”.
• After that, install Google Chrome again and check if the issue is now fixed.

Option 3 – Try running the Chrome Cleanup tool

You might want to run Google Chrome’s built-in Malware Scanner & Cleanup tool as it could also help in getting rid of any unwanted ads, pop-ups, and even malware, as well as unusual startup pages, toolbars, and anything else that might overtake the network and could affect the performance of the browser.

Option 4 – Try to run the Network 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.

Option 5 – Reset Chrome

Resetting Chrome can also help you fix the error. This means that you will be restoring its default settings, disabling all the extensions, add-ons, and themes. Aside from that, the content settings will be reset as well and the cookies, cache, and site data will also be deleted. To reset Chrome, here’s what you have to do:

• Open Google Chrome, then tap the Alt + F keys.
• After that, click on Settings.
• Next, scroll down until you see the Advanced option, once you see it, click on it.
• After clicking the Advanced option, go to the “Restore and clean up option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
• Now restart Google Chrome.

Same as in Windows 10, Windows 11 also features a lock screen. IN this lock screen by default, you will see a clock and date above the standard Windows 11 background. Not all users will be happy with this choice but do not worry, you can choose and customize your lock screen to better suit your idea of it.

To personalize the lock screen do:

1. Right-click on Desktop and select Personalize
2. Click on the lock screen
3. Choose one of three options and customize it

   • Personalize Your Lock Screen

     this option will let you set a custom image or slideshow for your lock screen. Choose either one that best suits you. Under selecting picture or pictures for the slide show you can uncheck the option to see tips, tricks, and facts on your lock screen.

   • Lock screen status

     when clicking on this option you can select the application widget that you wish to be shown on the lock screen like weather, mail, calendar, etc. Choose if you would like one by clicking on it.

   • Show the lock screen background picture on the sign-in screen

     as self-explanatory this switch will enable or disable chosen lock screen wallpaper on your login credentials screen.
4. Close settings

All settings will be automatically saved and applied and when you wish to lock the screen easiest way is to press ⊞ WINDOWS + L shortcut on your keyboard.

Troubleshoot CoreFoundation dll Error

CoreFoundation dll Error – What is it?

The CoreFoundation dll error is a common error associated with Apple Software products. Most of the Apple Software products rely on this dll file to load and run. This dll file is Apple’s proprietary. The error message is prompted in the following format:

“CoreFoundation.dll was not found” or “Apple Application Support is missing’.

Solution

Error Causes

The CoreFoundation.dll error message is triggered because of several reasons. These include:

• Deleted CoreFoundation dll file
• The CoreFoundation dll file has been overwritten
• Poor installation of the Apple software
• Corrupt software due to viral infection
• Registry problems

Further Information and Manual Repair

It is advisable to fix CoreFoundation dll error code right away to avoid inconvenience. This error may stop you from accessing and running your desired Apple application. Here are some of the best ways to resolve this error on your system:

1. Restore the Deleted CoreFoundation dll File

Since Dynamic Link Library is a shared program, if you happen to delete an Apple program on your PC, chances are you might have deleted that file too in the process. Therefore, the easiest way to recover and restore the CoreFoundation dll file and resolve the error is to look for the file in the recycle bin. If you can’t locate it, then another way to restore the missing CoreFoundation dll file is to download the files from the internet.

2. Reinstall  Apple Software

If the error still persists then it is advisable to re-install Apple software via iTunes or any other Apple Software that you have on your PC. For example, if you have iTunes, then to reinstall it first go to the start menu and then the control panel. Now click on Add/Remove programs and locate iTunes software. Click the Uninstall button next to iTunes. Wait for a while until the program is completely uninstalled. After the installation is complete, restart your PC and then download the latest version on iTunes and install it. Now try running the software again. Hopefully, this will resolve the issue.

3. Scan for Viruses

Another way to resolve CoreFoundation dll error on your system is to scan for viruses. Run an antivirus to detect viruses and remove them from your PC.

4. Clean Your Registry

Remember DLL file errors also indicate a corrupt registry. When you don’t clean the registry it overloads with unnecessary and obsolete files like junk files, cookies, temporary internet history, and bad /invalid registry entries. When these files accumulate, they damage the registry, dll, and system files too. It also causes disk fragmentation. To repair the registry and fix dll files again, download a registry cleaner. Whether you want to scan for viruses or clean the registry, it is advisable to download Restoro. This is a multi-functional and advanced PC Fixer deployed with an intuitive algorithm and multiple powerful utilities. These include an antivirus, a registry cleaner, Active X controls, and class scanner, and a system optimizer. The registry cleaner detects all registry issues and resolves them instantly. It wipes out the unnecessary files cluttering and damaging the registry. It fixes and restores the damaged dll files including CoreFoundation dll file thereby resolving the error. It takes a few clicks to resolve this error. The antivirus feature scans your entire PC and removes all kinds of malicious software including spyware, malware, viruses, and Trojans. To ensure the antivirus does not slow down the speed of your PC, Restoro also features a system optimizer that boosts the performance of your computer significantly. It is powerful and bug-free software with a user-friendly interface that makes it quite easy to operate. You can download it on any Windows version as it is compatible with all. Click here to download Restoro and resolve CoreFoundation dll error now!

Error 0x800706be is a Windows error code that pops up when a particular system file is having some issue. This error pops up on other Windows-compatible software as well as driver vendors. This error signifies a misconfigured or corrupted system file so you might encounter this error in different instances. For instance, this error might pop up when you click the audio icon from the system tray or when the Windows Upgrade or Update has failed. Needless to say, this error can be caused by different factors. Anyhow, this post will show you what you can do to fix the problem when the error pops up during a Windows Update or Upgrade. If you are seeing this error when you try to install the latest Windows updates, it will show a Windows Update failed message and you obviously won’t be able to update your Windows 10 PC until you fix this error. You will keep seeing this error even when you try to reboot or update it a couple of times. As mentioned, the error code 0x800706be appears when there is something wrong with your system files – they are either corrupted or misconfigured. This error is most likely caused by the corrupted Windows Update Components. Corruption of these files is not unusual and it could happen anytime. So since the Windows Update files or components are corrupted, you won’t be able to successfully install the latest Windows Updates. Here are some options you can try to fix the problem.

Option 1 – Try running the Windows Update Troubleshooter

Running the Windows Update troubleshooter is one of the basic things to do when facing any kind of issue with Windows Updates. As long as it can it will detect the issue and automatically solve them so that there will be no need for you to do more technical steps to resolve the issue.

• Tap the Windows and R keys on your keyboard to open the Run dialog box.
• Then type in “control.exe /name Microsoft.Troubleshooting” in the field and tap Enter to open the Windows Update Troubleshooter.
• After that, click Windows Update and follow the next on-screen instructions.

Option 2 – Try resetting the Windows Update Components

This is another basic thing to do in fixing the error 0x800706be. It is also one of the solutions that mostly worked for users who also got this error when trying to install Windows updates. And since the problem is caused by corrupted Windows update components, the most logical thing to do is to delete old files and reset components. To reset the Windows Update components, follow the given instructions below carefully.

• Tap the Windows key once.
• Then in the Windows Start Search, type in “command prompt”.
• From the search results displayed, right-click on Command Prompt and select the “Run as administrator” option.
• After that, type in “net stop wuauserv” and tap Enter.
• Next, type in “net stop cryptSvc” and tap Enter.
• Then type in “net stop bits” and tap Enter.
• Type in “ren C:\Windows\Software\Distribution Software\Distribution.old” and then tap Enter.
• Afterward, type in “C:\Windows\System32\catroot2\Catroot2.old” and tap Enter.
• Next, type “net start cryptSvc” and tap Enter.
• Then type “net start bits” and tap Enter.
• Finally, type in “net start msiserver” and tap Enter.
• Now close Command Prompt and then try updating Windows once more.

In this post, you will be guided on how you can fix error 0x80070013 while executing various operations in your Windows 10 computer like System Restore, Windows Backup, or Windows Updates. When you encounter error 0x80070013, you will see the following error messages. For System Restore, it states:

“System Restore did not complete successfully. Your computer’s system files and settings were not changed. Details: System Restore failed while scanning the file system on the drive <Partition Letter> The drive might be corrupt. You might want to retry System Restore after running chkdsk /R on this disk. An unspecified error occurred during System Restore. (0x80070013) You can try System Restore again and choose a different restore point. If you continue to see this error, you can try an advanced recovery method.”

Whereas in Windows Backup, it states:

“Check your backup, Windows Backup failed while trying to read from this shadow copy on one of the volumes being backed up. Please check in the event logs for any relevant errors. The backup failed, The media is write protected (0x80070013).”

On the other hand, you will see the following error message in Windows Update:

“There were some problems installing updates, but we’ll try again later. If you keep seeing this and want to search the web or contact the support for information, this may help: (0x80070013).”

There are several suggestions you can check out to fix the error depending on where you encountered it. If you encountered it while running Windows Updates, then you can try to reset the Windows Update components or run the Windows Update Troubleshooter. And if you got the error when running System Restore, you can try to run a System File Checker scan or the DISM tool as well as the CHKDSK utility. Lastly, if you got this error when running the Windows Backup service, you can try to check its status in the Services Manager. Error 0x80070013 in Windows Updates:

Option 1 – Try to reset the Windows Update components

• Open Command Prompt with admin privileges.
• After that, type each one of the following commands and hit Enter after you key in one after the other.
  • net stop wuauserv
  • net stop cryptsvc
  • net stop bits
  • net stop msiserver

Note: The commands you entered will stop the Windows Update components such as Windows Update service, Cryptographic services, BITS, and MSI Installer.

• After disabling WU components, you need to rename both the SoftwareDistribution and Catroot2 folders. To do that, type each one of the following commands below, and don’t forget to hit Enter after you type one command after the other.
  • ren C:/Windows/SoftwareDistribution/SoftwareDistribution.old
  • ren C:/Windows/System32/catroot2/Catroot2.old
• Next, restart the services you’ve stopped by entering another series of commands. Don’t forget to hit Enter after you key in one command after the other.
  • net start wuauserv
  • net start cryptsvc
  • net start bits
  • net start msiserver
• Close Command Prompt and reboot your PC.

Option 2 – Run the Windows Update Troubleshooter

You might also want to run the Windows Update Troubleshooter as it could also help in fixing error 0x80070013. 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. Error 0x80070013 in System Restore:

Option 3 – Try to run both Systems File Checker scan and DISM tool

Running the System File Checker scan as well as the DISM tool can help you resolve error 0x80070013 while performing System Restore. Refer to these steps to do so.

• Open the Command Prompt with admin privileges.
• After opening Command Prompt, execute this command to run a System File Checker scan: sfc /scannow
• Once the scan is completed, restart your computer and then see if the error is now fixed. If not, you can run the DISM tool.
• Open Command Prompt with admin privileges again.
• Then type in the following commands and make sure to hit Enter right after you type each one of them in order to properly run the DISM tool:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-image /Restorehealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 4 – Run the CHKDSK utility

• In the Windows Search box, type “command prompt” and from the search results, right-click on Command Prompt and select “Run as administrator”.
• After opening Command Prompt, type this command and tap Enter: chkdsk <Partition Letter>: /f /r /x /b
• The command you entered will start to check for errors and fix them automatically. Else, it will throw an error message saying, “Chkdsk cannot run because the volume is in use by another process. Would you like the schedule this volume to be checked the next time the system restarts? (Y/N)”.
• Tap the Y key to schedule Disk Check the next time your computer restarts.

Error 0x80070013 in Windows Backup:

Option 5 – Try checking the status of the Windows Backup Service

• First, you need to tap the Win + R keys on your keyboard to open the Run dialog box.
• Next, type “services.msc” in the field and click OK or tap Enter to open the Windows Services Manager.
• After that, you will see a list of services and from there, look for the Windows Backup Service and double click on it to open its Properties.
• Then check if its Startup type is set to Disabled. If it is, then change it to “Manual”. Note that this service is essential as it provides backup and restores capabilities.
• Now click on the Apply and OK buttons to save the changes made and then restart your computer. Check if the error is now gone.