Logo

Cannot find a system image on this computer

If you are trying to restore your computer using a System Image that has been created by the Windows Backup and Restore tool but encountered an error message instead that says, “Windows cannot find a system image on this computer”, you’ve come to the right place as this post will walk you through in fixing this error. Here’s the complete context of the error message:

“Windows cannot find a system image on this computer, Attach the backup hard disk or insert the final DVD from a backup set and click Retry. Alternatively, close this dialog for more options.”

In the error message, you are offered two choices – to either Retry or Cancel the operation. You can try to select Retry to try again but you will most likely get the same error if you do so. This kind of error can occur if the name of the WindowsImageBackup folder or any of its sub-folders has been modified. On the other hand, this error can also pop up if this folder or any of its sub-folders have gone missing or have become corrupted. To resolve the error, you can try to move the WindowsImageBackup folder or check its sub-folders. You can also try to isolate the System Image file or rename the System Image folder or remove all the unwanted sub-folders as well as use Command Prompt in Repair mode.

Option 1 – Try to move the WindowsImageBackup folder

The WindowsImageBackup folder must be stored in the root of the volume where it is stored, in line with the functioning of the System Restore utility. For example, if the WindowsImageBackup folder is stored in the “C:/Backups/System Restore Backups/New” location, then you have to move it to the C: drive as well.

Option 2 – Try to check the subfolders of the WindowsImageBackup folder

The classification of folders and files plays an important part to restore in restoring a computer from a System Restore point. Thus, if have modified the names of any files or folders inside the WindowsImageBackup folder, then you need to set the defaults. After that, run System Restore again and check if it fixes the error.

Option 3 – Try to isolate the System Image file

If the System Image file is stored in a USB storage device along with various System Restore images, then it’s no wonder why you’re getting this error. To set things right, you have to make sure that the System Restore image you wish to restore your computer from, is the only one that’s present at the root of the USB storage device.

Option 4 – Try renaming the System Image folder

If you have renamed the System Image folder prior to running System Restore, then it is most likely the reason why you’re getting the “Windows cannot find a system image on this computer” error. This error pops up because the System Restore utility in Windows 10 looks out for the WindowsImageBackup folder so if you have renamed it, you need to change its name back to what it originally was to fix the error.

Option 5 – Try to remove all the sub-folders of the WindowsImageBackup folder

If you have stored some foreign files inside the WindowsImageBackup folder, you need to get rid of them right away and return the folder to its default state as this folder must be left alone and should not be meddled with if you want to run System Restore smoothly.

Option 6 – Try to use Command Prompt in Repair Mode

  • Open Command Prompt while your computer is in the Repair Mode.
  • Next, type and enter this command where you need to replace “<Partition Letter>” with your drive’s letter: dir <Partition Letter>
  • After you’ve found the WindowsImageBackup folder in any of the partitions, type and enter this command: dir <Parition Letter>WindowsImageBackup /s
  • The command you entered will display all the contents of the folder exceeding 10 GB in total size. You can check and confirm the integrity of the folder and if you find that the integrity is violated, then it is the reason why you’re getting the error.

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

Fix Storport.sys BSOD errors in Windows
As you can notice in Blue Screen errors, most of them point out a file that’s related to the errors. One of these files is the Storport.sys file which is a system file related to the storage of data in the storage unit of a computer. This file is created by the Microsoft Storage Port Driver. So if this file ends up getting dragged on Blue Screen errors, there can be a number of reasons for why it’s happened. Blue Screen errors related to the Storport.sys file may include conflicts with the hardware, incompatible firmware issues, corrupted drivers, missing or corrupted system files, to name a few. Here are some of the common Blue Screen errors related to the Storport.sys file:
  • KMODE_EXCEPTION_NOT_HANDLED
  • KERNEL DATA INPAGE
  • PAGE FAULT IN A NONPAGED AREA
  • SYSTEM THREAD EXCEPTION NOT HANDLED
  • IRQL NOT LESS OR EQUAL
  • SYSTEM SERVICE EXCEPTION
Microsoft Windows is the one that provides the Storport.sys file a storage port driver that is suited especially for the use of high-performance buses like fiber channel buses and RAID adapters. There are a number of advantages in using Storport instead of the SCSI Port, according to Microsoft:
  • “Improved performance, both in terms of throughput and the system resources that are utilized.
  • Improved Miniport driver interface that addresses the needs of high-end storage vendors, particularly host-based RAID and fiber channel vendors.”
If you encounter any of the above-mentioned Blue Screen of Death errors, then here are some troubleshooting options that might help but before you get to them, you can try to perform a System Restore first especially if you have the habit of creating System Restore points. This might fix the problem. To perform a system restore, refer to these steps:
  • First, 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. In addition, you also have to boot into Safe Mode with Networking before you carry out the troubleshooting steps below.

Option 1 – Try to update or rollback your device drivers

The first thing you can try to fix the Storport.sys Blue Screen error is 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. Note that the main drivers that might be the cause behind the Storport.sys Blue Screen error will be listed under the “ID ATA/ATAPI controllers” section as well as the “Storage controllers” section.
  • 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 also directly download the relevant drivers of your computer from the manufacturers’ website. So if you have an SSD, the issue might be due to an old storage driver. Option 2 – Try to recreate the Storport.sys file If the first option didn’t work, the next thing you can do is to recreate the Storport.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 Storport.old.
Note: As you can see, the file’s extension has changed from .sys to .old.
  • Now restart your computer and check if the Storport.sys Blue Screen error is now fixed.

Option 3 – Run System File Checker or SFC 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 to 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.
 Reboot your PC.

Option 4 – Try to run the DISM commands

You might want to repair potentially corrupted files in your system as having them could also trigger the Storport.sys Blue Screen error. To repair these corrupted system files, you can run the DISM commands:
  • Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
  • After that, input each one of the commands listed below sequentially to execute them:
    • Dism /Online /Cleanup-Image /CheckHealth
    • Dism /Online /Cleanup-Image /ScanHealth
    • Dism /Online /Cleanup-Image /RestoreHealth
  • Once you’ve executed the commands given above, restart your computer and check if the dxgkrnl.sys Blue Screen error is now fixed.

Option 5 – Run the Blue Screen Troubleshooter

Troubleshooting Blue Screen of Death errors wouldn’t be complete without the Blue Screen troubleshooter. As you know, it is a built-in tool in Windows 10 that helps users in fixing BSOD errors like Storport.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.
Read More
Change Legacy to UEFI without reinstalling
There are some new generation motherboards for laptops and PCs that bring in support for both the Unified Extensible Firmware Interface or UEFI as well as the Basic Input Output System or BIOS. The main advantage of UEFI over the traditional BIOS is the fact that UEFI supports a hard drive that has a capacity of more than 2 terabytes. However, the disadvantage of UEFI is that it only supports the x64 Windows operating system versions and that the hard drive is supposed to use the GPT structure. So if your PC is compatible with and supports UEFI and you want to change from Legacy to UEFI, then you’ve come to the right place as this post will guide you on how you can exactly do that without having to reinstall it. There are two ways to change Legacy to UEFI. You can convert MBR to GPT using either the built-in utilities in Windows or using the Recovery Environment. Before you proceed, make sure that your computer fulfills the following prerequisites:
  • Your PC’s motherboard should support both Legacy and UEFI.
  • Your PC should be running at least the 1703 Windows 10 version or newer on an MBR partition.
Once you’ve made sure that your computer covers the aforementioned prerequisites, refer to the given options below.

Option 1 – Convert MBR to GPT via Windows built-in utilities

  • In the Windows Search box, type “command prompt” and from the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
  • After that, execute this command: exe /convert /allowfullOS
  • Now, wait until the process is completed since you can track its process on your screen.
  • Once it’s done, go to Settings > Update & Security > Advanced Startup options and from there, click on Restart Now. This will restart your computer and give you advanced options.
  • Next, select Troubleshoot > Advanced Options where you will see further options including System Restore, Startup Repair, Go back to the previous version, Command Prompt, System Image Recovery, and UEFI Firmware Settings.
  • Now select the UEFI Firmware Settings. This will take you to the BIOS. Boot Mode is typically available under Boot > Boot Configuration. Once you’re there, set it to UEFI and then save the changes you’ve made. After that, your computer will restart.

Option 2 – Convert MBR to GPT via the Recovery Environment

  • When the message appears on your screen while running Windows Setup, you need to tap the Shift + F10 keys to open Command Prompt.
  • Make sure to run Command Prompt as admin and then execute this command: exe /convert
  • After that, wait until the process is completed. When it’s done, you have to go to the BIOS just like in the first given option above.
  • As mentioned, you can usually find the Boot Mode under Boot > Boot Configuration. Once you’re there, set it to UEFI.
  • Now save the changes made and exit as your computer will restart.
Read More
Disable password asking in Windows 10
To turn password login in Windows 10 you will need approximately one minute of your time. So let's do it fast and efficient Press ⊞ WINDOWS + X to open the secret menu keyboard with windows and x markedClick on command prompt (admin) Windows menu command prompt adminType in command prompt following:
powercfg /SETDCVALUEINDEX SCHEME_CURRENT SUB_NONE CONSOLELOCK 0
press ENTER
powercfg /SETACVALUEINDEX SCHEME_CURRENT SUB_NONE CONSOLELOCK 0
press ENTER And you are done! Next time when you open your laptop from sleep you will no longer need to type in the password.
Read More
Fix DRIVER_CORRUPTED_EXPOOL Error
If you suddenly encounter the DRIVER_CORRUPTED_EXPOOL Blue Screen of Death error when using your computer, then there might be some issues with the device drivers on your Windows 10 computer. This kind of BSOD error can occur at any point while you are using your PC. Its main cause is due to some error in the System Pool where a driver becomes incompatible with the operating system or when the configuration files get corrupted for some reason. If you are one of the users who are currently inconvenienced by the DRIVER_CORRUPTED_EXPOOL error, worry not, as this post will give you some potential fixes that might help resolve the problem.

Option 1 – Perform a System Restore

Performing System Restore might help you in fixing the DRIVER_CORRUPTED_EXPOOL Blue Screen error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.
  • 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.

Option 2 – 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 DRIVER_CORRUPTED_EXPOOL error. 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.

Option 3 – Update the Device drivers

The device driver installed in your computer might be incompatible with your operating system which is the reason why the DRIVER_CORRUPTED_EXPOOL Blue Screen error occurs. To fix that, you have to update your device drivers.
  • Tap the Win + R keys on your keyboard to open the Run dialog box.
  • After that, type “msc” in the field and hit Enter or click OK to open the Device Manager.
  • After opening the Device Manager, update all the outdated Device drivers on your computer.
  • Next, right-click on all the driver entries that are appropriately labeled, and then click the Update driver option.
  • Now restart your PC and check if the BSOD error is fixed or not.

Option 4 – Uninstall any faulty device drivers

  • Tap the Win + R keys on your keyboard to open the Run dialog box.
  • After that, type “msc” in the field and hit Enter or click OK to open the Device Manager.
  • From there, look for any device driver which has a yellow exclamation mark which indicates that something is wrong with them.
  • And then right-click on each one of them and click on Uninstall.
  • Once you’re done uninstalling the faulty drivers, restart your computer and allow your computer to reinstall the drivers you just uninstalled.

Option 5 – Try running the System File Checker

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 that might be causing the Machine Check Exception BSOD error. 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.

Option 6 – Try updating the BIOS

As you know, the BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.
  • Tap the Win + R keys to open the Run dialog box.
  • Next, type “msinfo32” in the field and press Enter to open System Information.
  • From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
  • After that, you should see the developer and version of the BIOS installed on your PC.
  • Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
  • If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
  • Now double click on the downloaded file and install the new BIOS version in your computer.
  • Now restart your computer to apply the changes made.

Option 7 – Try resetting Windows 10

To fix this BSOD error, you can try resetting Windows 10. Doing so won’t get rid of any file in your system – instead of erasing all your media files and documents, this reset option resets all the system settings and files.
Read More
USB Keeps Connecting and Disconnecting
External hard drives have become essential these days as they tend to be very useful to many users. They are usually used for storing system images like system backups, Windows installation media, or for personal use. However, if you are not able to utilize your external drivers for some reason then that could be a huge problem. One of the common issues with hard drives is when your USB device or external hard drive just keeps connecting and disconnecting. This kind of issue could be caused by a faulty USB port, some issues with the USB drivers, your computer’s Power Options, corrupted or damaged system files, and many other factors. The connecting and disconnecting issue with USB devices and external hard drives isn’t really new and has been experienced by many users for years now. Although this issue has somewhat decreased in Windows 10, there are still some users who encounter it every now and then. Worry not though for there are fixes that you can try to resolve the problem. Refer to the following straightforward solutions to resolve the issue with your USB device or external hard drive.

Option 1 – Plug your external device on a different port

If your USB device keeps on connecting and disconnecting then the first thing you can do is to try connecting it to a different port. This will help you isolate the problem. In some cases, the port where the USB is connected can be malfunctioning or obsolete so you need to check that possibility by plugging your USB device into a different USB port.

Option 2 – Update or reinstall your USB drivers

As mentioned earlier, the problem could be due to some issues with the USB drivers. It could be that it has to be updated or you need to reinstall it. To do that, follow these steps:
  • First, click the Start button and type “device manager”.
  • Then click on the “Device Manager” from the search results to open it.
  • From there, look for the “Universal Serial Bus controllers” option and then right-click on each one of the USB drivers and select the Update Driver from the menu.
  • Restart your PC and then click the “Search automatically for updated driver software” option.
You also have the option to update the motherboard and the USB driver from the manufacturer’s official website.

Option 3 – Try turning on the USB External drive

There are times when your system turns off some drives in order to conserve your computer’s power, etc. as a result, the driver that’s required to run your external hard drive properly ends up getting disabled. To fix this, you can prevent your system from turning off your external USB drive by following these steps:
  • You need to make sure that the external drive is connected to your system first.
  • Next, go to the Start Menu and type “device manager” in the field, and click on the appropriate result to open the Device Manager.
  • After opening the Device Manager, expand the category of the Universal Serial Bus controllers.
  • Then double click on your USB Mass Storage device and take note that the name might be different on your system.
  • Now go to the Power Management tab and uncheck the checkbox for the “Allow the computer to turn off this device to save power” option and click OK to save the changes made.

Option 4 – Turn off USB Selective Suspend

Another thing you can try is to turn off USB Selective Suspend especially when the issue has something to do with the Power Options. There are certain systems that are configured to disable USB devices after some time which could be the root cause of the problem. Thus, you need to turn off USB Selective Suspend. Here’s how you can do it:
  • In the Start Menu, search for “control panel” and open the related search result.
  • Then go to Power Options and click on the “Change plan settings” option.
  • Next, select “Change advanced power settings” and look for the USB settings and then expand it.
  • From there, you will see the USB Selective Suspend setting. Disable it and click OK.
  • Now restart your computer and check if it resolves the problem or not.

Option 5 – Format your drive

  • To get started formatting your drive, tap the Win + E keys and then go to the access page of the drive.
  • Next, right-click on the drive and select Format.
  • After that, uncheck the “Quick Format” option and then format your drive properly.
  • Now once the formatting process is finished, unplug the drive and plug it back in afterward.
  • Check if the error is already fixed. If the drive is not initialized, tap the Win + R keys and hit Enter.
  • After opening the Run dialog box, type “diskmgmt.msc” and hit Enter to open Disk Management.
  • From there, right-click on the drive volume and select initialize disk.
  • Next, select the correct partition type and proceed.
Read More
Cannot start new hardware device, Error 49
In case you don’t know, the Windows Registry contains a System Hive which is a core part of Windows. The Windows operating system store various settings, options, and configurations. And if you encounter a Device Manager Error 49 for a device then it means that the system hive has exceeded its size limit. Worry not for this post will provide you with possible solutions that can help you in fixing error code 49. You will see the following error message when you encounter error code 49:
“Windows cannot start new hardware devices because the system hive is too large (exceeds the Registry Size Limit), (Code 49)”
There are instances when it may so happen that the device or devices are no longer attached to the computer but they are still listed in the system hive of the registry. For instance, if you were removing hardware and application for years but they weren’t removed from the registry then the size of the system hive keeps on growing until it hits the maximum limit. As you know, making changes in the registry manually, no matter how knowledgeable you are on such things is not sage since the registry is not only important but also complex. In addition, the System Hive is also a permanent part of the Registry associated with a set of files that contain information related to the configuration of the computer on which the OS is installed. To resolve this error, you must remove or uninstall any hardware devices that are no longer in the system. In fact, the Device Manager hides them by default so you need to enable hidden or non-present devices. Follow the instructions given below to set the Devices Manager to display devices that are no longer connected to the computer. Step 1: Tap the Win + R keys to open the Run dialog box. Step 2: After that type in “cmd” and hit Enter to open the Command Prompt. Step 3: Type “set devmgr_show_nonpresent_devices=1” in the Command Prompt and hit Enter to enable the hidden devices option. Step 4: After that, exit Command Prompt and tap Win + X + M to open the Devices Manager. Step 5: After opening the Devices Manager, click on View and then select the “Show hidden devices” option. This will show you all the devices that are not connected to the computer but are still mentioned. Step 6: Next, select a non-present device and click Uninstall from the Driver tab. Step 7: After that, repeat what you’ve done on step 5 for any other device that you no longer use. Step 8: Restart your computer. You can check the device Properties dialog box in the Device Manager after you’re done removing all the useless devices, to check if the error is now fixed or not. Moreover, you can also try running the Hardware and Devices Troubleshooter as it can also help resolve hardware-related problems. To use it, refer to the steps below.
  • The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
  • After opening Settings, look for the Update and Security option and select it.
  • From there, go to the Troubleshoot option located on the left-hand side of the list.
  • Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
  • After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.
Read More
Microsoft Store Error 0x80072F7D in Windows
Check your connection. Microsoft Store needs to be online. It looks like you’re not. Check connection Code: 0x80072F7D
This is the error that you get if trying to open the Microsoft store on Windows 10 and it fails. If you experienced this error and are unable to access the store do not despair we are here to help you. This particular error is usually due to some internet issues, follow the presented guide step by step in order to solve it and be able to access the Windows store again.
  1. Check your Internet connection

    Since this error is closely tied to internet connection it is advisable to first eliminate the obvious and check if your computer is connected to the internet.
  2. Run Network troubleshooter

    Built-in Windows troubleshooter is a great tool and we will be using it in the next few segments in order to locate the issue and fix it. Open Windows 10 Settings app using the WINDOWS + I Click on Network & Internet Click on Network troubleshooter Select network adapter to diagnose Press the Next button.
  3. Run Internet Connections troubleshooter

    Press WINDOWS + I to open the Settings app Click on the Update & Security Click on the Troubleshoot Select Additional troubleshooters option Click on Internet Connections option Hit Run the troubleshooter button.
  4. Run Windows Store Apps troubleshooter

    Press WINDOWS + I to open the Settings app Select Update & Security Click on the Troubleshoot Use the Additional troubleshooters option Click on the Windows Store Apps option Press Run the troubleshooter button
  5. Temporarily disable security software

    Your antivirus or firewall might be interfering with the application, sometimes, in some cases store is detected as a false positive in some security applications, and its access to the internet is cut. Disable your security suite to see if this is the case.
Read More
System32 Folder Keeps Popping up at Startup
The System32 folder contains vital configuration and information that are essential to the operating system. It is located inside the “Windows” folder and it consists of important DLL files as well as executable files. You probably have noticed some errors that have the “System32” word in them but that does not necessarily mean that the System32 folder is the one that triggers them as these kinds of errors have only occurred when some important files are corrupted or missing. Some users recently reported that each time they start their computers, the System32 folder will automatically open up in the File Explorer. If you encounter the same problem, read on as this post will guide you on what to do to fix it. This kind of issue is most likely caused by service or application interference – it is possible that there is a third-party application installed in your computer or a Windows service that triggers the System32 to pop up during startup. It is also possible that this is a result of system modification. Thus, you need to identify the third-party program or restore your computer to its previous state.

Option 1 – Put your computer in a Clean Boot State

As pointed out, it is possible that some third-party program or service is the one that’s behind the problem. To isolate this possibility and to identify the culprit, you have to put your computer into a Clean Boot State. To do so, follow the steps below.
  • 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 putting your PC in a Clean Boot State, try creating a system restore point and see if the problem still occurs. Clean Boot troubleshooting is designed to help you isolate the problem. For you to execute a clean boot troubleshooting, you must do a couple of actions (the steps given above) and then restart your PC after every action. You might have to disable one third-party app after the other to really isolate the issue. And once you’ve narrowed down the problem, you can either disable the third-party app that’s causing the problem or remove it. Note that you must switch your PC back into the Normal Startup mode after you’re done troubleshooting the problem. Here’s how you can do it:
  • From the “Start” menu, go to System Configuration.
  • After that, switch to the General tab and click the option for “Normal Startup”.
  • Next, go to the Services tab and clear the checkbox for “Hide all Microsoft services”.
  • Then find and click “Enable all” and if prompted, you have to confirm.
  • Afterward, go to the Task Manager and enable all the Startup programs and confirm the action.
  • Restart your PC when prompted.

Option 2 – Perform System Restore

  • First, press 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.

Option 3 – Run System File Checker scan

You might also try running the System File Checker or SFC scan to fix the issue. System File Checker is a command utility built into your computer that helps restore corrupted files and missing files. Refer to the following steps to run it:
  • Hit the Win + R keys 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 and see if the System32 folder still pops up at startup or not.
Read More
Driver Power State Failure Error in Windows
Driver state power failure error can be linked to three things happening in your computer. Incorrect power settings, driver issues, or incompatible hardware. Sadly when this error happens you only receive a blue screen of death with this message: Blue screen of death driver power state failureSadly receiving this blue screen does not really explain which of the three cases is the correct one and causing the unwanted issue. That being said, this article will not offer you a direct solution this time, it will be more like a guide on what to check and to do in order to remove this error, reason for this is the nature of the error itself. If your computer is booting properly and you can enter Windows without issues the first thing you can try is going into power options and set it to high performance, if you are on a laptop set high performance both ways, when plugged and when on battery. Power performance settings can reflect on some hardware and can cause mayhem. After setting reboot the computer and see if the error repeats itself. If the error persists go to the device manager and see if there is hardware that has any kind of warning beside it. If there is, update the driver or remove the driver of the device to see if this fixes the issue. If all of the previous two things fail there is another thing you could try. Turn off your computer and disconnect all hardware except the most basic one. Now, this may take a long period of time but boot your computer and then repeat this process but each time add a new piece of hardware to eliminate and find which one is causing the issue. When found try to see if it is repairable through driver updates or get a new device.
Read More
Fix cannot open IPv4 Properties in Windows 10
Many Windows 10 users often change the IP addresses of their computers’ network adapter in order to connect to the internet or network they belong to in times when there is no automatic connection for their computers. In most cases, access to modifying this setting is restricted for some odd reason even if you are an administrator. So if you are one of the users whose Windows 10 VPN IPv4 Properties are not working, this post can help you remedy that so that you can open and edit the IPv4 Properties on your Windows 10 PC. The common way to change IP settings is by going to Settings > Network and then to Internet > Change adapter options > Select Network adapter > right click and open Properties. From there, you can select TCP/IP 4 and modify it. If you aren’t able to do this, refer to the instructions laid out below to troubleshoot the problem in accessing the IPv4 Properties.

Option 1 – Try using PowerShell to manually set the IPv4 properties

As you are not able to set it using the interface, you can do so using PowerShell instead. Note that this option will only work for you if you run PowerShell with administrator privileges. After opening PowerShell, according to many users, you have to run the this command – set-DnsClientServerAddress -InterfaceAlias “Ethernet” -ServerAddresses xxx.xx.xxx.xxx,x.x.x.x,xxx.xx.xxx.xxx,x.x.x.x Usually, Ethernet is the name of your network adapter which is set by default. If you want to see the actual name of your network adapter, you can just type this command and tap Enter after doing so – Get-NetAdapter -physical | where status -eq 'up' After entering the given command, you will see a list of active Ethernet adapter in your computer as you can see on the image above. Note that the 4 sets of X like the one on the image below should match with the sequence:

Option 2 – Try editing the rasphone.pbk files

The rasphone.pbk files stores property for the connections and since you are not able to access the IPv4 properties, it is most likely that it has been disabled here. The good thing is that you can open these files and edit them using Notepad. Refer to the steps below to do so.
  • Open the Windows Explorer and then enable the show hidden files option.
  • After that, look for the files at this location – C:Users <username>AppDataRoamingMicrosoftNetworkConnectionsPbk_hiddenPbkrasphone.pbk
  • Then right-click on it and select the “Open with” option and choose the Notepad app.
  • After opening the file, look for “IpPrioritizeRemote” from the long list.
  • Once you found it, set its value from “1” to “0”.
  • After that, look for “IPInterfaceMetric” and set its value to “1” and tap Ctrl + S to save the changes you’ve made, and then exit and try accessing the IPv4 properties again. It should work, but if you’re still unable to access it, try the next option below.

Option 3 – Enable the Split Tunneling if you use VPN

All data goes back and forth when you are using a VPN service on your computer. And since you are using VPN, it could be that it disables the IPv4 interface. If that’s the case, you need to stay connected with both the local network and VPN and to do so, you have to enable Split Tunneling. How? Follow these steps:
  • Open PowerShell with administrator privileges.
  • Next, type in “Get-VpnConnection” and tap Enter. After doing so, it will give you the exact name of your VPN.
  • After that, type in “Set-VpnConnection -Name “yourVPNName” -SplitTunneling $True” and tap Enter. Once you enter the command, it will free your IPv5 settings so that you can change it to connect with your local network if you prefer it to.
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