Logo

There is a system repair pending

If you are running a System File Checker scan but got an error message instead that says, “There is a system repair pending which requires reboot to complete, Restart Windows and run SFC again”, worry not for this post will walk you through how you can fix the problem.

This kind of error can be addressed and fixed with several potential fixes which will be provided in this post. You can try to restart your computer and run a System File Checker scan again or delete the pending .xml file or use the “revertpendingactions” parameter for the DISM tool. For more information, refer to each one of the options given below.

Option 1 – Try restarting your computer and run the SFC again

The first thing you can do to fix the problem is to restart your computer and let the pending process be completed. After your computer restarted, try to run System File Checker again and see if the error is now fixed or not. If not, refer to the other options below.

Option 2 – Try deleting the pending .xml file

The next thing you can do to fix the problem is to delete the pending .xml file. How? All you have to do is navigate to this location at CWindowsWinSxS and from there, look for a pending .xml file and rename it or delete it. This will get rid of any pending tasks and will build a fresh new check.

Option 3 – Try to use the “revertpendingactions” parameter for the DISM tool

If the two options given above didn’t work, you can try using the revertpendingactions parameter for the DISM tool. If you’re not able to boot into Windows, then run Command Prompt from the Recovery Console and execute the given command below.

dism.exe /image:C: /cleanup-image /revertpendingactions

After you execute the command, restart your computer and try to run System File Checker again and see if it has fixed the problem or not.

Do You Need Help with Your Device?

Our Team of Experts May Help
Troubleshoot.Tech Experts are There for You!
Replace damaged files
Restore performance
Free disk space
Remove Malware
Protects WEB browser
Remove Viruses
Stop PC freezing
GET HELP
Troubleshoot.Tech experts work with all versions of Microsoft Windows including Windows 11, with Android, Mac, and more.

Share this article:

You might also like

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED CMUSBDAC.sys
If you encounter a Blue Screen error that points out to the CMUDA.sys, read on as this post will guide you in fixing it. The CMUDA.sys file is a Windows operating system driver file that is related to the USB Device Audio capabilities of a computer. There are times when this file causes Blue Screen error due to some conflicts in RAM or some incompatible firmware or hard disk issues, corrupted drivers or malware infection, and so on. There are various Blue Screen errors that are related to the CMUDA.sys file such as:
  • KMODE EXCEPTION NOT HANDLED
  • PAGE FAULT IN A NONPAGED AREA
  • IRQL NOT LESS OR EQUAL
  • SYSTEM THREAD EXCEPTION NOT HANDLED (CMUSBDAC.sys)
In most cases, the CMUDA.sys file usually triggers the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Blue Screen error. Although this Blue Screen error may seem complicated, its workarounds are straightforward so you won’t have any problems in following them.

Option 1 – 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.
  • After opening the Device Manager, locate the device drivers that are marked with a small yellow exclamation mark icon and right-click on each one to open their Properties. On the other hand, you can also look for sub-entries under Sound, video, and game controllers like the C-Media USB Audio Class
  • 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. You can download the as C-Media USB Audio Class driver from the cmedia.com website.

Option 2 – Try to recreate the CMUDA.sys file

The first thing you can try is to recreate the CMUDA.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. Which 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 CMUDA.old.
Note: As you can see, the file’s extension has changed from .sys to .old.
  • Now restart your computer and check if the CMUDA.sys Blue Screen error is now fixed.

Option 3 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors. 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.
  • After that, 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.
On the other hand, you can also try running the online Windows 10 Blue Screen troubleshooter from Microsoft. It is a wizard that could help you fix any Stop errors related to the CMUDA.sys file and will offer you helpful links as you use it.

Option 4 – Try running the DISM tool

You can try running the Deployment Imaging and Servicing Management or DISM tool to fix the Wdf01000.sys Blue Screen error. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.
  • Open the Command Prompt with admin privileges.
  • Then type in the following commands and make sure to hit Enter right after you type each one of them:
    • Dism /Online /Cleanup-Image /CheckHealth
    • Dism /Online /Cleanup-Image /ScanHealth
    • 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.

Option 5 – Run System Restore

Running System Restore might also help in fixing Blue Screen errors related to the CMUDA.sys file.
  • 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.
Read More
How to Fix Error Code 0xc1900106 on Windows 10

Error Code 0xc1900106  – What is it?

One of the most common errors encountered by Microsoft users upgrading from Windows 7 or Windows 8/8.1 to Windows 10 is the Error Code 0xc1900106. Microsoft users experience a failure in the installation process. Either they will be notified that the installation process was ended but failed or that Windows is not able to install the update.

Solution

Restoro box imageError Causes

More and more Windows users are having trouble upgrading their operating system to Windows 10. There are a lot of errors being encountered by users and one of them is the Error Code 0xc1900106. This error is normally due to the misconfigured system files. If a Windows user encounters this error, most likely their device has some registry problems.

Further Information and Manual Repair

Fixing error code-related issues could be best resolved to do manual repair methods. Applying repair methods manually can help Windows users address the root causes of the errors they encounter, as well as apply definite solutions to rectify the issue.

Most Windows users can be able to implement manual repair methods themselves but there are some cases where help from a Windows professional is needed. If you’re not a very tech-savvy person and not confident performing the manual repair methods yourself, it would be advisable to seek help from a professional Windows technician who is knowledgeable enough to address the errors or problems you are encountering. However, if you don’t want to resort to seeking help from a professional, you can also consider using a powerful automated tool.

In trying to fix Error Code 0xc1900106, here are the following manual repair methods you can take:

Method One: Custom Installation

  1. Make a backup of your personal files
  2. Users of Windows 8/8.1 should Refresh first then proceed to upgrade.
  3. If the Refresh process does not work, reset your device then try again.
  4. If resetting your device still does not work, you can proceed with a custom installation.
  5. When your Windows installation media is ready, you need to choose to boot from CD, DVD, or USB drive to begin setup. (For example purposes, this article will discuss booting from DVD).
  6. When your device is all set to boot from DVD, you will be prompted to Press any key to boot from CD or DVD…
  7. Once you’ve pressed any key, the screen will show the Windows logo which might take a while. No need to worry though, as long as you can see the indicator, you’re good.
  8. Choose your Language, Time, and Keyboard method from the drop-down menu then hit Next.
  9. Click on the Install Now button then wait until Setup begins.
  10. Tick on the I accept the license terms check box then select Next.
  11. Choose Custom: Install Windows only (advanced)
  12. Choose the Primary partition then select Next. You will be prompted by the following warning: The partition you selected might contain files from a previous Windows Installation. If it does, these files and folders will be moved to a folder named Windows.old. You will be able to access the information in Windows.old, but you will be able to use your previous version of Windows. Just click the OK button then wait as the Windows continue to install. Windows will restart once this phase of the setup completes and will reboot into setup once again.
  13. At this point, Windows will detect and install your hardware. Once this finishes, Windows will restart again.

Method Two: Reset Windows Update Components

  1. From your device’s desktop, hit Windows key + X to open the command prompt as admin.
  2. Once the command prompt window appears, you can type or copy and paste the following commands (all at once):

net stop wuauserv net stop cryptSvc net stop bits net stop msiserver ren C:WindowsSoftwareDistribution SoftwareDistribution.old ren C:WindowsSystem32catroot2 catroot2.old net start wuauserv net start cryptSvc net start bits net start msiserver pause

  1. Exit the command prompt.
  2. After you reset the Windows Update components, see if you receive Windows Updates which includes the firmware updates for your computer.

Method Three: Ensure Windows is Updated

  1. If you have an antivirus, make sure to disable it during the upgrade process.
  2. Run Windows Update to check if the system is updated.
  3. Ensure that the latest firmware and drivers are installed. To be able to do this, go to the computer manufacturer’s website or you can also try contacting company support.
Read More
Fixing To use System Restore you must ...
There are cases when you want to undo some changes you’ve made to your computer and to do that you have to perform the System Restore task. However, if you encounter an error that states “To use System Restore you must specify which Windows installation to restore”, when doing so, read on as this post will help you fix the problem. This kind of error in System Restore could be due to corrupted files in the system. There are also situations where you are not able to boot up once you encounter this error which could be a big problem. On the other hand, this error might have something to do with corrupted BCD files. Whatever the cause is, here are some potential fixes you have to try.

Option 1 – Try to run System File Checker offline

Like pointed out, since the error might be due to corrupted system files, you can try to run System File Checker offline. How? Refer to these steps:
  • You need to go to the Advanced Startup Options and from there select Troubleshoot.
  • Next, select the Advanced Options and then Command Prompt.
  • After opening Command Prompt, type the commands given below and tap Enter right after you type each one of them.
    • Cd /
    • Dir
  • If you can see the “Users” folder, that is your system’s drive. However, if you can’t see it, you can just change the drive-by assigning “D” as its alphabet volume.
  • Then execute this command where “C” is the system drive: sfc /scannow /offbootdir=C: /offwindir=C:Windows
  • Now repeat the given steps sequentially.

Option 2 – Try to run DISM tool

You can also run the DISM tool to repair the potentially corrupted system image. First, you have to check the health of the system like checking the integrity of the system files and Windows services. To run DISM, follow the given steps below sequentially.
  • Open Command Prompt from the Advanced Startup options.
  • After that, execute this command where “C:” is the system volume: DISM /Image:C:Windows /Cleanup-Image /RestoreHealth /Source:C:WindowsWinSxS
  • If you encounter an error after executing the given command, insert the Windows USB or DVD and then execute this next command where “E:” is the USB or DVD drive: DISM /Image:C:Windows /Cleanup-Image /RestoreHealth /Source:esd:E:SourcesInstall.esd:1 /limitaccess
  • In some cases, “install.esd” would be “install.wim” and in such case, you have to modify and execute this command: DISM /Image:C:Windows /Cleanup-Image /RestoreHealth /Source:wim:E:SourcesInstall.wim /limitaccess

Option 3 – Try to repair corrupted BCD

As mentioned, the error could also be due to corruption in BCD, and to fix it, you can use Bootrec.exe – a built-in command-line tool used to troubleshot issues related to boot up and Windows Startup. Before you run this tool, make sure that you have inserted a bootable USB or DVD into your computer. Once you have that covered, follow these steps:
  • You need to go to the Advanced Startup Options.
  • Then click on Troubleshoot.
  • Next, select the Advanced Options and then Command Prompt.
  • Once Command Prompt has been pulled up, enter each one of the following commands and in the sequence that they are given to rebuild BCD files and repair MBR files:
    • Bootrec /Fixmbr
    • Bootrec /FixBoot
  • After you execute the commands given above, you should see a confirmation message that says, “The operation completed successfully”.
  • Now type the “Bootrec /RebuildBCD” command to rebuild BCD.
  • Finally, close Command Prompt and then restart your computer to successfully apply the changes made.

Option 4 – Try to run the Automatic Repair Utility

You might also want to use Automatic Repair in fixing the error. To do so, follow the steps below.
  • You can start by creating and booting from a bootable Windows 10 USB Stick.
  • After that, click on Repair your computer located in the bottom left corner when you are on the initial Windows Startup screen.
  • Next, click on Troubleshoot, and then on the other screen, click the Startup Repair option.
  • Now select the operating system you want to repair. Once you do that, it will start to repair your operating system. Wait until the process is completed and then check if the problem’s now fixed.

Option 5 – Try to use the Windows Recovery Environment

If the four options given above didn’t help fix the problem, you could try running Windows Repair and a Windows bootable USB or DVD.
  • First, insert the bootable USB or DVD and boot into it, and select the “Repair your computer” option.
  • Next, once you see the manufacturer logo on your computer, tap the key to enter into Windows Recovery Environment.
  • After that, change the Boot sequence to DVD drive under the UEFI Firmware settings and restart your computer.
  • Once your computer has restarted, select the boot order and make changes accordingly as displayed in the BIOS.

Option 6 – Try running System Restore in Advanced Startup Options

Since you probably can’t boot into your Windows 10 computer, you can try to run System Restore again in the Advanced Startup Options.
  • Boot your computer into the Advanced Startup Options screen.
  • From there, you will see some options to troubleshoot when you can’t log in to Windows in the usual way.
  • Now select Troubleshoot > Advanced Options > Command Prompt.
  • After that, type “exe /OFFLINE:C:Windows” and hit Enter to execute the command which will start the System Restore process.
Note: You need to replace “C” with the drive where Windows Installation is located.
Read More
Quick Guide to Fixing Error Code 29

What is Error Code 29?

Code 29 is a Device Manager error commonly seen whenever a hardware device driver reports a problem. This error code indicates that the resources needed for operation are not available.

The computer hardware basically requires drivers to interface with the operating system. Drivers comprise multiple components and are supplemented with other resources provided by the BIOS (a physical chip on the motherboard).

The BIOS contains a set of basic input and output instructions for the computer system to boot, load drivers, and more.

Its firmware provides resources that drivers require to interface with other essential components. However, when the firmware fails to provide the requested resources, the device drivers stop functioning; this results in error codes like code 29.

Error code 29 is usually displayed in the following format:

“This device is disabled because the firmware of the device did not give it the required resources” Code 29

Solution

driverfix boxError Causes

Error code 29 may be triggered due to several reasons. These include:

  • Outdated drivers
  • Corrupted drivers
  • BIOS misconfiguration
  • The device firmware is corrupt
  • Previous attempt to update the driver failed

To avoid inconvenience and to ensure your computer keeps working at its optimal pace, it is recommended that you repair error code 29 on your PC immediately. Delay may limit you from using certain hardware attached to your system properly.

Further Information and Manual Repair

To repair error code 29, you don’t have to hire a professional and spend hundreds of dollars. Here are some quick and effective DIY methods that you can try to resolve this issue in minutes even if you don’t have any technical background.

Method 1 - Reboot Your PC

Sometimes, error codes like code 29 may pop up on your computer screen due to some temporary glitch with the hardware. Rebooting can resolve the issue easily.

Therefore, before you do anything, try restarting your PC. It could be all you need to repair code 29. However, if the error code continues to persist, try the other methods given below.

Method 2 - Clear the CMOS

This may sound technical but it isn’t. To begin, with CMOS is an acronym for Complimentary Metal Oxide Semiconductor.

It is a term that is used to describe motherboard memory that contains the BIOS settings. Clearing CMOS helps reset the BIOS settings to their default manufacturer levels. It’s easy to do and is an effective troubleshooting step to resolve error code 29.

To do this, simply:

  1. Enter the BIOS setup utility  by restarting your PC
  2. Watch for an entering setup message
  3. Enter the BIOS access key. Usually, the key is F2 or F12. However, the key may differ from manufacturer to manufacturer. You may want to check the manufacturer’s website first to find out the BIOS access key before you restart your PC.
  4. ‘Reset BIOS settings’ to their default factory levels.

Method 3 - Enable the Device in the BIOS

Error code 29 may appear if a device is disabled. In such a scenario, simply follow the same steps as discussed in method 2, and in the advanced BIOS settings, look for disabled devices.

Enable the devices in the BIOS so that you use them easily.

This will hopefully resolve the issue. If it doesn’t, then this means the error code 29 is caused by either corrupted or outdated drivers. Try method 4 to resolve this issue successfully.

Method 4 - Identify the Problematic Device Drivers and Update them

Whether the error code 29 is caused by a misconfigured, corrupted, or outdated driver, simply update the new driver version to resolve. When doing it manually, you will first have to find and identify the problematic device drivers in the Device Manager.

You can access the Device Manager by going to the start menu and then simply typing Device Manager in the search bar.

Access the Device Manager and the properties to identify problematic drivers. Problematic drivers are normally displayed with a yellow exclamation mark.

Once you have spotted problematic drivers, simply update new drivers to resolve them. Though there is nothing technical about it but it may be time-consuming.

Method 5 - Install Driver Assist to Update Drivers Automatically and Regularly

A good alternative to manual driver update is DriverFIX. Simply download and install DriverFIX on your PC to update all problematic drivers in seconds. This is a cutting-edge program designed to resolve all kinds of device driver problems.

It is user-friendly and compatible with all Windows versions.

The intelligent programming system deployed inside this software program enables it to identify and detect all problem drivers automatically thereby sparing you from the hassle.

Furthermore, it also matches the drivers with the latest and compatible versions and updates them on a regular basis.

It takes the guesswork out of finding misconfigured and corrupted drivers and fixes driver-related problems and error codes like code 29 right away.

Click here to download DriverFIX to repair Device Manager error code 29 on your system without any hassle.

Read More
Windows won’t go Sleep, Legacy Kernel Caller
If the display of your Windows 10 computer turns on all of a sudden no matter how put it to sleep over and over again, it always wakes up, read on as this post will guide you in resolving this peculiar issue. In case you don’t know, the Windows 10 computer Sleep state is made in such a way that if it’s really important, it wakes up. You may have configured this kind of behavior or there could be some hardware component that’s interrupting its Sleep state. Thus, this post will give you some troubleshooting tips to fix the Sleep state issue caused by the Legacy Kernel Caller. The Legacy Kernel Caller points to the external hardware that’s causing your Windows 10 to wake up even when it’s in a Sleep state. Step 1: Find out what’s keeping your computer from going to sleep. To figure out what really is keeping your computer from going to sleep, you can execute the “powercfg –requests” command instead of checking the power configuration of your computer. This command will look for requests from applications and drivers that prevent the computer from turning off the display or from going to sleep. To execute the command, simply open Command Prompt and type “powercfg –requests” and hit Enter. After that, you will see part of the result that looks like this:
“SYSTEM [DRIVER] USB AUDIO DEVICE An audio stream is currently in use [DRIVER] Legacy Kernel Caller.”
Step 2: The next thing you have to do is remove all the external hardware connected to your computer. In this step, you have to disconnect external hardware from your computer. Based on reports from users who experienced the same issue, the “TV card” is the culprit so make sure you remove that one. Once you’ve removed it, open Command Prompt and run the “powercfg –requests” command again and you’ll see that the “Legacy Kernel Caller” will no longer be on the list. In addition, your computer will get into its regular sleep mode once the hardware is removed. Once you do that, the driver gets hung and won’t release the power request despite being used. Step 3: Try using the request override option The powercfg command also offers a request override option which allows users to disable the requests from applications and services to wake the computer from sleep mode. To run this command, simply open Command Prompt with admin privileges. After you open Command Prompt, type the following command and hit Enter to disable requests from applications and services that causes the computer to wake from sleep state.
Powercfg -requestsoverride Driver "Legacy Kernel Caller" System
Step 4: Check the streaming and media applications You also have to check if your computer is running an audio or video service in the background. In such cases, your computer won’t be able to go to sleep mode if these services are running in the background. You might have noticed that when you play a video or audio, your computer never goes to sleep. And if you have put it to sleep in between watching the video, then it’s probably why your computer is waking up. Thus, you have to stop these services. Step 5: Check the devices that can wake your computer If you didn’t see the Legacy Kernel Caller in the result after you execute the ”powercfg –requests” command, then you can try to execute the following command instead.
powercfg –devicequery wake_armed
After you enter this command, it will give you a list of all the devices that can wake your computer. So if there is anything other than the mouse, keyboard, touchpad, you have to check the power configuration of that device. To do that, go to the Device Manager and disable the device’s “Allow this device to wake the computer” option in its Properties Step 6: Check the Sleep Advanced Settings
  • Click on the Windows key and type “control panel” in the field and select the related search result.
  • Next, select the Security and Maintenance option and click on the Power Options.
  • After that, you have to select the Change Plan Settings but keep in mind that this option is barely readable so you need to read each option carefully.
  • Now click on the Change advanced power settings button and a new window will appear.
  • Then look for the “Sleep” option and expand it. Make sure that the “Allow hybrid sleep” option is on.
  • Reboot your computer and check if your computer now functions properly. If it still didn’t work, you may have to reverse the changes you’ve made.
On the other hand, you could also run the Power Troubleshooter to resolve the Sleep state issue. This built-in troubleshooter will automatically fix any power-related issues in your computer.
Read More
Recent Items aren't visible under Taskbar
In this post, you will be guided on what to do if the Recent Items are no longer visible in the Taskbar icons in Windows 10. This can be quite inconvenient especially if you work simultaneously on many files and documents together and would require you to visit them regularly to incorporate changes. Thus, if you find that the Recent items are not visible in the Windows Taskbar, read on. In order for the Recent Items to appear on the taskbar icons in Windows 10 again, there are four potential fixes you can check out. You can try to show the recently opened items via Settings or clear the cache of the recent items. You could also make some changes in the Windows Registry or use the Group Policy Editor. But before you proceed with these potential fixes, it’s best if you create a System Restore Point first just in case something goes wrong after you made changes in the system. The System Restore Point allows you to undo these changes and bring back the previous state of your computer. Thus, you need to create one and then carefully follow the given options below.

Option 1 – Show the recently opened items via Settings

The first thing you can do to fix the problem is to show the recently opened items through the Settings app.
  • Open the Settings app and select Personalization.
  • From there, select the Start option and scroll down until you see the “Show recently opened items in Jump Lists on Start or the taskbar” option.
  • Make sure that its toggle button is turned on.

Option 2 – Try to clear the Recent Items cache

  • Tap the Win + E keys to open File Explorer.
  • Next, copy and paste this link on the address bar: %AppData%Microsoftwindowsrecentautomaticdestinations
  • Once you’re in the given location, you should see multiple files. Now select all these files and completely delete them.
Note: These files are automatically recreated when you interact with the system like performing tasks such as opening apps or accessing files.
  • After that, go to this next location: %AppData%Microsoftwindowsrecentcustomdestinations
  • Once there, delete all of its files and restart your computer. This should resolve the problem.

Option 3 – Try making changes via Registry Editor

The next thing you can do to fix the problem is to apply some tweaks in the Registry by following these steps:
  • Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and hit Enter to open the Registry Editor.
  • Next, navigate to this registry sub-path: HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersion
  • From there, select the Policies Explorer folder located in the left pane.
  • Then move to the right pane and look for the “NoRecentDocsHistory” entry and right-click on it.
  • Now delete this entry.
Note: This entry is the one that stores the Group Policy setting for “Do not keep the history of recently opened documents. The Group Policy adds this entry to the registry with a value of 1 if you enable the “Do not keep the history of recently opened documents” policy. On the other hand, if you disable the policy by setting it to “Not configured” or deleting it, the Group Policy will delete the entry from the registry, and the system will act as though the value is 0 – for instance, it keeps the history of the recently opened files in your computer.

Option 4 – Try to use the Group Policy Editor

  • Tap the Win + R keys to open the Run utility and type “gpedit.msc” in the field and tap Enter to launch the Group Policy Editor.
  • Next, navigate to User Configuration > Administrative Templates > Start Menu and Taskbar.
  • Afterward, double click on the “Do not keep a history of recently opened documents” policy located on the right panel. This is the policy that lets you enable or disable recent items and frequent places.
  • Now to enable the recent items, as well as the frequent places, feature, click on the “Disabled” or the “Not Configured” option.
  • Once you’re done, close the Group Policy Editor and restart your PC.
Note: If you choose to enable this setting, the system and Windows programs will not create shortcuts to documents opened while the setting is in effect. Aside from that, they also stay but won’t display the existing document shortcuts and the system will empty the Recent Items menu on the Start menu and the Windows programs won’t also display shortcuts in the Start Menu. In addition, the Taskbar won’t also show the recently opened or frequently used folders, files, or websites.
Read More
Fixing corrupted system files in Windows
Windows has a lot of built-in tools that help you fix tons of system-related issues. One of them is the System File Check which is the tool you can use to conveniently replace potentially corrupted or missing system files with good ones. But what happens when it does not work? Well, you’ve come to the right place as in this post, you will be guided on how you can replace a corrupted single Windows system file manually with a known good copy of the file if the System File Checker scan is not working. When you encounter this issue with the System File Checker, it will be unable to replace the corrupted system files and returns an error message instead. And so to fix and replace corrupted system files in your Windows 10 computer without the help of System File Checker, you can refer to the instructions provided below. Step 1: First, you need to open the log files listed below and identify which particular file has been corrupted:
  • %userprofile%Desktopsfcdetails.txt
  • Log %WinDir%LogsCBSCBS.log
Step 2: You will see all the details on the given log files. Once you find out the name and the path of the file, you have to take ownership of this corrupted system file. Step 3: To take ownership of the corrupted file, you need to pull up Command Prompt by tapping Win + R keys on your keyboard and then type “cmd” and tap Enter. Step 4: After opening Command Prompt, type and enter the command below to execute it:
takeown /f FileNameAndPath
Note: In the given command, “FileNameAndPath” represents the name and the path of the corrupted file. For instance, the corrupted file is named “wuapi.dll”, then you need to type “takeown /f C:/Windows/System32/wuapi.dll” Step 5: Next, you need to grant administrators full access & control to the corrupted file and you can do that via Command Prompt again. Step 6: In the elevated Command Prompt, type and enter the following command to execute it:
icacls FileNameAndPath /GRANT ADMINISTRATORS:F
Note: We’re going to use the wuapi.dll again as an example. So the command should be like this: icacls “C:/Windows/System32/wuapi.dll /grant administrators: F”. Step 7: Now all that’s left to do is replace the corrupted system file with a good copy from a trusted source. Once you have a copy, open an elevated Command Prompt again and execute the following command:
copy NewFileLocation FileNameAndPath
Note: In the command given above, the “NewFileLocation” is the location where you have saved the copy of the file. For instance, if you’ve saved it on your desktop, this is how it should look: “copy C:/Users/<username>/Desktop/wuapi.dll C:/windows/system32/wuapi.dll”
Read More
0x80070780, The file cannot be accessed
Error 0x80070780 is a particularly nasty error since it means we can not access files on our hard drive. This might be an important file from work or anything similar and it can be frustrating when we can access it. In this article, we will address solutions to this error so you can continue with your activities where you have left off. Follow the guide step by step in the given order to minimize file damage and find the solution quickly.
  1. Run File and Folder built-in troubleshooter

    The simple and clean solution, try first by running Windows built-in tools. Leave troubleshooter to scan and attempt repairs and try to access a file after that.
  2. Run disk checker

    Maybe the file is corrupted or slightly damaged but repairable, run a built-in Windows disk checker and let it scan and repair any error found. Try accessing your file after the scan.
  3. Try copying file

    If the file is under a bad sector or cluster on a disk drive that could be a reason why you can not access it, try copying the file to another location and then opening it, if the operation fails, boot Windows in safe mode and try to copy or move file then. If you are successful with copying files in safe mode, reboot your computer and try to open the file.
  4. Reinstall the driver for the hard drive

    Like when the driver for USB is not working and you can not access files same can happen on your hard drive. Go to the device manager and reinstall the driver for your hard drive.
Read More
Android apps inside Windows 11
Android apps inside Windows 11The euphoria around Windows 11 is not dying and reveal that Android apps will work natively inside Windows 11 has raised many emotions and questions. So, Microsoft has announced that Android apps will run natively inside Windows 11 OS and that they will reside alongside your other installed ones as icons, etc. It is no secret that many users have been using emulation software to run Android apps inside Windows so far, so what is the difference?

It is still emulation

Whatever you would like to believe it is still emulation and Android apps are at the end of the day still Android apps running inside emulated environment. This time we will not need third-party emulation software running inside Windows, we will have third-party emulation services running inside Windows. Intel has teamed up with Microsoft in order to integrate Intel bridge algorithms in order to run Android apps, meaning that yea, pretty much we have emulation services running in order to run the application. The problem with this kind of approach is that well emulation software is running and consuming system resources only when we start it, this kind of service is always running and always consuming resources and for someone who really does not care about Android apps at all, this is just a waste of resources.

Android store

The store is another issue here, instead of the Google play store we will have the Amazon app store integrated inside the new Microsoft store. This means that any kind of for example game progress or login information from Google store cannot be transferred into Windows 11, add to that information that in the Amazon app store there are tons of missing applications like SLACK, TRELLO, BitWarden, etc and we might have a serious question here about the use of this feature.

Android apps that do not use Android services

If you even look past that it is still emulation and that it is available on the Amazon app store there is still concern about applications not using Google services for their running. Many Android apps are relying on Google services like location or optimize their use of on-device resources, handle in-app purchases, etc. that cannot be found on this system. Uber is a prime example that uses Google location service to determine your location and for its mapping data, with that application, is useless. Other like Guardian will even pop up message that says Google play service is required in order to even work.

Android apps without Eero system

Amazon Eero system for enhanced internet access is not even yet available in its own app store which brings us to missing some key players like Bank of America, Chase mobile, Bueller, etc. And across the board, the apps that are present in the Amazon Appstore are often as good as abandoned. Lots of titles are numerous versions behind their up-to-date Play Store counterparts, and plenty of programs you encounter in the Amazon environment clearly haven't been touched in years.

Conclusion

Many new Windows 11 features are quality features that I personally consider good but although this one seems innovative and good I simply cannot stand back it up. Android apps were already inside Windows with emulation software which used google services and was working just fine, this was not needed in my opinion.
Read More
Fix Windows Setup Error code 0x80070006
Windows 10 setup is a bit complicated which is why it’s uncommon to encounter errors along the way. One of these errors you can encounter when running Windows Setup is the error code 0x80070006. If you are trying to fix this error, you’ve come to the right place as this post will guide you on how to do so. When you get the error code 0x80070006, you will see the following error message:
“Windows cannot install required files. Network problems may be preventing Windows from accessing the file. Make sure the computer is connected to the network and restart the installation. Error code: 0x80070006.”
As stated in the error message, this kind of error in Windows Setup is due to an unstable or unreliable network connection. Such problems can also be triggered by network hardware which includes the network adapters and the network routers. To fix this error, you need to check your internet connection and router or run the built-in network troubleshooter. You could also try using a different USB port or recreate a bootable USB drive as well as get a new Windows image file.

Option 1 – Try checking your internet connection and router

As mentioned, this Windows 10 setup error could be due to an unstable internet connection. To fix it, the first thing you have to do is to check the status of your internet connection and see if it is stable and has enough speed to run the setup. If it’s slow, then it’s no wonder that the setup process failed. To fix that, you can try to reboot your router from its admin panel or you can just turn it off manually and then turn it back on after a couple of seconds. In addition, you also have to check if it’s plugged in properly.

Option 2 – Try to run the Network Adapter troubleshooter

The next thing you can do is to run the Network Adapter troubleshooter. This built-in troubleshooter can help resolve any network issues. It can reset the adapters, remove cached settings, and many more. To run it, follow these steps:
  • Go to Settings > Update & security and from there select Troubleshoot.
  • Next, scroll down and select the “Network Adapter” option from the right pane.
  • Then click on the Run Troubleshooter” button.
  • After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.

Option 3 – Try to use a different USB port

You might want to check the integrity of the USB port where connected the device if you are using a bootable USB storage device to run the setup for Windows 10. All you have to do is switch the USB port or try to use another bootable USB device and see if it fixes the problem.

Option 4 – Try recreating the Windows 10 installation USB

Recreating the Windows 10 installation USB might help in fixing the problem. You can use a USB drive to do so but make sure that it has a great read-write speed. Follow the steps below to recreate Windows 10 installation USB”
  • Click this link and then click the Download Tool Now button.
  • Next, click the “Use the tool to create installation media (USB flash drive, DVD, or ISO file)…” option and follow the next given instructions on the screen.
  • Now select the ISO file option in step 5.
  • After that, you should now have an ISO file.
  • Next, go to the location where you’ve downloaded the ISO file.
  • Then right-click on the Windows 10 ISO file and select the Open with option and then select File Explorer.
  • Now click on “setup.exe” and follow the next instructions that appear on the screen. When asked, you have to select either Nothing (clean install) or Keep personal files only option. Take note that you must not select the “Keep personal files, apps, and Windows settings since it doesn’t really work.

Option 5 – Try getting a new Windows image file

If none of the four given options above worked, you might want to get a newer installation image using the Windows Media Creation tool. After that, create the bootable USB drive and once completed and then try to run the Windows 10 setup again.
Read More
1 2 3 171
Logo
Copyright © 2023, ErrorTools. All Rights Reserved
Trademark: Microsoft Windows logos are registered trademarks of Microsoft. Disclaimer: ErrorTools.com is not affiliated with Microsoft, nor claims direct affiliation.
The information on this page is provided for information purposes only.
DMCA.com Protection Status