How to Fix the Error Code 3

What is Backup Error 0x80070002?

Error 0x80070002 shows once you’re done backing up files through the Windows Backup program on a system running Windows 7, you see a notification that pops up with a message that reads something like: “Check your backup results. The backup completed but some files were skipped.” You try finding out the reason and you hover over to the Options button beside the message, then you get to read the following lines: “Check your backup results. The backup completed but some files were skipped. View skipped files.” Upon clicking the “View Skipped Files” option, the backup error 0x80070002 pops up on your screen and you’re left scratching your head, wondering what you’re going to do now.

Solution

Error Causes

There are multiple error logs that you will encounter in backup error 0x80070002 as per different conditions. The two most common cases in which this error shows up are stated below:

Case 1

You will see the following message when you press “View skipped files”: “Backup encountered a problem while backing up file C: Windows/System32/config/systemprofile. Error: (The system cannot find the file specified. (0x80070002))” You will face this case if you have backed up a library that included custom folders that were located in your user profile.

Case 2

Upon pressing “View Skipped files” you will encounter the below-mentioned messages: “Backup encountered a problem while backing up file C:/Users<User>AppDataLocalLow. Error: (The system cannot find the file specified. (0x80070002))” “Backup encountered a problem while backing up file C:/Users<User>Contacts. Error: (The system cannot find the file specified. (0x80070002))” “Backup encountered a problem while backing up file C:/Users<User>Searches. Error:(The system cannot find the file specified. (0x80070002))” You are likely to encounter any of these messages in case:

• The Windows Backup program is trying to back up your files in either one or all of these folders (LocalLow, Searches, Contacts).
• All three of these folders don’t exist in your system.

Keep in mind that all three of these folders exist due to the installation of certain programs and applications on your system.

Notes

The backup error 0x80070002 is also found to occur while using USB devices instead of storage devices. Other occurrences include the times when input/output (I/O) operations are performed on the USB device, which results in failure.

Further Information and Manual Repair

To make sure this issue is resolved, you will have to follow either one of the following solutions as appropriate to your situation:

Solution for Case 1

1. Ignore the error. The store files of the custom library in your user profile will not be created as backups.
2. Transfer the library folder from where it currently exists to a place outside its current folder (user profile). For instance, you can move the library folder to an entirely new destination such as “C: My Folders”
3. Remove the library folder from the list of files that you are backing up using the Windows Backup program. Then, add the original place of the library’s content in the list.
4. Go back and check step two. If carried out successfully then add a link to the folder you moved from the library. Check to see if the backup includes the library folder. To make sure, you have to do as follows:

• Go to Start and select your username.
• Hover across to the folder you wish to move, right-click on it and select “Cut”.
• Head to the navigation pane and search for the area you will store the folder in, right-click and select “Paste” so that the folder is moved to that location.
• Right-click on the folder that you just moved and select “Copy”.
• Go back to Start, select your username, right-click any vacant space in your folder and select “Paste Shortcut”.

Note: If you want to store the folder in a different place other than the folder in which it currently exists (user profile), you will need to create a new folder. In order to do so, go to the Windows Explorer menu and look up the root of the drive. Hit “New Folder” and then choose edit to change its name. You can set it as any name for instance, “My Folders”.

Solution for Case 2

You can ignore this error safely. However, if you wish not to see this error in the future during your backup operations then you will need to carry out the following steps:

1. Create all the folders listed in the error message including LocalLow, Contacts, and Searches.
2. Remove all of these folders from the Backup settings to make sure they aren’t being backed up then add the folders which are in their original place. To carry out this procedure, you will have to follow the below-mentioned steps:

• Head over to the Control Panel and open “Backup & Restore”.
• Go to the Backup section and select “Change Settings”.
• Click Next in the Setup backup dialog box.
• Select “Let me choose” in the dialog box termed “What do you want to back up” then proceed by clicking Next.
• Expand Data Files, expand <user> Libraries, expand Additional Locations then proceed by clearing out the AppData Folder, searches, and Contacts checkboxes.
• Expand Computer as well as the item for your system drive (expand Local Disk (D:)), expand users, expand <user>, then go to AppData, Searches and Contacts and mark them if they are present.
• Proceed by clicking next and select “Save Settings” then exit.
• Back to Backup & Restore, select Back up now and your new backup will begin proceeding. The entire process will be complete without any errors now.

If your Windows PC encounters an error, it will display a Blue Screen of Death or BSOD error which usually comes up for a fraction of second and creates some logs or Dumps Files as what other user prefers to call it and then boots your PC suddenly. This process usually takes place quickly that most users find it hard to get the error code and won’t probably be able to check what really went wrong with their PCs. This is where the dump files come in. They are stored internally in your computer and can only be accessed by an administrator. They are classified into 4 main types and in Windows 10 they are either:

1. Complete Memory Dump
2. Kernel Memory Dump
3. Small Memory Dump (256 KB)
4. Active Memory Dumps

Dump Files are useful as they could help you in resolving the problem and so you need to configure your Windows 10 PC to create them but first, you need to make a system restore point. This is essential as you are about to modify some system files as well as critical Windows 10 settings. There are two ways you can create Dump files – first is by modifying the settings in the Startup and Recovery and lastly is via the WMIC command line. Refer to the instructions prepared below to be guided on how you can create Dump files after any BSOD error using these options.

Option 1 – via Startup and Recovery

• Type in “control panel” in the Cortana Search box and then click on Control Panel from the search results to open it.
• After opening Control Panel, you need to make sure that you view the contents by their Category then click on the header link which is labeled “System and Security” or you could also right-click on the This PC icon and then click on Properties.
• Next, select the Advanced system settings from the left panel. Once you do, a new and small window will pop up.
• Under the newly opened window, look for the section called Startup and Recovery and then click on the Settings button.
• And from the System Failure section, you can choose any option from the drop-down for Write debugging information such as:
  • None – this means that there is no dump file created by Windows
  • Small Memory Dump – this means that Windows will create a Minidump file on BSOD
  • Complete Memory Dump – this means that Windows will create a Complete Memory Dump file on BSOD
  • Automatic Memory Dump – this means that Windows will create an Automatic Memory Dump file on BSOD
  • Active Memory Dump – this means that Windows will create an Active Memory Dump file on BSOD

Note: The complete dump needs a page file that is allowed to be the size of the physical memory installed in your PC with a dedicated 1 MB of space for just the page header.

• Now once you have selected the most suitable option for you, just click on OK/Apply and then exit.
• Restart your PC to successfully apply the changes made.

Option 2 – via the WMIC command line

• The first thing you need to do to create Dump files via the WMIC command line is to tap the Win + X keys combination or simply right-click on the Start button and then select the Command Prompt (Admin) option. You could also type in “cmd” in the Cortana search box and then right-click on Command Prompt from the results and select Run as administrator.
• After that, type in any of the commands given below depending on your preferences so that your Windows 10 PC will be configured to create Dump Files:
  • No dump file: wmic RECOVEROS set DebugInfoType = 0
  • Small Memory Dump: wmic RECOVEROS set DebugInfoType = 3
  • Kernel Memory Dump: wmic RECOVEROS set DebugInfoType = 2
  • Complete Memory Dump: wmic RECOVEROS set DebugInfoType = 1
  • Automatic Memory Dump: wmic RECOVEROS set DebugInfoType = 7
  • Active Memory Dump: wmic RECOVEROS set DebugInfoType = 1

Note: A complete dump has to have a Page file which is allowed to be the size of the physical memory installed on your PC accompanied by a 1 MB space for just the page header.

• Now type in “exit” in the Command Prompt to exit it.
• Restart your PC to apply the changes made successfully.

Error Code 0x80240016 - What is it?

Error Code 0x80240016 is an error that appears when the Windows Update tool is unable to complete its operation. While it most commonly occurs in Windows 10, versions of this error are also present in past Windows systems, as well. The steps to resolve the error are the same for each of these systems. Common symptoms include:

• Inability to complete the Windows Update process
• Sluggishness or freezing
• Crashing of your programs
• The message that states “IMAP_LOGINFAILURE”

There are a number of different issues that can cause Error Code 0x80240016, so it is important to follow the steps below to address each of them in turn. While basic users can implement several of the methods, some of the methods may require advanced skills or knowledge. If needed, always get in touch with a qualified Windows repair professional to assist you in the process of error resolution.

Solution

Error Causes

Error Code 0x80240016 happens when the system believes that another installation is already occurring on your device while the Windows Update tool is attempting to run the installation of its own updates. While there may not always be an actual installation going on that prohibits Windows Update from running, several programs can leave traces of background activity that prevent Windows from proceeding as necessary.

Malicious software can also cause your system to believe that files are in use, so several of the methods to fix the error can address this particular set of issues.

Further Information and Manual Repair

There are a number of different background issues that can cause Error Code 0x80240016 to appear on your machine. Follow the steps below to address each aspect of the error code, making sure to restart your computer after each attempt. If you have difficulty in completing these steps, contact a qualified technician to assist you.

Here are the top methods to resolve Error Code 0x80240016:

Method One:  Use the Troubleshooting Tool in Windows Update

The first step to addressing Error Code 0x80240016 is to open up the Windows Update tool and click on the option to run the Troubleshooting Wizard. This can identify many of the issues associated with the error. If this tool makes any changes, make sure to restart your computer after it finishes.

Method Two:  Run the Registry Repair Tool

The registry repair tool can be a great resource for Error Code 0x80240016. Use it to run a scan on all of your registry entries and to repair any that may be extraneous, faulty, or missing. This step may take some time, so be prepared to wait a while for it to finish. Always restart your computer after running the registry repair tool so that any necessary changes can fully take effect and be recognized by your device.

Method Three:  Scan Your Computer for Malicious Software

Use the Microsoft Security Essentials tool to perform a scan of your computer to see if any malicious software has changed or corrupted your system files. Once all the files had been scanned and problems have been addressed, you can restart your computer to see if the error has been successfully resolved. You can also download a powerful automated tool to rectify Windows 10 error code 0x80240016.

Method Four:  Update Your Drivers and Perform Updates for Your Software and Operating System

Another method that can help to address Error Code 0x80240016 is to open up your driver settings from the control panel and scan to see if any updates are needed. If there are updates waiting to be installed, go ahead and perform those updates first, then restart your computer.

Next, check your Windows Update tool to see if there are any program or system updates that need to be performed. Allowing updates to stack up can cause a number of errors on your system, so it is important to keep your updates in check. Restart your computer after you finish this process.

Method Five:  Backup Your Files, Then Reinstall Your Operating System Version

If none of the above methods have completely fixed the problem, you may need to reinstall your operating system. Before doing so, make sure that you have a backup copy of any important programs and files so that you don’t lose anything during the fresh installation.

TPM, also known as Trusted Platform Module, is a specialized chip used for security as well as encryption of users’ private data like Fingerprint, Facial data, and many more. TPM also comes with a Management Console and if you are not able to load the Management Console and you got the “Cannot load Management Console” error instead, read on as this post will guide you in fixing the problem. This type of issue usually happens when you clear or disable the TPM using the settings in the BIOS and so when you run the Trusted Platform Module Management console, you encounter the error. To fix the “Cannot load Management Console” error in your Windows 10 computer, here are some options you should check out.

Option 1 – If TPM is cleared in the BIOS:

If the Trusted Platform Module is cleared in the settings of the BIOS, you have to close and restart the TPM Management console or TPM.msc once again. It could be that the TPM Management has to reload the changes again after you’ve made them which is why you encounter the “Cannot load management console” error.

Option 2 – If TPM is disabled in the BIOS:

If you opted to disable TPM using the BIOS settings or you have turned it off by accident, then you have to enable it back and you have two options to do that – you can either enable TPM from the BIOS or using the Windows PowerShell. For more details, refer to the instructions below.

Enabling TPM from the BIOS:

• You need to first reboot your PC and then go to the BIOS.
• From there, look for TPM under the security options and in case the TPM management option has been disabled or greyed out, refer to the sub-steps given below to make it active again
  • Enable the Admin password in the BIOS.
  • Then go back to the TPM settings and check if the TPM management is already available.
• After that, you should now be able to enable TPM. Remember that it’s always a good idea to have an ADMIN password for your BIOS as it makes sure that no one can change the settings in your computer BIOS and Security level options.

Enable TPM via Windows PowerShell:

• This second option is a lot easier compared to the first one if you have admin privileges. So once you’ve opened the Windows PowerShell with admin privileges, you need to run the following command:
  • $tpm = gwmi -n rootcimv2securitymicrosofttpm win32_tpm
  • $tpm.SetPhysicalPresenceRequest(6)
• After you execute the commands given above, you need to restart your computer.
• Now, once your computer has restarted, you need to accept any BIOS prompts and then check if the “Cannot load management console” error is now fixed.

Error Code 8024001F – What is it?

During the Microsoft Windows 10 upgrade, certain users have experienced an issue with error code 8024001F. Users should note that this error is also known as Windows Update 8024001F and 0x8024001F. This error code is relatively common and is usually caused by a faulty internet connection. Thanks to this common reasoning, the error is generally fixed easily, and users are able to restart their Microsoft Windows 10 upgrade. Common symptoms include:

• A dialog box appears with the Error Code 8024001F when attempting to upgrade to Microsoft Windows 10.
• Your current version of Windows is unable to recognize the need for an update to Microsoft Windows 10.

Solution

Error Causes

With only three issues causing error code 8024001F, it is relatively easy to determine your particular issue and then follow the steps below to rectify the situation.

• Your computer is not connected to the internet.
• The Windows firewall is interfering with the Microsoft Windows 10 update.
• Your third-party antivirus and firewall software is interfering with the Microsoft Windows 10 update.
• Your system is infected with the Conficker worm, which is preventing the Microsoft Windows 10 update from processing correctly.

Microsoft Support asks that you contact them directly for further assistance if you are able to rule out these three reasons for error code 8024001F.

Further Information and Manual Repair

Error code 8024001F is easily corrected using one of the following methods. Each of these methods should be convenient and comfortable for a basic computer user at home. If at any time you are unsure or feel you need more assistance, Microsoft Support asks that you contact them directly for more guided support.

Method 1- Access the Troubleshooter

1. Access the Windows Update Troubleshooter
2. When the dialog box pops up, click OK.
3. Click NEXT on the following dialog box.
4. Windows will then run the Troubleshooter, attempting to detect any known issues with your system.
5. Depending upon the results you should be able to follow the on-screen prompts which will alleviate the update issue.

Method 2- Correct your internet connections

1. Closeout of the error code 8024001F dialog box.
2. Close the Microsoft Windows 10 updater.
3. Attempt to access the internet through your normal browser.
4. ** If you can successfully access the internet, then an internet connection is not the cause for this error code.
5. If you are unable to access the internet verify that you are plugged into your network, both at the router/wall and at your computer jack.
6. If you use a router, verify that all of the lights are on and active (showing an active internet connection).
7. Establish an internet connection if possible. If you are unable to establish an internet connection, you may need to contact your internet provider.
8. If you are able to reestablish an internet connection, then you should have no problem running your Microsoft Windows 10 update.

Method 3- Adjust the Windows Update settings

1. Log into your current version of Windows as the Administrator (enter a password if prompted).
2. Click the START button on your keyboard or screen.
3. Search for the term “admin”, press ENTER
4. Click the “administrative tools” option
5. Select the “services” file, re-enter your password.
6. Open the Windows Update file by right-clicking on the name.
7. Choose the “properties” option
8. Under the GENERAL tab, make sure that the “startup type:” is set to AUTOMATIC (DELAYED START)
9. Under the “Service Status” header, click the START button.
10. Click OK
11. Restart the Microsoft Windows 10 update.

Method 4- Scan for the Conficker Worm

1. Access the web address to be directed to the Microsoft Safety Scanner.
2. Run this free scanner provided by Microsoft to verify if the Conficker Worm is your issue.
3. If this worm is causing your error, Microsoft will walk you through the steps necessary to remove the worm.

Method 5- Firewall and Anti-Virus software

1. If you are using the Windows firewall or a third-party anti-virus and firewall software, disable these programs.
2. Run the Microsoft Windows 10 upgrade.
3. After the upgrade is complete, turn your antivirus and firewall software back on.

Users should not have a problem employing the above methods. Start with the simplest solutions first, and then work your way to the more intricate methods. In some cases, depending on why this particular error code was caused, you may have to use a powerful automated tool to have it resolved.

If you were trying to install a program on your Windows 10 computer but encounter an error instead that says, “Error 1310, Error writing to file: <PATH>, Verify that you have access to that directory” then read on as this post will guide you on how you can fix it. This kind is a fairly common type of error encountered by many Windows users. You can get this error when you try to install certain programs like Excel, AutoCAD, Adobe Photoshop, and some other Adobe products on Windows. One of the most likely causes for this error is that the required files or location is already used by some other software which means that Windows finds that you are trying to overwrite a software that is already installed. Aside from that, it could also occur if the program installer does not have access to write to that directory. To fix Error 1310, here are some potential fixes that could help.

Option 1 – Clear up temporary or junk files

The error could be caused by some temporary or junk files in your computer and so you need to clear them up to fix the problem. You can achieve that using the Storage Sense feature.

• 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. Make sure that Storage Sense is on.
• Next, 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
  • The system created Windows Error Reporting Files
  • Thumbnails
  • Temporary Internet Files
  • Previous Windows Installation Files
  • Delivery Optimisation Files
  • DirectX Shader Cache
• Choose the files you want to get rid of and then click on the remove files option. Note that you’ll have an idea of the total size as you select any of the junk files listed above.
• Now go to the “Free Up Space Now” section and click the Clean Now button. This will get rid of all the temporary or junk files in your computer and should hopefully fix Error 1310.

Option 2 – Reinstall the program in a Clean Boot State

You can also troubleshoot Error 1310 in a Clean Boot state. It could be that there are some third-party applications in your computer that's preventing the program from getting installed and to isolate this possibility, you need to boot your computer in a Clean Boot State and then try installing the program again. Putting your computer in this state can help you identify which program is the culprit and thus isolates the problem. In a Clean Boot state, your computer will start using only the pre-selected minimal set of drivers and startup programs. Note that you have to disable and enable one process at a time.

• 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 you’ve set your computer into a Clean Boot State, make sure that you’re signed in as administrator and then try to install the program again.

Option 3 – Try to unregister and re-register the Windows Installer Module

• Tap the Win + R keys to open the Run dialog box.
• Then type the “msiexec /unregister” command and hit Enter to unregister the Windows Installer Module.
• Next, type the “msiexec /regserver” command and hit Enter to re-register the Windows Installer Module.
• Now restart your computer and see if un-registering and re-registering the Windows Installer Module fixed the problem or not.

Option 4 – Take ownership of the location where you want to install the app

The next thing you can try to do is to take ownership of the particular folder as this worked for some users who experienced the same problem. But before you do that, you have to create a System Restore Point first, once that’s done, proceed to the given steps below.

• First, locate the concerned folder and right-click on it then select Properties.
• Next, click on the Edit button in the Properties window and click OK to confirm if you got a User Account Control elevation request.
• After that, select user/group from the permission windows or click on the Add button to add another user or group. It would be best if you add “Everyone” to give permission.
• Then check “Full Control” under the “Allow” column to assign full access rights control permissions.
• Now edit the permission to Full Control for “Everyone”.
• Click OK to save the changes made and then exit.
• Finally, try to install the application again.

Athwbx.sys or the Qualcomm Atheros driver file is known to trigger several Blue Screen of Death errors. This occurs when the driver gets corrupted or when the operating system is unable to access or find it. In addition, bad sectors in the hard disk or RAM can also cause BSOD errors. The athwbx.sys file is known to cause the following BSOD errors listed below:

• SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (athwbx.sys)
• STOP 0x0000000A: IRQL_NOT_LESS_EQUAL (athwbx.sys)
• STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED (athwbx.sys)
• STOP 0×00000050: PAGE_FAULT_IN_NONPAGED_AREA (athwbx.sys)
• Your PC ran into a problem and needs to restart. You can search online later for this error: athwbx.sys

Before you proceed with the troubleshooting tips given below, you might want to try performing System Restore as it could resolve Blue Screen errors caused by the athwbx.sys file. To run System Restore, follow these steps:

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

If System Restore didn’t help in fixing the Blue Screen error, now’s the time for you to resort to the troubleshooting tips provided below but before you get started, make sure that you create a System Restore point first.

Option 1 – Try recreating the athwbx.sys file

The first thing you can try is to recreate the athwbx.sys file. Every time your Windows 10 PC boots up, it looks for all the system drivers in place and if it is unable to find them, it tries to create them. This is why if you remove your corrupt driver file, chances are, you might get a fixed file recreated just for you. How? Refer to the steps below.

• Boot your Windows 10 PC in Safe Mode.
• Then open File Explorer and navigate to this location: C:/Windows/System32/drivers
• From there, look for the file named sys and rename it to athwbx.old.

Note: As you can see, the file’s extension has changed from .sys to .old.

• Now restart your computer and check if the athwbx.sys Blue Screen error is now fixed.

Option 2 – Try to update or rollback your device drivers

If the first option didn’t work for you, then it’s time to either update or roll back the 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.
• Then locate the device drivers and right-click on them to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

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 3 – Run the System File Checker Scan

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 with 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

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.

Option 4 – Try to run the CHKDSK utility

Running the CHKDSK utility might also help you resolve the athwbx.sys Blue Screen error. 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 5 – Run the Memory Diagnostic Tool

Running the Windows Memory Diagnostic tool in Windows 10 might also help you in fixing the athwbx.sys Blue Screen error. Refer to the steps below on how to run this tool:

• 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 6 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like athwbx.sys. 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.

As you know, the Office Language Packs need to be installed right after installing Office. It also has to be on the correct version of Office so if any of these conditions are not met, you will most likely get error codes 30053-4 or 30053-39 when you install a language pack in Microsoft Office. If you are currently facing this error, read on as this post will help you fix the problem. Here’s the full context of the error message:

“Something went wrong, Sorry, installation cannot continue because no compatible office products are detected.”

When you have to work on two different languages, that’s where the language packs come in handy. You might have to work on one language but when it comes to proofreading or help, you need another language. Note that some language accessory packs offer partial localization which is why some parts of the Office might show the default language. If you are using Office 365 or Office 2019, 2016, 2013, or 2010, you need to go to the language accessory pack page from office.com and select your language. Once you see the download link, click on it to start downloading the pack. It includes the display in the chosen language, proofing tools for the selected language, as well as the Help in the selected language. Once the installation is complete, follow each one of the given options below to configure the language accessory pack properly.

Option 1 – Select Editing and Proofing language

• You need to open any Office program and navigate to File > Options > Language.
• From there, you need to make sure that the language you want to use is in the list under the Choose Editing Languages section.
• After that, you can add or remove the language that Office uses for editing and proofing tools.

Option 2 – Configure the Display and Help languages

In this option, you can change the default display and help languages for all the Office applications so whatever you choose will be used for all the buttons, menus, and support of all the programs. After you select the language, restart all the Office applications to apply the changes made successfully. On the other hand, if you are using Office volume license versions, note that only an administrator account can install this if you are using the Volume License version of Microsoft Office 2016. You have to download the ISO image of the language packs, language interface packs, and the proofing tools from the VLSC or Volume Licensing Service Center. This process can be quite complicated so you might have to go to the docs.microsoft.com page to be guided accordingly. After you installed everything correctly, the error code 30053-4 or 30053-39 should now be fixed.

When you get an igfxem.exe error in Windows, it is not really clear what does this means, usually, Windows throw us some code or we get a DLL error, rarely we get an EXE error. So what does this error means? Intel Graphics Executable Main Module, shortly called as IgfxEM module is a part of the Windows operating system. When you run Microsoft .NET Framework applications that use the AS/400 Data Queue ActiveX control (Mseigdq.dll) to read from and to write to IBM iSeries (AS/400) data queues, you may experience this error. In order to overcome this error and cope with it try the following things:

1. Increase Virtual Memory

   Go to the Start Menu and click on Settings. Type performance. Choose Adjust the appearance and performance of Windows. In the new window, go to the Advanced tab and under the Virtual memory section, click on Change. At the bottom of the new window, check what the Recommended value is and how it compares to Currently allocated. If the current setting is significantly less than the recommended, uncheck the Automatically manage paging file size for all drives box at the top of the same windows and then click on Custom size. Enter the Recommended value in the Initial Size box, and a larger figure in the Maximum size box. Click OK to save the new settings.

2. Download and update .NET framework

   Go to the Microsoft website and download the latest .NET framework. Once the download is complete, install the package following onscreen instructions.

3. Reinstall INTEL graphic drivers

   Go to the intel website and download the latest graphic drivers for your graphic card model. Once the download is complete, install the package following onscreen instructions.

4. Run SCF scan

   If all else fails, run command prompt and inside type sfc /scannow

One of the most useful and powerful built-in utility in Windows 10 is the DISM tool. This tool can be used with the Command Prompt command line as well as for other purposes. However, it is not without flaws and there are times when you may encounter some issues while using it. One of the problems you can get while using the DISM tool is the following error:

“The scratch directory size might be insufficient to perform this operation”

This kind of error in DISM occurs when the DISM command is executed from the Windows Recovery Environment due to the limited size permissions of a delivery where the operating is being performed. To fix this DISM error, you need to follow the instructions laid out below. Step 1: First, tap the Win + R keys to open the Run utility and then type “cmd” in the field and tap Enter to open Command Prompt. Step 2: Next, you have to specify a scratch directory that contains the Windows folder and to do that, you can either use the DIR command or the BCEDIT command. So in the elevated command prompt type and enter “dir” or “bcedit”. Step 3: After that, you will see a list of folders inside the C: partition. Now you have to create a folder named “scratch” inside the partition. To do so, execute the following command:

mkdir C:Scratch

Note: The command you just entered will create a directory inside the root of the C: partition named Scratch. Step 4: Now that you’ve created the Scratch folder, note that each time you run any of the DISM commands, you have to enter the following code snippet in them:

/ScratchDir:C:Scratch

 Note: For instance, if you are using the DISM tool to repair the offline Windows image, instead of executing the “Dism /Online /Cleanup-Image /RestoreHealth” command, you now have to execute the “DISM /Image:C: /ScratchDir:C: Scratch /Cleanup-Image /Restorehealth” command. And if you want to remove a selected installed update package, you can use the “DISM /image:C: /ScratchDir:C:Scratch /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e75~amd64~~16299.196.4.9” command. Keep in mind that the mentioned package is only an example. And lastly, you also have to replace the drive letter in the new code snippet when you execute the commands given above.