Fix The drive is not a valid backup location

The error code 0X8019019A is shown when a user fails to add his Yahoo account to the Mail app due to the outdated or corrupt installation of the Mail app. Not using an App-specific but a normal Yahoo account password may also result in the error at hand. In this guide, we will show you how to effectively fix this error so you can set up Yahoo mail.

1. Reboot PC

   Perform a restart of your system to rule out a temporary glitch in the system. Also, check if you can successfully access your email through a web browser using the same credentials as you are using with the Mail app. Additionally, make sure that no VPN or proxy server is being used to access the internet (VPN/proxy may work fine with the web version of Yahoo mail but may hinder the access through a mail client).

2. Update Windows and the Mail App to the Latest Build

   If your system is not updated to the latest build it can create incompatibility between the OS modules. Updating the Windows and Mail app of your system to the latest build may solve the problem.

3. Re-add the Yahoo Account to the Mail App

   The Yahoo account issue could be a result of a temporary glitch in the communication modules of the system. The glitch may get cleared if you remove and then re-add the Yahoo account to the Mail app.

4. Reset the Mail App to the Defaults

   You may fail to add the Yahoo account to the Mail app if the installation of Mail itself is corrupt. In this scenario, resetting the Mail app to the defaults may solve the problem.

5. Generate an App Password and Use it to Add the Yahoo Account to the Mail App

   Yahoo has implemented tons of security features to its accounts. One such feature is the use of app-specific passwords for less secure apps like the Mail app. If your Yahoo username or password is not working with the Mail app, then using the App-specific password may solve the problem.

CLR20R3 error is received when you are launching an application in Windows 10. It can happen because of two reasons, a corrupted application file or missing system components. Keep on reading in order to find solutions to fix this error.

1. Run the program in compatibility mode

   Locate problematic application executable file Right-click on executable Click on properties Go to the compatibility tab and try running the application in the previous version of Windows or as an administrator.

2. Reset Windows media component

   Right-click on Start, then left-click on command prompt (admin) In command prompt type next command and after each line of command press ENTER regsvr32 atl.dll cd C:\WINDOWS\eHome ehSched /unregServer ehSched /service ehRecvr /unregServer ehRecvr /service ehRec.exe /unregServer ehRec.exe /regserver ehmsas.exe /unregServer ehmsas.exe /regserver

3. Reinstall Windows media player

   Go to control panel Click on Program and Features > Turn Windows feature on or off. Expand Media Features, uncheck Windows Media Player, and click Ok. Restart your PC, go through the same steps, tick Windows Media Player, and restart your computer once again.

4. Reinstall .NET framework

   Go to control panel Click on Program and Features > Turn Windows feature on or off. Uncheck “.NET Framework 3.5” and “.NET Framework 4.8”, and click Ok. Restart your computer, go through the same steps, check “.NET Framework 3.5” and “.NET Framework 4.8”, and restart your computer once again.

5. Update Windows

   Go to settings and check for updates

Hello and welcome to our user account notifications in Windows 10 tutorial where we will dive a little more into how you can control notification and behavior settings for your or someone else's user account in your Windows 10. If you are annoyed with confirmation windows each time you start a new application or install one please keep reading and I am sure you will find just the right setting for you. User account options are a little hidden and not so obvious, well at least not in Windows 10 compared to previous Windows versions. Since we will not be able to find them under typical and standard settings we will need to do few tricks in order to get to them.

Opening control panel

First thing is to press ⊞ WINDOWS + R on your keyboard so the run dialog window pops up on your desktop. Once run dialog is shown type in it control panel as shown in the picture and press OK If you have followed the steps precisely, you should be now in the control panel of Windows 10. Click on the top-right view and choose large icons. The Control panel will switch to a grid-like view, in the current view go to the far-right and almost bottom icon where it says User Accounts and click on it.

User account settings

Once the user account opens click on the bottom link which says Change User Account Control settings. Please note that you will need to be logged in as an administrator or have administrator privileges in order to change this setting. Once you click on the link you will be presented with a User account control slider on the left and a brief explanation on the right Here in the picture, we see Windows default setting and an explanation of when and how he will notify you. If you wish to turn all notifications linked to programs changing computer or you making windows changes, click on the left slider and bring it all the way to the bottom where it says never notify me. If you prefer some notifications try to find which of the remaining 3 settings best suit your needs. Once you are done and satisfied with your choice click on OK.

Microsoft just released Windows 11 Insider build 22000.71. Let’s dive in and see what it brings with you.

Changes and features

New entertainment widget. The entertainment widget allows you to see new and featured movie titles available in the Microsoft Store. Selecting a movie will direct you to the Microsoft Store to see more information about that title. Just open widgets and click or tap on the “Add widgets” button and choose the entertainment widget. For now, the entertainment widget is available for Insiders in the following countries: US, UK, CA, DE, FR, AU, JP. The new context menus and other right-click menus have been updated to use acrylic material. We are testing the usability of a SplitButton for making new folders and files in the File Explorer command bar. The Taskbar previews (when you mouse-over open apps on the Taskbar) have been updated to reflect the new visual design of Windows 11.

Fixes

Taskbar:

• We fixed an issue where if you drag app icons on the Taskbar to rearrange them, it was making the apps launch or minimize when you released the icon.
• Using a long press with a touch on an app icon in the Taskbar to open the jump list should now work.
• After right-clicking the Start icon in the Taskbar, clicking somewhere else should now dismiss the menu more reliably.
• Shift + Right-click on an app icon in the Taskbar will now bring up the window menu like it used to and not the jump list.
• We’ve addressed an issue that was making your mouse move slowly when hovering over the Taskbar previews.
• We’ve included the fix for an issue when using multiple Desktops where an app icon in the taskbar might give the appearance of multiple windows being open when that wasn’t the case on that Desktop.
• When using the Amharic IME you should no longer see an unexpected X next to the IME icon in the taskbar.
• The issue where if you click on the input indicator on the Taskbar and it would unexpectedly highlight Quick Settings has been fixed.
• When you hover over Task View, the preview flyout for your Desktops will no longer pop back up after using Esc to dismiss them.
• We made a fix to address an issue where explorer.exe might crash after hovering over the Task View icon in the Taskbar.
• We fixed an issue where the selected date in the calendar flyout was out of sync with the date in the Taskbar.
• We made an update to address a scenario resulting in some Insiders not seeing the lunar calendar text in the calendar flyout when enabled in Settings.
• This flight addressed an issue that could unexpectedly make the Taskbar background transparent.
• Right-clicking the focus assist icon in the taskbar should now show a context menu.
• The issue from the previous flight where icons in the taskbar corner were getting crushed against the top of the Taskbar has been addressed.
• The tooltip for the location in use icon in the Taskbar should no longer appear blank sometimes.

Settings:

• We fixed an issue making Settings crash on launch periodically.
• Using the volume mixer sliders in Sound Settings should be more responsive now, as well as the page responsiveness as a whole.
• We fixed an issue resulting in Disk and Volumes Settings’ change size option being clipped.
• There was a non-functional verify link under Backup Settings – this has been fixed.
• The Power and Battery Settings page should no longer be reporting that the battery saver is engaged if it’s not.
• The Power and Battery Settings page should also now not crash when launched from Quick Settings.
• We fixed a grammatical error in the Sign-in Settings text.
• The “I forgot my PIN” link was unexpectedly missing in Sign-in Settings when a PIN was set up and has now been returned.
• The issue where the Move option under Apps & Features in Settings wasn’t working reliably should be addressed in this build.
• We’ve mitigated a problem where some of the colors in Settings weren’t updating after switching between dark and light mode, leaving the unreadable text.
• We’ve done some work to help improve the performance of Settings when switching between light and dark mode.
• We addressed an issue where some of the elements of the Themes page in Settings would end up crowded together when the window size was small.
• We resolved an issue where the Pen menu toggle under Taskbar Settings was not in sync with the actual state of the feature.
• Changes made to “Dismiss notification after this amount of time” in Accessibility Settings should now persist.
• Some of the icons you could enable in Taskbar Settings were erroneously labeled Windows Explorer even though that’s not what they were – this should now be fixed.
• The Connect text in Quick Settings has been updated to say Cast.

File Explorer:

• Clicking the command bar button twice should now close any dropdown that appeared.
• The new command bar should now appear when “Open folders in a separate process” is enabled under File Explorer Options > View.
• This build addresses an issue where right-clicking a file and selecting Open With > Choose another app might launch the file in the default app rather than opening the Open With dialog.
• Fixed an issue the desktop and File Explorer context menu would stop launching.

Search:

• We fixed an issue where the option to verify your account in Search wasn’t working.
• Hovering over the Search icon on a secondary monitor will now show the flyout on the correct monitor.
• Search should now work if you open Start and start typing after having gone to the apps list and back.

Widgets:

• When using the Outlook client with a Microsoft account, Calendar, and To-Do updates should sync faster down to the widgets.
• We addressed an issue where if you added multiple widgets quickly from the widget's settings, it could result in some of the widgets not being visible on the board.
• We fixed a bug where widgets could all become stuck in a loading state (blank squares in the window).
• The traffic widget should now follow the Windows mode (light or dark).
• The title of the sports widget should no longer mismatch with the content of the widget.

Other:

• This build addresses an issue where ALT + Tab was getting stuck open sometimes after you released the keys and had to be manually dismissed.
• We made a fix for an issue where Narrator's focus wasn’t ending up on the emoji panel after using the keyboard shortcut to open it.
• Magnifier’s lens view has been updated so the lens now has rounded corners.
• We found an issue that was noticeably impacting Start launch reliability for some Insiders, and have addressed it with this flight.
• We’ve updated the “Most Used” text in the Start menu’s app list so it should no longer be getting clipped.
• Using the semantic zoom in Start’s app list should no longer result in the list being pushed down and to the right off the edge of the window.
• We fixed an issue where if you pressed ⊞ WIN + Z you would need to press Tab before you could use the arrow key to navigate through the snap layouts.
• We addressed an issue where an acrylic area could get left on the screen after repeatedly snapping and unsnapping a window with touch.
• We’ve done some work to mitigate an unexpected flash when moving a snapped window with touch.
• We made a change to help window borders have a little more contrast when “Show accent color on title bars and windows borders” was turned off.

Known issues in Windows 11 repaired

Start:

• In some cases, you might be unable to enter text when using Search from Start or the Taskbar. If you experience the issue, press ⊞ WIN + R on the keyboard to launch the Run dialog box, then close it.
• Based on feedback, we are working on adding access keys to ⊞ WIN + X so that you can do things like “⊞ WIN + X M” to launch Device Manager. Insiders may see this functionality in this build, however, we are currently investigating an issue in which sometimes the option is unexpectedly unavailable.

Taskbar:

• There is an issue in this build where Explorer.exe will crash when the date and time button on the Taskbar is clicked to access new notifications with Focus Assist turned off. The workaround for this is to enable Focus assist to priority or alarms mode. Note that when focus assist is turned on, notification popups won’t appear, but they will be in the notification center when opened.
• The Taskbar will sometimes flicker when switching input methods.
• Taskbar previews may draw partially offscreen.

Settings:

• When launching the Settings app, a brief green flash may appear.
• When using Quick Settings to modify Accessibility settings, the settings UI may not save the selected state.
• The button to rename your PC doesn’t work in this build. If needed, this can be done using sysdm.cpl.
• Settings will crash when clicking “Facial recognition (Windows Hello)” under Sign-in Settings if Windows Hello is already set up.
• Reset this PC and Go back buttons in Settings > System > Recovery does not function. Reset and rollback can be accessed from the Windows Recovery Environment by selecting System > Recovery > Advanced startup, and pressing Restart now. Once in Windows Recovery, choose Troubleshoot.
• Choose Reset this PC to perform a reset.
• Choose Advanced options > Uninstall Updates > Uninstall latest feature update to perform a rollback.

File Explorer:

• exe crashes in a loop for Insiders using the Turkish display language when the battery charge is at 100%.
• When right-clicking the desktop or File Explorer, the resulting context menu and submenus may appear partially off-screen.
• Clicking a desktop icon or context menu entry may result in the wrong item being selected.

Search:

• After clicking the Search icon on the Taskbar, the Search panel may not open. If this occurs, restart the “Windows Explorer” process, and open the search panel again.
• When you hover your mouse over the Search icon on the Taskbar, recent searches may not be displayed. To work around the issue, restart your PC.
• The search panel might appear black and not display any content below the search box.

Widgets:

• Widgets board may appear empty. To work around the issue, you can sign out and then sign back in again.
• Launching links from the widgets board may not invoke apps to the foreground.
• Widgets may be displayed in the wrong size on external monitors. If you encounter this, you can launch the widgets via touch or WIN + W shortcut on your actual PC display first and then launch on your secondary monitors.

Store:

• The install button might not be functional yet in some limited scenarios.
• Rating and reviews are not available for some apps.

Windows Security:

• Device Security is unexpectedly saying “Standard hardware security not supported” for Insiders with supported hardware.
• “Automatic sample submission” is unexpectedly turned off when you restart your PC.

Localization:

• There is an issue where some Insiders may be missing some translations from their user experience for a small subset of languages running the latest Insider Preview builds. To confirm if you have been impacted, please visit this Answers forum post and follow the steps for remediation.

That's is so far, the latest update information on Windows 11 insider build. Stay tuned for more information when it comes as it comes.

One of the most useful built-in tools in Windows 10 is the Check Disk or CHKDSK utility. It is the one that maintains the integrity of the disk that’s connected to a computer which can be launched using the GUI or graphical user interface and using the command line. There are a lot of things that warrant the running of this built-in utility and one of these things is the readability of the disk. Recently, a number of users reported that they encountered an error when they tried to run the CHKDSK utility – the error states, “Cannot open volume for direct access”. This kind of error in CHKDSK appears each time the command line is launched according to the affected users. As per the users who encountered this issue, they receive the following error messages when they tried running a ChkDsk command:

“C:WINDOWSsystem32>chkdsk /f g: Cannot open volume for direct access. C:WINDOWSsystem32>chkdsk /f f: The type of the file system is NTFS. Volume label is 0529357401.”

To fix the “Cannot open volume for direct user access” error, here are some suggestions that might help. Follow them carefully.

Option 1 – Try running the CHKDSK utility on Boot

On the other hand, you can also try to run the CHKDSK utility on Boot so you can fix the error and recover any damaged segments of the drive.

• Open an elevated Command Prompt and enter this command: chkdsk /x /f /r
• After that, you will a message that says, “Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? (Y/N)”
• Type Y and tap Enter to schedule a CHKDSK scan once your computer reboots next time.

Option 2 – Try to run the Primary Hard Disk Self Test

The next thing you can do to fix the problem is to run the Primary Hard Disk Self Test by following the steps below.

• You need to boot your computer into the BIOS first.
• After that, go to the Diagnostics tab and select the “Primary Hard Disk Self Test” option. Note that it may be different depending on the motherboard with different manufacturers but they should imply the same thing.
• Now, wait until the test is completed, and then boot your computer normally.

Option 3 – Try to check the hard drive’s health

The next thing you can do to resolve the issue is to check the health of your hard drive using the WMIC utility in the Windows Command Prompt. This utility will check if your hard drive has any problems which resulted in the “Cannot open volume for direct user access” error.

Option 4 – Try to disable various restrictions on your hard drive

You might also want to disable the various restrictions on your hard drive since it is possible that it is encrypted or restricted which explains why you are unable to perform any operations in it and throws the “Cannot open volume for direct user access” error instead. For instance, if you have BitLocker, you can try to disable it and see if it fixes the error or not.

Option 5 – Try to uninstall or disable the Drive Locking feature on your hard drive

You could also look for any Drive Locking feature on your hard drive that tricks disk changes as it might be the root cause of the problem. Thus, if you find one, you need to either uninstall or disable it and then execute a check disk command to resolve the problem.

Option 6 – Try to disable the application service

Disabling the application service can also help you fix the problem. How? Refer to 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 Services Manager.
• Next, scroll down among the list of services and look for the service related to the security software or disk checker software.
• Once you find it, right-click on that service and select Properties.
• After that, change its Startup type to Disabled and click on the OK and Apply buttons to save the changes made.
• Now restart your computer and don’t forget to enable the service back once the disk check is completed.

Option 7 – Try to use Repair Volume via Windows PowerShell

You could also try to use the Repair Volume using Windows PowerShell. All you have to do is open PowerShell as admin and type the “repair-volume -drive letter <DRIVE LETTER>” command and then tap Enter to run Repair Volume. This should resolve the error.

Socket Error 10060 - What is it?

Socket Error 10060 is a typical Outlook Express error. This error often occurs when the connection to the server fails. It specifically refers to a timeout while communicating with the email providers servers. The vast majority of all emails use SMTP for outgoing mail. Socket error 10060 in most instances is related to the SMTP settings for the user’s email. The error message is sometimes displayed in the following format:

Outlook Express Socket Error10060 - The connection to the server failed Account:’ your account’

Another thing you must know about this error is that it only stops the user from sending emails. This means that you can only receive emails, not send them.

Solution

Error Causes

The cause of this error code is hard to narrow down typically because there are many causes that can trigger the socket error code 10060. Some of the most common causes of this error code are:

• Issues in email settings
• Authentication settings
• Firewall settings
• Malware

Though this is not a critical error code it is advisable to fix it immediately without any delays. This error can hamper your communication via email and slow down your work productivity especially if you use Outlook for communication across the organization.

Further Information and Manual Repair

Here are some of the many methods to fix and resolve this error code. To help you resolve this issue, we have selected and listed down the best, quick, and easy do-it-yourself methods. Try them and repair Socket error code 10060 all by yourself without any professional assistance.

Method 1 - Check the Names of POP3 and SMTP Servers

To begin with, first check the names of the POP3 and SMTP servers to ensure that they are correct. Then check the outgoing SMTP port. Contact your email provider to determine the correct settings. Sometimes email providers change this value more than any other in their individual settings. Get it verified. Change the settings if needed.

Method 2 - Outgoing SMTP Server Requires Authentication

Sometimes the error code may occur due to authentication issues. If this is the reason then, don’t worry it is easy to fix. Simply go to the settings options and check the box ‘My server requires authentication’. Once you check the box, try sending the email again. This is most likely to resolve the socket error 10060 on your PC.

Method 3 - Disable Firewall

Your Firewall security may sometimes be the reason for socket error 10060 too. Therefore if after trying method 1 and 2, the error still persists, then it is advisable to disable firewall. Once you disable it, try sending an email using your Outlook account. If it works, the error is resolved.

Method 4 - Scan for Malware

There is a possibility that the Socket error 10060 is popping on your PC due to malware infection. If so, then it is advisable to download Restoro. This is a highly functional and a user-friendly PC fixer deployed with a powerful antivirus and several other scanners. Run it on your PC to scan for malware. It detects and removes all types of malware including Trojans, viruses, adware, spyware, and more in seconds. Click here to download Restoro to resolve socket error 10060 on your system today.

If you are using the Camera app on your Windows 10 computer but encountered an error code 0xa00f429f with an error message that says, “Can’t start your camera”, read on as this post will guide you in fixing this problem. This kind of error in the Camera app could be due to a recent update gone wrong or it could also be due to a corrupted driver. If you are certain that the camera is connected and is properly installed, you can try to check for updated drivers. The error code signifies that the drivers have to be updated. However, that isn’t always the case sometimes as the problem could also have something to do with corruption in the driver. The effective ways to troubleshoot this problem would be trying to reinstall or reset the Windows Camera app, or update, rollback or uninstall some device drivers as well as use the Registry Editor. Before you proceed with the instructions provided below, make sure that you have admin privileges and don’t forget to create a System Restore point.

Option 1 – Try to reset or reinstall the Windows Camera app

As pointed out earlier, you can also reset the Camera app to fix the error. To do so, follow the steps below.

• The first thing you have to do is go to the My Pictures folder under the C: drive of the File Explorer and then delete the Camera Roll folder.
• Once you’re done, right-click on an empty area on your screen and create a new folder and name it “Camera Roll”.
• Then from the Start menu open the Settings app and select System.
• From there, navigate to the Apps and features section.
• Now go to Camera and click on the Advanced Options and click the Reset button.

Option 2 – Try to reinstall the Camera app

If resetting the Camera app didn’t help, you might want to reinstall it by following these steps:

• Tap the Win + X keys and select the “Windows PowerShell (Admin)” option from the menu to open Windows PowerShell as admin.
• Next, type this command to uninstall the Camera app: Get-AppxPackage *camera* | Remove-AppxPackage
• Once done, exit the Windows PowerShell and restart your computer and then try to install the latest version of the Camera app from Microsoft Store.

Option 3 – Try to rollback, update or disable drivers

The next thing you can do to fix the error code 0xa00f429f in the Camera app is to roll back, or update, or disable device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• After opening the Device Manager, look for the device drivers which have a yellow exclamation mark.
• Then right-click on each one of them. If you haven’t updated this driver in a while, select the “Update Driver” option. On the other hand, if you’ve just updated this driver, then select the Uninstall Device option.
• Next, follow the screen option to update or uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically if you have chosen to uninstall them.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 4 – Try to use the Registry Editor

• Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and then hit Enter to open the Registry Editor.
• Next, navigate to this registry key: ComputerHKEY_LOCAL_MACHINESOFTWAREWOW6432NodeMicrosoftWindows Media FoundationPlatform
• From there, right-click on any empty space on the right side part of the window and select New > DWORD (32-bit) Value.
• Then name it as “EnableFrameServerMode” and double click on it.
• Now set its value data to “0” and its base value as Hexadecimal and then click on OK.
• After that, restart your computer and see if it helped in fixing the problem or not.

If you are trying to update your Windows 10 computer but encounter the Windows update error 0x80244019 instead, read on as this post will help provide you some possible fixes to resolve the problem. This kind of Windows Update error is usually caused by your Windows Update settings or the Windows Update components. Many users who encountered this error reported that the update fails with the said error which keeps them from enjoying the latest features that the Windows Update brings. In such cases, some of the common culprits for this Windows Update error are the Windows Update settings, Windows Update configuration, third-party antivirus programs, and so on. To resolve this error, you can check out the options provided below.

Option 1 – Restart your computer and try installing the Updates again

You can restart your computer and then try installing the updates once again. There are instances when a simple restart resolves Windows Update errors. Aside from that, it would also be better if you make sure that your internet connection is working and that it’s stable. And so after you restart your computer, check for updates once again and see if you’re still getting the error or not.

Option 2 – Try to change the Windows Update settings

You might also want to try tweaking the Windows Update settings. This will prevent other Microsoft products from being updated and besides, you can always turn the option back on afterward. To change Windows Update settings, follow these steps:

• Tap the Win + I keys to open Settings.
• Next, go to Updates and Security and click on the Advanced Options.
• From there, turn off the “Get me updates for other Microsoft products when I update Windows” option.

Option 3 – Run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter is one of the things you can first check out as it is known to automatically resolve any Windows Update errors like error code 0x80244019. To run it, Refer to these steps:

• Tap the Win + I keys to open Settings.
• From there, click Update and Security and go to the Troubleshoot section.
• Next, select Windows Update and click the “Run the troubleshooter” button and wait until it’s finished, and then try to run Windows Update again.

Option 4 – Try to disable the third-party antivirus program

Disabling the antivirus program or any security software installed in your computer is always a good idea you can try when the Windows Update process does not go smoothly. There are times when you encounter Windows Update errors like 0x80244019 due to interference of third party antivirus programs. So before you try updating your computer again, make sure to disable the antivirus or security program and once the Windows Update is done, don’t forget to enable the antivirus program back again.

Option 5 – Try to manually install the Windows Updates

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

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

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

Option 6 – Restart some Windows Update services

The first thing you have to do is to restart Windows Update-related services. Refer to the steps below to do so.

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

net stop wuauserv net stop bits

• After entering these commands, it will stop the Windows Update Service and the Background Intelligent Transfer Service.
• Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.
• Once all the contents in the Software Distribution folder are deleted, restart your PC and then go back to Command Prompt and input the following commands again.

net start wuauserv net start bits

 Since the folder has already been flushed, it will be populated afresh the instant your restart your computer and open Windows Update. Now try to update your computer again and see if the error is fixed or not.

Error Code 0x800704c7 – What is it?

Error code 0x800704c7 occurs when Windows users attempt to update their system. It affects various Windows users including those using Windows 7, Windows 8, and 8.1 and Windows 10. It usually occurs due to poor maintenance of the system and includes common symptoms such as the following:

• Inability to upgrade your Windows operating system
• Message box with error code 0x800704c7

Solution

Error Causes

Error code 0x800704c7 in Windows 10 can occur due to several reasons. For instance, it may be due to corrupted or missing system files. It may also result from malicious programs affecting your system or occur when a program or several programs are running in the background of one’s system while the user attempts to run the update.

To correct this issue, Windows users will need to select one or a few methods, depending on the issues affecting their PC.

Further Information and Manual Repair

Some of the best solutions for error code 0x800704c7 available to Windows users including using tools to scan for missing systems files or correct other issues inherent within your system.

These methods may include the use of Command Prompt and the performance of technical repair procedures. If you are uncertain of your skills, avoid compounding the issue or causing further damage to your PC by contacting a skilled Windows repair technician. This IT professional will be best equipped to use Windows tools and other methods to resolve error code 0x800704c7.

Method One: Scan Your System for Missing or Corrupt System Files

Using System File Checker Tool (SFC), Windows users can check their system for missing o corrupt system files. These utility tools within your Windows device will be able to replace missing files and repair corrupted ones, resulting in a more efficient system.  Run this tool by following the steps below:

• Step One: Go to Start and type Command Prompt or CMD.
• Step Two: Run as Administrator
• Step Three: Type sfc /scannow. (Be sure to place a space between “sfc” and “/scannow”).

After running these procedures, check if the error code has been resolved. Go to Settings > Update & security > Windows Update. Update your Windows operating system. If error code 0x800704c7 reoccurs, you will need to try the next method below.

Method Two: Restore your System

System Restore is one of the best manual repair solutions Windows users can apply when they come across error codes like error code 0x800704c7. That’s because this method requires no technical or advanced knowledge and therefore can be performed by anyone. Simply follow the steps below to restore your system to a period of time in the past where the error was not present on your system. If done correctly, this could enable you to resolve the issue with little frustration on your part.

• Step one: Type Control Panel in the search bar near the Start button
• Step two: Select Control Panel, then Recovery
• Step three: Select System Restore then click Next
• Step four: Select a restore point before appeared on your Windows 10 system
• Step five: Select Next then Finish

Note that once System Restore is enabled it will remove drivers, apps, and even updates installed after the restore point. For this reason, be careful to choose the most appropriate restore point. Also once you’ve completed this task, check to see if you are able to update your system. If the update stops before the process is complete and a message box occurs with the error code 0x800704c7, proceed to the next manual repair option below.

Method Three: Check for and Remove Malware

Viruses or other forms of malware can adversely affect your system, causing error codes and other issues to take place. To resolve error code 0x800704c7 in Windows 10, check for and remove malware using a reputable anti-malware program.

If no anti-virus software is present on your system or if you scan your device but fail to spot an issue, proceed to method four.

Method Four: Use an Automated Tool

This method involves the use of a powerful automated tool. But why is this important you might ask? A third-party tool is often the best solution when all manual repair efforts fail. Automated tools come equipped to tackle the most serious PC problems including error codes which can cause frustration and result in reduces PC performance.

During Windows 10 installation, you will see all the beautiful user interfaces, however, what’s more, important are the drivers, your processor, and free storage disk in order for the installation to be successfully completed. So if you are getting the CompareExchange128 error during the installation of Windows 10, this means that the CPU lacks a very important instruction known as “CMPXCHG16B”. Thus, if you don’t have CMPXCHG16B, then it will result in the CompareExchange128 error when you install Windows 10. In fact, CMPXCHG16B, PrefetchW as well as LAHF/SAHF is a criterion for you to be able to use Windows 10 64-bit version when upgrading from an earlier version of Windows. So what exactly is the CMPXCHG16B instruction? The CMPXCHG16B instruction is the one that performs an atomic compare-and-exchange on 16-byte values. This instruction can also be referred to as “CompareExchange128”. The atomic compare-and-exchange means that the CPU compares the contents of a memory location with a given value. So if the values are the same, it modifies the contents of that memory location to a new given value. Note that this kind of issue only happens to the 64-bit Windows 10 version and the only way to resolve it is by getting an update on the hardware level from the OEM. On the other hand, if nothing really works, it’s maybe time for you to get a new CPU but before you resort to that, in the meantime, you can try following the options given below to fix the CompareExchange128 error during the installation of Windows 10.

Option 1 – Try to update the BIOS and Chipset Drivers

One of the best things you can do to fix the CompareExchange128 error is by updating the BIOS and chipset drivers which is why you need to check if your OEM has an update available for your computer’s BIOS as well as the related chipset drivers. But before that, you need to first check the BIOS version. To do so, follow these steps:

• Type “msinfo32” in the search bar and hit Enter to open the System Information Tools.
• After opening the System Information Tools, check the BIOS version.
• Then take note of that BIOS version. You also need to use the BIOS utility that came with your computer and use it for the upgrade. Note that it is different for every computer and if you don’t have it, you can just go to the OEM website and see if there is an option to download it there.

Option 2 – Try to downgrade to the 32-bit Windows 10 version

If option 1 didn’t work as the BIOS update is not available, you can also try downgrading to the 32-bit version of Windows 10. Keep in mind that this will bring restrictions on the amount of RAM installed and other places but that won’t be a problem as you can still switch.

Option 3 – Try buying a new hardware

If none of the first two options didn’t work for some reason then maybe it’s time for you to purchase new hardware especially if your computer is way too old. In such cases, it’s better to buy new hardware or better yet, a new computer that can keep up for the next couple of years.