Fix Windows Update Error 0x80072EE2

If you are trying to restore your computer using a System Image that has been created by the Windows Backup and Restore tool but encountered an error message instead that says, “Windows cannot find a system image on this computer”, you’ve come to the right place as this post will walk you through in fixing this error. Here’s the complete context of the error message:

“Windows cannot find a system image on this computer, Attach the backup hard disk or insert the final DVD from a backup set and click Retry. Alternatively, close this dialog for more options.”

In the error message, you are offered two choices – to either Retry or Cancel the operation. You can try to select Retry to try again but you will most likely get the same error if you do so. This kind of error can occur if the name of the WindowsImageBackup folder or any of its sub-folders has been modified. On the other hand, this error can also pop up if this folder or any of its sub-folders have gone missing or have become corrupted. To resolve the error, you can try to move the WindowsImageBackup folder or check its sub-folders. You can also try to isolate the System Image file or rename the System Image folder or remove all the unwanted sub-folders as well as use Command Prompt in Repair mode.

Option 1 – Try to move the WindowsImageBackup folder

The WindowsImageBackup folder must be stored in the root of the volume where it is stored, in line with the functioning of the System Restore utility. For example, if the WindowsImageBackup folder is stored in the “C:/Backups/System Restore Backups/New” location, then you have to move it to the C: drive as well.

Option 2 – Try to check the subfolders of the WindowsImageBackup folder

The classification of folders and files plays an important part to restore in restoring a computer from a System Restore point. Thus, if have modified the names of any files or folders inside the WindowsImageBackup folder, then you need to set the defaults. After that, run System Restore again and check if it fixes the error.

Option 3 – Try to isolate the System Image file

If the System Image file is stored in a USB storage device along with various System Restore images, then it’s no wonder why you’re getting this error. To set things right, you have to make sure that the System Restore image you wish to restore your computer from, is the only one that’s present at the root of the USB storage device.

Option 4 – Try renaming the System Image folder

If you have renamed the System Image folder prior to running System Restore, then it is most likely the reason why you’re getting the “Windows cannot find a system image on this computer” error. This error pops up because the System Restore utility in Windows 10 looks out for the WindowsImageBackup folder so if you have renamed it, you need to change its name back to what it originally was to fix the error.

Option 5 – Try to remove all the sub-folders of the WindowsImageBackup folder

If you have stored some foreign files inside the WindowsImageBackup folder, you need to get rid of them right away and return the folder to its default state as this folder must be left alone and should not be meddled with if you want to run System Restore smoothly.

Option 6 – Try to use Command Prompt in Repair Mode

• Open Command Prompt while your computer is in the Repair Mode.
• Next, type and enter this command where you need to replace “<Partition Letter>” with your drive’s letter: dir <Partition Letter>
• After you’ve found the WindowsImageBackup folder in any of the partitions, type and enter this command: dir <Parition Letter>WindowsImageBackup /s
• The command you entered will display all the contents of the folder exceeding 10 GB in total size. You can check and confirm the integrity of the folder and if you find that the integrity is violated, then it is the reason why you’re getting the error.

Error Code 0xc004c008 - What is it?

This specific Windows 8.1 or Windows 10 error code has to do with the number of times you can use your license number to install windows programs on computers. All windows activation codes are licensed to be used one time for a device, to control piracy, but what happens when your PC crashes, or you have to change a hard drive component and are forced to re-install Windows Operating System. Luckily, there is an easy fix for this issue.

Solution

Error Causes

Basically, when you need to re-install the Windows operating system that you have previously bought and installed on another computer an error code will be displayed with a message telling you that the activation server determined that the specific key could not be used for activation. This occurs because the key has already been used on that computer, or a different one, to install operating systems. There are a few easy fixes for this issue, and most of them should be easily completed on your own.

Further Information and Manual Repair

There aren’t many explanatory ways to repair Error Code 0xc004c008. Below are two methods to go about addressing this issue.

Methods 1:

1. The first step is to open the “Run” Window. You can do this in two ways. First, press the “Window” key and press the “R” key simultaneously. This will open the “Run” menu. Or you can start the “run” window by going to the Start menu and selecting Run.
2. In the Run window type “SLUI 4” and click enter.
3. A Phone Activation window will open up, after which you'll need to select a few options.
4. First chose the country in which you registered the product for the first time.
5. Choose your country and a phone number will be displayed specific to your choice. You will now need to call the number provided.
6. After you’ve dialed you will be prompted to write your “Installation ID”. Type your “Installation ID” on the phone.
7. After that step, you will be asked how many copies of Windows have been installed using this license. Choose “1”, should anything else be chosen but “1”, this will not work.
8. After the process is completed, you will be given a confirmation ID and should be able to proceed as normal with installation. You will have a workable product key again.
9. Install whatever copy of the Windows Operating System you are attempting to with the new product key.

Method 2:

If the first method did not work, the only other option is to call Microsoft and walk through the process with a technician. To do this, dial “1-800-936-5700”. Explain the error that you received and the steps in the update process during which it was displayed. The technician will be able to walk through the steps from getting a new product key to finishing the installation.

If you're not a tech-savvy individual but would like to solve this problem without the aid of a technician, download a powerful automated tool to fix error code 0xc004c008.

Error 1713 - What is it?

If you use Microsoft-developed programs, then you might experience this error code on your PC. It indicates programming limitations. This error, Error 1713 may pop up during the installation of 2007 or 2010 Microsoft Office Suite. The error message appears in the format stated below:

“Error 1713: Microsoft Office has encountered a problem and needs to close. We are sorry for the inconvenience.”

Common symptoms for error 1713 include system crashes, system freeze and sometimes you may feel your Windows running sluggishly.

Solution

Error Causes

Error 1713 may be triggered due to many reasons. However, common causes for this error occurrence include:

• Corrupt Microsoft Office Software
• Corrupt Windows Registry
• Malware
• Deleted Microsoft Office Related Files

Further Information and Manual Repair

No matter, what the cause of this error is, it is advisable to resolve it immediately without any delays. This error may pose serious threats to your PC is not repaired timely and also cause you a great deal of inconvenience limiting you from using Microsoft software programs. Here are some of the best and easy DIY methods that you can try to resolve this issue. To work around these methods you don’t have to be a technical whiz or a computer programmer. Let’s get started:

Method 1 - Use System Restore to Undo Changes Made Recently

During any program deletion, you may have accidentally deleted Microsoft related files because of which you may be experiencing error 1713 on your PC. In such an event, the best way to resolve is to undo recent system changes. To do this, use Windows System Restore Utility. This is inbuilt in Windows. To access System Restore Utility, simply press start and type System Restore in the search box and press enter. Now follow the steps in the Wizard to choose a restore point. Once you select, reboot your PC to activate changes.

Method 2 - Update Drivers

One of the many causes of error 1713 is hardware failure. Hardware failure indicates driver issues. To resolve the problem it is advisable to delete the outdated drivers and update new versions on your PC.

Method 3 - Scan for Malware

Malware can also trigger such error codes on your system and corrupt important files. Therefore remove malware immediately from your PC by running an antivirus. Antivirus will detect and delete all malicious programs in no time.

Method 4 - Repair the Registry

Broken entries, junk files, and invalid registry keys corrupt the registry thereby generating error codes. To resolve you first need to clean the registry and repair it. For this download Restoro. It is a PC Fixer deployed with a registry cleaner. The registry cleaner removes all bad entries stored in the registry, cleans it and repairs the damaged files in just a few clicks. Click here to download Restoro.

What is SYNTP.SYS file? it is a system file created by Synaptics Touchpad drivers that are responsible for all the gestures and tracking users’ touch on the Touchpad. However, what happens when this driver fails? Well, it’s either that your touchpad will partially stop working or it will completely stop working at all. And in such cases, you will encounter the SYNTP.SYS Blue Screen error along with any of the following error codes:

• IRQL_NOT_LESS_EQUAL
• KMODE_EXCEPTION_NOT_HANDLED
• INVALID_PROCESS_ATTACH_ATTEMPT

To resolve the problem, use the instructions given below as a reference.

Option 1 – Run the Memory Diagnostic Tool to check for Memory leaks

• Tap the Win + R keys to open Run and type exe and hit Enter to open the Windows Memory Diagnostic Tool.
• After that, it will give two options such as:
  • Restart now and check for problems (Recommended)
  • Check for problems the next time I start my computer
• Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Note: After you select the option, your PC will restart and check for memory-based issues. If it finds any issues, it will automatically fix them and if there’s no issue found, then it’s most likely not a memory-based issue so you should try the other options given below.

Option 2 – Try reinstalling the Synaptics Driver

You might want to reinstall the Synaptics driver to resolve the SYNTP.SYS Blue Screen error.

• Tap the Win + R keys to open the Run dialog box.
• After that, type “appwiz.cpl” in the field and hit Enter to open the Programs and Features section in the Control Panel.
• Next, you have to look for the “Synatics Point Device driver” and right-click on it, and then click on Uninstall to remove it from your computer.
• Restart your PC and then check for updates under the Windows Update section.
• After that, it will find the latest available and stable Synaptics driver and then install it.
• Then click the “Check or Updates” under the Windows update section and it will automatically look for the latest available Synaptic driver and install it for you.
• Now restart your PC and for the changes to take effect.

Option 3 – Try to run a System File Checker scan

You can also try to run a System File Checker or SFC scan in order to scan your computer for corrupted files that might be the cause behind the Error 0x80000003. Once it finds any corrupted system files, it will automatically fix them. To run System File Checker, here’s what you have to do:

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Restart your computer after the scan is completed.

Option 4 – Perform a System Restore

Performing System Restore might help you in fixing the SYNTP.SYS Blue Screen error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

Option 5 – Try to run the CHKDSK utility

Running the CHKDSK utility might also help you resolve the SYNTP.SYS errors. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the following command and hit Enter:

chkdsk /f /r

• Wait for the process to be completed and then restart your computer.

Option 6 – Use the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like SYNTP.SYS Blue Screen error. It can be found on 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.

Windows 11 has some cool animations including fading effects which make working in it feels nice and futuristic but the cost of this is that there is a slight delay to certain actions performed. If you want the snap fast feature in Windows 11 and do not care about this eye candy there is an easy way to turn animations off inside it.

• First, open Windows Settings by pressing ⊞ Windows + I on your keyboard
• Alternatively, click on Start, search for Settings, and then click its icon.
• When Settings appears, look in the sidebar and select Accessibility.
• In Accessibility settings, click on Visual Effects.
• In Visual Effects, switch Animation Effects to Off.

That’s it, changes will be applied automatically, you can close settings and continue working inside Windows 11 without animations and fades. You can always switch animations back On via settings if you change your mind.

Error 0x00000643 - What is it?

This is a Windows Vista printer error. It occurs when you try to use the plug-and-play service to install a WSD printer on your PC. WSD is the abbreviation for Web Services for Devices. It is a Microsoft API to simply programming connections to web service enabled devices such as printers, file shares and scanners.  The error 0x00000643 code is displayed in the following format:

“Operation could not be completed (error 0x00000643)”

Solution

Error Causes

The error 0x00000643 may occur due to multiple reasons, including:

• No suitable driver installed for your printer
• A firewall or other security program is too restrictive
• Registry file has invalid entries
• Virus and Trojan
• Outdated system drivers

Further Information and Manual Repair

To resolve this error code on your PC, you don’t have to hire a professional technician and spend hundreds of dollars to perform system repair. You can resolve it all by yourself, even if you are not a computer programmer or lack technical expertise. Here are some of the easiest and proven methods to fix the error 0x00000643 on your PC:

1. Update Outdated Drivers

This can be done by accessing the ‘Device Manager’. All you have to do is, go to the start menu and type Device Manager in the start search box. Then click on the Device Manager in the list. On the action menu, click the scan for hardware changes or update the driver.

2. Delete the WSD Port to Resolve Error

Go to the start menu and type printers in the search box. Click printers in the given program list and then click the option add a new printer. After that, select the existing WSD port and any printer driver. Now delete the printer. The WSD will be deleted automatically. Once this is done, connect the printer to your computer. You will see the plug-and-play service will begin to install the printer again. This process is most likely to resolve the issue and reinstall your printer.

3. Disable Firewall

Sometimes the error may occur if the security programs are too restrictive such as the Firewall. To fix the problem simply disable Firewall.

4. Viral Infection

If the underlying cause of the error is a viral infection, then download a powerful antivirus and run it on your PC. Scan for viruses and delete them.

5. Registry Invalid Entries

If you don’t clean the registry regularly, this overloads with unnecessary, redundant and obsolete files like cookies, internet history, junk files, bad registry keys and invalid entries. This damages the registry and generates such error codes. Although you can resolve and repair the registry manually, but that method is slight tricky and time consuming. It may require technical expertise. However, another quick and easy way to clean and restore the registry and resolve error 0x00000643 on your system is to download Restoro. This is a next-generation, advanced, and highly functional PC Repair Tool. It is deployed with an intuitive algorithm and multiple utilities such as a smart registry cleaner, a powerful antivirus, and a system optimizer. The registry cleaning utility detects all registry issues on your PC, removes invalid entries cluttering the registry, and repairs it right away thereby resolving error 0x00000643. The antivirus simultaneously detects malware on your PC and removes them while the system optimizer boosts the speed of your computer significantly. Restoro is bug-free, safe, and efficient. It has simple navigations and a user-friendly interface. This software is compatible with all Windows versions including Vista. To fix error 0x00000643 on your system in seconds, click here to download Restoro now!

Getting a few errors here and there when updating your Windows 10 computer is not uncommon. Some of these errors won’t allow the Windows Update service to initiate while the other ones will halt the process while it’s running. So in this post, we’ll show you what you can do to fix the Windows Update error 0x80070020. The Windows Update error 0x80070020 is most likely caused by some programs installed in the system which interferes with the Windows Update process. It might be an antivirus program, an incompatible program, a potentially unwanted program, or worse, malware. In addition, corrupted or missing files might also be the culprit. Whichever the cause may be, here are some suggestions you need to check out to resolve the problem.

Option 1 – Try to reset the Windows Update components manually

• To manually reset the Windows Update components, first, you need to stop the Background Intelligent Transfer Service, Windows Update, and the Cryptographic Services. To do so, run the following command in Command Prompt and make sure to press Enter after you enter each one of them:
  • net stop bits
  • net stop wuauserv
  • net stop cryptsvc
• Next, delete the “qmgr*.dat” file in order to reset the Windows Update components. To do delete this file, run the following command in Command Prompt:
  • Del “%ALLUSERSPROFILE%Application DataMicrosoftNetworkDownloaderqmgr*.dat
• Now you have to rename both the SoftwareDistribution and Catroot2 folders by entering the following command in Command Prompt:
  • Ren %systemroot%SoftwareDistributionSoftwareDistribution.bak
  • Ren %systemroot%system32catroot2catroot2.bak
• Reset BITS and Windows Update service by entering the following commands in Command Prompt:

• • sc.exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
  • sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
• Now enter the following command:

• cd /d %windir%system32

• RE-register BITS and other Windows Update related files by typing each one of the following commands:

• • regsvr32.exe atl.dll
  • regsvr32.exe urlmon.dll
  • regsvr32.exe mshtml.dll
  • regsvr32.exe shdocvw.dll
  • regsvr32.exe browseui.dll
  • regsvr32.exe jscript.dll
  • regsvr32.exe vbscript.dll
  • regsvr32.exe scrrun.dll
  • regsvr32.exe msxml.dll
  • regsvr32.exe msxml3.dll
  • regsvr32.exe msxml6.dll
  • regsvr32.exe actxprxy.dll
  • regsvr32.exe softpub.dll
  • regsvr32.exe wintrust.dll
  • regsvr32.exe dssenh.dll
  • regsvr32.exe rsaenh.dll
  • regsvr32.exe gpkcsp.dll
  • regsvr32.exe sccbase.dll
  • regsvr32.exe slbcsp.dll
  • regsvr32.exe cryptdlg.dll
  • regsvr32.exe oleaut32.dll
  • regsvr32.exe ole32.dll
  • regsvr32.exe shell32.dll
  • regsvr32.exe initpki.dll
  • regsvr32.exe wuapi.dll
  • regsvr32.exe wuaueng.dll
  • regsvr32.exe wuaueng1.dll
  • regsvr32.exe wucltui.dll
  • regsvr32.exe wups.dll
  • regsvr32.exe wups2.dll
  • regsvr32.exe wuweb.dll
  • regsvr32.exe qmgr.dll
  • regsvr32.exe qmgrprxy.dll
  • regsvr32.exe wucltux.dll
  • regsvr32.exe muweb.dll
  • regsvr32.exe wuwebv.dll
• Now type each one of those commands below.
  • net start bits
  • net start wuauserv
  • net start cryptsvc

Option 2 – Install the updates in a Clean Boot State

You might want to try putting your computer in a Clean Boot state and then install Windows Updates again without any trouble. During this state, you can start the system with a minimum number of drivers and startup programs that will surely help you in isolating the root cause of the issue.

• Log onto your PC as an administrator.
• Type in msconfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• After that, try to install the Windows Updates or upgrade again.

Option 3 – Clear the contents of both the SoftwareDistribution and Catroot2 folders

• 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.

Option 4 – Try to run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update error 0x80070020. 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.

Option 5 – Try restarting the Windows Update Services

• Open the Services Manager.

From there, make sure that you set the following services and Startup types:

• Background Intelligent Transfer Service: Manual
• Cryptographic Service: Automatic
• Windows Update Service: Manual (Triggered)

If you encounter the “Diskpart failed to clear disk attributes” error when you try to change the read-only state of a storage device using the Diskpart application and the request is denied, worry not for this post will give you a couple of fixes to resolve the problem. As you know, Diskpart is used for resolving read-only storage devices by changing their attribute via the command line. So if it is not able to change the attribute of the storage device, then you will most likely encounter an error such as this one. This kind of error is not uncommon and as long as there are no damaged physical attributes, you can resolve it right away. There are tons of reasons why you’re getting this error while using Diskpart, it could be that the storage device has a physical write-protected switch or the disk is hidden or has bad sectors. It could also be because the storage drive might be in RAW format or that you are running the Diskpart application without admin privileges. Whatever the cause may be, here are some options you can try to fix the problem but before you proceed, make sure that you log on to your PC as an administrator.

Option 1 – Check if there is a physical switch on the storage device

There are some USB devices and SD card readers that have a write-protected physical switch that disables all the writable options on the storage device and so if it is turned on, Diskpart won’t be able to change the disk attribute to writable. To check, simply look for the physical switch on both sides of the device and once you found it, make sure that it is toggled off and then plug the storage device back in then try running Diskpart once again.

Option 2 – Modify the WriteProtected key in the Registry Editor

Before you proceed, you have to create a System Restore Point first.

• Tap the Win + R keys to open Run and type “Regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to the following path:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlStorageDevicePolicies

• After that, look for the “WriteProtect” registry entry which is located on the left side of the window, and then double click on it.
• Change its value to “0” and click OK to save the changes made and exit the Registry Editor.

Option 3 – Run CHKDSK to check the drive for errors

When it comes to some issues concerning the hard drive or removable devices, there is a utility in Windows that might help which is called “chkdsk”. This error check utility can help with several issues in the system including the “Diskpart failed to clear disk attributes” error.

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

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

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

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

Option 4 – Clear the attributes on RAW

• Tap the Win + S keys then type “diskpart” in the field.
• Click the Diskpart application and if a User Account Control dialog box pops up, click Yes to proceed.
• After opening an elevated Command Prompt, type in the commands listed below and make sure to tap Enter right after you key in one command after the other.
  • list volume
  • select volume ‘n’ (In this command, you have to replace ‘n’ with the volume number of the drive)
  • format fs=fat32 quick (In this command you also have the flexibility to change the format to ‘ntfs’ or ‘exfat’)
• After executing the commands given, unplug the removable storage device and wait for a couple of seconds and then plug it back in.
• Now try any normal write operations and see if the error no longer appears.

Option 5 – Try checking the hardware components

On the other hand, it is also possible that the issue has something to do with a hardware problem and so you need to check the hardware components on your computer to determine that.

The Local Security Authority Subsystem Service or LSASS.exe is a process in the Windows operating system that is valuable as it enforces the security policy on the computer. Every time you log in to the Windows Server, the LSASS.exe is the one that handles the password changes and creates the access tokens while updating the security log. However, it is also frequently targeted by malware and is often imitated. The original location of this file is at “C:/Windows/System32” so if you open the Task Manager and notice that a process with a similar name has a different location then it is definitely a threat and is exploiting the security of your computer. To resolve issues related to LSASS.exe, here are some fixes that could help.

Option 1 – Use the Performance Monitor’s Active Directory Data Collector

Note that this option will only work on the recent Windows server versions. Refer to the steps below to use the Performance Monitor’s Active Directory Data Collector set on your computer.

• Tap the WINKEY + R button to open the Run dialog box.
• Then type “Perfmon.msc” in the field and hit Enter to open the Performance Monitor and from there open the Server Manager.
• Next, navigate to Diagnostics > Reliability and Performance > Data Collector Sets > System from the left side of the navigation bar.
• Then right-click on “Active Directory Diagnostics” and select Start from the context menu. This will take about 5 minutes or 300 seconds depending on the performance capabilities of your hardware to gather the data required and then take some more time to compile a report from the gathered data. Note that these timings are dependent on one another.
• After the report is compiled, you can find it under Diagnostics > Reliability and Performance > Reports > System > Active Directory Diagnostics. The report will contain all the information as well as conclusions. However, it does not mean that it will also contain the exact cause of the problem with LSASS.exe. Nevertheless, it should help you in fixing the problem.

Option 2 – Try to run the System File Checker

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files that might be the cause why the LSASS.exe file is having some issues. To run the SFC command, follow the steps given below.

• Type “cmd” in the Start search and then right-click on the appropriate search result.
• Next, select “Run as administrator” to open Command Prompt with admin privileges.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

 Now restart your computer and see if the problem is fixed or not.

Option 3 – Put your computer in a Clean Boot State

If none of the options given above helped, you can try putting your computer in a Clean Boot State as this can help you in finding any incompatible programs that’s causing the problem.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

Once you’ve found any incompatible programs, you need to uninstall them. Refer to the steps below to do so.

• In the search box, type in “control” and then click on Control Panel (desktop app) among the search results.
• After that, select Programs and Features from the list which will give you a list of all the programs installed on your computer.
• From there, look for the concerned program and select it and then uninstall it.

Note: If you have downloaded the app from the Windows Store, you can simply right-click on it from the application list and then uninstall it.

If you are trying to install a Windows 10 upgrade but was interrupted with an error saying, “0x80070003 – 0x2000D, The installation failed in the SAFE_OS phase with an error during MIGRATE_DATA operation”, then you’ve come to the right place as this post will help you sort this problem out. When you get this kind of error while trying to upgrade your computer, although there could be various reasons for this, the primary one is that when you upgrade from one update to another, something stopped the upgrade process to migrate the user data. To fix this error, you can try to run both the DISM tool and the System File Checker to automatically repair any corrupted system files. You could also try checking the free storage space of your primary drive and if you have any file lock apps like BitLocker, consider disabling them for they could also be the reason why you’re getting the error.

Option 1 – Run the DISM tool

Running the DISM Tool helps in repairing the Windows System Image as well as the Windows Component Store in Windows 10 which might be the reason behind the Windows Upgrade error 0x80070003 – 0x2000D. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt as admin.
• Then type in this command: exe /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.
• Once it’s done, restart your computer and then check if the issue is resolved or not on the next startup.

Option 2 – Run the SFC scan

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the Windows Upgrade error to appear. SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow and hit Enter.

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Reboot your PC.

Option 3 – Try checking the free storage space on your primary drive

The next option you can try to resolve the error is to see if you have enough free storage space on the primary drive because if you don’t then it’s probably the reason why you’re getting this error. To fix it, you need to free up some storage space by following these steps:

• Open Setting > System > Storage from the WinX Menu.
• From there, you will see a list of all the local and connected storage devices along with the details on the free space.
• Now make sure that the Storage Sense feature is turned On then go find a link that says “Free Up Space” and click it to open.
• After that, a screen which is the built-in program in Windows 10 will appear and will scan your computer for the following junk files so you can free up disk space:
• Windows Upgrade Log Files
• System created Windows Error Reporting Files
• Thumbnails
• Temporary Internet Files
• Previous Windows Installation Files
• Delivery Optimisation Files
• DirectX Shader Cache

Note: Once you’re done freeing up space on your drive, try to run the setup file again.

Option 4 – Try disabling BitLocker and other file lock apps

If you are using BitLocker or other file lock apps, then it could be the reason why you’re getting the error. Usually, file lock apps don’t cause any kind of issue, however, if you have something that works on file level like BitLocker, you can try to disable it. Once you’ve disabled it, try to install the Windows 10 Upgrade again and after you do, enable BitLocker again. This should fix the problem.