Windows defender error 0x800700AA, service can not be started comes when the user is trying to run Windows defender scan on their system.
This kind of behavior happens for two reasons mostly, third-party application conflict or corrupted system files.
In this article, we will tackle both scenarios and provide you with solutions in both cases.
In this rare scenario when Windows defender can not start scan due to conflict with installed service or application in the system solution is quite simple. Restart your PC into safe mode and run the scan from there. In a safe mode environment, minimum drivers and services are only loaded eliminating any conflicts that might occur when everything is booted. If Windows defender can not run the scan in safe mode and you get the same 0x800700AA error then you can eliminate application conflict as a reason and move to the next solution which will tackle corrupted system files. If you, however, managed to run a scan then you have a rare third-party application conflict, you can boot normally into windows and try to eliminate one by one to see which one is causing the issue. The safest bet would be to start with security software because most of the time that is what causes conflicts in running services and applications.
If the previous solution has 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:
SFC scan is a built-in Windows tool for solving corrupted system files 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
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
“Error 2753, The File is not marked for installation.”Note that this kind of error is not bound to only some specific files but it can also happen with any file, be it an executable file or an MSI file. To fix this error, here are some possible solutions that you could try.
"ERROR_FULLSCREEN_MODE" and/or as the hexadecimal value 0x3EF.”
“There were some problems installing updates, but we’ll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x80244022).”To fix error code 0x80244022, refer to the potential fixes provided below.
Disk Write Error in Steam is thrown at you while you try to download or update the game in your library. If you are an unfortunate user of Steam that has encountered this error do not sweat, the error is usually tied to permission in windows or file corruption and not to hardware issues and can be easily resolved.
In this guide, we will go through solutions for this specific error and it is advisable to go through solutions as they are presented since they go from the easiest and most common issues.
The easiest and quickest way of resolving this issue is just a simple restart of the Steam client. Just completely quit Steam and they run it again, if this has not solved the issue try rebooting your PC. In most cases, this can solve the issue since this error is known to be introduced with some communication issues with OS (Windows)
Disk write permissions could also cause this error because if by any chance the Steam library folder has been set or changed to the read-only client would be unable to write anything in it. To easily solve this issue completely exit the Steam client and rerun it as administrator. Just right-click on it and select Run as Administrator. If this has solved your issue run Steam always as an administrator.
To run always as an administrator right click on the steam executable, go to properties, and inside properties go to the compatibility tab. In the compatibility tab check run as administrator and click on OK.
If for any reason cache has become corrupted there is a big chance that this might be an issue why there is a disk drive error in Steam. To clear download, cache goes into your client, and on top drow down menu click on steam. Find and open settings and inside go to the downloads tab. Locate a clear download cache and immediately you will be prompted to restart Steam. After restart, you will be asked to login into steam and the issue with disk write should be gone.
Library folder issues can also be the source of disk write annoyance so let's repair them. Click steam in the top left and go to the settings. Locate and click on Downloads and then go to Steam library folders. You will be here shown all disk drivers you are using for steam games and all of the games that are downloaded.
Select the game you are getting errors with and click on three dots on the far right. From the menu choose the repair folder option. Take note that the more games you have installed, the more time the repair process will need.
Sometimes the issue is not at your end at all, servers can experience problems and outrages and this can directly reflect at your end with a disk write error. If any of the previous solutions have not resolved the issue this is the next logical step to try. If the server is facing issues then changing the download server will resolve the issue at your end.
Click on settings in the top drop-down menu and then click on the Steam library folder. Find the downloads page and then click on download region, Choose another server than one nearest to your location since that's what will Steam choose by default.