Capture screen with Windows 10

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.

Third-party application conflict

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.

Corrupted system files

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:

1. Run SFC scan

   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

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

The file is too large for the destination file system is the error when you try to copy a file larger than 4GB on a drive formatted in the FAT32 file system. FAT32 is the old file system used in previous Windows versions and it was replaced by superior NTFS, altho FAT32 is still used because of its compatibility fact that it could be accessed in various operating systems its disadvantage among others is that it can not hold files larger than 4GB in size. This refers to the size of a single file, so if you have a file that is this large and when you try to copy or move it on a drive formatted in FAT32 you will get this message, and the operation will not be able to complete.

Format drive

In order to actually transfer the file in its glorious size, I am afraid that you will need to format destination drive in NTFS or if you have data on drive which you do not want to lose with formatting, use third-party software to convert file system from FAT32 to NTFS without losing data. I would recommend AOMEI partition assistant, it is a free and proven application letting you both manage your partitions and convert any one of them into another file system without data loss. You can get AOMEI here.

Split file

Another option if you are not keen on installing third-party tools or formating is to divide large files into smaller ones that are less than 4GB in size. You can use any archiving application since built-in Windows ZIP support will not let you split file into various different sizes. The best tool in my humble opinion is WinRAR, but you can choose any proven one. When file is split into parts less than 4GB in size, you will have no issues copying or move the file to the destination drive.

If you suddenly noticed that your Onscreen keyboard in Windows 10 has become completely white or transparent for some reason, then you’ve come to the right place as this post will guide you on what you can do to resolve this kind of issue in your computer. As you know, the on-screen keyboard is included in Windows 10 and has an executable file named “osk.exe”. The on-screen keyboard is a part of the Ease of Access feature in Windows 10 which allows users to navigate the computer with the help of the mouse instead of the physical keyboard. However, there are times when you might encounter some issues when using the on-screen keyboard. One of the issues reported recently is that the on-screen keyboard becomes transparent or it only displays the borders but there is no way for you to access it. You also won’t be able to move it from the view completely. To fix this problem, there are several suggestions you can check out. You can try to check the Fade button or run the Windows Touch Keyboard troubleshooter. You can also restart its process in the Task Manager. For more details, refer to each one of the given options below.

Option 1 – Try to check the Fade button

The first thing you can do is to check the Fade button on the on-screen keyboard. You can find it at the bottom right corner of the keyboard. If it is enabled, then it’s probably the reason why your on-screen keyboard is transparent as it lets it fade in the background. Thus, you have to disable it to resolve the problem.

Option 2 – Try to run the Windows Touch Keyboard troubleshooter

The next option you can check out is running the Windows Touch Keyboard troubleshooter. This troubleshooter will help you identify the problem and would fix them automatically.

Option 3 – Try to restart the process of the on-screen keyboard via Task Manager

The next thing you can do is to restart the on-screen keyboard’s process in the Task Manager. Just follow the steps below.

• First, tap the Ctrl + Shift + Esc keys to open the Task Manager.
• Next, go to the Processes tab and look for the option that says, “Accessibility On-screen Keyboard”.
• Once you found it, click on the drop-down arrow next to it and right click on the “On-screen Keyboard” option, and select End task to end its process.
• After that, tap the Win + R keys to launch the Run utility and type “osk.exe” in the field, and then hit Enter to open the on-screen keyboard.

Error code 0x800ccc0f - What is it?

Error code 0x800ccc0f is an error that occurs when users attempt to send/receive emails in Outlook or Outlook Express. Though information regarding the error is limited and sometimes difficult to decipher to those unfamiliar with error code issues, the following are possible symptoms users can expect when this error occurs:

• Unexpected termination of the connection
• Inability to access email messages sent to one’s account
• Inability to send email messages

Solution

Error Causes

Errors in Outlook or Outlook Express may occur due to a multiplicity of reasons. It may be due to a problem with your network connection or the server. You may also encounter this problem after an extended period of inactivity.

Since the error could be due to one of many issues, several solutions are recommended. However, note that these suggestions require you to make changes that come with various risks. Be sure to implement these instructions correctly to avoid causing more problems to occur.

If you are not confident that you will be able to successfully implement the solutions below, get help from a certified Windows technician or IT professional.

Further Information and Manual Repair

As with other error codes, manual procedures are available which users can take to correct the problem. To implement manual repair, follow the methods suggested below:

Method one: Troubleshoot your Internet Connection

Since error code 0x800ccc0f may manifest itself due to an issue with your network, you can seek to rectify the problem by first checking your connection. To do this, open an Internet browser. Type a valid web address in the address bar and click Enter.

If you are unable to access the website, you may then seek to fix the Internet connectivity issue by using Microsoft Automated Troubleshooting Services. These free tools are available for download on Microsoft’s website.

Not only can these tools fix your Windows Firewall – if this is the cause of your connectivity issues. These automated troubleshooting tools can also resolve other issues related to your Internet browser or network.

However, if after downloading and running these tools error code 0x800ccc0f still persists in Outlook or Outlook Express, implement the solution below.

Method two: Verify your Network Connection

Verifying your network connection is another way you can resolve your Outlook issues, i.e. once the issue is in fact a network-based problem.

To verify your network connection, make sure your computer’s network devices are turned on and fully functioning. Also ensure that the cables that connect your computer to a network are secure. You may also contact your Internet Service Provider (ISP) to verify your connection.

If there is no issue with your network and error code 0x800ccc0f persists, you will need to implement method three.

Method three: Check your Firewall or Router Settings

Problems with sending or receiving email messages based on the 0x800ccc0f error code could also be due to configuration issues for individuals who connect using a router. If this is a misconfiguration issue, you may be able to resolve the problem by bypassing the router and connecting through your modem.

Before doing this, however, be sure to check if your firewall is turned on as connecting directly can leave your machine vulnerable. Prevent attacks by checking your Windows Firewall setting. After making adjustments where necessary to ensure the firewall is turned on, test your connectivity to ensure you can access a connection. Also, check Outlook to see whether the error message has been resolved. If the error persists, consider the next solution.

Method four: Disable Third-party Security Apps

Third-party apps like anti-virus software can sometimes cause interference, leading to errors. For this reason, check if the antivirus on your device is the source of the issue. Start by disabling the antivirus software. You may also turn off the software’s email scanning feature to verify whether or not that is the cause of the error.

Note that disabling your antivirus is only a temporary solution as it is not recommended that you use your computer without such protection in place. Consider replacing your antivirus or uninstalling and reinstalling for a permanent fix if indeed your issue with error code 0x800ccc0f was caused by interference from third-party apps.

Method five: Automated Tool

Also, consider downloading a powerful automated tool to protect your machine from possible errors in the future.

Like in Windows 10, Windows 11 will also support God mode to be enabled and used. For those readers that do know what God mode is, let me explain it in simple terms. God mode is the icon on the desktop that once clicked will open and let you adjust every option in the control panel and some hidden features for Windows inside one application. There are a lot of advantages to having this one-click fast access to features, especially if you are a power user. Luckily creating such an awesome icon and enabling God mode is very easy to accomplish, all you have to do is:

1. Create a new folder where you want to have the God mode icon
2. Rename folder exactly: {ED7BA470-8E54-465E-825C-99712043E01C}
3. Enjoy God mode

As you can see creating and accessing all settings at your fingertips is much easier than most people think. Enjoy your ultimate access to Windows 11 features and if you wish you can drag and drop sections from it into the desktop or anywhere for easy access to that specific topic.

After so many years World of Warcraft is still among the most played MMORPG games in the world. It is still constantly updated with new content and tweak graphically in order to be relevant and fresh. But even the best or most popular ones can still have some minor issues and bugs from time to time. CAS System Was Unable to Initialize is the error that was reported lately by WOW players all around the globe and it happens in multiple Windows systems. In this guide, we will take with this issue and provide you with solutions on how to fix it so you can get back to enjoying the game itself.

1. 1. Repair WOW

      In battle.NET launcher select WOW and click on Options Click on Scan and Repair Let the process finish and then launch the game again

   2. Clean Windows registry

      Windows cleaning registry operation is a complex task and we will not cover each possible scenario here, instead of trying manually to find issues and clean registry download and install third party registry cleaner software.

   3. Run WOW with command line argument

      One of the solutions for this particular error is to run WOW with a specific command line switch: Run battle.NET client as administrator by right-clicking on it and choosing run as administrator If you are not signed in, sign in now Click on World of Warcraft to select it Click on options Click on Game settings Check the box associated with Additional command-line arguments When the box is selected you should've able to add inline argument or switch, add -uid wow_engb and confirm Run World of Warcraft

   4. Enable Secondary logon service inside Windows

      It was reported that enabling this service can fix the issue. Press ⊞ WINDOWS + R to open the run dialog Inside run dialog type in services.msc to open services windows Locate the Secondary Logon service Right-click on Properties from the context menu Inside the properties, screen click on the general tab Change the Startup type to Automatic and hit Apply to save the changes Run World of Warcraft

   5. Delete the cache folder

      Both indices and cache folder needs to be deleted in order to reset corrupted data. Make sure that both World of Warcraft and battle.NET are fully closed For this step to work, you will need to go into the folder where you have installed the World of Warcraft game. By default this is in C:/Program Files/World of Warcraft/ but if you have used another folder go there via file explorer. Once you are inside the folder locate the indices folder and delete it After that locate and delete the cache folder as well Restart your computer and start battle.NET

   6. Remove read-only attribute from WoW folder

      Another reason for CAS System Was Unable to Initialize error is because the World of Warcraft folder has been set to read-only and since the client does not have write privileges it will throw this error. To remove the read-only attribute from the folder go to your World of Warcraft installation folder but do not enter it Right-click on it instead and choose properties Under properties uncheck the read-only box and confirm. Run World of Warcraft

Modem Error 633 error is a dial-up error that usually occurs when using a USB modem with a Windows computer. The Modem Error 633 error message is displayed as the following:

“Error 633: The Modem is already in use or not configured properly.”

Solution

Error Causes

This error can be triggered due to several reasons such as:

• A software program conflicts with the USB modem
• The modem is not configured properly
• The Telephon.ini file is missing or damaged
• There is some issue with the way Windows is managing the communication (COM) ports on your computer.

Further Information and Manual Repair

If you experience the Modem Error 633 on your PC, you don’t have to panic. Though this error does not pose any major threats like data loss, it may hamper your ability to use the internet therefore it is advisable to resolve the error. Repairing the Modem Error 633 is quite easy. There are a number of ways to fix this error. So, let’s get started:

Solution 1: Delete Incompatible Software and Non-Present Modems

• Click on the start menu and go to the ‘Control Panel’. Now choose the option ‘Phone and Modem’.
• Here you will see three tabs, the dialing rules, modems, and advanced. Choose the tab ‘Modems’. As you click on it, you will see modems installed on your PC. To repair the Modem Error 633, select and remove all the incompatible software and modems that are not present and click ‘OK’.
• Now to bring the changes into effect, restart your system with the modem plugged in and try connecting to the internet again.

Solution 2: Change the Communication Ports

If the error occurs because the modem is not properly configured, then this solution is possibly the best way to resolve this error. Here’s what you need to do:

• Click on the Start menu and choose My Computer.
• Now click on the option ‘Manage’ to open the Computer Management Window.
• Once it opens, click the option ‘Device Manager and then expand the option modems. Click on Properties, then the Advanced tab, and the Advanced Port Settings button.
• As you click on the Advanced Port Settings, then click on the COM Port Number drop-down box.
• Choose a new Communication Port. However, make sure it is not already in use.
• Once you make changes, click ‘OK’ and then restart your PC.
• Now Open Device Manager again. Open the Modern Properties Window and then Click the Diagnostics tab.
• After that view the command response window to verify if the error is fixed. If yes, then create a new dial-up connection and connect to the internet with ease.

Solution 3: Disable the Startup items

• Another way to resolve Modem Error 633 on your PC is to go to the start menu and type ‘msconfig’ into the search box and then press ‘enter’.
• Open the misconfig.exe program. As you open it, you will see 4 tabs, General, Boot, Service, Start-up, and Tools.
• Now click on the ‘Start-up’, ‘Disable All’, and then press Apply.
• After you press Apply, a window will pop up asking to restart the computer.
• Confirm it and click restart.
• Once the computer restarts now try connecting to the internet again. This will hopefully resolve the Modem Error 633.

Socket Error 10060 - What is it?

Socket Error 10060 is basically a connection time-out error. This error occurs when the remote FTP server does not respond to CuteFTP. This time-out error occurs after an FTP session is established but even the server doesn’t respond. The error message is displayed in the following format:

‘Connection timed out. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host failed to respond.’

Solution

Error Causes

Socket Error 10060 may occur due to multiple reasons including:

• Blocked port
• Data connection incorrect settings
• When the web proxy connection setting does not allow enough time to receive a response from the destination website and therefore the connection is timed-out.
• Registry issues
• Viral infection

Further Information and Manual Repair

Here are some of the best and quick DIY methods to resolve Socket Error 10060 on your PC.

Method 1: Troubleshoot the Web Proxy Connection

This method is workable and effective if Socket Error 10060 occurs only when the web proxy service is used. To execute it, here’s what you need to do: install the Winsock Proxy Client on your PC. Disable the web proxy settings under the LAN settings on the Connections tab of the internet options. Once you disable the settings, then try to go to the website that you giving you the error. If the site is accessible, the error is resolved.

Method 2: Increase Web Proxy Time out Settings

If disabling the web proxy settings doesn’t work, then try increasing time-out settings. To do so, you will also have to modify the registry. Remember serious problems may occur if you modify the registry incorrectly.

• Here’s what you need to do, click start, run and then type Regedit in the dialogue box.
• Navigate to the following registry subkey: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesW3ProxyParameters.
• On the right side of the Registry Editor, right-click Request TimeoutSecs and then click Modify.
• Click decimal, they type the number of seconds that you want the proxy service to wait until the session times out.
• To confirm changes, click OK.
• Now restart WWW publishing service by going to start, run and type cmd. Click OK to continue.
• Type net stop iisadmin/y and then press enter. After that type net start iisadmin /y and then press enter. Test the new settings by going to the website that displayed the Socket Error 10060 message.

Method 3: Switch from Passive Mode to Active Port Mode

This method is effective if the error occurs due to incorrect data connection settings. CuteFTP uses passive mode by default so to ensure the error is resolved, you may have to switch from passive mode to active port mode. To make this switch, open the site manager and then click once on the name of the problem website. Now on the Type tab change the data connection type to use the port.

Method 4: Configure Firewall Settings

Sometimes the error may also occur due to Firewall.  To resolve, configure Firewall settings to allow FTP protocol.

Method 5: Download Restoro

Whether the error occurs due to viral infection or registry issues, it is advisable to download Restoro. This is an advanced and multi-functional PC fixer embedded with multiple utilities like antivirus and a registry cleaner. The registry cleaning utility removes junk files, cookies, and invalid entries damaging the registry. It cleans, repairs, and restores the registry while the antivirus removes all types of viruses like spyware and Trojans in seconds thereby resolving socket error code 10060. It is safe, user-friendly, and compatible with all Windows versions. Click here to download Restoro today.

Error Code 0x801901F7 – What is it?

Error code 0x801901F7, also known as “The Server Stumbled” error because it shows a message saying “The Server Stumbled. We all have bad days” is associated with Windows Store. Server Stumbled Error 0x801901F7 is an error related to the MS server. The error occurs due to damaged registry files, malware, virus, and corrupted data. You should fix this error to prevent a system crash or a BSOD error. There are some things you can do to fix it. These are not so complex. So, anyone can try these methods to fix error 0x801901F7. Common Symptoms for error 0x801901F7:

• Problems with Windows startup
• System becomes very slow or the system freezes
• Blue screen of death appears
• Windows fails to start some process due to Stop error code 0x801901f7

Solution

Error Causes

• This error is generally caused by corrupt registry files.
• Virus infection can cause this problem.
• Outdated driver, missing .DLL files may also cause this error.
• Microsoft server overload may cause this problem as well.
• Incorrect configuration may cause this problem.

Further Information and Manual Repair

To fix error 0x801901f7, there are four methods listed below. Some might work for you and some might not. Please try all of them to fix this error.

Method 1:

Basic method to fix error code 0x801901F7: Resetting Windows Store Cache Most of the time clearing or resetting the cache helps. It doesn't always work, but you should try this first before moving on to some advanced methods which are mentioned below. To reset the Windows Store cache please follow the simple steps below

• Open RUN by searching or pressing "Windows Key + R"
• Type "wsreset.exe" and press Enter or click on OK.
• Windows Store will open automatically along with a command prompt.
• This will reset Windows Store and you might see it loading as it should.

This method might work but if it fails to solve Error 0x801901F7 then follow the method below.

Method 2:

Advanced method of fixing error code 0x801901F7: Deleting Windows Store database file. By using this method, you will be deleting the database file for Windows Store. This file is located on your C drive or the drive where you installed your Operating System. Follow the steps below.

1. Navigate to C:WindowsSoftwareDistributionDataStoreDataStore.edb.
2. Delete DataStore.edb file from there.
3. Now Open Windows Store and see if you still get error code 0x801901F7.

The Datastore.edb file that you deleted will be automatically created once you perform Step 3 which is launching Windows Store. If you still cannot get this error away then Close Windows Store and Reboot your PC then Launch Windows Store Again.

Method 3:

Modifying Windows update properties: Perform the steps below only if the above-mentioned methods fail. You will be tweaking a few things in the Windows update to see if it helps.

1. Open Task Manager by right-clicking on Taskbar, then click on Task Manager.
2. Go to Services Tab. Click on Open Services at the very bottom of the Window.
3. Now a new window will pop up. Scroll down & find "Windows Update" from the list.
4. Double click on Windows update to open up its Properties.
5. Now from the Startup Type drop-down list, select Automatic. Click on Apply, Start, and then Ok.

Now you need to perform just one more step. Reset Windows Store again (Refer to method 1 for Steps). This should fix your Windows Store error that shows The Server Stumbled with 0x801901F7 Error Code.

Method 4: 

If the error is due to a problem with a driver, then follow the method below to uninstall the current driver:

1. Open the Run command and type “sysdm.cpl” in the text box.
2. Click Enter.
3. Open the Hardware tab on the system properties dialog box.
4. Then press on Device Manager.
5. Double press on Device type and then press on the hardware device that is reporting error code 0x801901F7.
6. Go to the Driver tab and press on Uninstall button to uninstall the device driver completely.
7. Now, install the new driver on your computer.
8. Restart your computer.
9. Run virus scan of your PC
10. Try using a different USB port.

If you do not possess the technical expertise required to accomplish this yourself or do not feel comfortable doing so, download and install a powerful automated tool to get the job done.

Stop C00002lA Fatal System Error- What is it?

C00002lA Fatal System Error is a blue screen of death error that may occur when you start your Windows NT 4.0 based computer. This error causes the screen to turn blue and the system also shuts down. The stop C000021A error message is displayed in the following format:

Stop c000021a {Fatal System Error} The session manager initialization system process terminated unexpectedly with a status of 0xc0000017 (0x00000000, 0x0000000) The system has been shut down.

Error Causes

The stop C000021A error occurs when either Crsrss.exe or Winlogon.exe fails. When the Windows NT kernel identifies that either of these processes has failed, it stops and the error code stop C000021A appears on the computer screen. Here are some of the underlying causes for the stop C0000021A error:

• The incompatible third-party program
• Hard disk issues
• Service pack installation has failed
• Mismatched system files have been installed
• Bad and invalid registry keys

Further Information and Manual Repair

To resolve the stop C000021A Fatal System Error on your PC try the following solutions:

• Remove Incompatible Third Party Programs

If the error occurred after you recently installed a new program, then it is advisable to remove that program. The error occurs due to the incompatibility of the program. To remove the program go to the start menu and click on the control panel. Now click on Add/Remove Program tab and double click on the program name that you recently installed and remove it from the list. Once removed, not reboot your PC. Reinstall a compatible program and run it. It is most likely to resolve the issue. However, if the stop C000021A error still occurs, then it means the problem is critical. It is related to the registry.

• Repair and Restore the Registry

This procedure is slightly long and tricky. To try it, you need to be technically sound. Here’s what you have to do: first create a parallel installation of Windows NT. Start your PC to the parallel installation and then open the Registry Editor. On the Registry Editor’s Windows menu click HKEY_LOCAL_MACHINE on Local Machine and then click Load Hive. Now type the path %systemroot%system32configsystem into the System hive of the prior installation. Then click open. Here you will be prompted to enter the name of the key, type TEST. Note the setting for the current DWord value in the preceding registry key. This is 0x1 and is denoted by CURRENT:Reg_Dword: 0x1. This value indicated that the Current Control Set for your original Windows NT installation corresponds to ControlSet001 in this window. Now if the value is 2, it indicated that the Current Control Set corresponds to ControlSet002. Now locate the following registry key: HKEY_LOCAL_MACHINETESTControlSetXXXControlSession Manager. XXX is the Current Control Set Value. And delete any pending file rename operation entries. Then click TEST hive and then click Unload Hive. After that again repeat the process, open the registry menu and click load hive, here type the path %systemroot%system32configSoftware to the Software hive of the prior installation and then click open. Now you type TEST 2 when you are prompted for the name of the key. Remove any pending file rename operations entries in the following registry keys: HKEY_LOCAL_MACHINETEST2MicrosoftWindowsCurrentVersionRunOnce HKEY_LOCAL_MACHINETEST2MicrosoftWindowsCurrentVersionRunOnceEx Now click TEST2 hive and then click unload hive. Quit the Registry Editor and then restart your original installation. This will resolve the stop C000021A error.