Nvidia RTX 4090 & RTX 4080 unveiled

As you know, the Graphics Card in a computer is one of the important components in an operating system as they are responsible for rendering various objects in your computer. However, there are cases when the performance of this rendering can degrade and your computer can trigger a VIDEO_SCHEDULER_INTERNAL_ERROR Blue Screen of Death error instead. The VIDEO_SCHEDULER_INTERNAL_ERROR bug check has a value of 0x00000119 which means that the video scheduler has detected a fatal violation in your computer. Before you troubleshoot the problem, you might want to perform System Restore first as it might help you fix the Stop error. 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 Stop error is fixed or not.

If the VIDEO_SCHEDULER_INTERNAL_ERROR BSOD error is still not fixed after System Restore, then follow the given options below to further troubleshoot the problem.

Option 1 – Try to manually check the Graphics Card hardware

You might also want to check the physical status of your Graphics card and you can do this by disconnecting the Graphics card or any other external device connected to your computer. Once you’ve removed the external device, check it for any damages. If there’s none, connect it back to your computer and check if the VIDEO_SCHEDULER_INTERNAL_ERROR Blue Screen error is fixed or not.

Option 2 – Try removing hardware or drivers that you’ve installed recently

If you have recently installed some hardware or drivers, you might want to disable or remove them since external devices are proven to be one of the factors that trigger Blue Screen errors like VIDEO_SCHEDULER_INTERNAL_ERROR. All you have to do is physically disconnect any external devices that are connected to your computer and then check if it fixes the BSOD error or not.

Option 3 – Try to rollback, update, or disable the Graphics card drivers

Since the VIDEO_SCHEDULER_INTERNAL_ERROR Blue Screen error has something to do with Graphics card drivers, you can either roll back, update or disable them depending on your preference in order to resolve the error.

• 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 4 – Uninstall any faulty drivers

You can also uninstall any faulty drivers via Device Manager. How? Refer to these steps:

• Tap the Win + R keys to launch the Run dialog box.
• Then type “devmgmt.msc” in the field and tap Enter to open the Device Manager.
• From there, look for any faulty drivers. You can identify them easily as they will be marked with a yellow exclamation point. And then check which entries would not affect the normal functioning of your PC.
• Now click on the entries of every faulty driver and click on the Uninstall option.
• Once you’ve uninstalled them, restart your computer to allow your computer to reinstall the faulty drivers you’ve just removed.

Option 5 – Run System File Checker at boot time

• Once you get to the Welcome Screen part, click on Next.
• Afterward, click on the Repair your computer option located on the bottom-left part of the window.
• Then click on Troubleshoot.
• Next, select the Advanced Options and then Command Prompt.
• After opening Command Prompt, type the “sfc /scannow” command and hit Enter to run the System File Checker scan.
• Wait until the process is completed and type “exit” to close Command Prompt and then restart your computer to successfully apply the changes made.

Option 6 – Try to run the Blue Screen Troubleshooter

As you know, the Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like the VIDEO_SCHEDULER_INTERNAL_ERROR error. It can be found in the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

A couple of Windows 10 users have reported an error on domain-connected systems when they tried accessing their computer systems remotely. This occurs when the network level authentication or NLA is enabled on the computer. If you are one of these users, you better keep reading as this post will guide you on how you can fix this error. To resolve this issue, there are several workarounds you can try. You can either disable this option directly via properties or you can also modify some registry entries or sub-keys and restart the system. When you encounter this problem, an error message pops up that states:

“The remote computer that you are trying to connect to requires network level authentication (NLA), but your windows domain controller cannot be contacted to perform NLA. If you are an administrator on the remote computer, you can disable NLA by using the options on the Remote tab of the System Properties dialog box.”

Or you could also see this error message instead:

“The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact your system administrator or technical support.”

Before you proceed in troubleshooting the problem using the options provided below, you need to create a backup for your data or system restore point as well as make a copy of any registry entries you are going to modify.

Option 1 – Disable Network Level Authentication via Properties

The NLA is a useful tool that provides your computer with extra security and helps network administrators in controlling who can log into the system with just a click of a single box. However, there are times when it can become a disadvantage and could prevent you from accessing your system remotely. Thus, you need to disable it using Properties.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” and tap Enter to open System Properties.
• Next, go to the remote tab and uncheck the checkbox for the “Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)” option.
• Now click the Apply button to save the changes made and exit System Properties and then try logging into the remote computer again and see if the problem is fixed or not.

Option 2 – Disable NLA via Registry Editor

Note that you can only use this option if the first one didn’t work for you. Take note that this option will require you to restart your PC completely which could mean some downtime if your computer is running a production server. So make sure to save all your work.

• Tap the Win + R keys to open the Run dialog box and then type in “Regedit” in the field and tap Enter to open the Registry Editor.
• From there, click on File > Connect Network Registry and input the details of the remote computer and then try to connect.
• Navigate to the path below after you’re connected:

HKLM >SYSTEM > CurrentControlSet > Control >Terminal Server > WinStations > RDP-Tcp

• After that, change the values given below to “0”
  • SecurityLayer
  • UserAuthentication
• The navigate to PowerShell and execute this command – restart-computer

Option 3 – Disable NLA via PowerShell

PowerShell allows you to tap into the remote computer and once you’ve targeted the machine, you can execute the commands given below to disable NLA.

• Tap the Win + S to open Search and then type in “PowerShell” in the field. Right-click on the related result and select the “Run as administrator” option.
• After opening PowerShell, execute the command below:

2. Once in the PowerShell, execute the following command:

$TargetMachine = “Target-Machine-Name” (Get-WmiObject -class “Win32_TSGeneralSetting” -Namespace rootcimv2terminalservices -ComputerName $TargetMachine -Filter “TerminalName=’RDP-tcp'”).SetUserAuthenticationRequired(0) Note: In the command given, the “Target-Machine-Name” is the name of the machine you are targeting.

Option 4 – Use the Group Policy Editor to disable NLA

Another option you can use to disable NLA is via the Group Policy Editor. This is ideal for you if you are blanket disabling. Just take note that the Group Policy Editor is a powerful tool and that if you make some mistakes by changing values you have no clue about, you can render your computer useless so make sure that you create a backup for all the values before you proceed.

• Tap the Win + R keys to open the Run dialog box.
• Then type in “gpedit.msc” and tap Enter to open the Group Policy Editor.
• From there, go to this path – Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security
• After that, search for “Require user authentication for remote connections by using Network Level Authentication” and set it to disabled.
• Now check if the error is fixed or not.

So you have just got home from that new computer store with your fancy and all-new mouse, screen, keyboard, etc. You plugged in your new component, Windows detected it, installed drivers for it and it is working like a charm. A few months later down the road and the computer starts little by little to slow down. Plug and play is a great concept, and automatic detection is even greater but how time passes old unused stuff piles in your hard drive and in Windows itself thus slowing down your computer and taxing it more and more as new components and software are added. Old drivers from old components sadly are not removed from Windows itself and over some larger period of time they can pile up and slow down your daily operations on the computer or even cause some problems in it. This guide will teach you how to manually remove old unused device drivers from your Windows so it is fresh and like new again.

Making old devices visible

In order for us to remove old drivers, the first thing we must do is make them visible in our device manager, old drivers are hidden and will not show up, we must make this happen. We do this by pressing WINDOWS + X keys on your keyboard to bring up a hidden menu in Windows. Once the menu appears, click on Command Prompt (admin) Once the command prompt with administrator privileges comes on-screen type in it following string: The device manager will open, go to view > snow hidden devices in order to show unused devices.

Removing old device

Open any category and if there is a device that was once used and still has its drivers in the system it will be shown as faded out. Right-click on the device and click on uninstall device to remove it completely from your system. Please always be careful when removing devices so you do not remove the device which is being used by mistake and always double-check that you are removing something that you used to have on your system. This method will show all hidden devices even ones that are hidden but crucial to the system working properly.

There are instances when you open a picture or an image in the Windows Photo Viewer and instead of displaying the image, it displays nothing and you’ll see an error message instead that says, “Windows Photo Viewer can’t display this picture because there might not be enough memory available on your computer”. Although this may look like a clear-cut issue of less storage space or low RAM in your computer, that’s not always the case. Security experts noticed that even when your computer has enough resources and disk space, this kind of problem could still occur. So if you experience the same thing, you need to check the Color Profile of your screen. For more information, refer to the detailed instructions provided below but before you proceed, make sure that you close some processes in the Task Manager or restart your computer and see if it helps in fixing the problem. You can also try using the Disk Cleanup tool. To use it, refer to these steps:

• Tap the Win + R keys to open the Run dialog box and then type “cleanmgr” in the field and hit Enter to open the Disk Cleanup window.
• After that, select the drive you want to clean.
• Now click OK to clean the disk and restart your computer.

If the Disk Cleanup tool didn’t help in resolving the issue, refer to the instructions below. Step 1: In the search box, type “color management” and then select the “Change advanced color management settings for display” option from the search results. Or you could simply go to Settings > System > Display, Advanced display settings, and from there, select display and click on the Display adapter properties of Display. Step 2: Next, switch to the Color Management tab and click on the Color Management button. Step 3: Select the monitor where you’re getting the “Windows Photo Viewer can’t display this picture because there might not be enough memory available on your computer” error in the next window. And if you have two displays, make sure that you select the primary display. You also have an option to identify the monitor. Step 4: Once confirmed, select the “Use my settings for this device” checkbox. Step 5: After that, select the Profile listed under the “Profiles associated with this device” option and then click on Remove. Step 6: Next, go to the Advanced tab and make sure that all settings are set to System default which includes a device profile, perceptual images, rendering intent, Relative Colorimetric, and many more. Step 7: Once you’re done, you have to restart your computer and then try to open the same image you were trying to open earlier and then check if you can now open it instead of seeing the error.

When you receive Error 0x800704C8 when trying to move a file inside Windows 10 operation is stopped and it can not continue leaving you with the file in its original location without a copy. Several issues can be the cause of this type of behavior and error and after some digging and analyzing we are bringing you various solutions for this error and how to fix it.

Ownership issues

It turns out that not having ownership of fie can cause this error and prevent you from copying it. For some reason, Windows can assume that file is owned or used by another application or process and thus prevents you from making a copy since you do not have ownership of it. Resolving this particular issue will require you to install a third-party application that is tailored for this kind of task. After some talk and research, we found out that there is a freeware application that can solve this issue quite fastly. Unlocker is the name and the download link is here. Once downloaded, install it and run it. Once inside the application browse to the location where you need to change the ownership, click on it to select it, and click OK. Use the No Action drop drown menu to select Move, then click OK

Antivirus Issue

As with other file and application issues, this error could also be a product of antivirus marking it inaccessible to Windows and thus preventing copy or move operation on it. note: Do not turn off Windows defender since it was proven that it is not the cause of this kind of error, so if you are using only Windows defender you can skip this solution. How temporary turning off each security suite is different and it depends on the application itself we can not cover in detail the procedure here. Go to your security suite manufacturer's website and get information there or if you want, go directly to applications and features inside Windows and uninstall the software.

Visual Studio issue

• If the file you are trying to move is part of a Visual Studio project then the issue can be linked directly to Visual Studio itself, luckily the solution is quite easy. All you have to do it to exit Visual Studio and then run it with administrator privileges.
• In order to run Visual Studio with elevated privileges locate its executable file and right-click on it.
• Choose properties and go to the compatibility tab
• Inside compatibility tab check box that says run this program as an administrator

Corrupted system files

If the previous solutions have not provided you with results then you have system file corruption that needs to be fixed. Move from one solution to another as presented below:

1. Run SFC scan

   SFC scan is a built-in Windows tool for solving corrupted system file issues, it is fully automated and does not require from the user any kind of knowledge or information. To run it and scan the system do the following: Press ⊞ WINDOWS + X to open the secret menu Left-click on the command prompt (admin) In command prompt type SFC /SCANNOW and press ENTER Wait for the process to finish, do not interrupt it and once it is done, restart your computer

2. Run DISM scan

   DISM scan is similar to SFC scan but it tackles different types of system file corruption and it is recommended to run it also after SFC has been completed. Please note that for DISM scan to be successful you will need a stable internet connection since DISM will replace corrupted files with new ones downloaded from Microsoft. To run it do the following: Press ⊞ WINDOWS + X to open the secret menu Left-click on the command prompt (admin) inside command prompt type: exe /online /cleanup-image /scanhealth followed by ENTER, then type: Dism.exe /online /cleanup-image /restorehealth also followed with ENTER. Leave scan to finish and reboot your PC

Code 42 - What is it?

Code 42 Error is referred to as a Device Manager Error code. Before we explain what this code indicates, it is important to understand what ‘Device Manager’ is and its functions.

Device Manager is basically a Windows tool that helps manage devices attached to the system such as the Printer, Scanner and the USB Device. The Device Manager Error code 42 occurs when a duplicate device is detected.

Error Code 42 is displayed in the following format:

“Windows cannot load the device driver for this hardware because there is a duplicate device already running in the system. Code 42”

Solution

Error Causes

Narrowing down to one particular cause for error code 42 is not virtually possible because it may be triggered due to many underlying reasons. These include:

• When a bus driver incorrectly generates and creates 2 identically named devices
• When a device with a serial number is found in a new location without being removed from its original location
• Mis-configured drivers

No matter what the reason for this error code,, to avoid inconvenience and to ensure proper hardware performance, it is advisable to fix it right away without any delay.

Further Information and Manual Repair

If you’re not technically sound, the code 42 message display can panic you. But don’t worry, the error message sounds complex but it is quite easy to fix.

To resolve code 42 in a few minutes, simply try the methods given below. These methods are easy-to-perform, effective and more importantly require no technical expertise.

Method 1 - Restart Your System

Code 42 can pop up due to some temporary glitch in the Device Manager. By simply restarting your PC, you can resolve this problem.

Therefore, first things first, restart your system. However, in case it doesn’t work out, try other methods.

Method 2 - Launch the Troubleshooting Wizard

Launch the troubleshooting wizard to find the underlying problem and resolve it accordingly. To do this, proceed with the following steps:

• Go to the start menu
• Type Device Manager in the search bar and press enter
• Now click on the ‘General Tab’
• Then click on ‘Trouble Shoot’ to launch the Troubleshooting Wizard
• After that follow the instructions in this Wizard to diagnose the problem and resolve it.

Method 3 - Restore Your PC to its Previous State

Another method to fix code 42 is to use the System Restore tool to restore your PC to its previous working state before the error popped up. To do this,

• Go to the start menu
• Type System Restore in the search bar and press enter
• Now click on ‘Restore my computer to an earlier time’ and then click ‘Next’
• After that select the restore point on the restore point list and confirm settings
• Restart your PC to activate changes
• Before restoring your PC to its previous state, create a backup. By creating data backup you can avoid data loss issues, which are likely to occur during this process.

Creating backup manually can be time-consuming and a painstaking task. The best way to create backup and restore your PC to its normal state is to download DriverFIX.

It is a user-friendly device driver management software that helps create data backup automatically and simultaneously restores your PC back to its normal working state in a few seconds.

This software is compatible with all Windows versions.

Click here to download DriverFIX on your system to resolve error code 42.

When you have to connect to a drive that’s on a different computer or on external storage, that’s where the mapped network drives come in. Mapped network drives make accessing files a lot easier. However, there are times when it won’t work for some reason. Windows will notify you about the unavailability of mapped network drives in several ways. For one, Windows might display a red X on the network drives or it could be that its status will be unavailable when you try to use it from the Command Prompt or via a notification. It is recommended that you run a few scripts when you log in to your PC as it may so happen that the network drive takes more than usual to connect. Before you start troubleshooting the problem using the given options below, keep in mind that some workouts might only work under certain scenarios. You might need some network access at logon or you might need access to the Group Policy settings. So you need to choose what you prefer more. You can try the given workarounds below if the mapped network drives are not showing or connecting or working on your Windows 10 computer. These workarounds use scripts to make sure that you are connected to them as soon as you start to use your PC. As mentioned, before you can troubleshoot, you need to create scripts first. There are two scripts here namely MapDrives.ps1 which is executed by the second script named MapDrives.cmd and is done at a regular and non-elevated Command Prompt. Follow the steps below to get started.

• You have to create a script file named “MapDrives.cmd” first and then save it on a place where the files are safe. To do that, open a text editor like Notepad and then copy and paste the following script:

PowerShell -Command "Set-ExecutionPolicy -Scope CurrentUser Unrestricted" >> "%TEMP%StartupLog.txt" 2>&1 PowerShell -File "%SystemDrive%ScriptsMapDrives.ps1" >> "%TEMP%StartupLog.txt" 2>&1

• After that, save the file and name it “MapDrives.cmd”.
• Next, create a script file named “MapDrives.ps1” and then copy and paste the following content. Just make sure to save both scripts in the same folder.

$i=3 while($True){     $error.clear()     $MappedDrives = Get-SmbMapping |where -property Status -Value Unavailable -EQ | select LocalPath,RemotePath     foreach( $MappedDrive in $MappedDrives)     {         try {             New-SmbMapping -LocalPath $MappedDrive.LocalPath -RemotePath $MappedDrive.RemotePath -Persistent $True         } catch {             Write-Host "There was an error mapping $MappedDrive.RemotePath to $MappedDrive.LocalPath"         }     }     $i = $i - 1     if($error.Count -eq 0 -Or $i -eq 0) {break}     Start-Sleep -Seconds 30 } Note: Now that you’ve created the script files, it’s time for you to proceed to the options given below.

Option 1 – Try creating a startup item

Note that this option only works on devices that have network access at login. So if it’s not there, the script will fail to reconnect the network drivers automatically. To create a startup item, here’s what you have to do:

• Open the Startup folder located at %ProgramData%MicrosoftWindowsStart MenuProgramsStartUp.
• From there, copy and paste the MapDrives.cmd.
• After that, open the Scripts folder located at %SystemDrive%Scripts copy-paste MapDrives.ps1 and then copy and paste MapDrives.ps1 in there.

Note: After you complete the steps above, a log file named “StartupLog.txt” will be created in the %TEMP% folder. Now all that’s left for you to do is to log out of your computer and then log back in. This will ensure that the mapped drives are open.

Option 2 – Create a scheduled task

It is possible to create a scheduled task that runs as soon as you log in to your computer. To create a scheduled task, follow the steps below.

• You have to copy the MapDrives.ps1 script file to the scripts folder of Windows located at %SystemDrive%Scripts.
• After that, open the Task Scheduler and select Action > Create Task.
• Next, type a name and description of the task in the General tab.
• Then click on the Change User or Group button and select a local user group and click OK.
• Now check the box labeled “Run with highest privileges” and switch to the Triggers tab.
• From there, create a new trigger with the “At Logon” option in the Begin the task drop-down menu and then click OK.
• After that, switch to the Actions tab and create a new action then choose to Start a program.
• Next, type “Powershell.exe” in the Program/Script field, and in the Add arguments (optional) field, type the following:

-windowsstyle hidden -command .MapDrives.ps1 >> %TEMP%StartupLog.txt 2>&1

• And in the Start in the (optional) field, type “%SystemDrive%Scripts” as the location of the script file.
• Now under the Conditions tab, select the “Start only if the following network connection is available” option and then select Any connection and click OK.
• Restart your computer or log off from your account and then log back in so that the task will be executed.

Option 3 – Use the Group Policy settings

You need this option if the mapped network drives are defined via Group Policy settings. You have to update the action of the drive maps to Replace. As a result, it will delete the existing mapped drive and create the mapping on each logon again. However, any settings on the mapped drive that are changed from the Group Policy settings will be gone on each logon. So if the changes don’t work, you need to run the gpupdate command together with the /force parameter in order to refresh the Group Policy setting quickly.

There are various complex tasks that take place under the hood while you upgrade or clean install the Windows operating system on a computer. Because of its complexity, there are times when you might encounter some errors when you upgrade or clean install Windows 10. One of the errors you could encounter is the error that states, “Windows could not prepare the computer to boot into the next phase of installation. To install Windows, restart the installation”. This error does not only occur in Windows 10 as it could also occur on the other versions of Windows. There are a lot of possible causes for this error. It could be due to incompatible BIOS, corrupted system files, improper installation media or it could also be due to excessive hardware plugged into your computer and so on. Whatever the cause is, here are some potential fixes you need to check out to fix the problem.

Option 1 – Try to disconnect or disable newly installed hardware

In this option, you will have to disable or remove the hardware you’ve just installed recently since external devices could be the one that’s causing the Blue Screen of Death error to appear. To do that, just disconnect any external device that’s connected to your computer physically and then check if it fixes the error.

Option 2 – Try to update the BIOS

As you know, the BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “msinfo32” in the field and press Enter to open System Information.
• From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
• After that, you should see the developer and version of the BIOS installed on your PC.
• Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
• If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
• Now double click on the downloaded file and install the new BIOS version in your computer.
• Now restart your computer to apply the changes made.

Option 3 – Try to reconfigure all the created partitions

You could also try to reconfigure the partitions by deleting and recreating all the available partitions on your computer and then see if it fixes the problem.

Option 4 – Make a proper bootable USB Drive/Stick

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

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

If you see the following error message in the File History tab of the File Recovery utility of the Windows Backup module in your Windows 10 computer, read on as this post will guide you in fixing it with the help of two potential fixes.

“An internal error has occurred: The specified resource name cannot be found in the image file. (0x90070716).”

You can also encounter this error when you run the System Image Backup function. As mentioned, you can resolve this error using two potential fixes namely checking the status of the Windows Backup Service and checking the settings in the Windows Registry. For more details, refer to the instructions provided below but before you proceed, it would be better if you create a System Restore point first.

Option 1 – 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.

Option 2 – Try checking the Registry setting of Windows Backup

• Tap the Win + R keys to open the Run dialog box.
• Then type “Regedit” in the field and tap Enter to open the Registry Editor.
• After opening the Registry Editor, navigate to this registry key: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWindowsBackup
• From there, look for DWORDs named “ValidConfig” and “ValidSystemImageBackup” located in the right-side panel.
• Once you found them, delete them or set both of their values to “0” and make sure that the base is Hexadecimal and click OK.
• Now exit the Registry Editor and restart your computer to apply the changes made.

If you are trying to copy a folder or a file but encountered an error that says, “An unexpected error is keeping you from copying the folder. If you continue to receive this error, you can use the error code to search for help with this problem”, read on as this post will guide you on how you can fix this error. This kind of error is a CHKDSK error. It is the “Volume is dirty” error message with error code 0x80071AC3 which indicates that the CHKDSK operation on your computer did not go through due to some corrupted sector of your hard drive, data corruption, corrupted system files, malware infection, as well as improper installation of an application that left some residual folders and files and many more. To fix the Error 0x80071AC3, here are some potential fixes you can check out to resolve it:

Option 1 – Run the Check Disk utility

You can also run the Check Disk utility to fix the error when you connect your USB or external device.

• 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 /r /f <PARTITION LETTER>
• 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.

Option 2 – Try to check if a particular volume is dirty and exclude it

The next thing you can do to fix the problem is to check if the particular volume is dirty and exclude it. To do so, follow these steps:

• In the Start Search, type “command prompt” in the field 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: fsutil dirty query <PARTITION LETTER>
• After that, you will see either of the following results of the command you just executed:
  • “Volume <PARTITION LETTER> is dirty”
  • “Volume <PARTITION LETTER> is not dirty”
• If you see the “Volume <PARTITION LETTER> is dirty” message, then you can just skip checking the drive for errors by executing this command: CHKNTFS /X <PARTITION LETTER>

Option 3 – Try to format the destination drive

If the first two options above didn’t work, then you might want to try formatting the drive can also help you resolve the error. To format it, follow these steps:

• To get started formatting your drive, tap the Win + E keys and then go to the access page of the drive.
• Next, right-click on the drive and select Format.
• After that, uncheck the “Quick Format” option and then format your drive properly.
• Now once the formatting process is finished, unplug the drive and plug it back in afterward.
• Check if the error is already fixed. If the drive is not initialized, tap the Win + R keys and hit Enter.
• After opening the Run dialog box, type “diskmgmt.msc” and hit Enter to open Disk Management.
• From there, right-click on the drive volume and select initialize disk.
• Next, select the correct partition type and proceed.