Fixing the We can’t find a USB flash drive

There are times when the Windows Search results do not include what you want to search. However, if you are trying to search for something that’s located on your desktop and Libraries, they would appear right away on the search results. Actually, the issue is not with the search but with the list of files and folders that Windows can index. If you encounter this issue, read on as this post will guide you on how to fix it. The Windows 10 operating system, ever since Windows v1903 was released, offers two kinds of searches – the classic and the enhanced search. You may have to add more folders to the classic search or use the enhanced mode to resolve the issue. In other words, to fix the problem with the Start Menu Search, you can try to enable the Enhanced Mode or add folders to the Class Search or remove the excluded folders, as well as run the Search and Indexing troubleshooter. For more information, refer to each one of the options provided below.

Option 1 – Try to enable the Enhanced Mode

To fix the problem, you have to enable the Enhanced Mode search and configure the folders you want to be indexed. How? Follow these steps:

• First, you have to go to Settings > Search > Searching Windows.
• Next, select the radio button for the Enhanced option.
• After that, select the folders you want the Windows Indexer to exclude from the Enhanced Search mode.

Option 2 – Try to add folders to the Class Search

If you don’t want to enable the Enhanced search mode, then you might want to add folders that are important to you. All you have to do is configure the Search Indexing Options by following these steps:

• Go to Settings > Search > Classic and from there, click on the “Customize search locations” option.
• Next, click on Modify in the pop-up window that appears.
• Then add drives and folders that are important to you. Once the indexing is completed, Windows will be able to find the file and display it in the search results.

Option 3 – Try removing the excluded folders

If you have already enabled the Enhanced mode but your files still don’t appear, then you might want to check out the excluded folder list.

• The first thing you have to do is go to Search and from there, you will find a list of folders under the Excluded folder list.
• Next, click on the excluded folder that you want to remove by clicking on the “Remove Excluded folders” button.
• If you are using the Classic search, you have to check if the index has restrictions on the file type. You can find it in Advanced options > File Types.

Note: If you want to search in Documents, you could also enable the Index Properties and File Contents. This should resolve the problem.

Option 4 – Try to run the Search and Indexing troubleshooter

You might also want to run the Search and Indexing troubleshooter in Windows 10 as it checks whether the settings for the Windows Start Search are in place and automatically corrects any issues if the update or software installation has changed the settings. To run it just click on the Start button and select Settings > Updates and Security > Troubleshoot. From there, select the Search and Indexing Troubleshooter.

The Volsnap.sys is a Windows operating system file that is related to the Volume Shadow Copy Service or VSS. It is known to cause a Blue Screen of Death error. The main cause of the Volsnap.sys Blue Screen errors include conflicts with the RAM, issues with the hard disk, incompatible firmware, corrupted drivers, malware infection, and many more. Despite its many possible causes, its fixes are quite straightforward so won’t have any problem following them. The Blue Screen errors that are related to the Volsnap.sys file are:

• KMODE EXCEPTION NOT HANDLED
• PAGE FAULT IN A NONPAGED AREA
• SYSTEM THREAD EXCEPTION NOT HANDLED
• IRQL NOT LESS OR EQUAL

You might want to try performing System Restore as it could resolve Blue Screen errors like the ones related to the Volsnap.sys before you proceed with the troubleshooting tips given below. 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 – Check if the Volume Shadow Copy service is running and restart it

The first thing you need to do is check if the Volume Shadow Copy service. To do that, refer to the following steps:

• Click on Start and type “cmd” and right-click on Command Prompt from the search results.
• Then select the “Run as administrator” option to open Command Prompt with admin privileges.
• After that, type “net stop sdrsvc” and hit Enter to execute the command in stopping the Volume Shadow Copy service.
• Next, type the “net start sdrsvc” command and hit Enter to start the service again.

Note: You can also restart the service using the Windows Services Manager.

• In the Cortana search box, type “services” and click on the Services icon to open the Services Manager. Alternatively, you can also tap the Win + R keys to launch the Run prompt and then type “services.msc” in the field and hit Enter to open the Services Manager.
• From there, look for the Volume Shadow Service (sdrsv) from the list of services. Its Startup type should be set to Manual by default.
• Restart the service and if you don’t encounter any error while you turn it on, re-run the backup service and see if the backup process runs successfully.

Option 2 – Try checking the Memory for the Errors using Memory Diagnostic Tool

The Memory Diagnostic tool in windows can help resolve the Volsnap.sys Blue Screen error by checking and automatically fixing any memory-based issues. To run it, refer to these steps:

• Tap the Win + R keys to open Run and type mdsched.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 your preferred option, your computer 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 3 – 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 rollback 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 go to the section of IDE ATA/ATAPI controllers as well as Storage Controllers 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 4 – Try to run the CHKDSK utility

Running the CHKDSK utility might also help you resolve the Volsnap.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 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 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 Volsnap.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.

Qtcore4.dll Error - What is it?

Qtcore4.dll is a dynamic link library file that helps Microsoft Windows in loading several key components of the system. The Qtcore4.dll error occurs when the Qtcore4.dll file cannot be loaded to run the application supported by this .dll file. The Qcore4.dll missing error message may occur while booting your system or launching a certain program. It is a blue screen of death error type. The Qtcore4.dll error code is often displayed as:

BLUE SCREEN ERROR - QtCore4.dll Not Found

Filei386QtCore4.dll could not be loaded. The error code is 7. Setup cannot continue. Press any key to exit.

Solution

Error Causes

This error code is triggered by a variety of reasons such as:

• Windows file allocation file gets damaged
• Your computer BIOS (Basic Input/Output System) are misconfigured
• The Qtcore4.dll file gets corrupt
• Registry gets damaged and corrupt
• Non-Microsoft program not running in tandem with Windows
• Malware attack
• Improper hardware driver software

It is advisable to fix the Qtcore4.dll error code immediately as this error can pose serious threats to your system. Qtcore4.dll error can lead to system breakdown.

Further Information and Manual Repair

Here are some ways of fixing the Qtcore4.dll error on your system:

1. Re-install the Program Causing Qtcore4.dll error message to pop up

As dll files are shared files sometimes due to program deletion and installation .dll file settings can get misconfigured, damaged, and corrupt. In such a scenario, you can try reinstalling the program that is causing Qtcore4.dll error message to appear on the screen.

2. Reconfigure your Mis-configured BIOS

If BIOS misconfiguration is the cause of this error code on your system, then try reconfiguring your system’s misconfigured BIOS.

• To do this boot the computer and then press the BIOS designated keys to enter the BIOS. The keys may vary from manufacture to manufacture but typically, the setup keys are F2, F10, F12, and Del.
• Once you figure out the setup keys, press them rapidly when booting the computer.
• After successfully hitting the setup keys, the BIOS will load and you will see the BIOS setting menu on your screen. Adjust settings. Go to SATA Operation and change RAID AHCI to RAID ATA. Save changes and then exit.

3. Scan Your PC with a Registry Cleaner and an Antivirus

However, after adjusting the BIOS if the error still pops up on your screen, then this indicates the problem is bigger than you think. It triggers either malware attack or registry corruption. If these are the underlying causes for the Qtcore4.dll error on your system then you need to scan your PC with a registry cleaner and an antivirus. Registry is the main database of your system; if this gets corrupt it is most likely to result in system failure and valuable data loss. And as for malware, the biggest concern is data security threats. Today’s advanced and lethal malware like viruses and spyware can give easy access to hackers to enter your system from a remote location, browse through your confidential and private data and manipulate it to their advantage. This has led to a surge in various types of cyber crime, data breaches, and identity theft cases over the years. To avoid all this while resolving the error code Qtcore4.dll on your PC, registry cleaning and repair and antivirus scan are needed. You can either download 2 separate tools on your system to scan your PC which by the way will take a lot of time and increase your chances of the system slow down or you can download Restoro.

Why Restoro?

• Total System Care is an advanced, user-friendly, high, and multi-functional repair.
• It is deployed with a powerful and intuitive registry cleaner. It also functions as a system optimizer. It spares you from downloading numerous tools to address and resolve different errors on your PC.
• It is your one-stop solution for not only Qtcore4.dll problems but practically all PC-related issues.
• The registry cleaner utility detects all the malicious, unnecessary, and obsolete files overloading and corrupting your RAM.
• This includes junk and temporary files. It wipes them out thus clearing your disk space. Simultaneously, it also repairs the damaged and misconfigured dll files including the Qtcore4.dll file, and fixes the corrupt registry.
• The privacy error utility has the properties of an antivirus. It detects and removes malware, viruses adware, and spyware from your system in seconds.
• Total System Care resolves the Qtcore4.dll error on your system and boosts the performance of your system. It has a simple and neat interface which makes it quite easy for users to operate it, even those who are not technically adept.
• It is compatible with all Windows versions

Click here to download Restoro and repair the Qtcore4.dll error on your PC.

0x80042109 - What is it?

0x80042109 is a Microsoft Outlook error. The 0x80042109 error code occurs mostly while sending emails. The error message is often displayed in the following format:

“Sending reported error (0×80042109): Outlook cannot connect to your outgoing (SMTP) e-mail server.”

Solution

Error Causes

It is not easy to narrow down the cause for the error code 0x80042109. This error can occur due to many reasons. This includes:

• Corrupt emails and PST files
• Incorrect Outlook account settings
• Unavailability of the mail server
• Incomplete Outlook installation
• Spyware or viral infection

Further Information and Manual Repair

To resolve the 0x80042109 error code on your PC, here are some easy and effective DIY solutions you can try:

Method 1 - Check Mail Settings

Check your mail settings to see if your outgoing server SMTP is selected or not. If it is not, then it could be the reason for the issue. To check mail settings and select the option, here’s what you need to do:

1. Click Tools, select Account Settings, and then POP 3 account and click change.
2. Now check your name field and email address.
3. Check the incoming and outgoing mail server fields and make sure that it is correct.
4. Now click on the outgoing server and make sure that the option ‘My Outgoing Server (SMTP) requires Authentication is selected.
5. After that, click Advanced and tick the option that says ‘This server requires an encrypted connection (SSL).
6. Now click OK to confirm settings.

Method 2 - Reinstall Outlook on your PC

The error may also occur due to incorrect Outlook installation. Therefore reinstall it on your PC. To do this first you will have to uninstall the software and then re-install it. Once the software is reinstalled try sending the email again. If it is sent successfully, then this means the error is related to incomplete installation. However, if the error still persists then it is advisable to restore the points by going to the System Restore option and choosing the option ‘Restore My Computer to an Earlier Time’ point. This will revert the changes.

Method 3 - Try Disabling Firewall

If you have firewall program installed on your PC, then try disabling it and then send an email through your Outlook account.

Method 4 - Scan for Viruses

Another way to resolve the error code is to scan for viruses. Viral infection and spyware and also affect your Outlook account and activities. However, installing an antivirus on your PC may slow down its performance as such programs are notorious for doing that. Therefore, it is advisable to download Restoro. Restoro is a next generation and a highly advanced PC Fixer embedded with powerful and multiple utilities including an antivirus and a system optimizer. Its intuitive algorithm enables it to scan your entire PC and remove all kinds of malicious software affecting your system including malware, adware, spyware, viruses and Trojans. The system optimizer utility works simultaneously and ensures your PC performs at its optimum speed. It is safe, bug-free, and efficient. It has a user-friendly interface which makes it simple and very easy to operate. You can download it on all Windows versions. Click here to download Restoro to resolve error 0x80042109 today!

What is Error Code 1309?

Error code 1309 is an error code that occurs when installing either Microsoft Office 2003 or Microsoft Office Project 2003. This error code may hamper your ability to run and use applications associated with Microsoft Office. To ensure installation is successful, it is first advisable to fix this error code. Error 1309 is displayed in any one of the two formats illustrated below. When installing Microsoft Office Project 2003, the error message may pop up as:

Error 1309. Error reading from file:    pathfilename.cab. Verify that the file exists and that you can access it.

When installing Microsoft Office 2003, the error message may appear in the following format: Fatal Error During Installation

Solution

Error Causes

Error code 1309 message may appear during Microsoft Office installation due to several reasons. These include:

• Problems in the Oclncore.opc file. Project 2003 uses this version of the file for program installation.
• Lack of adequate use permission
• The requested file was not found
• Setup registry entries are modified in an unacceptable manner

To avoid inconvenience and access Microsoft Office 2003 or Microsoft Office Project 2003, it is recommended to fix the error immediately.

Further Information and Manual Repair

To resolve this error you don’t need to be a technical whiz. Here are some of the best, easiest, and proven do-it-yourself methods to resolve error 1309 on your computer screen instantly.

Method 1 - Change CacheLevel Settings

If the problem is related to Oclncore.opc file then try changing CacheLevel settings. Follow these steps to work around this method.

1. First, locate the PRJPRO*.XML file in the FILESSETUP folder of the Project 2003 installation source and then open this file in the Notepad.
2. Also, make sure that you do not open the file as read-only and make sure that a checkmark is not displayed next to Word Wrap on the Format menu.
3. The next step is to search the file for the following text string: OCLNCORE.OPC_1033.
4. Now on the line where this string is located, change the CacheLevel=’1’ setting to the following CacheLevel=’3’ save the file back to the original location, and then quit Notepad.

After the changes are activated, try installing the software again on your system. If it installs successfully, then this means error 1309 is resolved. If the error still persists then try other given methods.

Method 2 - Configure security settings to get full permission

When the cause of error 1309 on your PC is related to lack of adequate permission issues, then configure security settings to resolve. To do this, simply locate the folder on your installation drive. Then right-click the folder and click Properties. On the Security tab, click edit and now make sure your user name is added to the list. Grant required security permissions and then click OK to save changes. After this, try installing Microsoft Office 2003 again on your system.

Method 3 - Copy the requested file from another source

If the error 1309 pops up because the requested file was not found, then try this method. Simply copy the file specified in the error to the destination directory. For example, if the error shows data1.cab was not found, then copy this file from another source and paste it into the directory specified in the error description.

Method 4- Remove bad registry entries

Bad registry entries are responsible for registry setup modification. If this is the reason for error code 1309, then download Restoro. This is a user-friendly PC Repair Tool embedded with a powerful registry cleaner. It scans and removes all bad and invalid entries accumulated in the registry. It cleans and repairs the registry resuming it back to its normal function. Click here to download Restoro and repair error 1309 today.

Some Windows users are encountering the 0x800705b3 error code after failing to install a pending update on Windows 10. Most commonly this particular issue is reported to occur with Integrated webcam drivers updates and Bluetooth adapter driver updates. Follow the guide below in order to fix the issue and update your Windows successfully

Running the Windows Update Troubleshooter

The majority of users that were dealing with this issue reported that the issue was fixed after they ran the Windows Update Troubleshooter and applied the recommended fix.

1. Open a Run dialog box by pressing ⊞ WINDOWS + R. Inside the text box, type ‘ms-settings:troubleshoot’ and press ENTER to open up the Troubleshooting menu. Opening the Troubleshooting tab on Windows 10
2. Once you’re inside the Troubleshooting tab, move over to the right-hand section of the screen and click on Windows Update (under Get up and Running). Next, from the context menu that just appeared, click on Run the Troubleshooter.
3. Once you’re inside the Windows Update troubleshooter, wait until the initial scan is complete and see if a viable repair strategy is found.
4. If the scan has identified a strategy with the potential to fix your ongoing issue, click on Apply this fix and wait until the procedure is complete. Applying the fix Note: Depending on the type of fix that was recommended, you might need to follow an additional set of instructions before the fix will be properly imposed.
5. After you’ve done this, reboot your computer and wait for the next startup to complete.
6. Open Windows Update once again and see if the installation of this pending update is now successful.

Installing the pending Update Manually

Whether you’re experiencing this issue with an integrated webcam driver or with anything else, chances are you’ll be able to circumvent the apparition of the 0x800705b3 error by using the Microsoft Update Catalog to find, download and install the pending update manually.

1. Open your default browser and navigate to the root web page of the Microsoft Update Catalog.
2. Once you’re inside the Microsoft Update Catalog, use the search function (top-right corner of the screen) to search for the update that is failing.
3. After the search is completed and you get the list of results, look for an updated driver version that is compatible with your Windows version and CPU architecture.
4. Once you manage to identify the correct Windows Update, click on the hyperlink associated with the update that you want to install, then click the Download button and wait for the process to complete.
5. After the download is complete, use File Explorer to navigate to the location where you previously downloaded the update.
6. When you get to the correct location, right-click on the .inf file and choose Install from the context menu that just appeared. Note: If you have multiple failing updates with the same 0x800705b3, repeat the instructions above with every Windows Update that you’re having trouble installing.
7. At the end of this operation, reboot your computer and see if the problem is fixed at the next computer startup.

Enabling the Windows Installer Service

The Windows installer service is responsible for installing pending updates that get downloaded by the Windows Update component. If this service is disabled on your configuration, none of the updates waiting to get installed will get completed.

1. Press ⊞ WINDOWS + R to open up a Run dialog box. Inside the text box, type ‘services.msc’ and press ENTER to open up the Services utility.
2. Once you’re inside the Services screen, move over to the right-hand tab of the screen, scroll down through the list of services and locate the Windows Installer service. When you find it, right-click on it and choose Properties from the context menu that just appeared.
3. Once you are inside the Properties screen of the Windows Installer services, access the General tab, click on the Start button to force-start the service. Note: If you can, also change the Startup type to Automatic via the associated drop-down menu. However, depending on your administrator settings, this might not be possible.
4. Restart your computer and wait for the next startup to complete. Once your PC boots back up, attempt to reinstall the driver that was previously triggering the 0x800705b3 error and see if the issue is now fixed.

Performing a Winsock Reset

In case the 0x800705b3 error is related to some kind of network inconsistency (TCP or IP related), you might see Windows Updates failing due to bad data that forces the Windows to abort the installation of new pending updates. In this case, you should proceed by doing a complete Winsock reset procedure to fix the majority of the socket and temporary data-related issues that might cause this behavior. Several affected users have confirmed that this method was the only thing that allowed them to finally fix the Windows Update issue and install pending updates normally. Here are some step-by-step instructions that will walk you through the process of performing Winsock Reset:

1. Open up a Run dialog box by pressing ⊞ WINDOWS + R. Inside the text box, type ‘cmd’, then press CTRL + SHIFT + ENTER to open up an elevated Command Prompt. Accessing an elevated CMD prompt Note: When prompted by the UAC (User Account Control) prompt, click Yes to grant admin access.
2. Inside the elevated CMD prompt, type and taste the following commands in order and press ENTER after each one to effectively reset the TCP and IP data that might be responsible for the apparition of the 0x800705b3 error code:

   nbtstat -R
   nbtstat -RR
   netsh int reset all
   netsh int ip reset
   netsh winsock reset

3. Once every command above is processed successfully, you can go ahead and close the elevated Command Prompt and reboot your computer.
4. After the next startup is complete, repeat the installation of the Windows Update that was previously failing and see if the issue is now fixed.

Performing SFC and DISM Scans

If none of the ‘superficial’ causes have worked in your case, you should start considering some type of system corruption that might affect your computer’s ability to complete pending updates that are currently waiting to be installed. In case you find yourself in this particular scenario, you should run a couple of built-in utilities capable of fixing corrupted instances that might be currently affecting the Windows Update component. Our recommendation is to start with a simple System File Checker scan. An SFC scan will cross-check every Windows File against a local archive that maintains healthy copies. In case corrupted instances are found, this utility will swap the corrupted instance with the healthy equivalent.

Performing an SFC scan

Once the SFC scan is complete, reboot your computer and wait for the next startup to complete. After your computer boots back up, initiate a DISM scan. This utility works differently in the sense that it relies on a sub-component of Windows Update to download healthy copies for the corrupted Windows files that need to be replaced. Because of this, it’s important to make sure that you have a reliable Internet connection before initiating this operation.

Doing a DISM scan

After the DISM scan is complete, reboot your computer one final time and see if the issue is fixed once the next startup is complete.

Hello all the wonderful people and welcome to our new article where we take a little different turn than usual and discuss why keeping old electronics around the house is not such a good idea. We all have some drawer or in some bag around the house and in the end of the day if that electronic has battery inside it is probably not the smart thing to keep it.

So naturally, the question comes why it is a bad idea to have old electronics with batteries in them? Well unlike a battery failure with, say, some AA batteries jammed in the back of an old toy, the risk with a lithium-ion battery failing isn’t just some leaking and corrosion in the battery compartment, it’s a potential fire as the battery swells up and the gases (combined with the stored energy) turn the battery into a potential fire hazard.

Good thing is that the battery will not explode just like that, it will swallow over time and get bigger and bigger until the breaking point is reached and all the fire breaks lose. So if by any chance you have some old gadgets lying around you can check up on them and see if has swelling process started, if yes, dispose properly of that piece of the old device immediately.

How to keep old electronics

If you’re not ready to get rid of the gadget then it’s best to charge it properly for storage. Proper charging keeps the battery cells and circuits in optimum health.

While recommendations vary by manufacturer and application, the general consensus is that lithium-ion batteries should be charged to approximately 40%. (Some manufacturers recommend charging 50% or 60% instead.)

Really, the important part here isn’t the exact percentage. What’s important is ensuring that the battery is charged to roughly half capacity and not stored with a completely discharged or completely full battery.

Discharge rates on lithium-ion batteries in completely powered-off devices are very slow, but you should still plan to top off the charge every 12-18 months or so to keep it around 50%.

If you wanted to go above and beyond, a metal storage container with a snug lid on a basement shelf with a desiccant pack inside to control the moisture would offer optimum conditions.

If you are trying to install or upgrade your Windows 10 computer but suddenly encountered an error message saying, “Windows could not configure one or more system components”, read on as this post will show you how you can fix the problem. You are not alone in experiencing this problem as other users also reported having the same scenario. Some of them reported getting the following error message:

“Windows could not configure one or more system components. To install Windows restart the computer with error code 0xc1900101-0x30018.”

When you check on the Windows 10 rollback log, you will see a part with the “iisetup.exe” that’s related to the abort. Usually, the upgrade process completes over 50% and gets stuck and then rolls back later on and generates the error logs. This kind of error, in most cases, appears during the upgrade of Windows 10 and is related with the Internet Information Services or IIS in Windows 10. For some unknown reason, it restricts the installation or the upgrade which causes the error to appear. To fix the “Windows could not configure one or more system components” error, you can try to remove the IIS from the Windows Features or rename the “inetsrv” folder. You could also move all the folders related to IIS to another drive. For more details, refer to the options provided below.

Option 1 – Try to remove the IIS from Windows Features

The IIS is installed from the Windows Features and you can find it at Control Panel > Programs. From there, uncheck the checkbox for the Internet Information Services. Once done, click on the OK button to save the changes. Note that this process will get rid of all the related programs, services, and folders from Windows 10. So if you want to, you can just install them later on or use an offline installer from the official site of Microsoft.

Option 2 – Try renaming the inetsrv folder

The next option you can check out to resolve the problem is to rename the “inetsrv” folder. If you have uninstalled IIS from the Windows Features, this should remove the folders as well, however, it didn’t remove the folder then you have to delete the folders that are related to the IIS by following these steps:

• First, you have to boot into the Advanced Recovery Mode and from there, open Command Prompt.
• Next, execute this command to rename the folder from this location, C:Windowssystem32inetsrv: rename C:/Windows/system32/inetsrv/inetsrv.old
• Once done, boot into your computer normally and try to upgrade Windows 10 again, and check if the problem is fixed or not.

Option 3 – Try to move the folders related to IIS to a different drive

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• Next, look for the Application Host Helper Service from the list of services and stop it.
• Once done, take ownership of the “WinSxS” folder and then move the *windows-iis*.*” folders to another drive. You can just search using the “*windows-iis*.*” keyword in the Start Search.
• Next, tap the Ctrl + X keys and paste the folders to another drive.
• After that, start the update process for Windows 10 again.

System image backup error 0x807800A1 & 0x800423F3 appears when you are trying to create a system image backup and the operation fails to do so. If you’re faced with any of these error codes, try our recommended solutions in the order presented below and resolve the issue.

Check Volume Shadow Copy & Software Protection Services

To restart the Volume Shadow Copy Service (VSS) on Windows 10, do the following:

• Press ⊞ Windows + X to bring up the Windows menu.
• Click on command prompt (admin)
• In the command prompt window, type the commands below and hit Enter after each line:

net stop vss net start vss

Once the commands execute successfully, try the system image backup again. The operation should complete successfully. You need to also check if the Software Protection Service is disabled. If it is, then Start it and ensure that it is set to default which is Automatic (Delayed Started).

Create System Image using PowerShell

Command lines are less prone to errors provided the syntax is correct, unlike GUIs that can suffer a glitch every now and then. To create a system image with PowerShell do the following:

1. Open the Windows PowerShell as administrator. To create a System Image in Windows 10 using PowerShell, you will have to run the Wbadmin command.
2. Inside the Powershell window type, then press Enter: wbadmin start backup-backup target: E:-include: C:-quiet-allCritical E: is the target drive where you’re going to save the system image, and C: is the system root drive where Windows is currently installed
3. To extract the created system image, starting over from Windows 10 USB installation media, select advanced startup or open run and type: C: \ Windows \ System32 \ Shutdown.exe / r / o

Use third-party imaging software

If the previous two solutions have not managed to solve the issue there is always an option to use a third-party imaging solution. There are free open source and buying options offering various advantages each. Find out which one works best for you and use it.

If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.