How to Fix 0x0000001A Error Code in Just a Few Clicks!

We couldn’t update system reserved partition” - What is it?

Customers will most likely encounter the “We couldn’t update system reserved partition” error when upgrading to Windows 10 from Windows 7 or Windows 8.1. This error may also come with error code 0xc1900104 or error code 0x800f0922.

Solution

Error Cause

“We couldn’t update system reserved partition” Windows 10 upgrade error is normally caused by too little space on the System Reserved Partition (SRP). The System Reserve Partition is an additional small partition created by Windows, which stores boot files. The SRP can be filled up with security apps and third-party anti-virus. Once this partition has insufficient space, the system will not be able to upgrade to Windows 10.

Further Information and Manual Repair

Caution: The following steps are complex and need to be done by experienced users especially using the command line. Once an error is made in entering commands, there’s a chance that your device can be put in a no-boot situation, or data stored on the device can possibly get lost.

To upgrade to Windows 10, your device needs to have at least 15MB free space on the System Reserved Partition. Follow the procedure below and then try upgrading again.

First, know if the System Reserved Partition is whether in GPT or MBR partition style:

1. Open the Run window by pressing the Windows key + R. Type msc in the window then press Enter.
2. Right-click on the Disk where SRP is located then select
3. Click over the Volumes
4. On the Partition Style line, you’ll see which partition style your device is using, either Master Boot Record (MBR) or GUID Partition Table (GPT)

Second, determine which method you will need:

Depending on what partition style your device has and whether you’re currently on Windows 7 or Windows 8/8.1, there are various methods you need to do.

Method 1: Windows 7 or 8/8.1 with GPT partition

1. Click on the Start button and search for cmd. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.
2. Type mountvol y: /s at the command prompt then press Enter. This command will add the Y: drive letter where you can access the System Partition.
3. Type taskkill /im explorer.exe /f then hit Enter. Afterward, restart explorer in Admin mode by typing exe and hitting Enter.

NOTE: While in Admin mode, some apps like OneNote will not run.

4. Open File Explorer then type Y:EFIMicrosoftBoot in the address bar. Hit Enter.
5. Choose the language folders you want to permanently delete. Language folders are named with four letters split with a hyphen. For instance, you want to delete the German language: choose de-DE.
6. Optional: You can also delete unused font files for more space. Type Y:EFIMicrosoftBootFonts in the address bar then press enter.
7. Once you permanently deleted the unnecessary files, reboot the device to return to explorer.exe to normal mode and remove the Y: drive letter.

Method 2: Windows 7 with MBR partition

Doing this method will make a permanent, but small increase in the free space of the device’s SRP.

1. Delete language folders

a. Open the Run window by pressing the Windows key + R. Type diskmgmt.msc then hit Enter. b. Select System Reserve partition then right-click on it.

c. Choose Change Drive Letter and Paths then select Add.

d. Type Y for the drive letter then click OK.

e. Click on the Start button and search for cmd. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.

f. Type Y: at the command prompt then press Enter.

g. Once you’ve switched to drive Y, type takeown /d y /r /f . then hit Enter.

NOTE: Ensure that the space and period after “f” is included in order for the command to work properly      

h. Type icacls Y:* /save %systemdrive%NTFSp.txt /c /t then hit Enter to back up the permission to the drive.

NOTE: Ensure that all files are marked as successful and that no files are marked as failed.

i. Type whoami then hit Enter. Record the username that appears. Afterwards, type icacls . /grant <username you got from whoami>:F /t then press Enter.

NOTE: Ensure that there’s no space between the username and “:F” or the command will not work.

j. In the File Explorer, open the SRP drive and select the Boot folder. Choose the             language folders you want to permanently delete. Language folders are named      with four letters split with a hyphen. For example: de-DE is the German language          while en-US is the U.S. English language.

2. Truncate the NTFS Log:

a. Open the Command Prompt then type chkdsk /L Y: to check the size of the NTFS Log. If the NTFS Log size is less than 5000KB, you need not truncate the file.

b. Type chkdsk /L:5000 /X /F then hit Enter to truncate the NTFS Log.

c. Return to Disk Management window. Select Action menu then select Check if the device’s SRP now has a larger amount of free space. Once there’s enough space, right click the System Reserve Partition then select Change Drive Letter and Paths. Choose Y: then select Remove.

3. If there’s still not enough available space after truncating the NTFS Log, resize the USN journal:

a. Open the command prompt then type fsutil usn queryjournal Y: to display the size in hex value. Convert the hex value to decimal then divide it by 1048576. The result you will get will be in MB. If the journal size is 30MB or more, proceed with truncating the file.

NOTE: To convert the Hex value to Decimal, open the Calculator app in Windows then choose View menu. Select Programmer then choose Hex. Type the Hex value then choose Dec.

b. Type fsutil usn deletejournal /D /N Y: then hit Enter to delete the journal. Type fsutil usn createjournal m=1500 a=1 Y: to recreate the journal having the new log size value.

4. Restore permissions

a. Type icacls Y: /restore %systemdrive%NTFSp.txt /c /t in the Command Prompt. Check if the files were successfully processed before proceeding. If you see a message saying some files failed while processing, this is normal since some of the files have already been deleted before performing a backup. However, if there are no successful files indicated, the command was not properly executed.

b. Type icacls . /grant system:f /t then hit Enter to adjust the ACL back to System. Now, you can set the owner of the drive by typing icacls Y: /setowner “SYSTEM” /t /c then press Enter.

c. Check if the device’s SRP now has enough free space by going back to Disk Management and refreshing the data. If the SRP already has sufficient space, you can now remove the drive letter. Right-click on the System Reserved Partition then choose Change Drive Letter and Paths. Select the Y: drive then choose Confirm deleting the drive letter by clicking OK.

Method 3: Windows 8/8.1 with MBR partition

This method makes a larger, but temporary, increase in the SRP free space.

1. Be sure you have an external drive having at least 250 MB free space and formatted as NFTS.

2. Open Run by pressing the Windows key + R. Type mscthen to choose the Recovery Partition. Right-click on it then choose Change Drive Letter and Paths.

3. Select Add then type Y for the drive letter, click

4. Click on the Start screen then type cmd in the search bar. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.

5. Switch to another drive by typing Y: in the command prompt. Once you’re in the drive Y, type takeown /d y /r /f .

NOTE: Ensure that space and period after “f” are included in order for the command to work properly.

6. Type whoami then hit Enter. Record the username that appears. Afterward, type icacls . /grant <username you got from whoami>:F /t then press Enter.

NOTE: Ensure that there’s no space between the username and “:F” or else the command will not work.

7. Once the command is completed, type attrib -s -r –h Y:RecoveryWindowsREwinre.wim then hit Enter.
8. Open File Explorer and check the drive letter of the external drive you’re using (In this case, let’s assume F: is the drive letter of the external drive so when you see F: for the rest of the steps, this means the drive letter of the external drive you’re using).
9. Type mkdir F:RecoveryWindowsRE in the Command Prompt then hit Enter. Afterward, type xcopy Y:RecoveryWindowsREwinre.wim F:RecoveryWindowsREwinre.wim /h
10. Type C:WindowsSystem32Reagentc /SetREImage /Path F:RecoveryWindowsRE /Target C:Windows to map the new path
11. Verify if the copy was successfully done then type del Y:RecoveryWindowsREwinre.wim /F
12. Return to Disk Management window. Click on the Action menu then hit Check if the device’s SRP now has a larger amount of available space. Once there’s enough space, you can proceed with the upgrade.
13. Upon completion of the upgrade, move back the wim file to the Recovery Partition. At this point, you can re-map now the location by:
    1. Open the Command Prompt then type xcopy F:RecoveryWindowsREwinre.wim Y:RecoveryWindowsREwinre.wim /h and press Enter.
    2. Type C:WindowsSystem32Reagentc /SetREImage /Path Y:RecoveryWindowsRE /Target C:Windows to re-map to the original path.
14. Return to the Disk Management window. Right-click on the Recovery Partition then choose Change Drive Letter and Paths. Select the Y: drive then choose Remove.

Method: Download a Powerful Automated Tool

Not inclined to go through a long and technical process (as highlighted above)? Download and install a powerful automated tool and get the job done in a jiffy.

Error Code 52 – What is it?

Error Code 52 is a device driver problem that users experience on any Windows 2000 operating system and later Windows systems.

The error occurs when the operating system prevents the peripheral device connected to the computer from functioning properly and is usually displayed by the following message:

“Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)”

Solution

Error Causes

Error Code 52 is triggered by the following factors:

• An incomplete program uninstallation
• An incomplete program installation
• Hardware is not removed properly
• System recovery from viruses
• An improper system shut down

Further Information and Manual Repair

Error Code 52 can pose severe risks to the overall health of your PC and any negligence in fixing it can be disastrous for your computer.

However, since the error code is like other device driver errors, resolving the error is relatively straightforward. Here are a few methods to resolve the error code.

Method 1 – Use System Restore

You can use system restore to roll back the system to a time when there was no error to eliminate the problem. Here is how you can use it:

1. Log in using an Administrator account
2. Click ‘Start’ button and select All Programs > Accessories > System Tools > System Restore
3. Click ‘Restore my computer to an earlier time’ and click ‘Next’
4. Select the last Windows restore point from the ‘On this list, click a restore point’ list, and click ‘Next’
5. Click ‘Next’ on the confirmation window to proceed
6. Restart your PC after restoration is complete

By restoring the system via a last saved system checkpoint, you can obtain undamaged Windows system registry files that can help avert the error code.

Method 2 – Run the Troubleshooting Wizard

If restarting your PC does not help, you will have to find the exact nature of the problem by running the troubleshooting wizard for the device and address the problem accordingly. To do this, proceed with the following steps:

1. Run Device Manager on your PC
2. Click on the program under the installed programs that are creating problems for you
3. Click on the ‘General’ Tab
4. Click ‘Troubleshoot’
5. Upon opening, the Troubleshooting Wizard will ask a series of questions regarding the error. Answer the questions and follow its directions for solving the error code.

After following the directions of the Troubleshooting wizard, make sure to restart your PC for the changes to take effect. Then check if your device is still causing problems.

Method 3 – Manually uninstall and reinstall the device driver

Uninstalling and then reinstalling the device driver can help solve the error.

You can do this by firstly logging in as Administrator and open Device Manager. Select the device that is causing the problem and double click it and make sure that the peripheral is connected properly to the PC.

Upon opening, click on the ‘Driver’ tab and then select ‘Update Driver’. Make sure to refer to the system documentation that you received with your PC or computer to check for the motherboard details and driver specifics.

Method 4 – Use software to automatically download the driver

Manually uninstalling and reinstalling the driver will do the trick, however, it may be time-consuming especially when you would have to resort to your hardware user manual.

Therefore, using a program such as DriverFIX can save you a lot of time and frustration in having your device work properly on your computer.

DriverFIX, with its user-friendly approach to help you fix your PC issues, comes with an integrated database that detects which drivers you need to reconfigure within just a few seconds and downloads it automatically.

It further ensures that your drivers are installed in their entirety leaving no room for any incomplete files to remain that create Error Code 52.

It also has the added advantage of being able to backup and restores your files should there be the slightest possibility of system file damage. DriverFIX is the answer to fixing your PC error codes accurately and quickly.

Click here to download DriverFIX to fix Error Code 52 quickly and effectively!

Why Can’t drag and drop files or folders happens? In case you don’t know, there is a feature in Windows 10 called drag and drop that can help you move or copy files or even folders from one location to another. This feature is useful and can help you move or copy folders and files easier and quicker. However, if you encounter some problem while using this feature, worry not for this post will guide you on what you can do to resolve the problem. There are several suggestions you can check out to fix the problem. You can try to simply tap the Esc key or you could also troubleshoot the problem in a Clean Boot State. Aside from that, changing the drag height and width or disabling the User Account Control via Registry Editor might also help. For more details, refer to the instructions laid out below.

Option 1 – Try to tap the Esc key

According to some users who experienced the same dilemma, by simply tapping the Esc key, they were able to resolve the problem. All they did was tap the Esc key before they drag and drop the folder or files. Thus, you can try doing the same thing as it might also work for you. After you tap the Esc key, you have to check all the background applications and if you see some that could be related to the hotkeys or keyboard, you might have to disable or remove them. Once done, check if the problem is fixed or not.

Option 2 – Try troubleshooting the problem in a Clean Boot State

There are some instances that some conflicting programs installed in your computer might be the reason why you’re having trouble using the drag and drop feature in Windows 10. To identify which program is causing the problem, you need to put your computer in 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” checkbox 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 to configure Windows to use the usual startup, just simply undo the changes.)
• From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

Option 3 – Try changing the drag height and width

The next thing you can do to resolve the issue is to try changing drag height and width by following these steps:

• Tap the Win + R keys to launch the Run utility and type “Regedit” in the field and then tap Enter to open the Registry Editor.
• Next, navigate to this registry key: HKEY_CURRENT_USERControl PanelDesktop
• From there, choose to modify both the “DragHeight” and “DragWidth” located on the right pane.
• After that, change the value to a very high number. Note that these values are nothing but pixel size to drag and drop folders or files.

Option 4 – Try disabling the User Account Control or UAC via Registry Editor

• Tap the Win + R keys to launch the Run utility and type “Regedit” in the field and then tap Enter to open the Registry Editor.
• After that, navigate to this registry key: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystem
• From this path, modify the value of “EnableLUA” from 1 to 0. This should disable the UAC in your Windows 10 computer.

The Windows 10 operating system comes with a user-friendly interface as well as better security features compared to its previous versions. One of these new features is the “Recently Opened Files” feature which displays all the files you’ve opened recently in File Explorer. Although it might seem useful, some users see this as a privacy concern especially if there are other users that use the same computer. If you are one of these users, read on as this post will guide you on how you can disable the “Recently Opened Files” feature in Windows 10. There are three ways you can disable the “Recently Opened Files” feature. You can manually clear the recent files, or disable the feature via Control Panel. You can also do it using the Group Policy Editor.

Option 1 – Manually clear the recent files

The first thing you can do is to clear the recent files manually. Since the information about the recently opened files is stored in the form of cached data, you can locate this data and delete it manually, from time to time. To do that, follow these steps:

• Tap the Win + R keys to open the Run utility and copy this address in the field: %AppData%MicrosoftWindowsRecent
• Next, tap the Ctrl + A keys to select all the items and then tap the Shift + Delete keys simultaneously.
• After that, a prompt will appear where you have to click on Yes. This will delete all the recently opened files in the File Explorer the next time you open it.

Option 2 – Disable the feature via Control Panel

The next option you can try to disable the feature is via Control Panel. Refer to these steps to do so:

• First, click on the Start Menu button and select the Settings icon.
• After that, click on Personalization and then on Start located on the left pane.
• Next, scroll down until you see the “Show recently opened items” in Jump Lists on the Start or the Taskbar and click on it and then toggle it off.

Option 3 – Disable the feature using the Group Policy Editor

If you are using the Windows 10 Pro version, then you have access to edit the functions in the Group Policy. The Group Policy function has the option that can disable all the default services of Windows 10. Note that in this step, you will permanently disable the “Recently Opened Files” feature. So before you proceed, make sure that you really want to disable this feature permanently and not in the meantime.

• Tap the Win + R keys to open the Run dialog box and type “gpedit.msc” in the field and click OK or tap Enter to open the Group Policy Editor.
• Next, on the left side pane, click on the “User Configuration” option and then click the “Administrative Templates” option.
• After that, select the “Start Menu and Taskbar” option and select the “Don’t keep the history of recently opened documents” option in the right pane.
• Now double click on this option and check the “Enabled” option and then click on Apply and OK buttons to save the changes made.

There has been recently discovered in the field of malware targeting Android devices. Affecting more than 10 million users of Android phones, the malware GriftHorse is doing its attacks via phishing and premium services scams. A lot of applications have been discovered that are hosts for this malware and many of them are inside the Google store and available for download. According to Zimperium zLabs, this malware that was recently detected has been doing its scams and attacks even in November of 2020 and has thus far accumulated hundreds of thousands of dollars in its scam. On the surface it looks very harmless, asking for typical permissions like internet access, calls, and other related needed functions, and then it waits. After few months the real attack happens when users get charged with premium service they never subscribed to in the first place.

List of Infected Applications that Carry GriftHorse Trojan

Zimperium zLabs listed out some of the apps with this malware. Users are advised to avoid installing them.

•     Amazing Video Editor
•     Bag X-Ray 100% Scanner
•     Bus – Metrolis 2021
•     Call Recoder Pro
•     Call Blocker-Spam Call Blocker
•     Cinema Hall: Free HD Movies
•     Coupons & Gifts: InstaShop
•     GPS Phone Tracker – Family Locator
•     Fingerprint Changer
•     Fitness Point
•     Free Calls WorldWide
•     Geospot: GPS Location Tracker
•     GPS Phone Tracker – Family Locator
•     Handy Translator Pro
•     Horoscope : Fortune
•     iCare – Find Location
•     iConnected Tracker
•     Instant Speech Translation
•     Lifeel – scan and test
•     My Chat Translator
•     My Locator Plus
•     Plant Camera Identifier
•     Racers Car Driver
•     Safe Lock
•     Screen Mirroring TV Cast
•     Slime Simulator
•     Smart Spot Locator

These are only some of the many infected apps available on the internet. Zimperium zLabs also warned that GriftHorse Trojan exists in over 70 countries worldwide. The infected app quickly changes the language and displays content depending on the user’s IP address.

What is Error 0xe0434f4d?

Error 0xe0434f4d displays when a remote computer runs an instance of the SQL Server 2005 but it fails to initialize. When the plan is started, this error displays in a status window on the SQL Server. Also, when the Update-OffilineAddressBook cmdlet is started in Microsoft Exchange Server, this error can occur.

Solution

Error Causes

Error 0xe0434f4d can occur for possibly two main reasons. The first one is when the System Attendant Service is not properly running, and the second when you don’t have the permission to run the update. Other causes are when the .NET Framework 2.0 security does not allow sqlplanlaunch access to run from a shared network. Another cause is when the Offline Address Book (OAB) is not found in the Configuration Domain Controller server that the server of OAB generation uses.

Further Information and Manual Repair

In case you didn’t know, the Offline Address Book generation server is a mailbox server, and in order to resolve error 0xe0434f4d, you will have to replicate the OAB object to the Configuration Domain Controller server. In order to do so, follow steps:

• Go to start and click on All Programs, then go and click on Microsoft Exchange Server 2010. Click on Exchange Management Console
• In Exchange Management Console, go to Server Configuration and click on Mailbox
• In the details, go to mailbox server that generates Offline Address Book and right-click it, then go to Properties
• In the Properties, click on System Setting and locate the domain controller name in the box that reads Domain controller servers being used by Exchange

Make sure the OAB object is reproduced in the Configuration Domain Controller Server. Follow these steps to do that:

• Go to Start and click on Run. Type Adsiedit.msc in Open box and press Enter. Right-click on ADSI Edit and click on Connect to
• Locate a list reading Select a well-known naming context, and from there select Default naming context. In a Select or type a domain or server window, type FQDN (fully qualified domain name) of the Configuration Domain Controller server which was determined in step 1, and click OK
• Expand Configuration [dc.domain.com], expand CN=Configuration, DC=domain, DC=com, expand CN=Services, expand CN=First Organization, and expand CN=Address Lists Container
• Click on CN=Offline Address Lists and make sure the OAB object is listed on the details pane

When the OAB generation server receives this, then it will connect to the Configuration Domain Controller server and will locate the OAB object. If the OAB generation server is unable to find the OAB object, then the error will return on the cmdlet. On SQL Server, you should change the .NET permissions to allow sqlplanlaunch application access to run from shared administration. For that, follow these steps:

• On ArchiveIQ Server, open System from the Control Panel and note down the computer name
• On SQL Server, log in as administrator and open the command prompt
• On the command prompt type, ‘C:windowsmicrosoft.netframeworkv2.0.50727caspol.ece –m –ag l – url file:\[Archive IQServer Computer Name]AlQRemote$*FullTrust and Press Enter. Type yes and press Enter again to confirm the permission changes.

As you know, Microsoft is consistent in pushing updates to its supported versions of the Windows operating systems in order to make it better and defend it from different kinds of vulnerabilities. And pushing billions of active Windows computers every now and then is really not an easy thing to do since it calls for a complex Windows Update delivery module. These complexities often give rise to various errors like the Windows Update error code 0x80004005. When you encounter this kind of Windows Update error, you will see the following error message on your screen:

“There were problems installing some updates, but we’ll try again later. If you keep seeing this and want to search the web or contact support for information, this may help 0x80004005.”

This kind of Windows Update error occurs due to an issue while either installing or downloading an update. There are several ways you can fix the problem. You can try to replace the dpcdll.dll file, reset the Windows Update-related services, run the Windows Update troubleshooter or manually install the Windows Updates. For more details, check out the options given below.

Option 1 – Try to replace the DLL file with a trusted source

The first thing you can do is to replace the dpcdll.dll file with a trusted source.

• First, you need to get the new dpcdll.dll file from another computer with preferably the same file version number as your computer.
• After that, you need to boot your PC into Safe Mode and navigate to the paths listed below and then replace the file using a USB drive or other external storage devices.
  • For x86: This PC > C:/Windows/System32
  • For x64: This PC > C:/Windows/SysWOW64
• Next, type “cmd” in the Cortana search box and right-click on Command Prompt, and select “Run as administrator” to open it with administrator privileges.
• Now type the “regsvr32 dpcdll.dll” command and hit Enter.
• Restart your PC and check if the error is now fixed.

Option 2 – Try to reset the Windows Update components

If by any chance that the third option didn’t work, you can also try resetting the Windows Update components as it could also help you resolve the Windows Update error. How? Refer to the following steps:

• Open Command Prompt with admin privileges.
• After that, type each one of the following commands and hit Enter after you key in one after the other.
  • net stop wuauserv
  • net stop cryptsvc
  • net stop bits
  • net stop msiserver

Note: The commands you entered will stop the Windows Update components such as Windows Update service, Cryptographic services, BITS and MSI Installer.

• After disabling WU components, you need to rename both the SoftwareDistribution and Catroot2 folders. To do that, type each one of the following commands below and don’t forget to hit Enter after you type one command after the other.
  • ren C:WindowsSoftwareDistribution SoftwareDistribution.old
  • ren C:WindowsSystem32catroot2 Catroot2.old
• Next, restart the services you’ve stopped by entering another series of commands. Don’t forget to hit Enter after you key in one command after the other.
  • net start wuauserv
  • net start cryptsvc
  • net start bits
  • net start msiserver
• Close Command Prompt and reboot your PC.

Option 3 – Run the Windows Update Troubleshooter

You might also want to run the Windows Update Troubleshooter as it could also help in fixing Windows Update error 0x80004005. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 4 – Try downloading and installing the Windows Updates manually

Windows Update Error 0x80004005 might be due to a Windows Update that has failed. So if it is not a feature update and only a cumulative update, you can download the Windows Update and install it manually. But first, you need to find out which update has failed, and to do so, refer to the following steps:

• Go to Settings and from there go to Update and Security > View Update History.
• Next, check which particular update has failed. Note that Updates that have failed to install will be displayed under the Status column which has a label of “Failed”.
• After that, go to the Microsoft Download Center and look for that update using its KB number and once you find it, download and then install it manually.

Note: You can also use the Microsoft Update Catalog, a service from Microsoft that provides a list of software updates that can be distributed over a corporate network. With the help of this service, it can be easier for you to find Microsoft software updates, drivers as well as fixes.

Setting up the Windows operating system in a computer can be quite a complicated task since there are a couple of things that take place in the background to ensure a full and protected setup of the operating system which includes a number of programs, scripts, and so on. They work together in the background to guarantee the integrity of the Windows operating system. However, there are times when this piece of code could also go wrong. As a result, you might encounter errors like the “There was a problem running preinstall.cmd scripts” error. “Preinstall.cmd” is a type of CMD file associated with Applications & Drivers developed by Gateway for the Windows OS. To fix the “There was a problem running preinstall.cmd scripts” error, there are several things you can try. You can try to download a new Windows installation image or create a new bootable drive as well as uninstall conflicting or incompatible programs. In addition, you can also run the Windows Update troubleshooter or reset Windows 10.

Option 1 – Try to download a new Windows installation image

Your first option to fix the “There was a problem running preinstall.cmd scripts” error is to download a new Windows installation image. You can get the official ISO files for the latest release of Windows 10. After you’ve downloaded the ISO files, you can use them to upgrade to the latest Windows 10 version.

Option 2 – Try creating a new bootable drive

• Insert your USB drive into your PC.
• Tap the Win + R keys to open the Run dialog box and type in “cmd” and tap Enter to open the Command Prompt. Alternatively, you can also search for “cmd” in the Cortana search box to open Command Prompt.
• Once you’ve opened CMD, type in this command to open the DISPART utility – diskpart
• After that, you should see a new black and white window that would say, “DISKPART>”.
• Next, type in “list disk” in the command line and tap Enter to see the list of all the Storage devices as well as your hard disk connected to your PC. Here, you have to identify your disk’s number.
• Type in this command where “X” is the disk number you have identified and then tap Enter – disk X
• Type in this command and hit Enter to clear the table records and all the visible data on the drive – clean
• Now you have to recreate a new primary partition of the drive so you’ll have to type in this command and tap Enter right after – create part pri
• A new primary partition has been created so you have to select it by typing this command and tapping Enter – select part 1
• Now you have to format it to make it visible to normal users by typing – format fs=ntfs quick

Note: If your platform supports the Unified Extensible Firmware Interface or UEFI, replace the “NTFS” with “FAT32” in the command on Step 10.

• After that, type in this command and tap Enter after – active
• Finally, type this command and hit Enter to exit the utility – exit
• After you prepare the image for the operating system, save it to the root of your USB Storage device.

Option 3 – Try to uninstall conflicting programs

If you are using a computer made by Dell and got Windows 10 preinstalled in it, then you can try to uninstall the programs listed below and see if it fixes the problem.

• Dell Encryption Management service
• Dell Digital Library service

Option 4 – Run the Windows Update Troubleshooter

You might also want to run the built-in Windows Update Troubleshooter in Windows that could help you in resolving the “There was a problem running preinstall.cmd scripts” error. All you have to do is go to Settings > Update& security > Troubleshoot > Windows Update. From there, click on the Run the troubleshooter button and follow the next one-screen instructions that appear. After that, restart your computer and check if the error is now fixed or not by trying to install the update once again.

Option 5 – Run Microsoft’s online troubleshooter

Running Microsoft’s online troubleshooter might also help you fix the error. This online troubleshooter is known to help in fixing Windows Update errors, it scans your computer for issues that might be causing the problem and then fixes them automatically.

Option 6 – Try to reset Windows 10

• Tap the Win key or click on the Start button located in the Taskbar.
• Then click on the Power button at the bottom right portion of the screen.
• Next, press and hold the Shift key on your keyboard and then click on Restart. This will restart your Pc into the Advanced Startup options.

Note: Once you have access to the Advanced Startup options, you have to go to the setting which allows you to Reset your Windows 10 PC. All you have to do is select Troubleshoot > Reset this PC to reach the following screen Afterward, select either the “Keep my files” option and then proceed to the next on-screen instructions that follow to reset your Windows 10 computer without losing your files.

As you know, every Windows Update is essential for every Windows operating system. They have to be regularly installed, especially since they include various security updates that are important to the system. However, there are times when Windows Update fails to execute properly and you get errors like the error code 0x80070BC9. When you encounter this particular Windows Update error, you will get the following error message on your screen:

“0x80070BC9 – ERROR_FAIL_REBOOT_REQUIRED. The requested operation failed. A system reboot is required to roll back changes made.”

This kind of Windows Update error is most likely caused by a newly installed problematic software, corrupted Windows Update files, or policies that restrict the behavior of the Windows Module Installer. The Windows Module Installer, also known as “WMIW” or “TiWorker.exe”, is the one that checks for new updates from the Windows server and installs them on your computer. This is why you need to make sure that you do not have any policies that control the start behavior of the Windows Module Installer since this service must not be hardened to any start value and should be managed by the operating system. To resolve the Windows Update error code 0x80070BC9, you can check out the options provided below.

Option 1 – Try checking the status of the Windows Modules Installer Worker Service

Since the Windows Update error code 0x80070BC9 has something to do with the Windows Module Installer Worker service, you need to check its status in the Service Manager. Refer to the following steps to do so.

• 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 “MSC” in the field and hit Enter to open the Services Manager.
• After opening the Services Manager, look for the Windows Modules Installer Worker Service.
• Once you found it, check its status and make sure that its Startup type is set to Manual.
• Now click on the Start button and see if it fixes the Windows Update error.

Option 2 – Run the Windows Update Troubleshooter

You might want to run a built-in Windows Update troubleshooter to resolve the Windows Update error. It is one of the things you can check out as it is known to automatically resolve any Windows Update errors like error code 0x80072EE2. To run this troubleshooter, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 3 – Try contacting the IT administrator to modify the group policies

You could also try to contact the IT administrator to have the group policies modified. This option is applicable for company-managed systems. As mentioned, one of the possible causes of the Windows Update error 0x80072EE2 is the policies that control the start behavior of the Windows Module Installer. Thus, you need to have them removed so that the Windows Module Installer Worker service is managed by the operating system itself. And since there could be many policies, it is highly advised that you contact your company’s IT administrator to get the job done for you.

Option 4 – Try to install the Windows Updates in a Clean Boot State

There are some instances that some conflicting programs installed in your computer might be the one that’s causing Windows Update error code 0x80070BC9. To identify which program is causing the problem, you need to put your computer in 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.)
• From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

DirectX function GetDeviceRemovedReason error is a DirectX error that comes up during playing games on Windows 11 operating system. Usually, the error occurs in gaming systems powered by AMD and very rarely if any times at all on Nvidia or intel platforms. If you are one of the gamers affected by this error, fear not because we have a solution for you. Follow provided fix guide in order to correct this error and get back to gaming asap.

1. Update drivers

The first thing of course is to update your graphic card driver, you can do this with your graphic cards panel software or directly in Windows itself but the best practice and one that I would recommend is to go to your graphic card manufacturer’s website and download the latest driver there, and then install it inside Windows 11.

2. Change power mode

Changing power mode inside Windows 11 can solve this issue since sometimes Windows power manager if it is set to anything except best performance can interfere with the proper functioning of the graphic adapter, and because of this error. To change the power setting do the following:

1. Press ⊞ WINDOWS + I to open settings
2. Click on the System tab
3. Select power & battery on the right part
4. Click on the menu beside power mode
5. Select the best performance

3. Run SFC scan

Corrupted system files can also cause this error and if previous steps have not resolved it we will use Windows built-in tool SFC scan to find and repair all bad files in windows.

1. Press ⊞ WINDOWS + S to open the search menu
2. Type in Windows terminal and run it as administrator
3. If prompted click on YES on UAC
4. Press CTRL + SHIFT + 2 to run command prompt
5. Type in sfc /scannow and press ENTER
6. Wait for the whole process to finish and then reboot your system

4. Reinstall the problematic game

Sometimes game files can get corrupt and maybe even overwritten, try with game reinstallation if the problem still persists.